From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Warren <swarren@wwwdotorg.org>
Date: Thu, 19 Mar 2015 13:53:14 -0600
Subject: [U-Boot] [PATCH] Document config_distro_bootcmd environment
 variables for interactive booting.
In-Reply-To: <1426794079-8931-2-git-send-email-merker@debian.org>
References: <20150317161630.GH32541@bill-the-cat>
 <1426794079-8931-1-git-send-email-merker@debian.org>
 <1426794079-8931-2-git-send-email-merker@debian.org>
Message-ID: <550B292A.7080901@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 03/19/2015 01:41 PM, Karsten Merker wrote:

A brief description would be nice.

> diff --git a/doc/README.distro b/doc/README.distro

> +Interactively booting from a specific device at the u-boot prompt
> +=================================================================
> +
> +For interactively booting from a user-selected device at the u-boot command
> +prompt, the environment provides predefined bootcmd_<target> variables for
> +every target defined in boot_targets, which can be run be the user.
> +
> +Examples:
> +
> + - run bootcmd_usb0
> +   boots from the first USB mass storage device
> +
> + - run bootcmd_mmc1
> +   boots from the second MMC device

Should we enumerate all the possible device types, e.g. include 
bootcmd_sata0, bootcmd_ide0, ...?

We should definitely mention that bootcmd_usb is an internal 
implementation detail even though bootcmd_usb0 is a command that we 
intend users to run. In the text, perhaps rephrase bootcmd_<target> as 
bootcmd_<devtype><devnum>, and note that <devnum> is not optional in the 
command name?