From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: tegra: restrict usable RAM size further
Date: Wed, 05 Aug 2015 12:33:04 -0600 [thread overview]
Message-ID: <55C256E0.6010708@wwwdotorg.org> (raw)
In-Reply-To: <1438199278-29247-1-git-send-email-swarren@wwwdotorg.org>
On 07/29/2015 01:47 PM, Stephen Warren wrote:
> From: Stephen Warren <swarren@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).
TomW, what are your thoughts on applying this given the discussion
thread? Thanks.
next prev parent reply other threads:[~2015-08-05 18:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 19:47 [U-Boot] [PATCH] ARM: tegra: restrict usable RAM size further Stephen Warren
2015-07-30 11:04 ` Thierry Reding
2015-07-30 15:43 ` Stephen Warren
2015-07-30 15:52 ` Simon Glass
2015-07-30 18:47 ` Stephen Warren
2015-07-30 19:00 ` Simon Glass
2015-07-30 19:47 ` Stephen Warren
2015-08-05 18:33 ` Stephen Warren [this message]
2015-08-05 19:22 ` Tom Warren
2015-08-05 19:27 ` Stephen Warren
2015-08-05 19:30 ` Tom Warren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55C256E0.6010708@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox