From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Warren <swarren@wwwdotorg.org>
Date: Wed, 05 Aug 2015 12:33:04 -0600
Subject: [U-Boot] [PATCH] ARM: tegra: restrict usable RAM size further
In-Reply-To: <1438199278-29247-1-git-send-email-swarren@wwwdotorg.org>
References: <1438199278-29247-1-git-send-email-swarren@wwwdotorg.org>
Message-ID: <55C256E0.6010708@wwwdotorg.org>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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.