great that its resolved.. > omapfb.vram="0:4M" btw, its just single fb., and right now not sure why its mandatory to explicitly quote 4M size. will post, once i get update on it..
On Thu, Feb 18, 2010 at 5:37 PM, eternity <[email protected]> wrote: > So finally I found as posted by Deva R > > my bootargs was missing <omapfb.vram="0:4M"> which is mandatory for > eclair. > > according to > http://wiki.davincidsp.com/index.php/Dual_Frame_Buffer_on_OMAP35x > omapfb.vram allocate buffer for /dev/fb1. > > But I saw in kernel .config, CONFIG_FB_OMAP2_NUM_FBS=1 only, even to > make sure after android boots up I checked there is only one frame > buffer in sysfs (/dev/graphics/fb0) > > so, why that parameter is required??? > any guess?? > > > > On Feb 17, 3:27 pm, Tirtha Kanti Ghosh <[email protected]> wrote: > > >Also, i used below bootargs. > > >set bootargs 'console=ttyS3,115200n8 root=/dev/mmcblk0p2 rw rootdelay=1 > > > > mem=256M init=/init stdin=serial >stdout=serial stderr=serial > > omap_vout.vid1_static_vrfb_alloc=y omapfb.vram="0:4M" ' > > > > >set bootcmd 'mmcinit;fatload mmc 0 0x80300000 uImage;bootm 0x80300000' > > > > I am using almost same bootargs but my memory address is 0x81c00000 as > > mentioned inhttp://omappedia.org/wiki/Android_Getting_Started. > > > > >btw - regarding no UI coming up, i booted the same tree y'day and was > ok.. > > > > do u mean, keep trying until it boots up??? > > > > >attached my boot log till UI. check against yours. > > > > thanks a lot. > > > > regards, > > -- > unsubscribe: > [email protected]<android-porting%[email protected]> > website: http://groups.google.com/group/android-porting > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
