> -----Original Message----- > From: Russell King - ARM Linux [mailto:linux@xxxxxxxxxxxxxxxx] > Sent: Saturday, January 08, 2011 12:50 AM > To: Santosh Shilimkar > Cc: linux-omap@xxxxxxxxxxxxxxx; Tony Lindgren > Subject: Re: 4430SDP boot failure - solved + SPI bug fix > > On Sat, Jan 08, 2011 at 12:35:38AM +0530, Santosh Shilimkar wrote: > > > -----Original Message----- > > > From: Russell King - ARM Linux [mailto:linux@xxxxxxxxxxxxxxxx] > > > Sent: Saturday, January 08, 2011 12:23 AM > > > To: Santosh Shilimkar > > > Cc: linux-omap@xxxxxxxxxxxxxxx; Tony Lindgren > > > Subject: Re: 4430SDP boot failure - solved + SPI bug fix > > > > > > On Fri, Jan 07, 2011 at 11:55:10PM +0530, Santosh Shilimkar > wrote: > > > > > And, with one ARM errata disabled, the kernel finally boots. > So > > > the > > > > > "X-Loader hangs" message means that we did something that > non- > > > secure > > > > > mode prevented us from doing. > > > > > > > > > Actually it's not. The error message is quite misleading. > > > Basically in > > > > x-loader exception handlers are setup and all these handlers > > > report > > > > same message ("X-Loader hangs"). This should be fixed so that > it > > > can > > > > report more meaningful info like data abort, prefetch abort > etc. > > > > > > > > Till the vector relocation in the kernel exceptions are not > set up > > > > so code jumps to already installed exceptions in the x-loader > and > > > > hence the messege. > > > > > > I disagree with your "actually it's not". It was errata 742230, > > > which > > > requires access to the CP15, c15, c0, 1 register (a diagnostic > > > register) > > > which I bet provokes an undefined instruction trap from non- > secure > > > mode. > > > > > 742230 errata workaround is not implemented in the x-loader so I > > can surely say it's not the secure violation. > > Precisely. So when we directly read, modify and write this > diagnostic > register in the non-secure world during kernel boot, we end up > faulting. > Comment those instructions out, we don't get a fault, and the kernel > boots normally. I understand now. Was confused last time. So your custom build did have this errata CONFIG_ARM_ERRATA_742230 where there is an access to diagnostic register which is not accessible on OMAP4 from non-secure side. Thanks for clarification. Regards, Santosh -- 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
