Sorry, I was looking at your first post, not the latest boot dump. Also verify that the color bits are the the right locations for the userland libraries. I haven't been looking at the current sources for a while but a when I last worked on my AT91SAM9263-EK I had to add support for rgb:5:5:5 (Android had 5:6:5). Also, on these slow processors it takes a while for the Java programs to start (which is the real screen control code). I put logcat in the background and ran ps or vmstat until either the background came up or the board crashed.
On Oct 19, 7:07 pm, l l <android...@gmail.com> wrote: > I have checked the log. > It is nomal. > > I/EGLDisplaySurface( 1583): xres = 480 px > I/EGLDisplaySurface( 1583): yres = 272 px > I/EGLDisplaySurface( 1583): xres_virtual = 480 px > I/EGLDisplaySurface( 1583): yres_virtual = 544 px > > Is there anything wrong. > > 2010/10/20 Brad Davis <bda...@cove-mtn.com> > > > Android "double buffers" the screen and the kernel needs to allocate > > this memory for the screen. This usually shows up as the yres_virtual > > value is twice the yres value. > > > I/EGLDisplaySurface( 1405): xres = 480 px > > I/EGLDisplaySurface( 1405): yres = 272 px > > I/EGLDisplaySurface( 1405): xres_virtual = 480 px > > I/EGLDisplaySurface( 1405): yres_virtual = 272 px > > > On Oct 18, 11:05 pm, l l <android...@gmail.com> wrote: > > > Hello, > > > > After I changed the LCD' settings it can work during the Linux Kernel > > start. > > > > But after Android start the LCD can not show anything. > > > > I am troubling what's wrong. > > > > 2010/8/9 l l <android...@gmail.com> > > > > > Thank you for you reply. > > > > > I mounting the root filesystem by NFS and I have /system in the tree. > > > > > If I put the filesystem on the nand flash I will make enough partition > > > > tables. > > > > Now, the problem how to make the LCD working. > > > > > I have check the fb0 by console. > > > > I find that the fb0 is not under the path /dev/ but in the path > > > > /dev/graphics/ > > > > Does it normal? > > > > > I use cat to check the /dev/graphics/fb0 > > > > And the content seems normal. > > > > > I am troubling what's wrong. > > > > > Are there any problem with the LCD settings? > > > > Or is there any problem with the kernel? > > > > > 2010/8/6 Brad Davis <bda...@cove-mtn.com> > > > > > Just a few more points: > > > > >> You need to fix up your boot image. It looks as if you are > > > >> mounting the the root filesystem by NFS but you probably don't have / > > > >> system in that tree. You either need to add /system or you need to > > > >> change your init.rc to get /system from somewhere. > > > > >> If you are getting your partitions from flash, your kernel has two > > > >> partitions defined, but Android usually expects 4+ (bootstrap, kernel, > > > >> system, data, recovery?). You either need to make the kernel > > > >> partition tables or the boot parameters match your flash layout. > > > > >> You won't be able to get the full system running in 64m of ram. > > > >> You will see this when everything seems to be running but init crashes > > > >> with the cryptic message about something tried to kill it (comes from > > > >> a required app dying). > > > > >> -- > > > >> unsubscribe: > > > >> android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > > <android-porting%2bunsubscr...@googlegroups.com<android-porting%252bunsubscr...@googlegroups.com> > > > > >> website:http://groups.google.com/group/android-porting > > > -- > > unsubscribe: > > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > > website:http://groups.google.com/group/android-porting -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
