Linked by David Adams on Mon 19th Mar 2012 17:04 UTC, submitted by diegocg
Linux Linux 3.3 has been released. The changes include the merge of kernel code from the Android project. There is also support for a new architecture (TI C6X), much improved balancing and the ability to restripe between different RAID profiles in Btrfs, and several network improvements: a virtual switch implementation (Open vSwitch) designed for virtualization scenarios, a faster and more scalable alternative to the "bonding" driver, a configurable limit to the transmission queue of the network devices to fight bufferbloat, a network priority control group and per-cgroup TCP buffer limits. There are also many small features and new drivers and fixes are also available. Here's the full changelog.
Thread beginning with comment 511140
To read all comments associated with this story, please click here.
Android merge
by fran on Mon 19th Mar 2012 21:01 UTC
fran
Member since:
2010-08-06

Regarding the merge of kernel code from the Android project.
What precisely does this do?
Is a part of the Android code not java and such.
Or is it just real low level stuff.

Edited 2012-03-19 21:02 UTC

Reply Score: 3

RE: Android merge
by TemporalBeing on Mon 19th Mar 2012 21:59 in reply to "Android merge"
TemporalBeing Member since:
2007-08-22

Regarding the merge of kernel code from the Android project.
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.

Reply Parent Score: 9

RE[2]: Android merge
by Lennie on Tue 20th Mar 2012 15:15 in reply to "RE: Android merge"
Lennie Member since:
2007-09-22

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.

Reply Parent Score: 5

RE: Android merge
by Elv13 on Tue 20th Mar 2012 02:36 in reply to "Android merge"
Elv13 Member since:
2006-06-12

Android AOSP/LiNARO are getting bored of porting an heavy patch set to keep the Android fork of Linux up to date. So instead of another massive code drop that have no chance of getting merged, they go bit by bit to make the merge easier for everybody. This is a good thing if this get merged because Android drivers will start to work fine on regular Linux, a win for everybody (graphic drivers excluded).

Reply Parent Score: 4