On 06/25/2010 05:14 AM, Sunny Aujla wrote: > Hi Pankaj, > > There's not much difference.� > The Android kernel code has been removed from the main kernel tree as of > the 2.6.33 kernel release > > The Android code was in the main kernel tree before 2.6.33 kernel > release but no one cared about the code, so it was removed. Then google > had taken over this code. > Google has taken the Linux kernel, and nothing else from a traditional > Linux system, and created a portable and robust phone platform.� What > this means now is: > > Drivers written for Android hardware platforms, can not get merged into > the main kernel tree because they have dependencies on code that only > lives in Google's kernel tree, causing it to fail to build in the kernel > tree. Because of this, Google has now prevented a large chunk of > hardware drivers and platform code from ever getting merged into the > main kernel tree.
That's a pretty biased and simplistic narrative. Google has expended a lot of effort to mainline their power management code. Nothing prevents the authors of these "large chunks of hardware drivers and platform code" from isolating the wakelock callouts from the rest of their code, and mainlining the core parts. Sometimes out-of-tree code has to "stew" for years before being accepted in one form or another. In the mean time, I don't think it's productive to blame Google for lack of mainlining code that they mostly didn't write in the first place, when they've made serious attempts to mainline their stuff. ============================= Tim Bird Architecture Group Chair, CE Linux Forum Senior Staff Engineer, Sony Network Entertainment ============================= -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
