aboutsummaryrefslogtreecommitdiffstats
path: root/package/network
diff options
context:
space:
mode:
authorFreddy Leitner <hello@square.wf>2018-08-28 20:47:58 +0200
committerMathias Kresin <dev@kresin.me>2018-08-29 09:43:10 +0200
commit7aa5dc46ee79c095e53f2b8e19c640cee8a58e0f (patch)
tree386e35c7fdd6b6c489f392fd2e7f9fc3da5708de /package/network
parentc134210b8f7e18b43641b6c2176e7a3e6baed030 (diff)
downloadupstream-7aa5dc46ee79c095e53f2b8e19c640cee8a58e0f.tar.gz
upstream-7aa5dc46ee79c095e53f2b8e19c640cee8a58e0f.tar.bz2
upstream-7aa5dc46ee79c095e53f2b8e19c640cee8a58e0f.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 Acked-by: Christian Lamparter <chunkeey@gmail.com> Signed-off-by: Freddy Leitner <hello@square.wf>
Diffstat (limited to 'package/network')
0 files changed, 0 insertions, 0 deletions