aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
diff options
context:
space:
mode:
authorAndreas Böhler <dev@aboehler.at>2023-04-02 10:40:47 +0200
committerChristian Lamparter <chunkeey@gmail.com>2023-06-03 21:14:37 +0200
commit46b51e9e992884c81f4838440cd2967e67db3a79 (patch)
tree1c4c2341212f0de37a2b9a27de6bd5f4434f3fb0 /target/linux
parent21f713d5abf86fc5639b41d7f4e7535a5538d63a (diff)
downloadupstream-46b51e9e992884c81f4838440cd2967e67db3a79.tar.gz
upstream-46b51e9e992884c81f4838440cd2967e67db3a79.tar.bz2
upstream-46b51e9e992884c81f4838440cd2967e67db3a79.zip
ramips: tplink,mr600v2: fix image generation for sysupgrade image
The MR600v2 does not find its rootfs if it is neither directly after the kernel or aligned to an erase block boundary (64k). This aligns the rootfs to 0x10000 allowing the device to boot again. Based on investigation by forum user relghuar. Signed-off-by: Andreas Böhler <dev@aboehler.at>
Diffstat (limited to 'target/linux')
-rw-r--r--target/linux/ramips/image/mt7621.mk3
1 files changed, 3 insertions, 0 deletions
diff --git a/target/linux/ramips/image/mt7621.mk b/target/linux/ramips/image/mt7621.mk
index 2697f84bf76..9dbcf09eb2b 100644
--- a/target/linux/ramips/image/mt7621.mk
+++ b/target/linux/ramips/image/mt7621.mk
@@ -2158,6 +2158,9 @@ define Device/tplink_mr600-v2-eu
TPLINK_FLASHLAYOUT := 16Mltq
DEVICE_PACKAGES := kmod-mt7603 kmod-mt7615e kmod-mt7663-firmware-ap \
kmod-usb-net-qmi-wwan uqmi kmod-usb3 -uboot-envtools
+ IMAGE/factory.bin := tplink-v2-image -e -a 0x10000
+ IMAGE/sysupgrade.bin := tplink-v2-image -s -e -a 0x10000 | check-size | \
+ append-metadata
KERNEL := $(KERNEL_DTB) | uImage lzma
KERNEL_INITRAMFS := $$(KERNEL) | tplink-v2-header
TPLINK_BOARD_ID := MR600-V2-EU