On 12/05/2015 03:57 AM, York Sun wrote:
Secure memory is at the end of memory, separated and reserved from OS, tracked by gd->secure_ram. Secure memory can host MMU tables, security monitor, etc. This is different from PRAM used to reserve private memory. PRAM offers memory at the top of u-boot memory, not necessarily the real end of memory for systems with very large DDR. Using the end of memory simplifies MMU setup and avoid memory fragmentation.
"bdinfo" command shows gd->secure_ram value if this memory is marked as secured.
Signed-off-by: York Sun yorksun@freescale.com
Changes in v7: None Changes in v6: Move cmd_bdinfo change into this patch Move flag macros and comments of secure_ram into this patch
Changes in v5: None Changes in v4: None Changes in v3: Put ifdef around secure_ram Move defining CONFIG_SYS_MEM_RESERVE_SECURE to patch 2/2
Changes in v2: Do not use CONFIG_SYS_MEM_TOP_HIDE mechanism
Changes in v1: Initial patch. Depends on http://patchwork.ozlabs.org/patch/540248/
Applied to fsl-qoriq master. Awaiting upstream.
York