Shared publicly  - 
Lots of stable and longterm Linux kernel rc1 releases now out there, please go test.

For some not-so-stable stuff, the next linux-next Linux kernel release should almost boot an Android userspace, we are only missing one piece, ashmem, and that should hopefully land in my staging-next tree next week. The patches are still being tested and cleaned up by others.

Note, this does not include the wakelock code, that is being worked on by others, and isn't necessary for Android to boot, just needed so it doesn't drain your battery.

So hopefully, by the 3.3 kernel release, the majority of the Android code will be merged, but more work is still left to do to better integrate the kernel and userspace portions in ways that are more palatable to the rest of the kernel community. That will take longer, but I don't foresee any major issues involved.
Peng Huang's profile photoPatrick Bellasi's profile photoTerry Hendrix II's profile photoAnatoliy Sivov's profile photo
For anyone who's interested in seeing what this looks like take a look at:

Which contains basically the same Android patches, but with now "enablement" patches that typically sit on top. Instructions for using the build are included on the build site. Listed here for convenience:

bzr branch lp:linaro-image-tools

#insert SD card

./linaro-image-tools/linaro-android-media-create --mmc /dev/sdc --dev panda --system system.tar.bz2 --userdata userdata.tar.bz2 --boot boot.tar.bz2

A fully enabled build is here:

Instructions on the build page.
So does it mean that future Android kernel development will take place upstream? That would be something to consider, additions like ashmem, binder and wakelocks are nice features for embedded Linux in general but the way they have been introduced seems to have left a bitter taste inside the kernel community.
Hmm, could this possibly make a dual standard Linux/Android setup on the same device easier?
Greg S
I would love to see the benchmarks showing how much difference in power usage the wakelock stuff has.
Is anyone maintaining a set of Android patches against mainline or linux-next?
+Warren Togami Jr. not needed, they are all (with one exception), now in the linux-next tree. That one exception has been posted to lkml already for review last week.
Sweet! I see the LKML thread about "autosleep". Do you have any thoughts as to how much more work that requires for linux-next? And would Android devs be happy with the end result...
Feel free to post questions to and ask questions on #linaro on We look forward to hearing from you.
+Greg Kroah-Hartman Regarding "not needed, they are all (with one exception), now in the linux-next tree." That's not quite the case. Besides wakelocks, there's still stuff like paranoid networking, ion, interactive cpufreq gov, usb gadget and adb driver, that are still out of tree.

However, the android userland will come up with a 3.3 tree (with the addition of one required input patch:;a=commitdiff_plain;h=2ee03935a77a2493f740ecee3558cab5386aa9a9 ), which I see as great progress.
+Greg Kroah-Hartman Its an ABI break. I've got a patch to add an ioctl to select timestamp modes per client queued in Dimitry's next branch. But Android userland still needs to be converted to use the ioctl.
Could anyone tell me which kernel version 3.4.* have all android changes and what all the features they have merged
I want to learn the kernel. primarily to raise kernel.apakah version anyone can tell?
Add a comment...