To view parent comment, click here.
To read all comments associated with this story, please click here.
Actually, this is most if not all custom kernel code in Android except for the "portion per timers and battery efficiency" (Wavelocks):
"Immature
As anticipated, a number of Android specific drivers have now entered the staging area, including some drivers previously merged into the staging area, but later removed as because they were not being maintained (1, 2, 3, 4, 5 and others). These changes mean that the kernel should now contain everything required to boot an Android userland, but is still missing wake lock code or equivalent [1], which is required to achieve decent battery life.
John Stultz has put together some background information on the status of integration of Android-specific changes in this LWN.net article [2], in which he reports on a meeting of the Android mainlining interest group. [3]"
[1] http://thread.gmane.org/gmane.linux.kernel/1249726/focus%3D1256...
[2] http://lwn.net/Articles/484196/
[3] http://www.h-online.com/news/item/Android-drivers-to-be-included-in...
Progress is/seems slow, but still moving.




Member since:
2007-08-22
What precisely does this do?
Is a part of the Android code not java and such.
Or is it just real low level stuff.
Android/Google/OHSA had a number of changes in the Linux Kernel portion per timers and battery efficiency. They were initially rejected due to very big differences with the mainline kernel. So this is the merging of that code reworked to be more compatible with the mainline kernel - including drivers, etc.
At least, that's what I gather based on previous information about the incompatibilities of the patches to Android vs. the mainline kernel.