aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ramips/image/rt305x.mk
diff options
context:
space:
mode:
authorSzabolcs Hubai <szab.hu@gmail.com>2020-12-15 01:46:54 +0100
committerAdrian Schmutzler <freifunk@adrianschmutzler.de>2021-02-07 22:06:57 +0100
commit1e9afcca56190e7f9d9b7b1e2b7fcb007243f5b0 (patch)
tree2d8a508d717a648717d5aa13512ece392329c1ed /target/linux/ramips/image/rt305x.mk
parent1c0e13db43b41a1d527428b82bf88a032a916e84 (diff)
downloadupstream-1e9afcca56190e7f9d9b7b1e2b7fcb007243f5b0.tar.gz
upstream-1e9afcca56190e7f9d9b7b1e2b7fcb007243f5b0.tar.bz2
upstream-1e9afcca56190e7f9d9b7b1e2b7fcb007243f5b0.zip
ramips: disable default build for HooToo HT-TM02
While the latest version of 19.07 release is usable, the current master is unbootable on the device in a normal way. "Normal way" installations includes: - sysupgrade (e.g. from 19.07) - RESET button recovery with Ron Curry's (Wingspinner) UBoot image (10.10.10.3 + "Kernal.bin") - RESET button recovery with original U-Boot (10.10.10.254 + "kernel") One could flash and boot the latest master sysupgrade image successfully with serial access to the device. But a sysupgrade from this state still breaks the U-Boot and soft-bricks the device. Signed-off-by: Szabolcs Hubai <szab.hu@gmail.com>
Diffstat (limited to 'target/linux/ramips/image/rt305x.mk')
-rw-r--r--target/linux/ramips/image/rt305x.mk1
1 files changed, 1 insertions, 0 deletions
diff --git a/target/linux/ramips/image/rt305x.mk b/target/linux/ramips/image/rt305x.mk
index 7730b5aaa9..429afc7833 100644
--- a/target/linux/ramips/image/rt305x.mk
+++ b/target/linux/ramips/image/rt305x.mk
@@ -601,6 +601,7 @@ define Device/hootoo_ht-tm02
DEVICE_MODEL := HT-TM02
DEVICE_PACKAGES := kmod-usb-ohci kmod-usb2 kmod-usb-ledtrig-usbport
SUPPORTED_DEVICES += ht-tm02
+ DEFAULT := n
endef
TARGET_DEVICES += hootoo_ht-tm02