After closer inspection, the fbcon seems to have some kind of "lock" that doesn't allow other frame buffer to take over.
It gives a "BUG: Scheduling while atomic" on the screen, after that there are many stack trace and then it crashes. I've tracked the position aswell, drivers/video/fbmem.c, in function do_register_framebuffer and the call fb_notifier_call_chain(FB_EVENT_FB_REGISTERED, &event); After that I get the scheduling error messages. Is it because the earlier framebuffer is not unregistered? -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
