On Fri, Nov 16, 2012 at 09:13:33AM -0800, Tony Lindgren wrote: > * Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx> [121116 02:07]: > > > > So, we don't detect whether we're running in secure mode or not; as I've > > already stated, we don't have a way to do that. We instead only apply > > work-arounds which aren't already enabled prior to the kernel booting. > > So, even on a secure mode platform, we will avoid writing the bits if the > > work-around has already been applied. > > This all assumes that we can read the value of the diagnostic register, > and on my 4430 blaze the read returns zero. I have no idea if this is > the correct value for the register, or if reads always just returns 0. ARM Ltd has made that assumption since the inception of the errata work-arounds appearing in the kernel for v6+ CPUs... But your question may prove to be moot if we end up ripping all these out, like I'm beginning to think we should do. -- 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
