I've tried copy a binary to /dev/graphics/fb0, and it can work. My framebuffer driver works wellBut Android still not print something on the screem. It semms google make some modification on SufaceFlinger serives.As I trace the system bootup, it uses mmap to map /dev/graphics/fb0 to memory.

BTW, the boot very slow problem is solved, it's because my flash driver I/O thread's priority is too low.Now system can boot successfully, but still have nothing on screen

I've tried copy a binary to /dev/graphics/fb0, and it can work. My framebuffer driver works wellBut Android still not print something on the screem. It semms google make some modification on SufaceFlinger serives.As I trace the system bootup, it uses mmap to map /dev/graphics/fb0 to memory.

how did you copy it?

you need to do "cp -prd /dev/XXX /dev/graphics/" to copy the device, or, better yet, use "mknod" instead!

I've tried copy a binary to /dev/graphics/fb0, and it can work. My framebuffer driver works wellBut Android still not print something on the screem. It semms google make some modification on SufaceFlinger serives.As I trace the system bootup, it uses mmap to map /dev/graphics/fb0 to memory.

how did you copy it?

you need to do "cp -prd /dev/XXX /dev/graphics/" to copy the device, or, better yet, use "mknod" instead!

I use android's original init, and it creates device node automatically; /dev/graphics/fb0 (29, 0) is alreadly therewhen system boot-up.I mean I copy a binary image into the fb device, and there's something shown on screenAnd I also use mmap() to map the fb device, write something, and it works.My framebuffer driver seems works fine.

You mean you don't even care that the screen is black all the time? I've created an installable image from the new SDK. From what I see in the traces Android starts normally. It's just that there's nothing displayed...

You mean you don't even care that the screen is black all the time? I've created an installable image from the new SDK. From what I see in the traces Android starts normally. It's just that there's nothing displayed...

if you tap around on the screen, can you tell if something's happening by looking at debug output and any processes/threads running?

You mean you don't even care that the screen is black all the time? I've created an installable image from the new SDK. From what I see in the traces Android starts normally. It's just that there's nothing displayed...

Hi,

Have you got some IOCTL errors about /dev/fb or /dev/graphics in the debug output. The last time i've got a black screen problem when porting an appli, it was because of the use of a double framebuffer.The framebuffer was mmaped in ram with the size of two screens and it started with the second screen !!! and then tried to switch the base address of the visible window with "FBIOPAN" IOCTL (don't work with our driver).Maybe It's not our actual problem, but i have no other idea.

You mean you don't even care that the screen is black all the time? I've created an installable image from the new SDK. From what I see in the traces Android starts normally. It's just that there's nothing displayed...

Hi,

Have you got some IOCTL errors about /dev/fb or /dev/graphics in the debug output. The last time i've got a black screen problem when porting an appli, it was because of the use of a double framebuffer.The framebuffer was mmaped in ram with the size of two screens and it started with the second screen !!! and then tried to switch the base address of the visible window with "FBIOPAN" IOCTL (don't work with our driver).Maybe It's not our actual problem, but i have no other idea.

All of you make a great work about porting android !!!

I see no IOCTL errors of significance. All devices are created nicely when running the /init executable, including /dev/graphics/fb0. This is no double framebuffer as far as I can tell. All services start successfully (I don't see the errors as described in the first post).

The main difference between Qemu emulator and Zaurus seems to be the supported OpenGL options. From what I remember, the Zaurus doesn't support page flipping.

My guess for now. Let the Android use drivers/video/pxafb.c not platform driver in arch/arm/mach-pxa. I'm working on another project for now and my Zaurus is configured for m3 Android. Later I'd like to try to build the kernel with CONFIG_FB_PXA=m and see what happens.