From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Secure memory
Date: Mon, 9 Nov 2015 15:54:39 -0800 [thread overview]
Message-ID: <5641323F.5070102@freescale.com> (raw)
In-Reply-To: <563D2557.6040302@freescale.com>
On 11/06/2015 02:10 PM, York Sun wrote:
> Albert,
>
> I am trying to separate secure memory and non-secure memory for ARMv8. Before I
> go too far, I'd like to check with you to see if there is already some code
> implemented.
>
> Basically what I am trying to do is to mark most DDR memory non-secure because
> we have some non-secure masters such as SDHC DMA. I also want to reserve some
> memory for TrustZone application. In order to do that, I need to put the MMU
> tables in secure memory. I will need to modify common/board_f.c to process
> reserve_mmu() differently for secure and non-secure mode.
>
> Please let me know if running u-boot in non-secure mode is a bad idea.
>
I didn't hear from you so I went ahead to implement the change. Please review
the patches, coming soon.
York
next prev parent reply other threads:[~2015-11-09 23:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 22:10 [U-Boot] Secure memory York Sun
2015-11-09 23:54 ` York Sun [this message]
2015-11-10 12:17 ` Albert ARIBAUD
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=5641323F.5070102@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox