diff options
author | Ian Campbell <ijc@hellion.org.uk> | 2015-04-21 07:18:36 +0200 |
---|---|---|
committer | Tom Warren <twarren@nvidia.com> | 2015-05-13 09:24:15 -0700 |
commit | 73169874a2867cb8ee5ec79eb9f2b176d3af34b2 (patch) | |
tree | c54e48fe526faa9ef81f58de7460013646706d5b /fs/zfs/zfs_sha256.c | |
parent | ffdf9f9ae057131375534df5f1e798d1e64785e9 (diff) | |
download | u-boot-imx-73169874a2867cb8ee5ec79eb9f2b176d3af34b2.zip u-boot-imx-73169874a2867cb8ee5ec79eb9f2b176d3af34b2.tar.gz u-boot-imx-73169874a2867cb8ee5ec79eb9f2b176d3af34b2.tar.bz2 |
tegra124: Reserve secure RAM using MC_SECURITY_CFG{0, 1}_0
These registers can be used to prevent non-secure world from accessing a
megabyte aligned region of RAM, use them to protect the u-boot secure monitor
code.
At first I tried to do this from s_init(), however this inexplicably causes
u-boot's networking (e.g. DHCP) to fail, while networking under Linux was fine.
So instead I have added a new weak arch function protect_secure_section()
called from relocate_secure_section() and reserved the region there. This is
better overall since it defers the reservation until after the sec vs. non-sec
decision (which can be influenced by an envvar) has been made when booting the
os.
Signed-off-by: Ian Campbell <ijc@hellion.org.uk>
[Jan: tiny style adjustment]
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
Reviewed-by: Thierry Reding <treding@nvidia.com>
Tested-by: Thierry Reding <treding@nvidia.com>
Tested-by: Ian Campbell <ijc@hellion.org.uk>
Signed-off-by: Tom Warren <twarren@nvidia.com>
Diffstat (limited to 'fs/zfs/zfs_sha256.c')
0 files changed, 0 insertions, 0 deletions