There is a distinction here - Linux, the kernel, runs on pretty much every CPU in the universe. If it is presented with any CPU and chipset ever made, it can run on that.
Your PCI devices, your USB devices, etc are not guaranteed to have Linux drivers for that hardware. And if the producers of said hardware don't release driver documentation or support a Linux driver directly, you can't blame the Linux community for not being magicians that can force private companies to bend to their will.
Hell, Broadcom - one of the worst FOSS companies, in the same class as Nvidia for the longest time - is finally producing scant upstream NIC drivers. They support a tiny fraction of their product range, and they have another 2 proprietary drivers on top of those for Linux and those don't work either, but the situation is improving.
But that is all you can do. There is no "sit down and code" answer for undocumented motherboards, bad EFI implementations, and a 15 button mouse with a 50MB proprietary driver on Windows. Well, the latter actually you can just wireshark the usb bus and get all the signaling for the buttons, but that is a lot of work to do what the company itself could have done in minutes (publish the opcode manual they obviously have on the thing).
There is a distinction here - Linux, the kernel, runs on pretty much every CPU in the universe. If it is presented with any CPU and chipset ever made, it can run on that.
Your PCI devices, your USB devices, etc are not guaranteed to have Linux drivers for that hardware. And if the producers of said hardware don't release driver documentation or support a Linux driver directly, you can't blame the Linux community for not being magicians that can force private companies to bend to their will.
Hell, Broadcom - one of the worst FOSS companies, in the same class as Nvidia for the longest time - is finally producing scant upstream NIC drivers. They support a tiny fraction of their product range, and they have another 2 proprietary drivers on top of those for Linux and those don't work either, but the situation is improving.
But that is all you can do. There is no "sit down and code" answer for undocumented motherboards, bad EFI implementations, and a 15 button mouse with a 50MB proprietary driver on Windows. Well, the latter actually you can just wireshark the usb bus and get all the signaling for the buttons, but that is a lot of work to do what the company itself could have done in minutes (publish the opcode manual they obviously have on the thing).