summaryrefslogtreecommitdiffstats
path: root/arch
diff options
context:
space:
mode:
authorPaul Kocialkowski <contact@paulk.fr>2016-03-29 14:16:26 +0200
committerTom Rini <trini@konsulko.com>2016-04-01 17:18:06 -0400
commit523849a0887c2d400d379eb0bce5ec74fc7a4dcd (patch)
treeb997c0b16ea42889684a6e1281dcf9ea4fd04d1e /arch
parentc15ab5be8ff3d07b1afafac9f1e79b3e37ab8624 (diff)
downloadtalos-obmc-uboot-523849a0887c2d400d379eb0bce5ec74fc7a4dcd.tar.gz
talos-obmc-uboot-523849a0887c2d400d379eb0bce5ec74fc7a4dcd.zip
kc1: Proper reboot mode and boot reason validation
With the previous implementation, rebooting without registering a recognized reboot mode would end up with U-Boot checking for a valid power-on reason, which might result in the device turning off (e.g. with no USB cable attached and no buttons pressed). Since this approach is not viable (breaks reboot in most cases), the validity of the reboot reason is checked (in turn, by checking that a warm reset happened, as there is no magic) to detect a reboot and the 'o' char is recognized to indicate that power-off is required. Still, that might be overridden by the detection of usual power-on reasons, on purpose. Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud