On Thu, Aug 22, 2013 at 02:25:59AM +0200, Sebastian Reichel wrote: > Hi, > > On Wed, Aug 21, 2013 at 03:41:43PM -0400, Kyle McMartin wrote: > > 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) > > The initrd problem may be the same error I got, when I tried to boot > an OMAP DT kernel with an initrd file (I had no problems with kernel > arguments): > Definitely looks similar... I don't even get that far though. Spooky. Something definitely seems wonky. --Kyle -- 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
