From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Warren <swarren@wwwdotorg.org>
Date: Mon, 16 Jun 2014 13:52:56 -0600
Subject: [U-Boot] [PATCH v2 04/11] drivers:dfu: new feature: separated
 bootloader alt setting
In-Reply-To: <1402566394-23342-4-git-send-email-p.marczak@samsung.com>
References: <1402399510-8965-1-git-send-email-p.marczak@samsung.com>	<1402566394-23342-1-git-send-email-p.marczak@samsung.com>
	<1402566394-23342-4-git-send-email-p.marczak@samsung.com>
Message-ID: <539F4B18.2040406@wwwdotorg.org>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 06/12/2014 03:46 AM, Przemyslaw Marczak wrote:
> This patch introduces new feature: initialization of the dfu
> bootloader entity from a separate environmental variable which
> can be set on a boot time.
> 
> By default, DFU always check environmental variable: $dfu_alt_info.
> 
> Changes:
> - DFU will also look for environmental variable: $dfu_alt_bootloader
> - if any of dfu_alt_* variable is properly defined, then function
>   dfu_init_env_entities() will return success.
> 
> Use case:
> Some devices can boot from various media type (SD, eMMC, NAND, etc.)
> or some board configs are common for more than one board type.
> In a such case, bootloader is probably placed on a different
> devices or even offsets. So such DFU feature is welcome.

Why should the "dfu" command look at different environment variables?
Whatever code dynamically sets the value of $dfu_alt_bootloader should
simply set $dfu_alt_info instead.