diff options
author | Bernhard Nortmann <bernhard.nortmann@web.de> | 2015-09-17 18:52:53 +0200 |
---|---|---|
committer | Hans de Goede <hdegoede@redhat.com> | 2015-09-29 11:50:07 +0200 |
commit | f3b589c09b43a231706f11ab391e5ea7f9670f12 (patch) | |
tree | 31e5abb3dfaff721eadd1377e44b78b309b31805 /arch/arm/Kconfig | |
parent | af654d14613f22f4910601d86e584030ee392b94 (diff) | |
download | u-boot-imx-f3b589c09b43a231706f11ab391e5ea7f9670f12.zip u-boot-imx-f3b589c09b43a231706f11ab391e5ea7f9670f12.tar.gz u-boot-imx-f3b589c09b43a231706f11ab391e5ea7f9670f12.tar.bz2 |
sunxi: add "fel" boot target
This patch makes use of the previous changes to add a new "fel" boot
target for sunxi boards.
When booting via FEL, it's often desirable to work around the absence
of other (usable) boot devices - or to be able to override them,
deviating from the standard boot sequence. To achieve this, the "fel"
boot target gets the highest priority, but won't actually do anything
unless certain criteria are met.
The "bootcmd_fel" implementation proposed here first tests if an actual
FEL boot takes place (using the "fel_booted" env var), and secondly
checks that "fel_scriptaddr" was set (originating from the 'loader',
i.e. the sunxi-tools fel utility). If both checks pass, then it will
try to execute the boot script (boot.scr) at the given address. In case
of an error (e.g. an invalid image), the source command might return
"false", causing "distro_bootcmd" to proceed with the next boot target.
Signed-off-by: Bernhard Nortmann <bernhard.nortmann@web.de>
Acked-by: Siarhei Siamashka <siarhei.siamashka@gmail.com>
Acked-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Diffstat (limited to 'arch/arm/Kconfig')
0 files changed, 0 insertions, 0 deletions