Hi Manorit! On March 15, 2023 thus sayeth Manorit Chawdhry: > K3 devices have runtime type board detection. Make the default defconfig > include the secure configuration. Then remove the HS specific config. > > Non-HS devices will continue to boot due to runtime device type detection. > If TI_SECURE_DEV_PKG is not set the build will emit warnings, for non-HS > devices these can be ignored. > > Signed-off-by: Manorit Chawdhry <m-chawd...@ti.com> > Acked-by: Andrew Davis <a...@ti.com> > --- > MAINTAINERS | 2 - > configs/j721e_evm_a72_defconfig | 3 +- > configs/j721e_evm_r5_defconfig | 1 + > configs/j721e_hs_evm_a72_defconfig | 208 ----------------------------- > configs/j721e_hs_evm_r5_defconfig | 176 ------------------------ > 5 files changed, 3 insertions(+), 387 deletions(-) > delete mode 100644 configs/j721e_hs_evm_a72_defconfig > delete mode 100644 configs/j721e_hs_evm_r5_defconfig >
... > CONFIG_OF_BOARD_SETUP=y > -CONFIG_BOOTCOMMAND="run findfdt; run distro_bootcmd; run init_${boot}; run > main_cpsw0_qsgmii_phyinit; run boot_rprocs; run get_kern_${boot}; run > get_fdt_${boot}; run get_overlay_${boot}; run run_kern" > +CONFIG_BOOTCOMMAND="run findfdt; run envboot; run init_${boot}; run > main_cpsw0_qsgmii_phyinit; run boot_rprocs; if test ${boot_fit} -eq 1; then > run get_fit_${boot}; run get_overlaystring; run run_fit; else; run > get_kern_${boot}; run get_fdt_${boot}; run get_overlay_${boot}; run run_kern; > fi;" I'm curious, do we need to drop the distro_bootcmd step? ~Bryan