aboutsummaryrefslogtreecommitdiffstats
path: root/toolchain/fortify-headers
diff options
context:
space:
mode:
authorFreddy Leitner <hello@square.wf>2018-11-26 19:14:19 +0100
committerMathias Kresin <dev@kresin.me>2018-11-26 21:30:31 +0100
commit9671a2d2c8f91db78f0d4e084422743c9f66d38c (patch)
treef8bdd1f0386e1b7e82340bf9a68cb4cd67ce7d40 /toolchain/fortify-headers
parent26ebcc88e3de61cbfb7fc2845b617c5b3a73cac8 (diff)
downloadupstream-9671a2d2c8f91db78f0d4e084422743c9f66d38c.tar.gz
upstream-9671a2d2c8f91db78f0d4e084422743c9f66d38c.tar.bz2
upstream-9671a2d2c8f91db78f0d4e084422743c9f66d38c.zip
apm821xx: MBL: load kernel/dtb from SATA 0:1 first
This remedies an issue with the MBL Duo if both disks are inserted and contain OpenWrt. kernel and dtb would be loaded from SATA 1:1 while rootfs (/dev/sda2) would be mounted on SATA 0:1. Such a mix&match would obviously only work if both OpenWrt versions/ builds are identical, and especially fail after sysupgrade upgraded the system disk on SATA 0:1. The fallback to SATA 1:1 needs to be kept for MBL Single (only has SATA 1:1) and MBL Duo with one disk inserted on SATA 1:1. To speed up booting in those cases, the unneccesarily doubled "sata init" will only be called once. (In theory it could be omitted completely since the on-flash boot script already initializes SATA to load the on-disk boot script.) Tested on MBL Duo (all possible combination of disks) and MBL Single Signed-off-by: Freddy Leitner <hello@square.wf> Acked-by: Christian Lamparter <chunkeey@gmail.com>
Diffstat (limited to 'toolchain/fortify-headers')
0 files changed, 0 insertions, 0 deletions