sandbox: Change the range used for memory-mapping tags
Sandbox keeps a table of addresses which map to pointers which are outside its emulated DRAM. The current range from 10000000 conflicts with the PCI range, meaning that if PCI mapping is on, that particular address can be decoded by PCI instead of the table. Fix this by moving the range up to the top of memory. Update the docs while we are here. Signed-off-by: Simon Glass <sjg@chromium.org>
This commit is contained in:
@@ -655,14 +655,17 @@ Memory Map
|
||||
Sandbox has its own emulated memory starting at 0. Here are some of the things
|
||||
that are mapped into that memory:
|
||||
|
||||
======= ======================== ===============================
|
||||
======== ======================== ===============================
|
||||
Addr Config Usage
|
||||
======= ======================== ===============================
|
||||
100 CONFIG_SYS_FDT_LOAD_ADDR Device tree
|
||||
b000 CONFIG_BLOBLIST_ADDR Blob list
|
||||
10000 CFG_MALLOC_F_ADDR Early memory allocation
|
||||
f0000 CONFIG_PRE_CON_BUF_ADDR Pre-console buffer
|
||||
100000 CONFIG_TRACE_EARLY_ADDR Early trace buffer (if enabled). Also used
|
||||
======== ======================== ===============================
|
||||
100 CONFIG_SYS_FDT_LOAD_ADDR Device tree
|
||||
b000 CONFIG_BLOBLIST_ADDR Blob list
|
||||
10000 CFG_MALLOC_F_ADDR Early memory allocation
|
||||
f0000 CONFIG_PRE_CON_BUF_ADDR Pre-console buffer
|
||||
100000 CONFIG_TRACE_EARLY_ADDR Early trace buffer (if enabled). Also used
|
||||
as the SPL load buffer in spl_test_load().
|
||||
200000 CONFIG_TEXT_BASE Load buffer for U-Boot (sandbox_spl only)
|
||||
======= ======================== ===============================
|
||||
200000 CONFIG_TEXT_BASE Load buffer for U-Boot (sandbox_spl only)
|
||||
10000000 PCI address space (see test.dts)
|
||||
|
||||
ff000000 Memory-mapping tags start here
|
||||
======== ======================== ===============================
|
||||
|
||||
Reference in New Issue
Block a user