On Wed, 2015-01-07 at 13:22 -0700, Stephen Warren wrote:
On 01/07/2015 04:17 AM, Ian Campbell wrote:
On Wed, 2015-01-07 at 12:01 +0100, Sjoerd Simons wrote:
On Wed, 2015-01-07 at 10:22 +0000, Ian Campbell wrote:
This is about the default setup though, it would be really nice to get consistent behaviour. I would be inclined to say that the defaults should conservatively try the internal/main storage first (assuming there will be an OS is installed there) and only fallback to other options later.
I'm inclined the other way, which is to boot of a removable media first if someone has gone to the effort to plug one in. People building kiosks etc who want to lock it down to internal only can still do so.
Yes, I agree. This means that if you already have a (perhaps broken or old) distro installed on the internal media, you can place boot media into the external slot and boot that without having to fiddle with modifying the boot configuration variables. If that behaviour isn't what a particular user wants, they can just edit $boot_targets.
Each platform can make their own decision if they want though; the order of entries in BOOT_TARGET_DEVICES (part of the U-Boot config header file) determines the default order of entries in $boot_targets.
Fair enough. One thing i would like to mention though that respective of the preference here, It would be nice to have some guidelines here.
One thing which always irks me is that for every new ARM i get on my desk, I need to re-discover how this particular one happens to boot.. The distro bootcmd stuff goes a very long way here, but would be even nicer if the sequence was predictable as well (e.g. always external, internal, network boots unless the board has a boot selector switch). (One can wish right :p)