Am 14.04.2017 um 13:46 schrieb Heinrich Schuchardt: > To enable booting from MMC the MMC devices 0 and 1 are added to the
from eMMC > BOOT_TARGET_DEVICES. > > Signed-off-by: Heinrich Schuchardt <xypron.g...@gmx.de> > --- > This is a resubmission of > https://lists.denx.de/pipermail/u-boot/2017-April/287315.html > where this patch was part of patch series which was no longer applicable. > --- > include/configs/meson-gxbb-common.h | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/include/configs/meson-gxbb-common.h > b/include/configs/meson-gxbb-common.h > index cc2b5b6..388f239 100644 > --- a/include/configs/meson-gxbb-common.h > +++ b/include/configs/meson-gxbb-common.h > @@ -39,6 +39,8 @@ > #include <config_distro_defaults.h> > > #define BOOT_TARGET_DEVICES(func) \ > + func(MMC, mmc, 0) \ > + func(MMC, mmc, 1) \ What if booting on SD fails and eMMC is absent? Will that still iterate on to DHCP? Thanks, Andreas > func(DHCP, dhcp, na) > > #include <config_distro_bootcmd.h> > -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
