First see http://source.android.com/source/building-kernels.html especially section "Downloading sources".
Although android.googlesource.com/kernel/ hosts a git server with kernel source repositories for a variety of devices, each of those repositories has generally evolved independently. Usually an SoC vendor initially took some generic kernel commit, added their own device drivers and configuration, and then it was integrated with Android to form a particular device release. This then continued with successive generations. If you look at the repositories, it's usually a 1-1 match between SoC vendor and repository name. It would be a large amount of work (technically and management-wise) to attempt to have a single repository that was always up-to-date for all SoC vendors and devices, and the benefit is not enough to justify the cost. On Wednesday, March 13, 2013 8:14:21 PM UTC-7, Kristopher Micinski wrote: > > All, > > I'm asking a slightly uninformed question here just in hopes that I > won't have to delve into lots of code to understand what's going on. > I understand that Android maintains a different version of the kernel > for each specific platform. I was wondering why this is the case, and > why the code isn't simply offered as a single kernel with a > configuration set for relevant devices? > > Is it simply that modifying the kernel's build system is a pain, or is > there some deeper programming problem? > > Kris Micinski > -- -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel --- You received this message because you are subscribed to the Google Groups "Android Linux Kernel Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-kernel+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
