aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorThomas Schröder <tschroeder_github@outlook.com>2024-01-10 11:12:10 +0100
committerChristian Marangi <ansuelsmth@gmail.com>2024-01-15 17:21:29 +0100
commit4d7bac1dcaae019fb4992bfb74348ef12c02daa4 (patch)
treeeee1698e6ffa26a433be665bd09efacb7a34707e
parentfb45194305e6bf9b58f610c1528769320879c749 (diff)
downloadupstream-4d7bac1dcaae019fb4992bfb74348ef12c02daa4.tar.gz
upstream-4d7bac1dcaae019fb4992bfb74348ef12c02daa4.tar.bz2
upstream-4d7bac1dcaae019fb4992bfb74348ef12c02daa4.zip
mediatek: GL-MT6000: Change LED colors
Fine tuning PR: openwrt/openwrt#14355 Ref: 5a82bb909bf1 ("mediatek: GL-MT6000: Add missing LED state definitions") As the only LED is using white in the stock firmware when the device is running and blue for the bootloader I suggest following changes: - Using blue for the BL and preinit+failsafe - White for normal operation (like the original FW) and sysupgrade With this changes it's clear by looking to the LED in which operation mode the device is and a possible BL stuck can be seen easily. Tested with [GL-MT6000](https://openwrt.org/toh/gl.inet/gl-mt6000). Signed-off-by: Thomas Schröder <tschroeder_github@outlook.com> Tested-by: Hannu Nyman <hannu.nyman@iki.fi>
-rw-r--r--target/linux/mediatek/dts/mt7986a-glinet-gl-mt6000.dts6
1 files changed, 3 insertions, 3 deletions
diff --git a/target/linux/mediatek/dts/mt7986a-glinet-gl-mt6000.dts b/target/linux/mediatek/dts/mt7986a-glinet-gl-mt6000.dts
index 9a7031df539..26996e7b4a5 100644
--- a/target/linux/mediatek/dts/mt7986a-glinet-gl-mt6000.dts
+++ b/target/linux/mediatek/dts/mt7986a-glinet-gl-mt6000.dts
@@ -13,9 +13,9 @@
aliases {
serial0 = &uart0;
- led-boot = &led_white;
- led-failsafe = &led_white;
- led-running = &led_blue;
+ led-boot = &led_blue;
+ led-failsafe = &led_blue;
+ led-running = &led_white;
led-upgrade = &led_white;
};