> Good morning, > > We opted for the "Stay with omapfb", and disabled CONFIG_DRM_OMAP. > > Now the dev tree is showing all 3 fb devices, but still no video out 8-( > > Boot messages include: > > [root@apm002 johnea]# dmesg | grep omapfb > [ 0.000000] Kernel command line: console=ttyO2,115200n8 mpurate=auto > buddy=spidev camera=none vram=18MB omapfb.mode=dvi > omapfb.vram=0:6M,1:6M,2:6M omapdss.def_disp=dvi root=/dev/mmcblk0p2 > rootfstype=ext2 rootwait > [ 3.165069] omapfb omapfb: no driver for display: dvi > [ 3.165130] omapfb omapfb: no driver for display: lcd > [ 3.165161] omapfb omapfb: cannot parse default modes > > The "cannot parse default modes" message was eliminated by removing > "omapfb.vram=0:6M,1:6M,2:6M" from the boot params. > > This made me wonder if the omapfb boot params expected by 3.5.4 had changed. > So I tried a bunch of different permutations of boot params, with no effect > other than eliminating the "default modes" message mentioned above. > > I tried digging into the source to determine currently accepted omapfb boot > params, but had no success. > > It seems like we're really close. The latest config.gz and tar'd dmesg from > the running system are attached. > > Thank You again! for any advise on config, boot param, or other changes that > could make beagle DVI video work with 3.5.4... You guys are very close... Your "config-3.5.4-archarm-3" config just needed one more change: CONFIG_PANEL_TFP410=m -> CONFIG_PANEL_TFP410=y Tested on my Beagle xM... Regards, -- Robert Nelson http://www.rcn-ee.com/ -- 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
