2
0
Fork 0
mirror of https://github.com/AsahiLinux/u-boot synced 2024-12-27 21:43:45 +00:00
u-boot/board/keymile
Tom Rini 7f3092d713 Convert CONFIG_KM_COGE5UN et al to Kconfig
This converts the following to Kconfig:
   CONFIG_KM_COGE5UN
   CONFIG_KM_KIRKWOOD_128M16
   CONFIG_KM_KIRKWOOD
   CONFIG_KM_KIRKWOOD_PCI
   CONFIG_KM_NUSA
   CONFIG_KM_SUSE2

Cc: Holger Brunck <holger.brunck@hitachienergy.com>
Signed-off-by: Tom Rini <trini@konsulko.com>
Reviewed-by: Holger Brunck <holger.brunck@hitachienergy.com>
2022-04-01 10:28:46 -04:00
..
common kmtegr1: Drop CONFIG_KMTEGR1 2022-04-01 10:28:46 -04:00
km83xx board/km: update MAINTAINERS files 2021-10-14 19:45:07 -04:00
km_arm Convert CONFIG_KM_COGE5UN et al to Kconfig 2022-04-01 10:28:46 -04:00
kmcent2 event: Convert misc_init_f() to use events 2022-03-10 08:28:36 -05:00
pg-wcom-ls102xa event: Convert misc_init_f() to use events 2022-03-10 08:28:36 -05:00
scripts km/scripts: fix saveenv command syntax 2021-06-17 11:46:11 +05:30
secu1 board/km: update MAINTAINERS files 2021-10-14 19:45:07 -04:00
Kconfig km: common: implement field fail-safe u-boot update 2022-02-01 15:08:07 +05:30
README km: common: implement field fail-safe u-boot update 2022-02-01 15:08:07 +05:30

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Field Fail-Save U-boot Update
-----------------------------
Field Fail-Save u-boot update is a feature that allows save u-boot update
of FOX and XMC products that are rolled out in the field.

The feature is initially implemented for designs based on LS102x SoC, but in
theory can be used on all designs that are booting from parallel NOR flash.

The implementation expects redundant (secondary) u-boot image on a predefined
location in the NOR flash, u-boot execution will be transferred to the redundant 
(secondary) u-boot and redundant u-boot will be started if 'updateduboot' envvar
is set to 'yes'.
Update logic check_for_uboot_update() has to be invoked from the design early
before relocation just after SoC initialization, e.g from board_early_init_f or
misc_init_f functions.
By design it is expected that primary u-boot image is burned in the factory and
never updated, and in case u-boot update is required it can flashed and started
from secondary u-boot location.