On 20/12/2023 04:46, Simon Glass wrote:
Hi Caleb,
On Tue, 19 Dec 2023 at 09:04, Caleb Connolly caleb.connolly@linaro.org wrote:
[..]
== DT loading ==
Previously, boards used the FDT blob embedded into U-Boot (via OF_SEPARATE). However, most Qualcomm boards run U-Boot as a secondary bootloader, so we can instead rely on the first-stage bootloader to populate some useful FDT properties for us (notably the /memory node and KASLR seed) and fetch the DTB that it provides. Combined with the memory map changes above, this let's us entirely avoid configuring the memory map explicitly.
Running U-Boot as a secondary bootloader is the degenerate case. Are there any Qualcomm boards where U-Boot runs first? In that case, perhaps the DT could be used in SPL to determine the memory size as well?
Yes, I'm totally fine with having memory maps hardcoded in DT, this would be my go-to approach for running U-Boot as a first-stage bootloader.
(this series is fine to me, BTW)
Regards, Simon