On Tue, 2010-05-04 at 16:40 +0200, ext Tony Lindgren wrote: > * Tomi Valkeinen <tomi.valkeinen@xxxxxxxxx> [100504 00:21]: > > Hi, > > > > On Tue, 2010-05-04 at 02:52 +0200, ext Tony Lindgren wrote: > > > * Tony Lindgren <tony@xxxxxxxxxxx> [100430 13:47]: > > > > * Tony Lindgren <tony@xxxxxxxxxxx> [100430 13:32]: > > > > > Looks like CONFIG_FB_OMAP prevents somehow mounting root on MMC > > > > > at least on zoom3 for multi-omap. Disable CONFIG_FB until the > > > > > omap FB code is fixed. > > > > > > > > This one I'll drop as soon as the problem is sorted out with > > > > CONFIG_FB_OMAP. > > > > > > This one seems to be something under drivers/video/omap, so > > > I'll change CONFIG_FB_OMAP to be a module now. Updated patch > > > below. > > > > > > I'll update omap for-next accordingly, then Tomi can figure > > > it out :) > > > > This sounds... interesting... =) Any more info on what happens? Does it > > also affect new omapfb driver? > > Yeah this is interesting, it seems like the kernel cmdline gets > somehow corrupted for zoom3 with the omap3_defconfig if CONFIG_FB_OMAP=y. > Some options seem to be there, but for example rootwait option is > ignored and the root on MMC never mounts. This is in the current > omap for-next branch. Ok, so the cmdline parsing in omapfb could be broken. I'll check it out. > Hmm, what do you mean with "new omapfb" driver, the stuff you have > queued up? No, I mean the DSS2 version. drivers/video/omap is the old one, written mostly by Imre, and drivers/video/omap2 is the new one, written mostly by me. I guess most boards are still using the old omapfb driver. Tomi -- 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
