But the larger problem, he continues, is that Android uses a new lock type, new hooks for its „sometimes bizarre“ security model, and a revamped framebuffer driver infrastructure. All this, he says, prevents „a large chunk“ of Android drivers and platform code from merging into the main kernel tree. … „A number of [necessary] 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,“ he says.