diff options
author | Sven Eckelmann <sven.eckelmann@open-mesh.com> | 2016-05-17 17:51:34 +0200 |
---|---|---|
committer | Felix Fietkau <nbd@nbd.name> | 2016-05-23 12:19:22 +0200 |
commit | 6150c15ad109e49958cb393915679afa1bf12368 (patch) | |
tree | 0371e22df6ed848c2c629b63673b1375cf3965df | |
parent | 9b6b75d09df0013bb6b6fc967f6aa7a833fa262a (diff) | |
download | mtk-20170518-6150c15ad109e49958cb393915679afa1bf12368.zip mtk-20170518-6150c15ad109e49958cb393915679afa1bf12368.tar.gz mtk-20170518-6150c15ad109e49958cb393915679afa1bf12368.tar.bz2 |
ar71xx: Generate sysupgrade images for OpenMesh devices
Some OpenWrt based firmwares like Gluon expect that a sysupgrade image
exists when a device firmware can be updated via sysupgrade. This image
wasn't created until now because OpenMesh devices use the same image for
factory and sysupgrade flash. Copying the image from *factory.bin to
*sysupgrade.bin is therefore enough to make the sysupgrade functionality
visible.
Reported-by: Matthias Schiffer <mschiffer@universe-factory.net>
Signed-off-by: Sven Eckelmann <sven.eckelmann@open-mesh.com>
-rw-r--r-- | target/linux/ar71xx/image/legacy.mk | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/target/linux/ar71xx/image/legacy.mk b/target/linux/ar71xx/image/legacy.mk index bbaf684..78b7883 100644 --- a/target/linux/ar71xx/image/legacy.mk +++ b/target/linux/ar71xx/image/legacy.mk @@ -919,6 +919,9 @@ define Image/Build/OpenMesh "$(BUILD_DIR)/fwupgrade.cfg-$(4)" "fwupgrade.cfg" \ "$(KDIR_TMP)/vmlinux-$(2).uImage" "kernel" \ "$(KDIR)/root.$(1)" "rootfs" + if [ -e "$(call factoryname,$(1),$(2))" ]; then \ + cp "$(call factoryname,$(1),$(2))" "$(call sysupname,$(1),$(2))"; \ + fi endef |