Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

"A stable driver API would appear to solve this problem, but actually causes huge constraints for kernel development while not solving the actual driver quality issue. "

Why do you think that is?

(the criticism of GKI seems to be because of different issues)

As far as I understand, it is quite a deliberate choice of linux to actually force vendors to open source their drivers.

So what happens now is what you describe: the drivers get written against one lts kernel and then shipped and mostly forgotten. (Which is why I cannot really use my old android tablet anymore, despite the hardware did not degrade)

With a stable driver ABI, I could update to a newer android and keep the drivers as they are.

And with vendors writing drivers for a small and clear API - they could deliver better quality drivers, and update them - because they do not have tp deal with the very expensive whole kernel integration they have to redo for every kernel and every driver.

So yeah, in rainbow fairy unicorn world they all just open source everything and work in harmony and collaboration for the greater good of humanity. But in reality right now, with proprietary being the standard mode, it is just a mess. And I prefer pragmatic solutions that actually improve the status quo.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: