* Santosh Shilimkar <santosh.shilimkar@xxxxxx> [110212 00:45]: > Tony, > > -----Original Message----- > > From: Santosh Shilimkar [mailto:santosh.shilimkar@xxxxxx] > > Sent: Thursday, February 03, 2011 2:13 PM > > To: Tony Lindgren > > Cc: Anand Gadiyar; Russell King - ARM Linux; linux-arm- > > kernel@xxxxxxxxxxxxxxxxxxx; linux-omap@xxxxxxxxxxxxxxx; Keshava > > Munegowda; Felipe Balbi > > Subject: RE: [PATCH] omap4: Fix ULPI PHY init for ES1.0 SDP (Re: > > 4430SDP boot failure) > > > > > -----Original Message----- > > > From: Tony Lindgren [mailto:tony@xxxxxxxxxxx] > > > Sent: Thursday, February 03, 2011 1:19 AM > > > To: Santosh Shilimkar > > > Cc: Anand Gadiyar; Russell King - ARM Linux; linux-arm- > > > kernel@xxxxxxxxxxxxxxxxxxx; linux-omap@xxxxxxxxxxxxxxx; Keshava > > > Munegowda; Felipe Balbi > > > Subject: Re: [PATCH] omap4: Fix ULPI PHY init for ES1.0 SDP (Re: > > > 4430SDP boot failure) > > > > > > * Santosh Shilimkar <santosh.shilimkar@xxxxxx> [110201 22:04]: > > > > > > > > > > It's a ES1.0 blaze, with the patch below it reboots early > > > > > during the boot. I also have to disable omap_l2_cache_init > > > > > on this board to get it to boot. > > > > > > > > > Do you still get this problem with 'omap_l2_cache_init' ? > > > > As reported earlier, we don't see this issue on ES1.0 > > > > SDP. > > > > > > Yeah I do, it rarely makes it to the userspace. Works reliably > > > if I disable omap_l2_cache_init. > > > > > Ok. I shall try few experiments and try to reproduce it > > Not sure if it's the same issue but I managed to reproduce the > issue on ES2.0 itself. And after some experiments, it boiled > down to the V6 and V7 issue. By disabling OMAP2 from the build, > everything was fine again. Was this with linux-omap master branch or mainline? The V6 vs V7 issues should be sorted out with Russell's patches that we also have now in linux-omap master branch. 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