Searched hist:eda0ba38a8dfd2572089bd229a027d497c340158 (Results 1 – 3 of 3) sorted by relevance
/openbmc/u-boot/drivers/bootcount/ |
H A D | bootcount_env.c | eda0ba38a8dfd2572089bd229a027d497c340158 Mon Nov 04 07:04:59 CST 2013 Heiko Schocher <hs@denx.de> bootcount: store bootcount var in environment
If no softreset save registers are found on the hardware "bootcount" is stored in the environment. To prevent a saveenv on all reboots, the environment variable "upgrade_available" is introduced. If "upgrade_available" is 0, "bootcount" is always 0 therefore no need to save the environment on u-boot boot, if "upgrade_available" is 1 "bootcount" is incremented in the environment and environment gets written on u-boot start. So the Userspace Applikation must set the "upgrade_available" and "bootcount" variable to 0 (for example with fw_setenv), if a boot was successfully.
Signed-off-by: Heiko Schocher <hs@denx.de>
|
H A D | Makefile | eda0ba38a8dfd2572089bd229a027d497c340158 Mon Nov 04 07:04:59 CST 2013 Heiko Schocher <hs@denx.de> bootcount: store bootcount var in environment
If no softreset save registers are found on the hardware "bootcount" is stored in the environment. To prevent a saveenv on all reboots, the environment variable "upgrade_available" is introduced. If "upgrade_available" is 0, "bootcount" is always 0 therefore no need to save the environment on u-boot boot, if "upgrade_available" is 1 "bootcount" is incremented in the environment and environment gets written on u-boot start. So the Userspace Applikation must set the "upgrade_available" and "bootcount" variable to 0 (for example with fw_setenv), if a boot was successfully.
Signed-off-by: Heiko Schocher <hs@denx.de>
|
/openbmc/u-boot/ |
H A D | README | eda0ba38a8dfd2572089bd229a027d497c340158 Mon Nov 04 07:04:59 CST 2013 Heiko Schocher <hs@denx.de> bootcount: store bootcount var in environment
If no softreset save registers are found on the hardware "bootcount" is stored in the environment. To prevent a saveenv on all reboots, the environment variable "upgrade_available" is introduced. If "upgrade_available" is 0, "bootcount" is always 0 therefore no need to save the environment on u-boot boot, if "upgrade_available" is 1 "bootcount" is incremented in the environment and environment gets written on u-boot start. So the Userspace Applikation must set the "upgrade_available" and "bootcount" variable to 0 (for example with fw_setenv), if a boot was successfully.
Signed-off-by: Heiko Schocher <hs@denx.de>
|