Add explicit boot_targets to indicate the specific boot sequence to follow.
NOTE: The non-standard ti_mmc emulates what is done for distro_boot. With bootstd, this will eventually need to be replaced by equivalent class.
Signed-off-by: Nishanth Menon nm@ti.com --- New patch (part of bootstd transition) - we can argue that ti_mmc should'nt belong here - but I wanted to maintain the boot_ti_mmc target that is provided in ti_common.env
board/ti/am62x/am62x.env | 1 + 1 file changed, 1 insertion(+)
diff --git a/board/ti/am62x/am62x.env b/board/ti/am62x/am62x.env index f2dc87893a92..1cf56dbd8128 100644 --- a/board/ti/am62x/am62x.env +++ b/board/ti/am62x/am62x.env @@ -11,6 +11,7 @@ args_all=setenv optargs ${optargs} earlycon=ns16550a,mmio32,0x02800000 ${mtdparts} run_kern=booti ${loadaddr} ${rd_spec} ${fdtaddr}
+boot_targets=ti_mmc mmc0 mmc1 usb pxe dhcp boot=mmc mmcdev=1 bootpart=1:2