On August 6, 2026 thus sayeth Simon Glass: > Hi Bryan, > > On 2026-08-04T21:55:02, Bryan Brattlof <[email protected]> wrote: > > configs: am62lx_evm: add initial defconfig > > > > Add the initial minimum configuration needed to boot the AM62L3-SK > > reference boards. > > The commit message refers to AM62L3-SK but the defconfig is named > am62lx_evm_defconfig and selects CONFIG_TARGET_AM62L3_EVM. Please make > the naming consistent - either the board is an SK or an EVM, not both.
I'll fix the commit message. > > > > > Tested-by: Anshul Dalal <[email protected]> > > Signed-off-by: Bryan Brattlof <[email protected]> > > > > configs/am62lx_evm_defconfig | 138 > > +++++++++++++++++++++++++++++++++++++++++++ > > 1 file changed, 138 insertions(+) > > > diff --git a/configs/am62lx_evm_defconfig b/configs/am62lx_evm_defconfig > > @@ -0,0 +1,138 @@ > > +CONFIG_SPL_LOAD_FIT_ADDRESS=0x83000000 > > +CONFIG_BOOTSTD_FULL=y > > +# CONFIG_BOARD_INIT is not set > > Unlike the other AM62x A53 defconfigs there is no CONFIG_BOOTCOMMAND > and no CONFIG_BOARD_LATE_INIT here, and the .env file added in patch 6 > also has no bootcmd. Just to check - is this intentional (relying > entirely on the default bootstd behaviour), or an omission? The downstream teams modify this for their needs[0]. The goal here is to support as many boot methods as possible and let meta-ti do whatever they want for the downstream fork. [0] https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/?h=ti-u-boot-2026.01&id=c754b0419ef89c20e0ffb5e1beb82b4606953b13 ~Bryan
