aboutsummaryrefslogtreecommitdiffstats
path: root/tools/include
diff options
context:
space:
mode:
authorChristian Lamparter <chunkeey@gmail.com>2018-12-30 20:46:06 +0100
committerChristian Lamparter <chunkeey@gmail.com>2019-01-01 18:54:14 +0100
commit8a9b0b95df7d96bc51d6e4731264add11f72925d (patch)
tree8e60727070b02265b2ca60cd6511303e549b5340 /tools/include
parentafcdf099b7cc505acf9497a3dbccf4e6bdc29c27 (diff)
downloadupstream-8a9b0b95df7d96bc51d6e4731264add11f72925d.tar.gz
upstream-8a9b0b95df7d96bc51d6e4731264add11f72925d.tar.bz2
upstream-8a9b0b95df7d96bc51d6e4731264add11f72925d.zip
apm821xx: switch MX60(W)'s recovery images to multi-image method
In the past, the MX60(W)'s recovery images always had problems with the size restriction and never really worked without manual intervention. This patch reworks the initramfs, which allows the device to ease up on the impossible tight kernel size requirements for the initramfs image. This new initramfs can be loaded through the MX60(W) U-boot in the following way: => setenv bootargs console=ttyS0,$baudrate => tftpboot $meraki_loadaddr meraki_mx60-initramfs-kernel.bin [...] Load address: 0x800000 Loading: ################################################ [...] done [...] => bootm $fileaddr \## Booting kernel from Legacy Image at 00800000 ... ... For more information and the latest flashing guide: please visit the OpenWrt Wiki Page for the MX60(W): <https://openwrt.org/toh/meraki/mx60#flashing> Signed-off-by: Chris Blake <chrisrblake93@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (cherry picked from commit 36c19c9f0be23ad327085aa762e95de638e19b4a)
Diffstat (limited to 'tools/include')
0 files changed, 0 insertions, 0 deletions