On Wed, Jan 20, 2016 at 03:43:37PM +0100, Clemens Gruber wrote: > This enables boards to choose where to/from the environment should be > saved/loaded. They can then for example support using the same device > (dynamically) from which the bootloader was launched to load and save > env data and do not have to define CONFIG_SYS_MMC_ENV_DEV statically. > > In my use case, the environment needs to be on the same device I > booted from. It can be the eMMC or an optional SD card. > I therefore would override mmc_get_env_dev in the board code, read the > CPU registers to determine where we booted from and return the > corresponding device index. > > Cc: Tom Rini <tr...@konsulko.com> > Cc: Stephen Warren <swar...@nvidia.com> > Cc: Tim Harvey <thar...@gateworks.com> > Cc: Simon Glass <s...@chromium.org> > Cc: Hans de Goede <hdego...@redhat.com> > > Signed-off-by: Clemens Gruber <clemens.gru...@pqgruber.com> > Reviewed-by: Stephen Warren <swar...@nvidia.com> > Reviewed-by: Tom Rini <tr...@konsulko.com>
Applied to u-boot/master, thanks! -- Tom
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
