4 ms·
Drivers being kernel specific is really annoying
by psychphysic 3y ago
Drivers being kernel specific is really annoying
- IronWolve 3y agoMajor problem with android, stuck with whatever version of android due to binary blob drivers.
- pjmlp 3y agoThe major problem is Google not enforcing updates via their contracts. Project Treble has made Android a pseudo microkernel with stable ABI for drivers. However Google has decided it is still up to OEMs to decide if driver are to be shipped or not. With no legal enforcement for accessing Google services, OEMs rather sell updated hardware.
- Zambyte 3y agoThe obvious problem seems to be propriety device drivers, no? If they didn't shoot themselves in the foot with their licensing, the drivers would work with any kernel version.
- matheusmoreira 3y agoAll they have to do is upstream their drivers into the kernel instead of shipping proprietary blobs. Why is this so hard?
- nani8ot 3y agoBecause the Linux kernel has stringent guidelines how a driver should be written and work. Companies don't want to put in the work (i.e. pay someone with experience) to upstream their drivers. Whether this makes sense monetarily isn't really relevant to many decision makers. At least that's how I explain why Nvidia and Broadcom don't upstream their drivers.
- rbanffy 3y ago> Because the Linux kernel has stringent guidelines how a driver should be written and work Preventing poorly-written software to be added to the kernel is a Good Thing. The system is working as planned.