Yes, Both console and android.console is pointing to correct serial device i.e. ttyS2.
My uboot args is console=ttyS2,115200n8 androidboot.console=ttyS2 root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait init=/init vram=12M omapfb.mode=dvi:480x272MR-16@60omapdss.def_disp=lcd43 Isn't this correct? On Fri, Jul 15, 2011 at 5:44 AM, hedwin <hedwin.kon...@gmail.com> wrote: > > Check if console and android.console point to the correct serial device. > Both a kernel parameters sent by u-boot. > > Cheers, > > Hedwin > > On Thu, Jul 14, 2011 at 9:45 PM, Manish Shakya <manishshakya...@gmail.com> wrote: >> >> Hi , >> >> I am wondering what are the changes to be made if I have to make to port rowboat to gumstix overo module. >> >> I did following things but it didn't worked. :-( >> I made change in config file , board-overo.c and also added LCD driver. Compilation went fine with out errors. >> But when I tried to run the image. It show following log and gets stuck. >> >> 2731240 bytes read >> ## Booting kernel from Legacy Image at 82000000 ... >> Image Name: Linux-2.6.37-g06ebbba >> Image Type: ARM Linux Kernel Image (uncompressed) >> Data Size: 2731176 Bytes = 2.6 MiB >> Load Address: 80008000 >> Entry Point: 80008000 >> Verifying Checksum ... OK >> Loading Kernel Image ... OK >> OK >> >> Starting kernel ... >> >> Uncompressing Linux... done, booting the kernel. >> >> >> -- >> Manish Shakya >> http://www.manishshakya.com.np >> >> -- >> unsubscribe: android-porting+unsubscr...@googlegroups.com >> website: http://groups.google.com/group/android-porting > -- Manish Shakya http://www.manishshakya.com.np http://secs.oakland.edu/~ganesan/iMX/ -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
