On Fri, Mar 30, 2012 at 02:39:32PM -0700, Tony Lindgren wrote: > * Kumar Gala <galak@xxxxxxxxxxxxxxxxxxx> [120330 14:14]: > > > > On Mar 30, 2012, at 1:48 PM, Tony Lindgren wrote: > > > > > Hi, > > > > > > * Kumar Gala <galak@xxxxxxxxxxxxxxxxxxx> [120329 12:24]: > > >> As I'm new to the OMAP community this might be a stupid question but trying to just build and run a stock v3.3 kernel on a pandaboard. In doing so it seems as if some basic drivers are not enabled in omap2plus_defconfig for the board. I'm trying to figure out if this is normal for some reason or just an oversight. > > >> > > >> For example, USB and USB ethernet (SMC95xx). I notice the linaro kernel tree introduces an omap4_defconfig, so just wondering should I send patches to omap2plus_defconfig or what? > > > > > > We can add those to omap2plus_defconfig for sure, but let's have > > > them added as modules. Then distros can use that easily in a > > > standard way using initramfs-tools etc. > > > > > > Let's not change the drivers that are currently built in if they're > > > needed for mounting mmc or nfsroot. Those can be changed later on. > > > > I'll work up a patch, however I was doing this as I was trying to get NFS root working and thus would need USB + USB ethernet compiled in and not as modules for panda. Is that ok? > > Maybe, let's take a look how much bigger the kernel becomes. > Also we need to check if the same EHCI configuration works > for omap3/4. FWIW, the same EHCI + SMSC95xx config is used for Beagle xM for nfsroot. First thing I enable on any builds. -Matt -- 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
