Stories
Slash Boxes
Comments

SoylentNews is people

posted by Fnord666 on Thursday November 21 2019, @04:01AM   Printer-friendly
from the Google-wants-less-forking dept.

Google outlines plans for mainline Linux kernel support in Android

It seems like Google is working hard to update and upstream the Linux kernel that sits at the heart of every Android phone. The company was a big participant in this year's Linux Plumbers Conference, a yearly meeting of the top Linux developers, and Google spent a lot of time talking about getting Android to work with a generic Linux kernel instead of the highly customized version it uses now. It even showed an Android phone running a mainline Linux kernel.

But first, some background on Android's current kernel mess.Currently, three major forks happen in between the "mainline" Linux kernel and a shipping Android device (note that "mainline" here has no relation to Google's own "Project Mainline"). First, Google takes the LTS (Long Term Support) Linux kernel and turns it into the "Android Common kernel"—the Linux kernel with all the Android OS-specific patches applied. Android Common is shipped to the SoC vendor (usually Qualcomm) where it gets its first round of hardware-specific additions, first focusing on a particular model of SoC. This "SoC Kernel" then gets sent to a device manufacturer for even more hardware-specific code that supports every other piece of hardware, like the display, camera, speakers, usb ports, and any extra hardware. This is the "Device Kernel," and it's what actually ships on a device.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Thursday November 21 2019, @09:01AM (4 children)

    by Anonymous Coward on Thursday November 21 2019, @09:01AM (#922904)

    MediaTek are even worse, Samsung CPUs were pretty bad a few years back -- not that it matters much now since they're shutting down their CPU division. I'm surprised nobody has sued these companies for breaching the GPL.

  • (Score: 2) by darkfeline on Thursday November 21 2019, @09:22AM (3 children)

    by darkfeline (1030) on Thursday November 21 2019, @09:22AM (#922908) Homepage

    It's not really possible to sue for Linux GPL violations. Only the copyright holders can sue for copyright/license violations, so you'd have to get every single Linux contributor to participate in a lawsuit.

    This is why the FSF asks all contributors to assign copyright to the FSF, so that it's actually feasible for the FSF to sue for GPL violations.

    --
    Join the SDF Public Access UNIX System today!
    • (Score: 2) by DannyB on Thursday November 21 2019, @02:54PM (1 child)

      by DannyB (5839) Subscriber Badge on Thursday November 21 2019, @02:54PM (#922984) Journal

      If Linux were to have copyright holders sign over rights, who would they go to?

      Linus? Who pays him?

      The Linux Foundation? They were acquired by Microsoft (as a platinum member) in 2016. Talk about handing the copyright directly to the wolf.

      Other ideas?

      --
      People today are educated enough to repeat what they are taught but not to question what they are taught.
      • (Score: 1, Informative) by Anonymous Coward on Thursday November 21 2019, @03:58PM

        by Anonymous Coward on Thursday November 21 2019, @03:58PM (#923017)

        what about the other 27 platinum members?

    • (Score: 0) by Anonymous Coward on Thursday November 21 2019, @09:46PM

      by Anonymous Coward on Thursday November 21 2019, @09:46PM (#923158)

      You don't need every contributor; you just need one to enforce their rights under copyright law. Even better for your claim if they wrote part of the code being patched by the derivative work, but I've seen some analysis that even that may not be necessary under a "multiple-edition edited-volume" theory.