On Wed, Nov 14, 2012 at 10:53:35AM -0800, Tony Lindgren wrote: > Looks like enabling CONFIG_ARM_ERRATA_751472 causes omap4 blaze > to not boot when enabled. The ARM core on it is an earlier r1p2: > > CPU: ARMv7 Processor [411fc092] revision 2 (ARMv7), cr=10c53c7d > > Unfortunately I don't have the details of errata 751472, but I'm > guessing we need to disable it for r1p*.
Fails because it can't write the diagnostic register from non-secure mode or fails later? -- 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
