On Wed, Jul 29, 2015 at 01:47:58PM -0600, Stephen Warren wrote: > From: Stephen Warren <swar...@nvidia.com> > > Additionally, ARM64 devices typically run a secure monitor in EL3 and > U-Boot in EL2, and set up some secure RAM carve-outs to contain the EL3 > code and data. These carve-outs are located at the top of 32-bit address > space. Restrict U-Boot's RAM usage to well below the location of those > carve-outs. Ideally, we would the secure monitor would inform U-Boot of > exactly which RAM it could use at run-time. However, I'm not sure how to > do that at present (and even if such a mechanism does exist, it would > likely not be generic across all forms of secure monitor).
0xe0000000-0xffffffff is 512 MiB, surely a secure monitor can live with less than that! Thierry ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------
signature.asc
Description: PGP signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
