[Tribu-android-gestion] Problemas en el modelo de desarrollo del kernel Linux Android

[Pedro de las Heras Quirós]

Resumen:

"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.

In order to write a driver for hardware to work on Android, you need
to properly integrate into this new lock, as well as sometimes the
bizarre security model. Oh, and then there's the totally-different
framebuffer driver infrastructure as well.

This means that any 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.org 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. Effectively creating a kernel branch that a number of
different vendors are now relying on."


http://www.kroah.com/log/linux/android-kernel-problems.html
vía /.