News: 0001627010

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Linus Torvalds Merged The Code Beginning To Remove Intel 486 CPU Support In Linux 7.1

([Intel] 4 Hours Ago Intel 486 Kconfig Options)


As a follow-up to the news first-covered on Phoronix earlier this month about [1]Linux 7.1 expected to begin removing i486 CPU support : it indeed happened. Linus Torvalds took the initial removal bits today without any fuss today for beginning the phase out of M486 / M486SX / ELAN kernel support.

As explained in the prior article, the initial removal is getting rid of the kernel configuration (Kconfig) options for building M486 / M486SX / ELAN CPU support. With that Kconfig code now removed, building a Linux 7.1+ kernel with that Intel 486 support isn't possible and specifically affects AMD/Cyrix/IBM/Intel SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5S. The M486 Kconfig option is for 486-class CPUs such as the AMD/Cyrix/IBM/Intel 486DX/DX2/DX4 and UMC U5D.

Assuming no one complains or raises legitimate reasons for keeping the support around, in Linux 7.2 or later more of the actual 486 code removal can easily happy for those i486-only code paths. If you still are miraculously using a i486 CPU with modern Linux kernel versions, you can keep using the likes of Linux 6.18 LTS for having maintained kernel support for the next few years. 32-bit CPUs past the i486 are still maintained albeit don't look for any exciting advancements out of the modern kernel versions. It's also with Linux 7.1 there is [2]a change that may negatively impact 32-bit Linux users .

It's [3]this merge specifically of x86/platform material a short time ago that took that first step for i486 removal. No i486 nostalgia or other reasons kept Linus from beginning the removal process from the mainline kernel. Also in that pull for newer AMD CPUs is also a useful addition of [4]finally printing the AMD AGESA version to the Linux kernel log when detected for easier debugging and diagnosis.



[1] https://www.phoronix.com/news/Linux-7.1-Phasing-Out-i486

[2] https://www.phoronix.com/news/Linux-7.1-VFS-Kino-32-bit

[3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0972ba5605a0a0cd8a9e74558b97a9c9626adfb5

[4] https://www.phoronix.com/news/AMD-AGESA-Version-Linux-7.1



If you throw a New Year's Party, the worst thing that you can do would be
to throw the kind of party where your guests wake up today, and call you to
say they had a nice time. Now you'll be be expected to throw another party
next year.
What you should do is throw the kind of party where your guest wake
up several days from now and call their lawyers to find out if they've been
indicted for anything. You want your guests to be so anxious to avoid a
recurrence of your party that they immediately start planning parties of their
own, a year in advance, just to prevent you from having another one ...
If your party is successful, the police will knock on your door,
unless your party is very successful in which case they will lob tear gas
through your living room window. As host, your job is to make sure that
they don't arrest anybody. Or if they're dead set on arresting someone,
your job is to make sure it isn't you ...
-- Dave Barry