[go: up one dir, main page]

|
|
Log in / Subscribe / Register

An update on the Android problem

An update on the Android problem

Posted Nov 7, 2017 12:52 UTC (Tue) by toddpoynor (guest, #19973)
Parent article: An update on the Android problem

Galaxy Nexus was the first of the Nexus / Google-partnered devices to not receive a kernel upgrade, I believe (the Motorola Xoom tablet was probably the last to do so). Galaxy Nexus was largely a victim of the SoC vendor trying to do the right thing: TI engaged the kernel community to upstream much of the SoC support code, plus the remoteproc framework and other stuff written as part of that project. But the resulting large differences in code bases between the tested shipping code and the upstream code, and the likelihood of requiring a substantial effort to get the upstream version to product quality, caused a kernel upgrade to be deemed not worth the effort. (I believe the XDA folks wrestled with this for their firmware and ended up reverting a bunch of stuff done upstream.)

This situation reportedly continues to be the case for most if not all major SoC vendors: the internal trees used to produce products differ heavily from the code that undergoes community back-and-forth and gains acceptance upstream. The two codebases just can't be allowed to diverge very far, and that requires an ongoing level of investment that can be difficult to justify.


to post comments

An update on the Android problem

Posted Nov 7, 2017 20:46 UTC (Tue) by drag (guest, #31333) [Link]

This sort of thing is why Dell created DKMS.

They discovered that it's a huge pain in the rear to work on out of tree patches on older kernels and then forward port them to upstream. However it is relatively easy to go the other direction... work on upstream kernels and then back port drivers to older kernels.

Therefore if you are working on getting new SoC support done for a kernel it is then probably a bad idea to work on it in private on a 'Long Term Release' kernel then try to release patches to upstream. The good idea is to work on the patching the latest kernels, getting that to work first, and then backporting the changes to whatever kernel you have to ship with.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds