* Anand Gadiyar <[email protected]> [101019 07:41]: > Hi all, > > linux-next, as of 20101019, built with the omap2plus_defconfig fails > to boot on omap3 and omap4. (I've disabled CONFIG_ARCH_OMAP2 or > CONFIG_SWP_EMULATE to get the image to build). Building with only > ARCH_OMAP3 allows the resultant image to boot up on OMAP3. Likewise, > an image built with only ARCH_OMAP4 boots up on OMAP4 boards. > > earlyprintk does not provide any additional prints after > "Uncompressing Linux... done, booting the kernel." > > Any ideas where to look?
Hmm I did a quick test merge of linux-omap master and rmk/devel branches and that boots just fine. So it's probably something that already got fixed in rmk/devel but is not yet in next, or something that came from elsewhere, or something that we have in omap-testing branch that's not in for-next for some reason. 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
