diff options
author | Jeff Kletsky <git-commits@allycomm.com> | 2019-04-10 08:28:01 -0700 |
---|---|---|
committer | Christian Lamparter <chunkeey@gmail.com> | 2019-05-18 13:43:51 +0200 |
commit | b3770eaca39f223faecfcc0d169a1bb2f6f9464a (patch) | |
tree | 4697e1277e06775e1fdf0e36aadbe1f636b22806 /target/linux/mvebu/base-files/etc/init.d/linksys_recovery | |
parent | 4bdc873a5fda60557478a4294983cf71e7eccea6 (diff) | |
download | upstream-b3770eaca39f223faecfcc0d169a1bb2f6f9464a.tar.gz upstream-b3770eaca39f223faecfcc0d169a1bb2f6f9464a.tar.bz2 upstream-b3770eaca39f223faecfcc0d169a1bb2f6f9464a.zip |
mtd: base-files: Unify dual-firmware devices (Linksys)
Consistently handle boot-count reset and upgrade across
ipq40xx, ipq806x, kirkwood, mvebu
Dual-firmware devices often utilize a specific MTD partition
to record the number of times the boot loader has initiated boot.
Most of these devices are NAND, typically with a 2k erase size.
When this code was ported to the ipq40xx platform, the device in hand
used NOR for this partition, with a 16-byte "record" size. As the
implementation of `mtd resetbc` is by-platform, the hard-coded nature
of this change prevented proper operation of a NAND-based device.
* Unified the "NOR" variant with the rest of the Linksys variants
* Added logging to indicate success and failure
* Provided a meaningful return value for scripting
* "Protected" the use of `mtd resetbc` in start-up scripts so that
failure does not end the boot sequence
* Moved Linksys-specific actions into common `/etc/init.d/bootcount`
For upgrade, these devices need to determine which partition to flash,
as well as set certain U-Boot envirnment variables to change the next
boot to the newly flashed version.
* Moved upgrade-related environment changes out of bootcount
* Combined multiple flashes of environment into single one
* Current-partition detection now handles absence of `boot_part`
Runtime-tested: Linksys EA8300
Signed-off-by: Jeff Kletsky <git-commits@allycomm.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
[checkpatch.pl fixes, traded split strings for 80+ chars per line]
Diffstat (limited to 'target/linux/mvebu/base-files/etc/init.d/linksys_recovery')
-rwxr-xr-x | target/linux/mvebu/base-files/etc/init.d/linksys_recovery | 20 |
1 files changed, 0 insertions, 20 deletions
diff --git a/target/linux/mvebu/base-files/etc/init.d/linksys_recovery b/target/linux/mvebu/base-files/etc/init.d/linksys_recovery deleted file mode 100755 index b4f375ec99..0000000000 --- a/target/linux/mvebu/base-files/etc/init.d/linksys_recovery +++ /dev/null @@ -1,20 +0,0 @@ -#!/bin/sh /etc/rc.common -# Copyright (C) 2015-2016 OpenWrt.org -# Copyright (C) 2016 LEDE-Project.org - -START=97 -boot() { -. /lib/functions.sh - -case $(board_name) in - linksys,caiman|linksys,cobra|linksys,mamba|linksys,rango|linksys,shelby|linksys,venom) - # make sure auto_recovery in uboot is always on - AUTO_RECOVERY_ENA="`fw_printenv -n auto_recovery`" - if [ "$AUTO_RECOVERY_ENA" != "yes" ] ; then - fw_setenv auto_recovery yes - fi - # reset the boot counter - mtd resetbc s_env - ;; -esac -} |