[U-Boot] [PATCH v2] arm: imx: Switch Wandboard to use config_distro_bootcmd.h.

[Vagrant Cascadian]

On 2015-10-27, Fabio Estevam wrote:
> On Tue, Oct 27, 2015 at 5:49 PM, Vagrant Cascadian <vagrant at debian.org> wrote:
>
>> +#define BOOT_TARGET_DEVICES(func) \
>> +       func(MMC, mmc, 0) \
>> +       func(MMC, mmc, 1) \
>> +       func(USB, usb, 0) \
>> +       func(PXE, pxe, na) \
>> +       func(DHCP, dhcp, na)
>
>
> I never used config_distro_bootcmd, so let me ask you: is there a TFTP
> variant for func() as well?

Both PXE and DHCP download an extlinux-style config (or boot script) via
TFTP, which then decides what kernel, initrd, dtb, etc. to load. Other
boot methods work similarly, loading from local media.


> In the current script we can switch from TFTP/DHCP very easily.

You can override the default boot order by changing the boot_targets variable.


> Also, how can do we switch from booting the rootfs from mmc versus NFS mount?

That would be defined in the extlinux-style config or boot script.


So, it doesn't exactly replicate the prior functionality, though it
provides similar methods.

This is why I originally proposed to make it fallback to the old
behavior, then you could set boot_targets to empty and still have the
old style booting; but opinions may differ on all this. :)

Mostly, I'm seeking to standardize on a common configuration for as many
boards as we can in Debian (and ideally in upstream u-boot, to minimize
long-term maintenance), so that various supported boards at least behave
similarly by default.

A lot of goals and functionality is documented reasonably well in
doc/README.distro.


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151027/3a2b0d9c/attachment.sig>