aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ramips/image/rt305x.mk
diff options
context:
space:
mode:
authorSven Eckelmann <sven@narfation.org>2022-01-31 14:39:52 +0100
committerHauke Mehrtens <hauke@hauke-m.de>2022-02-03 22:27:15 +0100
commit7c3efd5273fde3ec53d7f80670963e16512c6f17 (patch)
tree5e97d0450882052a1dcdc07a0042ae477c0caf31 /target/linux/ramips/image/rt305x.mk
parentd16bd89c71da6bad5f4d37008217ced3bac4e5d6 (diff)
downloadupstream-7c3efd5273fde3ec53d7f80670963e16512c6f17.tar.gz
upstream-7c3efd5273fde3ec53d7f80670963e16512c6f17.tar.bz2
upstream-7c3efd5273fde3ec53d7f80670963e16512c6f17.zip
ramips: Switch Teltonika RUT5xx to kernel GPIO-line watchdog driver
The commit 04e91631e050 ("om-watchdog: add support for Teltonika RUT5xx (ramips)") used the deprecated om-watchdog daemon to handle the GPIO-line connected watchdog on the Teltonika RUT5xx. But this daemon has massive problems since commit 30f61a34b4cf ("base-files: always use staged sysupgrade"). The process will always be stopped on sysupgrades. If the sysupgrade takes slightly longer, the watchdog is not triggered at the correct time and thus the sysupgrade will interrupted hard by the watchdog sysupgrade. And this hard interrupt can easily brick the device when there is no fallback (dual-boot, ...). Signed-off-by: Sven Eckelmann <sven@narfation.org>
Diffstat (limited to 'target/linux/ramips/image/rt305x.mk')
-rw-r--r--target/linux/ramips/image/rt305x.mk1
1 files changed, 0 insertions, 1 deletions
diff --git a/target/linux/ramips/image/rt305x.mk b/target/linux/ramips/image/rt305x.mk
index e817c12e76..d8ea1d5673 100644
--- a/target/linux/ramips/image/rt305x.mk
+++ b/target/linux/ramips/image/rt305x.mk
@@ -990,7 +990,6 @@ define Device/teltonika_rut5xx
IMAGE_SIZE := 16064k
DEVICE_VENDOR := Teltonika
DEVICE_MODEL := RUT5XX
- DEVICE_PACKAGES := om-watchdog
SUPPORTED_DEVICES += rut5xx
endef
TARGET_DEVICES += teltonika_rut5xx