mirror of
https://github.com/ARM-software/arm-trusted-firmware.git
synced 2025-04-18 02:24:18 +00:00
![]() As per change [1], now HW_CONFIG gets loaded in secure and non-secure memory. Hence updated the documentation to show secure and non-secure load region of HW_CONFIG in FVP Arm platform. Additionally, added a note on how FW_CONFIG address gets passed from BL2 to BL31/SP_MIN. [1]: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/14620 Change-Id: I37e02ff4f433c87bccbe67c7df5ecde3017668b9 Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com> |
||
---|---|---|
.. | ||
alt-boot-flows.rst | ||
auth-framework.rst | ||
cpu-specific-build-macros.rst | ||
firmware-design.rst | ||
index.rst | ||
interrupt-framework-design.rst | ||
psci-pd-tree.rst | ||
reset-design.rst | ||
trusted-board-boot-build.rst | ||
trusted-board-boot.rst |