Hi Tom,
On Thu, 28 Oct 2021 at 10:43, Tom Rini trini@konsulko.com wrote:
On Sat, Oct 23, 2021 at 05:26:35PM -0600, Simon Glass wrote:
Switch this over, for testing purposes.
Signed-off-by: Simon Glass sjg@chromium.org
[snip]
#define CONFIG_EXTRA_ENV_SETTINGS \ "dhcpuboot=usb start; dhcp u-boot.uimg; bootm\0" \
"boot_targets=mmc0 mmc1 usb0 pxe dhcp\0" \So, based on this patch I went "oh, so we can still easily control the device order, per board and also for users to tweak". Then I looked for where boot_targets was used, saw it wasn't and looked over the documentation patch previous to this. That's not looking easier to configure than what we have now either.
Yes, I did originally implement the boot_targets env var, then decided it should be in the device tree instead, since you can do:
bootstd { compatible = "u-boot,boot-std"; bootdev-order = "mmc2", "mmc1"; };
(with nothing else in the devicetree)
I made this change since it seems that boot_targets is always set in the env and should not be touched by the distro. If that is not correct I can bring the code back...
BTW the MAC address was just for my testing.
Regards, Simon