ExternalVendorCode/openwrt
1
0
Fork 0
mirror of https://github.com/openwrt/openwrt.git synced 2024-12-27 17:18:59 +00:00
Code Issues Actions 9 Packages Projects Releases Wiki Activity
4e1e18af65
openwrt/target/linux/bcm63xx/base-files/etc/board.d/01_leds

108 lines
3.2 KiB
Plaintext
Raw Normal View History

brcm63xx: Add userspace support for Sagemcom F@ST2704V2 ADSL router This adds userspace support for Sagemcom F@st 2704 router. Signed-off-by: Marcin Jurkowski <marcin1j@gmail.com> Patchwork: http://patchwork.openwrt.org/patch/4215/ Signed-off-by: Jonas Gorski <jogo@openwrt.org> SVN-Revision: 39672
2014-02-22 11:16:33 +00:00
#!/bin/sh
#
brcm63xx: switch from uci-defaults to board.d Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> Acked-by: Jonas Gorski <jogo@openwrt.org> SVN-Revision: 47754
2015-12-04 12:32:36 +00:00
# Copyright (C) 2013-2015 OpenWrt.org
brcm63xx: Add userspace support for Sagemcom F@ST2704V2 ADSL router This adds userspace support for Sagemcom F@st 2704 router. Signed-off-by: Marcin Jurkowski <marcin1j@gmail.com> Patchwork: http://patchwork.openwrt.org/patch/4215/ Signed-off-by: Jonas Gorski <jogo@openwrt.org> SVN-Revision: 39672
2014-02-22 11:16:33 +00:00
#
all: drop old uci-defaults.sh Replace former uci-defaults.sh implementation with the uci-defaults-new.sh one and update all users accordingly. Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47867
2015-12-11 15:26:06 +00:00
. /lib/functions/uci-defaults.sh
brcm63xx: Add userspace support for Sagemcom F@ST2704V2 ADSL router This adds userspace support for Sagemcom F@st 2704 router. Signed-off-by: Marcin Jurkowski <marcin1j@gmail.com> Patchwork: http://patchwork.openwrt.org/patch/4215/ Signed-off-by: Jonas Gorski <jogo@openwrt.org> SVN-Revision: 39672
2014-02-22 11:16:33 +00:00
brcm63xx: switch from uci-defaults to board.d Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> Acked-by: Jonas Gorski <jogo@openwrt.org> SVN-Revision: 47754
2015-12-04 12:32:36 +00:00
board_config_update
bcm63xx: use model part of board name as variable in 01_leds This extracts the model part of the board name and uses it for the LED string identifiers in 01_leds. As this makes statements more generic, it will allow to merge more cases in the future. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-05-21 17:41:41 +00:00
board=$(board_name)
case "$board" in
brcm63xx: use compatible instead of manually setting board name This patch removes the translation of device model name into a board name in lib/brcm63xx.sh. The latter has been actually totally useless as we have the compatible which can be used instead of the board name (and actually is at other targets like ath79 or ramips). The change requires updating the base-files with the new identifiers based on compatible. With all "board names" replaced by the compatible, we do not need the old scripts to detect board name anymore and can also remove the obsolete treatment of "legacy" devices without DTS, as there are none of those left. So, this patch removes the target-specific board detection and uses the standard procedure in package/base-files/files/lib/preinit/02_sysinfo This also fixes several cases where the board name was not set or evaluated correctly: - asmax,ar1004g in 02_network - telsey,magic in 09_fix_crc/02_network - brcm,bcm96338gw in 02_network - brcm,bcm96338w in 02_network - brcm,bcm96348gw in 02_network - dynalink,rta1025w in 02_network - huawei,echolife-hg520v in 02_network - several cases in diag.sh The following orphaned identifiers are removed from board.d files: - dmv-s0 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 20:58:34 +00:00
actiontec,r1000h)
bcm63xx: remove model name from LED labels Like in the previous patches for various targets, this will remove the "devicename" from LED labels in bcm63xx, as it's useless and only creates complexity. The devicename is removed in DTS files and 01_leds, merging several cases on the way. A migration script is added for existing configurations. Note that a few labels were using "model::function" scheme without color specified, those were converting to just "function" and the necessary migrations were added to the migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-10-10 17:44:02 +00:00
ucidef_set_led_usbport "usb" "USB" "green:usb" "usb1-port1" "usb2-port1"
brcm63xx: use compatible instead of manually setting board name This patch removes the translation of device model name into a board name in lib/brcm63xx.sh. The latter has been actually totally useless as we have the compatible which can be used instead of the board name (and actually is at other targets like ath79 or ramips). The change requires updating the base-files with the new identifiers based on compatible. With all "board names" replaced by the compatible, we do not need the old scripts to detect board name anymore and can also remove the obsolete treatment of "legacy" devices without DTS, as there are none of those left. So, this patch removes the target-specific board detection and uses the standard procedure in package/base-files/files/lib/preinit/02_sysinfo This also fixes several cases where the board name was not set or evaluated correctly: - asmax,ar1004g in 02_network - telsey,magic in 09_fix_crc/02_network - brcm,bcm96338gw in 02_network - brcm,bcm96338w in 02_network - brcm,bcm96348gw in 02_network - dynalink,rta1025w in 02_network - huawei,echolife-hg520v in 02_network - several cases in diag.sh The following orphaned identifiers are removed from board.d files: - dmv-s0 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 20:58:34 +00:00
;;
bcm63xx: remove model name from LED labels Like in the previous patches for various targets, this will remove the "devicename" from LED labels in bcm63xx, as it's useless and only creates complexity. The devicename is removed in DTS files and 01_leds, merging several cases on the way. A migration script is added for existing configurations. Note that a few labels were using "model::function" scheme without color specified, those were converting to just "function" and the necessary migrations were added to the migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-10-10 17:44:02 +00:00
adb,a4001n|\
bcm63xx: add support for ADB P.DG A4101N A-000-1A1-AE ADB P.DG A4101N A-000-1A1-AE has a similar PCB as the OpenWrt's ADB P.DG A4001N1 with LEDs connected to different GPIO PINs in active low configuration. Hardware: * Board ID: 96328avngv * SoC: Broadcom BCM6328 (rev b0) @ 320MHz, CPU BMIPS4350 * RAM DDR2: 64 Mbyte - Winbond W9751G6KB-25 * Serial flash: 16 Mbyte - Winbond 25Q128BVFG * Ethernet: 4x Ethernet 10/100 baseT * Wifi 2.4GHz: Broadcom Corporation BCM43225 Wireless Network Adapter (rev 23) * LEDs: 1x Power, 1x DSL, 1x Internet, 4x ETH, 1x USB, 1x WLAN, 1x WPS, 1x TEL * Buttons: 1x Reset, 1x WPS, 1x unnamed * UART: 1x TTL 115200n8, VCC RX TX GND, on J502 connector Installation via CFE: * Stock CFE has to be overwritten with a generic 6328 one that can upload .bin images with no signature check (cfe6328_configured.bin) * Connect a serial port to the board * Stop the cfe boot process after power on by pressing enter * Set static IP 192.168.2.10 and subnet mask 255.255.255.0 * Navigate to http://192.168.2.50/ * Upload the OpenWrt image file A4101N GPIO LAYOUT: Power always on DSL GPIO483(03) Internet GPIO491(11) ETH1 GPIO505(25) ETH2 GPIO506(26) ETH3 GPIO507(27) ETH4 GPIO508(28) USB GPIO490(10) WLAN controlled by BCM43225 WPS GPIO489(09) TEL GPIO511(31) Key RESET GPIO503(23) Key WPS GPIO504(24) Key unnamed GPIO492(12) Signed-off-by: Daniele Castro <danielecastro@hotmail.it> [Amend commit description, DTS improvements, refresh patches] Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-09-09 01:21:14 +00:00
adb,pdg-a4101n-a-000-1a1-ae|\
bcm63xx: remove model name from LED labels Like in the previous patches for various targets, this will remove the "devicename" from LED labels in bcm63xx, as it's useless and only creates complexity. The devicename is removed in DTS files and 01_leds, merging several cases on the way. A migration script is added for existing configurations. Note that a few labels were using "model::function" scheme without color specified, those were converting to just "function" and the necessary migrations were added to the migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-10-10 17:44:02 +00:00
comtrend,ar-5315u|\
comtrend,vr-3032u|\
bcm63xx: Add support for D-Link DSL-2750u rev C1 This adds support for the D-Link DSL-2750u rev C1. (https://deviwiki.com/wiki/D-Link_DSL-2750U_rev_C1) It uses the same hardware as ADB P.DG A4001N. CPU: Broadcom BCM63281 (320 MHz) RAM: 32M (Winbond W9725G6JB) Flash: 8M (MXIC MX25L6445E) Ethernet: 4x 100 Mbps Wireless: 802.11b/g/n: BCM43225 USB: 1x 2.0 Flash instructions: 1. Assign static IP 192.168.1.100 to PC 2. Unplug the power source 3. Press the RESET button at the router, don't release it yet! 4. Plug the power source.Wait some seconds 5. Release the RESET button 6. Browse to http://192.168.1.1 7. Send the openwrt-bcm63xx-generic-DSL2750U-C1-squashfs-cfe.bin and wait some minutes until the firmware upgrade finish. Signed-off-by: Ahmed Naseef <naseefkm@gmail.com> [DTS improvements, proper board patch, refresh patches] Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-08-18 12:22:20 +00:00
d-link,dsl-2750u-c1|\
bcm63xx: remove model name from LED labels Like in the previous patches for various targets, this will remove the "devicename" from LED labels in bcm63xx, as it's useless and only creates complexity. The devicename is removed in DTS files and 01_leds, merging several cases on the way. A migration script is added for existing configurations. Note that a few labels were using "model::function" scheme without color specified, those were converting to just "function" and the necessary migrations were added to the migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-10-10 17:44:02 +00:00
huawei,hg253s-v2|\
nucom,r5010un-v2|\
sagem,fast-2704-v2)
ucidef_set_led_usbdev "usb" "USB" "green:usb" "1-1"
brcm63xx: use compatible instead of manually setting board name This patch removes the translation of device model name into a board name in lib/brcm63xx.sh. The latter has been actually totally useless as we have the compatible which can be used instead of the board name (and actually is at other targets like ath79 or ramips). The change requires updating the base-files with the new identifiers based on compatible. With all "board names" replaced by the compatible, we do not need the old scripts to detect board name anymore and can also remove the obsolete treatment of "legacy" devices without DTS, as there are none of those left. So, this patch removes the target-specific board detection and uses the standard procedure in package/base-files/files/lib/preinit/02_sysinfo This also fixes several cases where the board name was not set or evaluated correctly: - asmax,ar1004g in 02_network - telsey,magic in 09_fix_crc/02_network - brcm,bcm96338gw in 02_network - brcm,bcm96338w in 02_network - brcm,bcm96348gw in 02_network - dynalink,rta1025w in 02_network - huawei,echolife-hg520v in 02_network - several cases in diag.sh The following orphaned identifiers are removed from board.d files: - dmv-s0 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 20:58:34 +00:00
;;
adb,a4001n1)
bcm63xx: remove model name from LED labels Like in the previous patches for various targets, this will remove the "devicename" from LED labels in bcm63xx, as it's useless and only creates complexity. The devicename is removed in DTS files and 01_leds, merging several cases on the way. A migration script is added for existing configurations. Note that a few labels were using "model::function" scheme without color specified, those were converting to just "function" and the necessary migrations were added to the migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-10-10 17:44:02 +00:00
ucidef_set_led_netdev "lan" "LAN" "green:eth" "eth0"
ucidef_set_led_usbdev "usb" "USB" "green:3g" "1-1"
brcm63xx: Use model name for ADB P.DG A4001N1 This patch also makes use of the new leds script. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> Signed-off-by: Jonas Gorski <jogo@openwrt.org> SVN-Revision: 41585
2014-07-12 12:31:30 +00:00
;;
bcm63xx: fix ADB P.DG A4001N A-000-1A1-AX LEDs There's no eth0.2 since all ethernet ports as configured as LAN. LAN LED is unneeded since all ethernet ports have their own LED. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-12-06 18:20:04 +00:00
adb,pdg-a4001n-a-000-1a1-ax|\
technicolor,tg582n-telecom-italia)
bcm63xx: remove model name from LED labels Like in the previous patches for various targets, this will remove the "devicename" from LED labels in bcm63xx, as it's useless and only creates complexity. The devicename is removed in DTS files and 01_leds, merging several cases on the way. A migration script is added for existing configurations. Note that a few labels were using "model::function" scheme without color specified, those were converting to just "function" and the necessary migrations were added to the migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-10-10 17:44:02 +00:00
ucidef_set_led_netdev "wlan0" "WIFI" "green:wifi" "wlan0"
brcm63xx: add USB status LED in 01_leds for ADP P.DG A4001N Add a status LED in 01_leds for USB 2-1 connected devices. Signed-off-by: Daniele Castro <danielecastro@hotmail.it>
2020-09-14 01:49:30 +00:00
ucidef_set_led_usbdev "usb1" "USB1" "green:service" "1-1"
ucidef_set_led_usbdev "usb2" "USB2" "red:service" "2-1"
brcm63xx: add support for ADB P.DG A4001N A-000-1A1-AX ADB P.DG A4001N A-000-1A1-AX a.k.a. Telecom Italia ADSL2+ Wi-Fi N (AGPWI) has the same PCB as the OpenWrt's ADB P.DG A4001N1 with LEDs connected to different GPIO PINs in active low configuration. OpenWrt's ADB P.DG A4001N image is made for the ADB P.DG A4001N A-000-1A1-AE. It has different LEDs configuration and flash size/layout w.r.t the ADB P.DG A4001N A-000-1A1-AX. Hardware: * Board ID: 96328avng * SoC: Broadcom BCM6328 * RAM DDR2-800: 32 Mbyte - winbond W9725G6KB-25 * Serial flash: 16 Mbyte - MXIC MX25L 12845EMI-10G * Ethernet: 4x Ethernet 10/100 baseT * Wifi 2.4GHz: Broadcom Corporation BCM43224/5 Wireless Network Adapter (rev 01) * LEDs: 2x Power, 2x ADSL, 2x Internet, 2x Wi-Fi, 2x Service * Buttons: 1x Reset, 1x WPS (named WiFi/LED) * UART: 1x TTL 115200n8, TX NC RX, on J5 connector (short R192 and R193) NC GND NC Installation via CFE: * Stock CFE has to be overwriten with one for 96328avng boards that can upload .bin images with no signature check (cfe-A4001N-V0000_96328avng.bin) * connect a serial port to the board * Stop the boot process after power on by pressing enter * set static IP 192.168.1.2 and subnet mask 255.255.255.0 * navigate to http://192.168.1.1/ * upload the OpenWrt image file Signed-off-by: Daniele Castro <danielecastro@hotmail.it> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2019-12-02 15:13:44 +00:00
;;
brcm63xx: use compatible instead of manually setting board name This patch removes the translation of device model name into a board name in lib/brcm63xx.sh. The latter has been actually totally useless as we have the compatible which can be used instead of the board name (and actually is at other targets like ath79 or ramips). The change requires updating the base-files with the new identifiers based on compatible. With all "board names" replaced by the compatible, we do not need the old scripts to detect board name anymore and can also remove the obsolete treatment of "legacy" devices without DTS, as there are none of those left. So, this patch removes the target-specific board detection and uses the standard procedure in package/base-files/files/lib/preinit/02_sysinfo This also fixes several cases where the board name was not set or evaluated correctly: - asmax,ar1004g in 02_network - telsey,magic in 09_fix_crc/02_network - brcm,bcm96338gw in 02_network - brcm,bcm96338w in 02_network - brcm,bcm96348gw in 02_network - dynalink,rta1025w in 02_network - huawei,echolife-hg520v in 02_network - several cases in diag.sh The following orphaned identifiers are removed from board.d files: - dmv-s0 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 20:58:34 +00:00
adb,av4202n)
bcm63xx: remove model name from LED labels Like in the previous patches for various targets, this will remove the "devicename" from LED labels in bcm63xx, as it's useless and only creates complexity. The devicename is removed in DTS files and 01_leds, merging several cases on the way. A migration script is added for existing configurations. Note that a few labels were using "model::function" scheme without color specified, those were converting to just "function" and the necessary migrations were added to the migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-10-10 17:44:02 +00:00
ucidef_set_led_netdev "wlan0" "WLAN" "blue:wifi" "wlan0"
brcm63xx: Add support for ADB P.DG A4001N Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> Signed-off-by: Jonas Gorski <jogo@openwrt.org> SVN-Revision: 41852
2014-07-27 17:44:59 +00:00
;;
brcm63xx: use compatible instead of manually setting board name This patch removes the translation of device model name into a board name in lib/brcm63xx.sh. The latter has been actually totally useless as we have the compatible which can be used instead of the board name (and actually is at other targets like ath79 or ramips). The change requires updating the base-files with the new identifiers based on compatible. With all "board names" replaced by the compatible, we do not need the old scripts to detect board name anymore and can also remove the obsolete treatment of "legacy" devices without DTS, as there are none of those left. So, this patch removes the target-specific board detection and uses the standard procedure in package/base-files/files/lib/preinit/02_sysinfo This also fixes several cases where the board name was not set or evaluated correctly: - asmax,ar1004g in 02_network - telsey,magic in 09_fix_crc/02_network - brcm,bcm96338gw in 02_network - brcm,bcm96338w in 02_network - brcm,bcm96348gw in 02_network - dynalink,rta1025w in 02_network - huawei,echolife-hg520v in 02_network - several cases in diag.sh The following orphaned identifiers are removed from board.d files: - dmv-s0 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 20:58:34 +00:00
bt,home-hub-2-a)
bcm63xx: remove model name from LED labels Like in the previous patches for various targets, this will remove the "devicename" from LED labels in bcm63xx, as it's useless and only creates complexity. The devicename is removed in DTS files and 01_leds, merging several cases on the way. A migration script is added for existing configurations. Note that a few labels were using "model::function" scheme without color specified, those were converting to just "function" and the necessary migrations were added to the migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-10-10 17:44:02 +00:00
ucidef_set_led_netdev "lan" "LAN" "blue:broadband" "eth0.1"
ucidef_set_led_netdev "wlan0" "WIFI" "green:wireless" "wlan0"
ucidef_set_led_usbdev "usb1" "USB1" "blue:phone" "1-1"
ucidef_set_led_usbdev "usb2" "USB2" "green:phone" "2-1"
bcm63xx: add support for Comtrend VR-3032u Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-14 16:19:35 +00:00
;;
brcm63xx: use compatible instead of manually setting board name This patch removes the translation of device model name into a board name in lib/brcm63xx.sh. The latter has been actually totally useless as we have the compatible which can be used instead of the board name (and actually is at other targets like ath79 or ramips). The change requires updating the base-files with the new identifiers based on compatible. With all "board names" replaced by the compatible, we do not need the old scripts to detect board name anymore and can also remove the obsolete treatment of "legacy" devices without DTS, as there are none of those left. So, this patch removes the target-specific board detection and uses the standard procedure in package/base-files/files/lib/preinit/02_sysinfo This also fixes several cases where the board name was not set or evaluated correctly: - asmax,ar1004g in 02_network - telsey,magic in 09_fix_crc/02_network - brcm,bcm96338gw in 02_network - brcm,bcm96338w in 02_network - brcm,bcm96348gw in 02_network - dynalink,rta1025w in 02_network - huawei,echolife-hg520v in 02_network - several cases in diag.sh The following orphaned identifiers are removed from board.d files: - dmv-s0 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 20:58:34 +00:00
huawei,echolife-hg553)
bcm63xx: remove model name from LED labels Like in the previous patches for various targets, this will remove the "devicename" from LED labels in bcm63xx, as it's useless and only creates complexity. The devicename is removed in DTS files and 01_leds, merging several cases on the way. A migration script is added for existing configurations. Note that a few labels were using "model::function" scheme without color specified, those were converting to just "function" and the necessary migrations were added to the migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-10-10 17:44:02 +00:00
ucidef_set_led_netdev "lan" "LAN" "blue:lan" "eth0"
ucidef_set_led_usbdev "usb1" "USB1" "red:hspa" "1-1"
ucidef_set_led_usbdev "usb2" "USB2" "blue:hspa" "1-2"
brcm63xx: add support for Pirelli/ADB P.DG AV4202N This patch adds support for the ADB P.DG AV4202N aka Pirelli PRG AV4202N. Signed-off-by: Paul Wassi <p.wassi@gmx.at> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2016-12-23 23:24:44 +00:00
;;
brcm63xx: use compatible instead of manually setting board name This patch removes the translation of device model name into a board name in lib/brcm63xx.sh. The latter has been actually totally useless as we have the compatible which can be used instead of the board name (and actually is at other targets like ath79 or ramips). The change requires updating the base-files with the new identifiers based on compatible. With all "board names" replaced by the compatible, we do not need the old scripts to detect board name anymore and can also remove the obsolete treatment of "legacy" devices without DTS, as there are none of those left. So, this patch removes the target-specific board detection and uses the standard procedure in package/base-files/files/lib/preinit/02_sysinfo This also fixes several cases where the board name was not set or evaluated correctly: - asmax,ar1004g in 02_network - telsey,magic in 09_fix_crc/02_network - brcm,bcm96338gw in 02_network - brcm,bcm96338w in 02_network - brcm,bcm96348gw in 02_network - dynalink,rta1025w in 02_network - huawei,echolife-hg520v in 02_network - several cases in diag.sh The following orphaned identifiers are removed from board.d files: - dmv-s0 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 20:58:34 +00:00
huawei,echolife-hg556a-a|\
huawei,echolife-hg556a-b|\
huawei,echolife-hg556a-c)
bcm63xx: remove model name from LED labels Like in the previous patches for various targets, this will remove the "devicename" from LED labels in bcm63xx, as it's useless and only creates complexity. The devicename is removed in DTS files and 01_leds, merging several cases on the way. A migration script is added for existing configurations. Note that a few labels were using "model::function" scheme without color specified, those were converting to just "function" and the necessary migrations were added to the migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-10-10 17:44:02 +00:00
ucidef_set_led_netdev "lan" "LAN" "red:dsl" "eth0"
ucidef_set_led_usbdev "usb" "USB" "red:hspa" "1-2"
brcm63xx: use compatible instead of manually setting board name This patch removes the translation of device model name into a board name in lib/brcm63xx.sh. The latter has been actually totally useless as we have the compatible which can be used instead of the board name (and actually is at other targets like ath79 or ramips). The change requires updating the base-files with the new identifiers based on compatible. With all "board names" replaced by the compatible, we do not need the old scripts to detect board name anymore and can also remove the obsolete treatment of "legacy" devices without DTS, as there are none of those left. So, this patch removes the target-specific board detection and uses the standard procedure in package/base-files/files/lib/preinit/02_sysinfo This also fixes several cases where the board name was not set or evaluated correctly: - asmax,ar1004g in 02_network - telsey,magic in 09_fix_crc/02_network - brcm,bcm96338gw in 02_network - brcm,bcm96338w in 02_network - brcm,bcm96348gw in 02_network - dynalink,rta1025w in 02_network - huawei,echolife-hg520v in 02_network - several cases in diag.sh The following orphaned identifiers are removed from board.d files: - dmv-s0 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 20:58:34 +00:00
;;
bcm63xx: remove model name from LED labels Like in the previous patches for various targets, this will remove the "devicename" from LED labels in bcm63xx, as it's useless and only creates complexity. The devicename is removed in DTS files and 01_leds, merging several cases on the way. A migration script is added for existing configurations. Note that a few labels were using "model::function" scheme without color specified, those were converting to just "function" and the necessary migrations were added to the migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-10-10 17:44:02 +00:00
huawei,echolife-hg622|\
brcm63xx: use compatible instead of manually setting board name This patch removes the translation of device model name into a board name in lib/brcm63xx.sh. The latter has been actually totally useless as we have the compatible which can be used instead of the board name (and actually is at other targets like ath79 or ramips). The change requires updating the base-files with the new identifiers based on compatible. With all "board names" replaced by the compatible, we do not need the old scripts to detect board name anymore and can also remove the obsolete treatment of "legacy" devices without DTS, as there are none of those left. So, this patch removes the target-specific board detection and uses the standard procedure in package/base-files/files/lib/preinit/02_sysinfo This also fixes several cases where the board name was not set or evaluated correctly: - asmax,ar1004g in 02_network - telsey,magic in 09_fix_crc/02_network - brcm,bcm96338gw in 02_network - brcm,bcm96338w in 02_network - brcm,bcm96348gw in 02_network - dynalink,rta1025w in 02_network - huawei,echolife-hg520v in 02_network - several cases in diag.sh The following orphaned identifiers are removed from board.d files: - dmv-s0 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 20:58:34 +00:00
huawei,echolife-hg655b)
bcm63xx: remove model name from LED labels Like in the previous patches for various targets, this will remove the "devicename" from LED labels in bcm63xx, as it's useless and only creates complexity. The devicename is removed in DTS files and 01_leds, merging several cases on the way. A migration script is added for existing configurations. Note that a few labels were using "model::function" scheme without color specified, those were converting to just "function" and the necessary migrations were added to the migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-10-10 17:44:02 +00:00
ucidef_set_led_usbdev "usb" "USB" "green:usb" "1-2"
brcm63xx: use compatible instead of manually setting board name This patch removes the translation of device model name into a board name in lib/brcm63xx.sh. The latter has been actually totally useless as we have the compatible which can be used instead of the board name (and actually is at other targets like ath79 or ramips). The change requires updating the base-files with the new identifiers based on compatible. With all "board names" replaced by the compatible, we do not need the old scripts to detect board name anymore and can also remove the obsolete treatment of "legacy" devices without DTS, as there are none of those left. So, this patch removes the target-specific board detection and uses the standard procedure in package/base-files/files/lib/preinit/02_sysinfo This also fixes several cases where the board name was not set or evaluated correctly: - asmax,ar1004g in 02_network - telsey,magic in 09_fix_crc/02_network - brcm,bcm96338gw in 02_network - brcm,bcm96338w in 02_network - brcm,bcm96348gw in 02_network - dynalink,rta1025w in 02_network - huawei,echolife-hg520v in 02_network - several cases in diag.sh The following orphaned identifiers are removed from board.d files: - dmv-s0 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 20:58:34 +00:00
;;
inventel,livebox-1)
bcm63xx: remove model name from LED labels Like in the previous patches for various targets, this will remove the "devicename" from LED labels in bcm63xx, as it's useless and only creates complexity. The devicename is removed in DTS files and 01_leds, merging several cases on the way. A migration script is added for existing configurations. Note that a few labels were using "model::function" scheme without color specified, those were converting to just "function" and the necessary migrations were added to the migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-10-10 17:44:02 +00:00
ucidef_set_led_netdev "lan" "LAN" "red:traffic" "eth0"
ucidef_set_led_netdev "wan" "WAN" "red:adsl" "eth1"
ucidef_set_led_netdev "wlan0" "WIFI" "red:wifi" "wlan0"
brcm63xx: CPVA502+: fix userspace support Fix board name typo, fix network configuration and add a led trigger. Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com>
2017-02-14 15:37:04 +00:00
;;
brcm63xx: use compatible instead of manually setting board name This patch removes the translation of device model name into a board name in lib/brcm63xx.sh. The latter has been actually totally useless as we have the compatible which can be used instead of the board name (and actually is at other targets like ath79 or ramips). The change requires updating the base-files with the new identifiers based on compatible. With all "board names" replaced by the compatible, we do not need the old scripts to detect board name anymore and can also remove the obsolete treatment of "legacy" devices without DTS, as there are none of those left. So, this patch removes the target-specific board detection and uses the standard procedure in package/base-files/files/lib/preinit/02_sysinfo This also fixes several cases where the board name was not set or evaluated correctly: - asmax,ar1004g in 02_network - telsey,magic in 09_fix_crc/02_network - brcm,bcm96338gw in 02_network - brcm,bcm96338w in 02_network - brcm,bcm96348gw in 02_network - dynalink,rta1025w in 02_network - huawei,echolife-hg520v in 02_network - several cases in diag.sh The following orphaned identifiers are removed from board.d files: - dmv-s0 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 20:58:34 +00:00
netgear,dgnd3700-v1)
bcm63xx: remove model name from LED labels Like in the previous patches for various targets, this will remove the "devicename" from LED labels in bcm63xx, as it's useless and only creates complexity. The devicename is removed in DTS files and 01_leds, merging several cases on the way. A migration script is added for existing configurations. Note that a few labels were using "model::function" scheme without color specified, those were converting to just "function" and the necessary migrations were added to the migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-10-10 17:44:02 +00:00
ucidef_set_led_netdev "lan" "LAN" "green:lan" "eth0.1"
ucidef_set_led_netdev "wan" "WAN" "green:inet" "eth0.2"
ucidef_set_led_netdev "wlan0" "WIFI2G" "green:wifi2g" "wlan0"
ucidef_set_led_netdev "wlan1" "WIFI5G" "blue:wifi5g" "wlan1"
ucidef_set_led_usbdev "usb1" "USB1" "green:usb-back" "1-1"
ucidef_set_led_usbdev "usb2" "USB2" "green:usb-front" "1-2"
brcm63xx: Add DGND3700 v1 / DGND3800B support This adds support for the Netgear DGND3700 v1 and DGND3800B. DGND3700 v1 and DGND3800B are exactly the same router, only one difference, the factory firmware. This patch produces two factory firmwares for each router. The router includes an onboard NAND flash for extra storage. NAND is currently not supported in bcm63xx, so no code added for this part. The NOR flash (32MB) is enough for storing an openwrt firmware. Signed-off-by: Daniel Gonzalez <dgcbueu@gmail.com> [jogo: Add back commit message from v1] Signed-off-by: Jonas Gorski <jogo@openwrt.org> SVN-Revision: 44831
2015-03-16 11:52:10 +00:00
;;
bcm63xx: add NETGEAR DGND3700v2 support BCM6362 with 64M RAM, 32M NAND and BCM53125 switch. Switch is connected by MMAP, which is currently unsupported (no VLANs). More info: https://openwrt.org/toh/netgear/dgnd3700v2 Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-19 06:55:06 +00:00
netgear,dgnd3700-v2)
bcm63xx: remove model name from LED labels Like in the previous patches for various targets, this will remove the "devicename" from LED labels in bcm63xx, as it's useless and only creates complexity. The devicename is removed in DTS files and 01_leds, merging several cases on the way. A migration script is added for existing configurations. Note that a few labels were using "model::function" scheme without color specified, those were converting to just "function" and the necessary migrations were added to the migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-10-10 17:44:02 +00:00
ucidef_set_led_netdev "lan" "LAN" "green:ethernet" "eth0"
ucidef_set_led_usbdev "usb1" "USB1" "green:usb1" "1-1"
ucidef_set_led_usbdev "usb2" "USB2" "green:usb2" "1-2"
bcm63xx: add NETGEAR DGND3700v2 support BCM6362 with 64M RAM, 32M NAND and BCM53125 switch. Switch is connected by MMAP, which is currently unsupported (no VLANs). More info: https://openwrt.org/toh/netgear/dgnd3700v2 Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-19 06:55:06 +00:00
;;
brcm63xx: use compatible instead of manually setting board name This patch removes the translation of device model name into a board name in lib/brcm63xx.sh. The latter has been actually totally useless as we have the compatible which can be used instead of the board name (and actually is at other targets like ath79 or ramips). The change requires updating the base-files with the new identifiers based on compatible. With all "board names" replaced by the compatible, we do not need the old scripts to detect board name anymore and can also remove the obsolete treatment of "legacy" devices without DTS, as there are none of those left. So, this patch removes the target-specific board detection and uses the standard procedure in package/base-files/files/lib/preinit/02_sysinfo This also fixes several cases where the board name was not set or evaluated correctly: - asmax,ar1004g in 02_network - telsey,magic in 09_fix_crc/02_network - brcm,bcm96338gw in 02_network - brcm,bcm96338w in 02_network - brcm,bcm96348gw in 02_network - dynalink,rta1025w in 02_network - huawei,echolife-hg520v in 02_network - several cases in diag.sh The following orphaned identifiers are removed from board.d files: - dmv-s0 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 20:58:34 +00:00
netgear,evg2000)
bcm63xx: remove model name from LED labels Like in the previous patches for various targets, this will remove the "devicename" from LED labels in bcm63xx, as it's useless and only creates complexity. The devicename is removed in DTS files and 01_leds, merging several cases on the way. A migration script is added for existing configurations. Note that a few labels were using "model::function" scheme without color specified, those were converting to just "function" and the necessary migrations were added to the migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-10-10 17:44:02 +00:00
ucidef_set_led_netdev "lan" "LAN" "green:lan" "eth0"
ucidef_set_led_netdev "wan" "WAN" "green:wan" "eth1"
ucidef_set_led_netdev "wlan0" "WIFI" "green:wireless" "wlan0"
ucidef_set_led_usbdev "usb1" "USB1" "green:voip1" "1-1"
ucidef_set_led_usbdev "usb2" "USB2" "green:voip2" "1-2"
brcm63xx: use compatible instead of manually setting board name This patch removes the translation of device model name into a board name in lib/brcm63xx.sh. The latter has been actually totally useless as we have the compatible which can be used instead of the board name (and actually is at other targets like ath79 or ramips). The change requires updating the base-files with the new identifiers based on compatible. With all "board names" replaced by the compatible, we do not need the old scripts to detect board name anymore and can also remove the obsolete treatment of "legacy" devices without DTS, as there are none of those left. So, this patch removes the target-specific board detection and uses the standard procedure in package/base-files/files/lib/preinit/02_sysinfo This also fixes several cases where the board name was not set or evaluated correctly: - asmax,ar1004g in 02_network - telsey,magic in 09_fix_crc/02_network - brcm,bcm96338gw in 02_network - brcm,bcm96338w in 02_network - brcm,bcm96348gw in 02_network - dynalink,rta1025w in 02_network - huawei,echolife-hg520v in 02_network - several cases in diag.sh The following orphaned identifiers are removed from board.d files: - dmv-s0 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 20:58:34 +00:00
;;
sagem,fast-2704n)
bcm63xx: remove model name from LED labels Like in the previous patches for various targets, this will remove the "devicename" from LED labels in bcm63xx, as it's useless and only creates complexity. The devicename is removed in DTS files and 01_leds, merging several cases on the way. A migration script is added for existing configurations. Note that a few labels were using "model::function" scheme without color specified, those were converting to just "function" and the necessary migrations were added to the migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-10-10 17:44:02 +00:00
ucidef_set_led_netdev "wan" "WAN" "green:inet" "eth0.2"
bcm63xx: fix AD1018 WLAN led Standard AD1018 has lower case LEDs. Fixes: 5f826919232d ("bcm63xx: add unmodded SERCOMM AD1018 support") Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 06:40:52 +00:00
;;
bcm63xx: remove model name from LED labels Like in the previous patches for various targets, this will remove the "devicename" from LED labels in bcm63xx, as it's useless and only creates complexity. The devicename is removed in DTS files and 01_leds, merging several cases on the way. A migration script is added for existing configurations. Note that a few labels were using "model::function" scheme without color specified, those were converting to just "function" and the necessary migrations were added to the migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-10-10 17:44:02 +00:00
sercomm,ad1018|\
brcm63xx: use compatible instead of manually setting board name This patch removes the translation of device model name into a board name in lib/brcm63xx.sh. The latter has been actually totally useless as we have the compatible which can be used instead of the board name (and actually is at other targets like ath79 or ramips). The change requires updating the base-files with the new identifiers based on compatible. With all "board names" replaced by the compatible, we do not need the old scripts to detect board name anymore and can also remove the obsolete treatment of "legacy" devices without DTS, as there are none of those left. So, this patch removes the target-specific board detection and uses the standard procedure in package/base-files/files/lib/preinit/02_sysinfo This also fixes several cases where the board name was not set or evaluated correctly: - asmax,ar1004g in 02_network - telsey,magic in 09_fix_crc/02_network - brcm,bcm96338gw in 02_network - brcm,bcm96338w in 02_network - brcm,bcm96348gw in 02_network - dynalink,rta1025w in 02_network - huawei,echolife-hg520v in 02_network - several cases in diag.sh The following orphaned identifiers are removed from board.d files: - dmv-s0 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 20:58:34 +00:00
sercomm,ad1018-nor)
bcm63xx: remove model name from LED labels Like in the previous patches for various targets, this will remove the "devicename" from LED labels in bcm63xx, as it's useless and only creates complexity. The devicename is removed in DTS files and 01_leds, merging several cases on the way. A migration script is added for existing configurations. Note that a few labels were using "model::function" scheme without color specified, those were converting to just "function" and the necessary migrations were added to the migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-10-10 17:44:02 +00:00
ucidef_set_led_netdev "wlan0" "WLAN" "green:wifi" "wlan0"
brcm63xx: add support for the Actiontec R1000H gateway SOC: Broadcom BCM6368 (2 * Broadcom BMIPS4350 V3.1 / 400 MHz) Flash size: 32MB (split 16/16 dual boot) RAM size: 64MB Wireless: BCM432x 802.11a/b/g/n(pci) Ethernet: Broadcom BCM53115 USB: 1 x USB 2.0 Known issues: - Unable to detect 53115 switch attached to MDIO. Not supported - No support for the cable port More info on the device and the research can be found at: http://www.actiontec.com/212.html Same FCC ID as: https://wikidevi.com/wiki/Actiontec_V1000H_(Telus) Signed-off-by: Anthony Sepa <anthonysepa@yahoo.ca> [jonas.gorski: fix commit subject/message] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2017-02-19 18:27:36 +00:00
;;
bcm63xx: add support for the Sercomm H500-s Sercomm H500-s is an xDSL dual band wireless router based on Broadcom BCM63167 SoC. Hardware: SoC: Broadcom BCM63167 CPU: BMIPS4350 V8.0, 400 MHz, 2 cores Flash: NAND 128 MiB RAM: DDR3 128 MiB Ethernet: 4x 10/100/1000 Mbps Switch: BCM53134S Wireless: 802.11b/g/n: BCM435f (integrated) 802.11ac: Quantenna QT3740BC (onboard SoC) USB: 1x 2.0 LEDs/Buttons: 11x / 2x Flash instruction, web UI: 1. Reset to defaults using the reset button if the admin password is unknown 2. Login into the web UI as admin. Address: http://192.168.0.1 User: admin Password: VF-ESVodafone-H-500-s or l033i-h500s 3. Go to Settings -> Firmware Update, and select the Openwrt factory firmware 4. Update the firmware. 5. Wait until it finish, the device will reboot with Openwrt installed on the alternative image partitions keeping the stock firmware in the former. Notes: - The patch also adds support for the lowi version. Only the factory firmware is different. - The integrated Wifi in the Broadcom Soc isn't still supported. - The Quantenna 802.11ac wifi works ok, but needs to be configured with the Quantenna client application. It can't be configured with Luci nor any iw command since it's a separated subsystem linked via ethernet. - The BCM53134S external switch is managed via MDIO which isn't supported in this target. Therefore it will behave as a dumb switch. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
2020-06-07 08:55:56 +00:00
sercomm,h500-s-lowi|\
sercomm,h500-s-vfes)
bcm63xx: remove model name from LED labels Like in the previous patches for various targets, this will remove the "devicename" from LED labels in bcm63xx, as it's useless and only creates complexity. The devicename is removed in DTS files and 01_leds, merging several cases on the way. A migration script is added for existing configurations. Note that a few labels were using "model::function" scheme without color specified, those were converting to just "function" and the necessary migrations were added to the migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-10-10 17:44:02 +00:00
ucidef_set_led_netdev "wan" "WAN" "green:internet" "eth0.2"
bcm63xx: add support for the Sercomm H500-s Sercomm H500-s is an xDSL dual band wireless router based on Broadcom BCM63167 SoC. Hardware: SoC: Broadcom BCM63167 CPU: BMIPS4350 V8.0, 400 MHz, 2 cores Flash: NAND 128 MiB RAM: DDR3 128 MiB Ethernet: 4x 10/100/1000 Mbps Switch: BCM53134S Wireless: 802.11b/g/n: BCM435f (integrated) 802.11ac: Quantenna QT3740BC (onboard SoC) USB: 1x 2.0 LEDs/Buttons: 11x / 2x Flash instruction, web UI: 1. Reset to defaults using the reset button if the admin password is unknown 2. Login into the web UI as admin. Address: http://192.168.0.1 User: admin Password: VF-ESVodafone-H-500-s or l033i-h500s 3. Go to Settings -> Firmware Update, and select the Openwrt factory firmware 4. Update the firmware. 5. Wait until it finish, the device will reboot with Openwrt installed on the alternative image partitions keeping the stock firmware in the former. Notes: - The patch also adds support for the lowi version. Only the factory firmware is different. - The integrated Wifi in the Broadcom Soc isn't still supported. - The Quantenna 802.11ac wifi works ok, but needs to be configured with the Quantenna client application. It can't be configured with Luci nor any iw command since it's a separated subsystem linked via ethernet. - The BCM53134S external switch is managed via MDIO which isn't supported in this target. Therefore it will behave as a dumb switch. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
2020-06-07 08:55:56 +00:00
;;
bcm63xx: add support for Technicolor TG582n Technicolor TG582n has a similar PCB as the OpenWrt's ADB P.DG A4001N1 with LEDs connected to different GPIO PINs in active low configuration. Hardware: * Board ID: DANT-1 * SoC: Broadcom BCM6328 (rev b0) @ 320MHz, CPU BMIPS4350 * RAM DDR2: 64 Mbyte - Winbond W9751G6KB-25 * Serial flash: 16 Mbyte - MXIC MX25L6445EMI * Ethernet: 4x Ethernet 10/100 baseT * Wifi 2.4GHz: Broadcom Corporation BCM43227 Wireless Network Adapter (rev 30) * LEDs: 2x Power, 1x Ethernet, 1x Broadband, 2x Wi-Fi, 2x WPS, 4x ethernet * Buttons: 1x Reset, 1x WPS, 1x WiFi * UART: 1x TTL 115200n8, VCC GND TX RX, on J3 connector (short R62 and R63) Installation via CFE: * Stock CFE has to be overwritten with a generic 6328 one that can upload .bin images with no signature check (cfe6328_configured.bin) * Connect a serial port to the board * Stop the CFE boot process after power on by pressing enter * Set static IP 192.168.2.10 and subnet mask 255.255.255.0 * Navigate to http://192.168.2.50/ * Upload the OpenWrt image file PCB: |GPIO: |TG582n: LED2R |488(08) |red Power LED2G |484(04) |green Power LED10R |486(06) | LED13G |485(05) |green Ethernet LED11R |494(14) | LED14G |491(11) |green Broadband LED5R |487(07) |red Internet LED5G |481(01) |green Internet LED12R |498(18) | LED12G |499(19) | LED6R |482(02) |red Wi-Fi LED6G |483(03) |green Wi-Fi LED7R |490(10) |red WPS LED7G |489(09) |green WPS LED4 |508(28) |ethernet port 4 LED3 |507(27) |ethernet port 3 LED9 |506(26) |ethernet port 2 LED8 |505(25) |ethernet port 1 SW3 |503(23) |key Reset SW5 |504(24) |key WPS SW4 |495(15) |key Wi-Fi SW6 |493(13) | SW1 |492(12) | Signed-off-by: Daniele Castro <danielecastro@hotmail.it> [Fix base-files, refresh patch] Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-09-10 19:14:11 +00:00
technicolor,tg582n)
ucidef_set_led_netdev "wlan0" "WIFI" "green:wifi" "wlan0"
ucidef_set_led_usbdev "usb" "USB" "red:power" "1-1"
;;
brcm63xx: use compatible instead of manually setting board name This patch removes the translation of device model name into a board name in lib/brcm63xx.sh. The latter has been actually totally useless as we have the compatible which can be used instead of the board name (and actually is at other targets like ath79 or ramips). The change requires updating the base-files with the new identifiers based on compatible. With all "board names" replaced by the compatible, we do not need the old scripts to detect board name anymore and can also remove the obsolete treatment of "legacy" devices without DTS, as there are none of those left. So, this patch removes the target-specific board detection and uses the standard procedure in package/base-files/files/lib/preinit/02_sysinfo This also fixes several cases where the board name was not set or evaluated correctly: - asmax,ar1004g in 02_network - telsey,magic in 09_fix_crc/02_network - brcm,bcm96338gw in 02_network - brcm,bcm96338w in 02_network - brcm,bcm96348gw in 02_network - dynalink,rta1025w in 02_network - huawei,echolife-hg520v in 02_network - several cases in diag.sh The following orphaned identifiers are removed from board.d files: - dmv-s0 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 20:58:34 +00:00
telsey,cpva502plus)
bcm63xx: remove model name from LED labels Like in the previous patches for various targets, this will remove the "devicename" from LED labels in bcm63xx, as it's useless and only creates complexity. The devicename is removed in DTS files and 01_leds, merging several cases on the way. A migration script is added for existing configurations. Note that a few labels were using "model::function" scheme without color specified, those were converting to just "function" and the necessary migrations were added to the migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-10-10 17:44:02 +00:00
ucidef_set_led_netdev "lan" "LAN" "amber:link" "eth0"
brcm63xx: Add NuCom R5010UNv2 support This patch adds support for the NuCom R5010UNv2. It's a BCM6328 based board. It has an onboard BCM43217 wifi chip. For this wifi chip looks like the brcmsmac driver isn't still supported, b43 drivers are used for the profile of the router. It's worth mentioning this board was affected by a bug solved with https://dev.openwrt.org/changeset/46707 Tested-by: Angel Fontan <angel.fontan@gmail.com> Signed-off-by: Daniel Gonzalez <dgcbueu@gmail.com> Signed-off-by: Jonas Gorski <jogo@openwrt.org> SVN-Revision: 47697
2015-12-02 22:18:20 +00:00
;;
brcm63xx: Add userspace support for Sagemcom F@ST2704V2 ADSL router This adds userspace support for Sagemcom F@st 2704 router. Signed-off-by: Marcin Jurkowski <marcin1j@gmail.com> Patchwork: http://patchwork.openwrt.org/patch/4215/ Signed-off-by: Jonas Gorski <jogo@openwrt.org> SVN-Revision: 39672
2014-02-22 11:16:33 +00:00
esac
brcm63xx: switch from uci-defaults to board.d Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> Acked-by: Jonas Gorski <jogo@openwrt.org> SVN-Revision: 47754
2015-12-04 12:32:36 +00:00
board_config_flush
brcm63xx: Add userspace support for Sagemcom F@ST2704V2 ADSL router This adds userspace support for Sagemcom F@st 2704 router. Signed-off-by: Marcin Jurkowski <marcin1j@gmail.com> Patchwork: http://patchwork.openwrt.org/patch/4215/ Signed-off-by: Jonas Gorski <jogo@openwrt.org> SVN-Revision: 39672
2014-02-22 11:16:33 +00:00
exit 0
Reference in New Issue Copy Permalink