Android on OMAP

We have a Blaze device and run L27.12.1-P1 source on the device. We want to
integrate the android recovery mechanism in our source, but we found a
problem which can=92t direct write a BMP into frambuffer from mmap memory w=
ith
/dev/fb0, no change on the screen. Just like this,

In normal mode, we found there is the GFX lib and PVR service mechanism in
kernel space for framebuffer and overlay management. We also see the
=93framebuffer_test=94 source code from GFX DDK release, it using GRALLOC m=
odule
from GFX lib.

(And the normal mode can=92t write character on /dev/tty0 from android init
process, no =93ANDROID=94 on screen before the boot animation in the bootin=
g)

How can we bypass these mechanisms and show BMP on framebuffer in the
Android Recovery Mode (only Kernel+recovery_ramdisk, without android
system)?