Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Google Android Linux

Google Finally Shifting To 'Upstream First' Linux Kernel Approach For Android Features (phoronix.com) 9

Phoronix reports: Google's Android had been notorious for all of its downstream patches carried by the mobile operating system as well as various vendor/device kernel trees while in recent years more of that code has been upstreamed. Google has also been shifting to the Android Generic Kernel Image (GKI) as the basis for all their product kernels to further reduce the fragmentation. Looking ahead, Google is now talking of an "upstream first" approach for pushing new kernel features into mainline Linux before deploying them on Android. Google's Todd Kjos talked today during Linux Plumbers Conference (LPC2021) around their Generic Kernel Image initiative. With Android 12 and their Linux 5.10 based GKI image they have further cut down the fragmentation to the extent that it's "nearly eliminated."

With the Android 12 GKI, most of the vendor/OEM kernel features have now either been upstreamed into the Linux kernel, isolated to vendor modules/hooks, or merged into the Android Common Kernel. They are making good progress on the GKI front and also ensuring vendors adapt to the new approach to cut down on the kernel mess. But perhaps most exciting is their outlook for 2023 to 2024 for further reducing technical debt. They are going to pursue an "upstream first development model for new features" in making sure new code first lands into the mainline Linux kernel rather than aiming straight for lodging within the Android source tree.

This discussion has been archived. No new comments can be posted.

Google Finally Shifting To 'Upstream First' Linux Kernel Approach For Android Features

Comments Filter:
  • by klipclop ( 6724090 ) on Wednesday September 22, 2021 @02:54PM (#61821943)
    Hopefully Google can figure out how to do this while taking away the keys from hw vendors. The only input vendors should have is when they internally test updates before pushing it downstream to the end user devices. Kinda ridiculous Google is more than a decade into Android and just being developed.
  • Listen(* jingle_bells)
    means a fork is born.

  • by orbitalia ( 470425 ) on Wednesday September 22, 2021 @04:08PM (#61822171) Homepage

    I have just come out of working with Android Automotive for the last 6 years and being the first to deploy it in a real car (whilst also working on lots of other very large OSS platforms previously)
    Upstream is the only way, our SOC vendor was having to manage 500+ patches against android and linux which was an awful lot to manage everytime upstream changed.
    I see the price of being able to use OSS is to be a good citizen and upstream those patches you have which will also benefit your by reducing your maintenance burden, and as stated in the article keep down fragmentation.

    That said, Android will be changing to Fuchsia soon right so Linux will be a dead end for Android soon.

    • My understanding was that Fuscia is a new OS with a different Kernel (Zircon?) that can run android apps targeted at IoT devices and google had stated wont replace android, can you clarify?

  • What does this mean for LineageOS and other "degoogled" versions of android?

Brain off-line, please wait.

Working...