From: Tony Lindgren [mailto:tony@xxxxxxxxxxx] Sent: Wednesday, May 05, 2010 12:44 PM > * Aguirre, Sergio <saaguirre@xxxxxx> [100505 10:27]: > > Tony, > > > > > -----Original Message----- > > > From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > > > owner@xxxxxxxxxxxxxxx] On Behalf Of Tony Lindgren > > > Sent: Friday, April 30, 2010 3:34 PM > > > To: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx > > > Cc: linux-omap@xxxxxxxxxxxxxxx > > > Subject: [PATCH 11/11] omap2/3/4: Disable CONFIG_FB_OMAP in > > > omap3_defconfig > > > > > > 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 allows booting omap3_defconfig on various omaps. Tested on > > > 2420-n8x0, 3430-n900, 3630-zoom3 and 4430-blaze. Note that n8x0 > > > still has issues with starting user space because of TLS and > > > VFP. > > > > (Looping Tomi) > > > > Unfortunately, your patch is uncovering an issue with old DSS code to > > compile it as module, which I think is caused by this: > > > > A single omapfb.ko is attempted to be created in drivers/video/omap/ > folder, > > but the included source files (DSS code + lcd drivers), results in > multiple > > module_init entries added in a single module, and therefore giving > errors of > > duplicate init_module entries between omapfb_main.c and the lcd_*.c > files. > > > > So, either you disable old DSS driver completely, or you have it as > > built-in. > > OK thanks for pointing that out. I'll disable it so we have a > booting omap3_defconfig (with the modules compiling). In my local tree, I just have created this simple change, which could be reverted IF old DSS is intended to be used as a module in the future. I don't know how acceptable is to have it officially applied though. Regards, Sergio > > Regards, > > Tony
Attachment:
0001-omapfb-Remove-tristate-option-in-Kconfig.patch
Description: 0001-omapfb-Remove-tristate-option-in-Kconfig.patch
