From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH v1 1/2] armv8: fsl-layerscape: Reserve memory for PPA
Date: Tue, 10 Nov 2015 12:11:30 -0800 [thread overview]
Message-ID: <56424F72.8090705@freescale.com> (raw)
In-Reply-To: <20151110195203.20CA7383F07@gemini.denx.de>
On 11/10/2015 11:52 AM, Wolfgang Denk wrote:
> Dear York,
>
> In message <5642490C.9090407@freescale.com> you wrote:
>>
>>>> +- CONFIG_FSL_PPA_RESERVED_DRAM_SIZE
>>>> + If defined, this is reserved in highest address as secure memory
>>>
>>> What is Freescale-specific about the concept of reserving memory for a secure
>>> monitor?
>>
>> The PPA is a Freescale implementation of TrustZone application.
>
> That does not answer the question. What is so special here that you
> cannot use the existing CONFIG_PRAM ?
>
CONFIG_PRAM is reserved from the top of u-boot memory, which is not necessarily
the real top of memory.
I am putting this reserved memory under the name
CONFIG_FSL_PPA_RESERVED_DRAM_SIZE for now, because I don't know if this will
serve other SoCs. I would use a generic solution if I don't have MC and debug
server in my way. I am open to suggestions.
York
next prev parent reply other threads:[~2015-11-10 20:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 19:17 [U-Boot] [RFC PATCH v1 0/2] Make most DDR non-secure in MMU while keep a small block secure York Sun
2015-11-10 19:17 ` [U-Boot] [RFC PATCH v1 1/2] armv8: fsl-layerscape: Reserve memory for PPA York Sun
2015-11-10 19:31 ` Scott Wood
2015-11-10 19:44 ` York Sun
2015-11-10 19:51 ` Scott Wood
2015-11-10 20:24 ` York Sun
2015-11-11 2:08 ` Scott Wood
2015-11-10 19:52 ` Wolfgang Denk
2015-11-10 20:11 ` York Sun [this message]
2015-11-10 19:17 ` [U-Boot] [RFC PATCH v1 2/2] armv8: fsl-layerscape: Make DDR non secure in MMU tables York Sun
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=56424F72.8090705@freescale.com \
--to=yorksun@freescale.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.