Android Drivers To Be Included in Linux 3.3 Kernel


Recommended Posts

Android drivers are returning to the Linux kernel. Kernel maintainer Greg Kroah-Hartman has retrieved the Android drivers removed from the staging area of Linux 2.6.33 in the spring of 2010 and put them back into his development branch for version 3.3 of the Linux kernel.

The plan is for a Linux 3.3 kernel to be able to boot on an Android device without further patches ? although not all Android patches are being automatically carried over to the main development branch. For example, the WakeLock code, which helps Android devices' batteries last longer but is not necessary for booting, is not included.

The Linux Foundation's Consumer Electronics workgroup, along with a group at Linaro and various individual developers, is working with Kroah-Hartmann on this project. Tim Bird, chair of the Architecture Group, has launched the Android Mainlining Project with the goal of coordinating work on integrating the Android features. Developers interested in helping to integrate Android patches into the mainline kernel can sign up for the project's mailing list.

Source: The H Online

Android drivers can never be fully in the kernel, they rely on separate userspace drivers which are invoked via JNI interfaces for any meaningful device (camera, lights, sound, etc). So they would be mostly useless without the Android core itself.

Another example of Linux not sure what it wants... Linux should be getting together and create a more focused edition, not work on hundreds of distros. The community sure has resources to do it. The last few years they have been lagging too far behind both Mac and Windows.

Another example of Linux not sure what it wants... Linux should be getting together and create a more focused edition, not work on hundreds of distros. The community sure has resources to do it. The last few years they have been lagging too far behind both Mac and Windows.

This isn't an example of anything. Stuff can be added and removed at any time if there are issues with the code. The Android drivers mentioned are infact managed by Google and co companies, nothing to do with the Linux kernel maintainers. Those people need to decide what should be put in the mainline and what doesn't.

And yet again as I just said, this is to do with the Linux kernel, not distros.

Another example of Linux not sure what it wants...

They want to include drivers from Android in the kernel, that's all. Ability for users, not necessarily just hardware developers, to use the same kernel on various Android tablets/devices is a nice bonus, hardly fragmentation or anything.

If Windows included drivers for various hardware, would you call it "not knowing what it wants to be?" No, they would just include a new batch of drivers for different hardware.

Linux should be getting together and create a more focused edition, not work on hundreds of distros. The community sure has resources to do it. The last few years they have been lagging too far behind both Mac and Windows.

So you disagree with Windows 8 being available on tablets as well I take it?

I rather want the Linux community to use their time creating something for the desktop that can compete with Mac and Windows. Linux haven't been relevant to the desktop market. This is a step into the tablet market. Sure Linux can be relevant there, but not as long as "everyone" thinks what they do is better. Focusing on drivers is one thing. Why not use resources to make a kernel and api's that everyone need to use? Now Linux is so fragmented that you have several systems for audio, video, etc.

Sorry for ranting and going a bit off topic, but I really want Linux to be better that it is today. It's not that it is bad. Only that it can be so much better.

I rather want the Linux community to use their time creating something for the desktop that can compete with Mac and Windows. Linux haven't been relevant to the desktop market. This is a step into the tablet market. Sure Linux can be relevant there, but not as long as "everyone" thinks what they do is better. Focusing on drivers is one thing. Why not use resources to make a kernel and api's that everyone need to use? Now Linux is so fragmented that you have several systems for audio, video, etc.

Sorry for ranting and going a bit off topic, but I really want Linux to be better that it is today. It's not that it is bad. Only that it can be so much better.

Linux being relevant to the tablet audience == Android.

That's cool but do you think anyone will actually use this kernel.

It should help the custom rom/homebrew community that is being built around handset OEM's who are shipping phones with unlocked boot loaders - IIRC HTC's Android phones have unlocked boot loaders.

Another example of Linux not sure what it wants... Linux should be getting together and create a more focused edition, not work on hundreds of distros. The community sure has resources to do it. The last few years they have been lagging too far behind both Mac and Windows.

Linux is the kernel not the distribution - this has been covered so many times it isn't funny to hear the same ill-informed half baked comments like yours every time this topic appears on the radar. The issue is about drivers within the kernel source code rather than it being a separate project - the issue has been discussed on and off because Google was too lazy to properly support the drivers once they were in the tree but it appears things have changed and Google has finally taken on the responsibility required to have their code in the main tree.

They want to include drivers from Android in the kernel, that's all. Ability for users, not necessarily just hardware developers, to use the same kernel on various Android tablets/devices is a nice bonus, hardly fragmentation or anything.

If Windows included drivers for various hardware, would you call it "not knowing what it wants to be?" No, they would just include a new batch of drivers for different hardware.

no they'd call it bloat.

on linux it's "choice"....

no they'd call it bloat.

on linux it's "choice"....

That must be why Windows 7 takes more space installed currently, and supports less hardware out of the box, than a Linux distribution that fits on a single CD and comes with as much software.

I'd say there's still quite a lot of room left for "bloat" to be added.

That must be why Windows 7 takes more space installed currently, and supports less hardware out of the box, than a Linux distribution that fits on a single CD and comes with as much software.

I'd say there's still quite a lot of room left for "bloat" to be added.

1. You just proved my point

2. you need to learn what bloat is.

oh and yeah, but that's because MS sropped supporting crap from the 90's, and linux still doesn't support a lot of stuff from the 2000's :)

Adding drivers to the kernel tree doesn't mean that they will ship with every distro, just that they'll be properly mantained and that they'll work out of the box if they are enabled when the kernel is compiled.

You won't be seeing Android drivers enabled on a desktop distro that's not intended to run on Android related hardware.

I'd say the comments about bloat are largely ignorant.

2. you need to learn what bloat is.

Unnecessary things, which including more support for hardware that millions of users already have isn't. Then again, Windows includes DVD makers and useless crap that no one I know has ever used or most of the time doesn't even realize is included with it.

oh and yeah, but that's because MS sropped supporting crap from the 90's, and linux still doesn't support a lot of stuff from the 2000's :)

And Windows doesn't include a ton of modern hardware either - for example HP Printers that work out of the box on OSX or Linux still require manual installation of drivers from their website.

No they don't, just use the universal driver, which is what linux does. pf course it isn't as good as the individual driver for the product so it doesn't auto install it when the printer is connected.

and most printers have a usable life of years or less before they're no longer any purpose of having. so most won't be in the windows drivers because they weren't out when the disc was burned. Also with windows 7 MS delibaretaly removed many gigs of printer driver bloat from the disc because it was taking up space and was unnecessary for 99.99999% of people. s

eriously, the best you could come up with was printer drivers....

also any HP laser pritner will work OOB on ANY OS (whith the exception of a few low end cheap "widnowsPritners" or HostUSB printers as they're known internally and technically. These generally won't work on OSX or Linux at all due to lack of drivers. I don't think they do a lot of HostUSB printers anymore though.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Hasleo Disk Clone 5.8.2.1 by Razvan Serea Hasleo Disk Clone is a free and all-in-one disk cloning software for Windows 11/10/8/7/Vista and Windows Server that can help you migrate Windows OS to another disk, clone one disk to another disk or clone one partition to another location quickly and efficiently. Completely Free Windows Migration and Disk/Partition Cloning Software Migrate Windows from one disk to another without reinstalling Windows, apps. Clone one disk to another and makes the data on 2 disks are exactly the same. Clone a partition to another location without losing any data. Easily adjust the size and location of the destination partition. Convert MBR to GPT or convert GPT to MBR by cloning. Creation of Windows PE emergency disk. Extremely fast cloning speed and multi-language support. Supported OS: Windows Vista/Server 2008 or later, fully compatible with GPT and UEFI. Hasleo Disk Clone 5.8.2.1 changelog: Fixed an issue that caused disk enumeration to fail Fixed an issue where WinPE created under Windows ARM64 26H1 did not work properly Download: Hasleo Disk Clone 5.8.2.1 | 32.3 MB (Freeware) Link: Hasleo Disk Clone Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • This got me thinking, would you rather a self driving car prioritise protecting its passengers or everyone else? I'd choose the one that keeps me and my kids safest. At some point, these cars have to make those choices already, don't they? Wonder if we have a way to find out what way they lean.
    • The proportion (or number of iterations) has nothing to with this aspect of Copyright I am describing. In short, it doesn't matter how many times the manager tells you to change something or how. Your work product is always YOURS until and unless you then assign that to the person representing the client/company, usually for financial compensation -- either in salary or as a subcontract work for hire payment. if iterations determined copyright, then businesses would have learned to just keep making changes until they could claim they owned the copyright, without having to compensate the artist for their work. And that would be BAD. The only place where the amount of changes does have a role is in how much does a human modify a previous public domain work (from any source) before it is considered fair use or their own work, etc. For example, if a human makes substantial changes to a public domain (re: AI, by definition) work, then they can then claim that derivative work as their own...but NEVER the original version, of course. That's why anyone can make a movie about Dracula, for example, as long as it is based on the public domain novel, but not if they take new ideas from copyrighted movies made afterwards. As one of the people who personally advised the US Copyright Office on their recent ruling on these very issues, be assured that I specifically used the terminology precisely -- though I made it simple enough for laymen to understand it. If I made this confusing by doing so, I apologize. But, to be clear regarding your assumption that I would agree to your second statement that I quoted above -- the answer is NO. If AI does the work, no matter how much "direction" you give it, it cannot be copyrighted. All AI generated content is in the Public Domain and therefore the copyright cannot be assigned to ANYONE, even you -- until and unless substantial modifications are made to it BY A HUMAN BEING (yourself or a contracted artist/writer/etc.) and then that copyright on the derivative work is legally (in writing) transferred to you. This is a critical distinction. And it is important that people, especially AI sloppers, understand this. For example, YouTube is not paying AI slop generators for the copyright, etc. of their AI slop. What YouTube is doing is sharing AD REVENUE for permission to publish your AI slop. Copyright/ownership/rights never come into it. Importantly, that means that anyone can copy any AI slopware on YouTube, etc. and rehost it anywhere they want, even back on YouTube, and there is nothing legal that YouTube can do about it with regards to copyright protections, ownership, DMCA, etc. Anyone is legally free to use any AI slopware in any way they want. When this ruling was pending, I warned Disney legal of all of this before they did their OpenAI deal -- that it would literally dilute their entire IP portfolio forever. They ignored that warning for the PR and stock bump. But that is why, when the ruling came down last year, Disney quickly extricated themselves from that OpenAI deal, even eating the initial upfront fees -- followed closely by OpenAI ending their entire AI video generating business model. They adjusted their PR release dates to make this less obvious to shareholders, of course. Phew. I hope that this clears up the key distinctions for you and anyone reading. If you have any additional questions or even hypotheticals about AI and Copyright, please feel free to ask.
    • Each of the devices displayed on this page now has a little volume meter next to it to show if there is audio actively playing. About time.
    • Owing to the nature of Windows feature enablement updates, it was distributed over Windows Update services as a complete system upgrade rather than as an ordinary cumulative update
  • Recent Achievements

    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      557
    2. 2
      +Edouard
      188
    3. 3
      Michael Scrip
      78
    4. 4
      PsYcHoKiLLa
      74
    5. 5
      neufuse
      71
  • Tell a friend

    Love Neowin? Tell a friend!