On 20/02/2024 14:19, Peter Robinson wrote:
On Thu, 15 Feb 2024 at 21:03, Caleb Connolly caleb.connolly@linaro.org wrote:
Add a config fragment for building U-Boot such that it can be chainloaded by aboot/LK rather than being flashed directly to the aboot partition.
How does this work in practice? I think a lot of devices, one example I see is signed vs unsigned, or emmc vs other storage, have to configs, how would a user choose with LK vs the other option here?
I'm not sure I understand, maybe the commit message wording was a bit vague... There is only the default mode where U-Boot is flashed to the aboot partition, and then the chainloaded usecase where it's wrapped in an Android boot image and flashed to the boot partition.
Reviewed-by: Neil Armstrong neil.armstrong@linaro.org Signed-off-by: Caleb Connolly caleb.connolly@linaro.org
board/qualcomm/dragonboard410c/configs/chainloaded.config | 7 +++++++ 1 file changed, 7 insertions(+)
diff --git a/board/qualcomm/dragonboard410c/configs/chainloaded.config b/board/qualcomm/dragonboard410c/configs/chainloaded.config new file mode 100644 index 000000000000..3fd064924a1f --- /dev/null +++ b/board/qualcomm/dragonboard410c/configs/chainloaded.config @@ -0,0 +1,7 @@ +# CONFIG_ENABLE_ARM_SOC_BOOT0_HOOK is not set +CONFIG_TEXT_BASE=0x0 +# CONFIG_HAS_CUSTOM_SYS_INIT_SP_ADDR is not set +# CONFIG_REMAKE_ELF is not set +CONFIG_POSITION_INDEPENDENT=y +CONFIG_INIT_SP_RELATIVE=y +CONFIG_SYS_INIT_SP_BSS_OFFSET=524288
-- 2.43.1