Hi, On Thu, May 08, 2014 at 04:17:11PM -0700, Tony Lindgren wrote: > > OMAP1 fb is working very well. As a matter of fact, it's much more usable > > for me than fb on OMAP2/3 - apart from N900 (on which fb is working again > > with 3.15) none of my 4 other OMAP2/3 boards have a working display/fb > > in mainline yet. :-( > > I hear you.. What do you have in the .config for omap1? > Would be nice to enable the framebuffer in omap1_defconfig? Looks like the needed stuff is enabled there. Unfortunately I cannot test the full omap1_defconfig because of size limitations. > > > > Tony, any idea of omap1's fb? Are you able to test this? > > > > > > I have three omap1 boards in my rack that I use for my boot > > > testing. Tried to enable framebuffer but so far no luck on > > > any of them. So I'm not much of a help here. Looks like the > > > patch should work though.. > > > > > > Aaro & Janusz, care to take a look at the patch in this > > > thread? > > > > I couldn't figure out how to enter this code path. Amstrad E3 & Nokia > > 770 will take the alloc_fbmem() path & exit, and based on quick look > > I could not see way to enter mmap_kern(). Is that dead code? > > Could be. It may be something left from when we had code to keep > the bootloader logo displayed while booting kernel. The support for early fbmem alloc was removed in 2011 (1e434f9318efc3dddc0c0b8d2071712668154c2b, OMAPFB: remove early mem alloc from old omapfb), so I think we can safely delete this code. I can prepare & test a patch for this. A. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
