hecatae
4th February 2010, 08:51 AM
http://www.theregister.co.uk/2010/02/03/android_driver_code_deleted_from_linux_kernel/
http://www.kroah.com/log/linux/android-kernel-problems.html?seemore=y
So, what happened with the Android kernel code that caused it to be deleted? In short, no one cared about the code, so it was removed. As I've stated before, code in the staging tree needs to be worked on to be merged to the main kernel tree, or it will be deleted.
But there's a much bigger problem here.
The Android kernel code is more than just the few weird drivers that were in the drivers/staging/android subdirectory in the kernel. In order to get a working Android system, you need the new lock type they have created, as well as hooks in the core system for their security model.
2.6.33 kernel does not have android drivers as no-one wanted to work it into the main tree, so it was deleted on the 11th December 2009
both articles are a good read
When the Android code was merged into the staging tree, a number of kernel developers reviewed the code and pointed out places that needed to be cleaned up, and changed, in order for it to be accepted. A number of these changes will affect the kernel/userspace boundry, so some changes to the Android userspace logic would also need to be changed if these kernel changes are made, preventing anyone except a Google employee from making the changes necessary.
http://www.kroah.com/log/linux/android-kernel-problems.html?seemore=y
So, what happened with the Android kernel code that caused it to be deleted? In short, no one cared about the code, so it was removed. As I've stated before, code in the staging tree needs to be worked on to be merged to the main kernel tree, or it will be deleted.
But there's a much bigger problem here.
The Android kernel code is more than just the few weird drivers that were in the drivers/staging/android subdirectory in the kernel. In order to get a working Android system, you need the new lock type they have created, as well as hooks in the core system for their security model.
2.6.33 kernel does not have android drivers as no-one wanted to work it into the main tree, so it was deleted on the 11th December 2009
both articles are a good read
When the Android code was merged into the staging tree, a number of kernel developers reviewed the code and pointed out places that needed to be cleaned up, and changed, in order for it to be accepted. A number of these changes will affect the kernel/userspace boundry, so some changes to the Android userspace logic would also need to be changed if these kernel changes are made, preventing anyone except a Google employee from making the changes necessary.