arm-trusted-firmware/docs/getting_started
Samuel Holland f8578e641b bl31: Split into two separate memory regions
Some platforms are extremely memory constrained and must split BL31
between multiple non-contiguous areas in SRAM. Allow the NOBITS
sections (.bss, stacks, page tables, and coherent memory) to be placed
in a separate region of RAM from the loaded firmware image.

Because the NOBITS region may be at a lower address than the rest of
BL31, __RW_{START,END}__ and __BL31_{START,END}__ cannot include this
region, or el3_entrypoint_common would attempt to invalidate the dcache
for the entire address space. New symbols __NOBITS_{START,END}__ are
added when SEPARATE_NOBITS_REGION is enabled, and the dcached for the
NOBITS region is invalidated separately.

Signed-off-by: Samuel Holland <samuel@sholland.org>
Change-Id: Idedfec5e4dbee77e94f2fdd356e6ae6f4dc79d37
2019-12-29 12:00:40 -06:00
..
build-options.rst bl31: Split into two separate memory regions 2019-12-29 12:00:40 -06:00
docs-build.rst doc: Split the User Guide into multiple files 2019-11-27 10:45:54 +00:00
image-terminology.rst doc: Misc syntax and spelling fixes 2019-10-11 12:39:06 +00:00
index.rst doc: Split the User Guide into multiple files 2019-11-27 10:45:54 +00:00
initial-build.rst doc: Split the User Guide into multiple files 2019-11-27 10:45:54 +00:00
porting-guide.rst doc: Split the User Guide into multiple files 2019-11-27 10:45:54 +00:00
prerequisites.rst doc: Split the User Guide into multiple files 2019-11-27 10:45:54 +00:00
psci-lib-integration-guide.rst doc: Convert internal links to RST format 2019-10-08 15:58:03 +00:00
rt-svc-writers-guide.rst Changes to support updated register usage in SMCCC v1.2 2019-11-26 12:56:30 -06:00
tools-build.rst doc: Split the User Guide into multiple files 2019-11-27 10:45:54 +00:00