* Kyle McMartin <[email protected]> [130822 07:08]: > On Wed, Aug 21, 2013 at 11:34:50PM -0700, Tony Lindgren wrote: > > * Kyle McMartin <[email protected]> [130821 12:48]: > > > On Wed, Aug 21, 2013 at 11:43:21AM -0400, Kyle McMartin wrote: > > > > I've suspected there might be a config issue, as omap2_defconfig > > > > works alright, as does booting a uImage with an appended > > > > omap4-panda.dtb, but there's no love with a zImage + initrd + dtb > > > > (or even just zImage without initrd + dtb.) > > > > > > > > > > after some further investigation, something odd is going on... turns > > > out things have been working (at least until initrd time, but that's > > > another story) fine but none of the bootargs have made it into the > > > kernel, so console= was unset and no messages came out. > > > > Hmm I've seen that with extra quotes around the u-boot bootargs line. > > But if things work OK with omap2plus_defconfig, then it sounds that > > something gets trashed with your .config options. Care to post your > > .config file somewhere? > > > > Sure, CONFIG_CMDLINE is "" for us... > > http://kyle.fedorapeople.org/config-3.11.0-0.rc6.git0.1.fc20.armv7hl
Tried this on my 4430 SDP with the current tip of linux-omap tree at -rc6, had to disable FTRACE and ARCH_ZYNQ to compile. I can confirm that earlyprintk works, but no output from the serial console. Looking at the console output, looks like serial-omap probe is deferred because of no pinctrl driver. So having: CONFIG_PINCTRL_SINGLE=y fixes the issue at least for me booting to the point where it tries to mount root. It seems to be set to module in your .config. Note that there's still that one bug where earlyprintk does not properly work with serial-omap because of the idling of the device.. But that's a separate issue :) Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
