aboutsummaryrefslogtreecommitdiffstats
path: root/package/utils/ct-bugcheck/Makefile
diff options
context:
space:
mode:
authorFreddy Leitner <hello@square.wf>2018-11-26 19:14:19 +0100
committerChristian Lamparter <chunkeey@gmail.com>2018-12-27 16:40:07 +0100
commit459a40fce253a38437b9c63b4048a73704cc3b77 (patch)
treef1fc8a39ae76ee9328a909a10db87da1ecdedff6 /package/utils/ct-bugcheck/Makefile
parent202c3ceb13032b9fcb6eb2b87286a0ff7197a5de (diff)
downloadupstream-459a40fce253a38437b9c63b4048a73704cc3b77.tar.gz
upstream-459a40fce253a38437b9c63b4048a73704cc3b77.tar.bz2
upstream-459a40fce253a38437b9c63b4048a73704cc3b77.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>
Diffstat (limited to 'package/utils/ct-bugcheck/Makefile')
0 files changed, 0 insertions, 0 deletions