SRU: A workaround for highmem issue on OMAP4 platform
On Thu, Sep 30, 2010 at 11:14:34PM +0200, Dechesne, Nicolas wrote:
> > CONFIG_PL310_ERRATA_588369 errata is pretty much must for OMAP4 ES1.0. This
> > should always be enabled on OMAP4 ES1.0 not to see any undefined behaviour.
> but we are on ES2.0, not ES1.0. What is the impact of enabling this errata on ES2.0?
From the talk I had with Rob Clark:
<robclark> ndec / rsalveti: which errata?
<rsalveti> robclark: PL310_ERRATA_588369
<robclark> ok.. let me check
<robclark> rsalveti: ok.. this one seems to apply to the cortex-a9 IP, prior to r2p0
<robclark> (just need to check which rev on cortex is in es2.0)
<robclark> r1p2.. so keep the errata enabled
So it seems we're OK with it.
And during my tests I was finally able to run for more than 28 hours (14 builds)
without getting any errors, so it seems that it's finally better.
But unfortunatelly I can easily get errors when using highmem, no matter what
setup I'm using, so probably a different issue.
Good thing is that it seems we finally got a workaround to use 1GB at
Ricardo Salveti de Araujo
kernel-team mailing list