* Shilimkar, Santosh <santosh.shilimkar@xxxxxx> [100130 03:07]: > Tony, > > -----Original Message----- > > From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Tony > > Lindgren > > Sent: Saturday, January 30, 2010 7:31 AM > > To: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx > > Cc: linux-omap@xxxxxxxxxxxxxxx > > Subject: [PATCH 0/9] Initial multi-omap support for omap4 > > > > Hi all, > > > > These patches allow compiling in also omap4 into the multi-omap > > configuration. As I don't yet have omap4, I've only boot tested > > these on omap2 and omap3. > > > > Somebody with an omap4 board please boot test these with the > > omap3_defconfig and see what happens.. You might want to enable > > DEBUG_LL and EARLY_PRINTK with earlyprintk on the cmdline too. > Looks like this series have some dependent series because it doesn't > apply on mainline. Sorry, forgot to mention that these are against the earlier multi-omap patches. Basically stuff that's now queued for the merge window in the omap-for-linus branch. > So I tested this directly on linux-omap "multi-omap4" branch. It boots sufficiently > but doesn't proceed after "brd_init". Didn't get much time to debug so attached log Thanks for testing. Yeah these same are in the multi-omap4 branch also. Regards, Tony -- 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