Hello Tony,
Am 15.10.2015 um 00:20 schrieb Tony Lindgren:
* Tony Lindgren <tony@xxxxxxxxxxx> [151014 10:56]:
* Heiko Schocher <hs@xxxxxxx> [151012 22:58]:
Of this, secure content (including PPA) uses initial
portion of the SRAM. This chunk is not (and shouldn't
be) accessible from the public code.
The minimum size of this chunk (0x350) is used in this
patch. Available size is rounded off to 63K.
Both values would require a change if size of secure
content grows beyond 0x350.
Makes sense to me. And something similar is needed at least for
dm814x to get rid of the imprecise abort during boot with
commit bbeb92095159 ("ARM: 8422/1: enable imprecise aborts during
early kernel startup") applied.
Is this needed as a fix to the -rc cycle, or can this wait for
v4.4?
Actually I think we may have a regression somwhere. If you look
at commit 8b9a2810b02e ("ARM: OMAP4+: Move SRAM data to DT")
this should all be handled by drivers/misc/sram.c nowadays.
So for most SoCs, we should completely skip the plat-omap/sram.c
code.
Yes, correct. So it should be enough for changing the DT, thanks.
bye,
Heiko
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
--
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
