4 ms·
Linux Set to Shed Nearly 500k Lines of Code by Dropping Old CPUs
- jwilk 9y agoSee also: https://lwn.net/Articles/748074/ https://lwn.net/Articles/748074/
- jlgaddis 9y agoThanks. The link should be updated to point to this LWN article, IMO.
- ganeshkrishnan 9y agoGood. It's not as if they can't use Linux anymore. They can still use the older version of kernels.
- juliangoldsmith 9y agoI'm surprised that M68K isn't included in the list. I doubt there are many M68K machines that could run a current Linux kernel.
- jwilk 9y agoThe number of users doesn't matter that much as long as the port is actively maintained. Judging by the activity on the M68K mailing list, the port is alive and kicking: https://www.spinics.net/lists/linux-m68k/ https://www.spinics.net/lists/linux-m68k/
- PHGamer 9y agoso onto NetBSD then?
- jwilk 9y agoDoes NetBSD support any of the CPUs in question? I don't see them here: https://www.netbsd.org/ports/ https://www.netbsd.org/ports/
- caf 9y agoThe linked pull request ( http://lkml.iu.edu/hypermail/linux/kernel/1804.0/00306.html http://lkml.iu.edu/hypermail/linux/kernel/1804.0/00306.html ) is informative, in particular: In the end, it seems that while the eight architectures are extremely different, they all suffered the same fate: There was one company in charge of an SoC line, a CPU microarchitecture and a software ecosystem, which was more costly than licensing newer off-the-shelf CPU cores from a third party (typically ARM, MIPS, or RISC-V). It seems that all the SoC product lines are still around, but have not used the custom CPU architectures for several years at this point. In contrast, CPU instruction sets that remain popular and have actively maintained kernel ports tend to all be used across multiple licensees.
- throwawaymanbot 9y agoGreat stuff. Now theres more room for lines for Poettering to work with and add more systemd.