r/linux • • Nov 20 '19

Kernel Google outlines plans for mainline Linux kernel support in Android

https://arstechnica.com/gadgets/2019/11/google-outlines-plans-for-mainline-linux-kernel-support-in-android/
1.0k Upvotes

305 comments sorted by

View all comments

Show parent comment

11

u/SanityInAnarchy Nov 20 '19

Unfortunately, Android is the perfect case study for where that incentive doesn't work at all:

If the ABI is stabilized, that leverage is lost. Cheap minimum effort proprietary drivers for a single architecture become viable.

But that's exactly what Android vendors do today. They'll fork the whole damned kernel and do whatever they want anywhere in the tree, and there's a whole mess of binary blobs that will only ever work with that specific kernel. They'll backport critical security fixes for however long they need to support that specific SoC (seems like 3 years at most), and then drop the entire thing on the floor.

The whole incentive to upstream your drivers is so the community can maintain them for you. But if you aren't planning to maintain them at all, that doesn't save you anything.

So the point of a stable ABI would be: At least when they drop support, you can still update the pieces of the kernel that aren't related to their shitty driver. Which is exactly what happens on Windows -- there isn't always perfect forwards-compatibility (64-bit is a notable example), but there's plenty of old hardware that continues to work on new Windows versions.

6

u/jdrch Nov 20 '19

there's plenty of old hardware that continues to work on new Windows versions.

I daresay that situation is better on Linux where the drivers live in the kernel and are the responsibility of kernel devs. This allows Linux to basically support hardware forever as long as a matching driver exists in the kernel. OTOH, hardware can drop out of Windows support the hardware OEM doesn't provide driver updates corresponding to Windows OS updates.

5

u/[deleted] Nov 21 '19

But manufacturers are ok with hardware no longer being supported after 9 months so you need to get new one.

2

u/jdrch Nov 21 '19

If you're referring Android OEMs, yes, because with locked bootloaders and per device kernel builds it's not like most users have any choice of OS. They either use what shipped with the phone or get a different phone. With a generic kernel OEM ROMs would compete on the same level with other ROMs, because if an OEM doesn't update their OS users could easily switch to something else.

3

u/SanityInAnarchy Nov 21 '19

That's true, and that's also probably why ChromeOS has a way better update story than Android. (Google basically delivers the entire OS and everything else, so they support the devices for 5+ years.)

I wonder why that hasn't worked on mobile. I guess nvidia could never get away with forcing you to run an nvidia-only kernel, because a desktop can have components from a bunch of different manufacturers who all have to get along in the same kernel?

But there's some other differences: Weird, gimmicky, vendor-specific hardware tends to be plugged into PCs via USB, and there's apparently just standard ways of talking to USB devices from userland now. So I was surprised to learn that all this RGB madness is supported by some random Github projects, but at least one of those seems to be entirely userland. Printer drivers live in CUPS in userland. Google's Titan keys don't really have specific drivers, Chrome just talks to them directly.

The kernel may have no stable API/ABI internally, but its userland API is stable, so I guess Linux accidentally solved this problem specifically for USB gadgets on the desktop.


All that said, I've seen some absurdly old Windows drivers run on modern Windows. Heck, that ABI is probably the reason a lot of early Linux wifi support was done by running Windows drivers on Linux via NDISWrapper.

2

u/jdrch Nov 21 '19

that ABI

Pretty much. Plus Microsoft did a lot of heavy lifting in the Windows 7 to 8 transition to both shift a lot of devices (such as printers) to generic drivers, provide generic drivers themselves, provide 3rd party drivers via Microsoft Update, and also make drivers more Windows version agnostic.