diff options
author | Piotr Dymacz <pepe2k@gmail.com> | 2019-10-29 23:25:56 +0100 |
---|---|---|
committer | Piotr Dymacz <pepe2k@gmail.com> | 2019-11-24 21:44:29 +0100 |
commit | 7a62e909b286250e310a649a4cbe11d65f802f78 (patch) | |
tree | be432bb8c24bbe3708cee5e560cd422ab2a33cd2 /target/linux/rb532 | |
parent | ee71837e38571ac0d4becc396f5d87039e09daf9 (diff) | |
download | upstream-7a62e909b286250e310a649a4cbe11d65f802f78.tar.gz upstream-7a62e909b286250e310a649a4cbe11d65f802f78.tar.bz2 upstream-7a62e909b286250e310a649a4cbe11d65f802f78.zip |
ramips: support dual image feature on ALFA Network boards
New U-Boot version for MediaTek MT76x8/MT762x based ALFA Network boards
includes support for a 'dual image' feature. Users can enable it using
U-Boot environment variable 'dual_image' ('1' -> enabled).
When 'dual image' feature is enabled, U-Boot will modify DTB and divide
the original 'firmware' flash area into two, equal in size and aligned
to 64 KB partitions: 'firmware' and 'backup'. U-Boot will also adjust
size of 'firmware' area to match installed flash chip size.
U-Boot will load kernel from active partition which is marked with env
variable 'bootactive' ('1' -> first partition, '2' -> second partition)
and rename both partitions accordingly ('firmware' <-> 'backup').
There are 3 additional env variables used to control 'dual image' mode:
- bootlimit - maximum number of unsuccessful boot tries (default: '3')
- bootcount - current number of boot tries
- bootchanged - flag which informs that active partition was changed; if
it is set and 'bootcount' reaches 'bootlimit' value,
U-Boot will start web-based recovery which then updates
both partitions with provided image
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
(backported from commit bc173ddd8381b03dde8cc2e6c66d0cd392c62bbd)
Diffstat (limited to 'target/linux/rb532')
0 files changed, 0 insertions, 0 deletions