Vuelvo a poner este articulo de Steve kondik acerca de los customs kernel trabajando con CM.
Steve Kondik
28/04/2013 (modificado) - Público
Custom Kernels and CyanogenMod
If you've been around Android for more than five minutes, you know about how closely integrated userspace is with the kernel. For many HAL implementations, structs in kernel headers are used to communicate with the kernel from userspace via ioctls. For some fast-moving devices (such as most Qualcomm devices), this code is constantly being updated by our upstreams as well as ourselves. Since the userspace and kernelspace have to always be in sync, quite often we are breaking various custom kernels. It's usually just a simple matter of recompiling the userspace bits, so this is never an issue for us since we rebuild the entire platform everyday.
In order to keep evolving our code, this is always going to be a cat and mouse game. We're not doing it to break anyone's stuff on purpose. We work incredibly hard to provide the best device support possible, and it's difficult enough already. Everything we put out there is completely open source, and you're free to do with it as you please.
If you're using custom kernels with CM (particularly with nightly builds), be aware of this. Things will break. We aren't conspiring against you, nor are we "violating the spirit of the GPL". At the same time, I will freely admit that we aren't looking out for you either. If you want to run a fork of a single subsystem of a fast-moving highly interdepedent codebase, you will find dragons waiting for you.
That said, we totally encourage all of this and wouldn't be putting everything out there as opensource if not. Hopefully the good stuff finds its way back to us.Ocultar esta publicación