summaryrefslogtreecommitdiff
path: root/doc/develop/bootstd
diff options
context:
space:
mode:
authorTom Rini <[email protected]>2025-10-22 12:23:48 -0600
committerTom Rini <[email protected]>2025-10-22 12:23:48 -0600
commit8bc918ed97b4c79eecd56969a2898a8c75886c5a (patch)
treef4964b4e9a7dc85b72ebf0c72b3ca0211338257a /doc/develop/bootstd
parent29a96acaa3a84c68264d8dcf2182000bce71175e (diff)
parent342fd918b1bf2f00f52216297d5fe22272e8c7ca (diff)
Merge patch series "Add support for dynamic MMU configuration"
Anshul Dalal <[email protected]> says: In U-Boot, TI only provides a single memory map for all k3 platforms, this does not scale for devices where atf and optee lie outside the range 0x80000000 - 0x80080000 and 0x9e780000 - 0xa0000000 respectively. There are also issues for devices with < 2GiB of memory (eg am62SiP with 512MiB of RAM) as the maximum size for the first DRAM bank is hardcoded to 2GiB in the current memory map. Furthermore the second DRAM bank is mapped even for devices that only have a single bank. Therefore this patch set adds the required functionality to create the MMU table at runtime based on the device-tree. The patch set has been build tested on all effected platforms but boot-tested only on TI's K3 EVMs, the beagleplay and phytec's phycore-am6* platforms. The following effected boards have not been boot tested: - verdin-am62 - iot2050 Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'doc/develop/bootstd')
0 files changed, 0 insertions, 0 deletions