KumiSystems/openwrtv4
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
openwrtv4/target/linux/ramips/base-files/etc/diag.sh

326 lines
4.6 KiB
Bash
Raw Normal View History

ramips: add diag support SVN-Revision: 20799
2010-04-11 17:47:23 +00:00
#!/bin/sh
ramips: migrate to common led helper functions [juhosg: migrate to status_led_blink_{preinit,failsafe} helpers] Signed-off-by: Michael Heimpold <mhei@heimpold.de> Signed-off-by: Gabor Juhos <juhosg@openwrt.org> SVN-Revision: 35652
2013-02-18 09:56:29 +00:00
# Copyright (C) 2010-2013 OpenWrt.org
ramips: add diag support SVN-Revision: 20799
2010-04-11 17:47:23 +00:00
treewide: use the generic board_name function Use the generic function instead ot the target specific ones. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-05-12 20:36:07 +00:00
. /lib/functions.sh
ramips: migrate to common led helper functions [juhosg: migrate to status_led_blink_{preinit,failsafe} helpers] Signed-off-by: Michael Heimpold <mhei@heimpold.de> Signed-off-by: Gabor Juhos <juhosg@openwrt.org> SVN-Revision: 35652
2013-02-18 09:56:29 +00:00
. /lib/functions/leds.sh
ramips: add diag support SVN-Revision: 20799
2010-04-11 17:47:23 +00:00
get_status_led() {
treewide: use the generic board_name function Use the generic function instead ot the target specific ones. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-05-12 20:36:07 +00:00
board=$(board_name)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
case $board in
3g150b|\
3g300m|\
w150m)
status_led="$board:blue:ap"
;;
3g-6200n|\
ar670w|\
ar725w|\
br-6475nd|\
ramips: Archer C50 cleanup - setting read-only flag to important partitions - enabling PA to improve 2.4 GHz signal strength - add missing leds - rename colour led - add mac adress to 5GHz wlan interface - included <dt-bindings/input/input.h> and <dt-bindings/gpio/gpio.h> Signed-off-by: Henryk Heisig hyniu@o2.pl
2016-10-13 19:00:06 +00:00
c50|\
ramips: Add support for D-Link DCH-M225 D-Link DCH-M225 is based on Mediatek MT7620 with 64MB ram, 8MB flash, 3.5mm audio out support. but no ethernet and usb ports. so you must default enable wifi. Signed-off-by: Michael Lee <igvtee@gmail.com>
2016-05-02 03:57:40 +00:00
dch-m225|\
ramips: add button support and make LEDs known to userspace for DIR-860L B1 Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net> Reviewed-by: Jo-Philipp Wich <jo@mein.io>
2016-06-30 13:18:03 +00:00
dir-860l-b1|\
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
e1700|\
ramips: cleanup EX2700 and WN3000RPv3 LEDs This patch cleans up the WN3000RPv3 and EX2700 setup, bringing it in line with other similar devices: The power led is a bicolor one. The bootloader brings the red side on at powerup. Instead of blinking the red side in diag.sh and need to forcefully turn it off in 01_leds, this patch simplifies the setup by relying on the default off state of the gpio-led driver for the red side and blinking the green side as with other devices. Signed-off-by: Thibaut VARENE <hacks@slashdirt.org>
2017-07-30 13:42:38 +00:00
ex2700|\
ramips: add support for Netgear EX3700 Specifications: * SoC: MT7620A * RAM: 64 MB DDR * Flash: 8MB NOR SPI flash * WiFi: MT7612E (5Ghz) and builtin MT7620A (2.4GHz) * LAN: 1x100M The -factory images can be flashed from the device's web interface or via nmrpflash. Co-authored-by: Paul Oranje <por@xs4all.nl> Signed-off-by: Paul Oranje <por@xs4all.nl> Signed-off-by: Joseph C. Lehner <joseph.c.lehner@gmail.com>
2017-03-03 14:36:51 +00:00
ex3700|\
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
fonera20n|\
ramips: fix hg255d LED status support Use the green power LED for boot status indication. Source: https://my.oschina.net/osbin/blog/278782 Para 3 Signed-off-by: David Yang <mmyangfl@gmail.com>
2017-09-09 13:16:11 +00:00
hg255d|\
ramips: add new device ZyXEL Keenetic as kn This device exactly same as NBG-419N but with USB port and USB Led. Specification: - SoC: Ralink RT3052 (MIPS24Kc) @384MHz - RAM: 32 MiB - Flash: 8 MiB - WLAN: WiSoC 2T2R/300Mbps (2.4GHz) - LAN: 4x100M - WAN: 1x100M - USB: 1x2.0 Installation via serial console (57600 8N1) from TFTP server - rename the firmware to something shorter, for example "sysupgrade.bin" (max. 32 chars) - copy firmware TFTP server's directory - when you power on device, and see U-Boot log, immediatly push "2" once. - You will see this message: 2: System Load Linux Kernel then write to Flash via TFTP. Warning!! Erase Linux in Flash then burn new one. Are you sure? - Push "y", and enter: device IP, then TFTP server's IP, and then image firmware file name. The firmware will be downloaded within ~30 seconds and flashed to the device (It will take about 2 minutes). Signed-off-by: Alexey Belyaev <spider@spider.vc> [squash commits, compact commit message, fix compatible string, remove superfluous pinmuxes] Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-27 18:02:05 +00:00
kn|\
ramips: add support for ZyXEL Keenetic Omni / Omni II Factory image can be installed via Zyxel WebUI. Signed-off-by: Vitaly Chekryzhev <13hakta@gmail.com>
2016-11-28 18:41:51 +00:00
kn_rc|\
kn_rf|\
ramips: add support for ZyXEL Keenetic Viva Factory image can be installed via Zyxel WebUI. Signed-off-by: Vitaly Chekryzhev <13hakta@gmail.com> [removed linux,modalias parameter from flash node in dts] [removed sdhci node from dts; no sd card slot here] Signed-off-by: Mathias Kresin <dev@kresin.me>
2016-10-29 12:26:58 +00:00
kng_rc|\
ramips: fix support Planex MZK-750DHP. fix script for Planex MZK-750DHP. modification of the GPIO definition. add Profile. Signed-off-by: YuheiOKAWA <tochiro.srchack@gmail.com> SVN-Revision: 49205
2016-04-20 17:19:05 +00:00
mzk-750dhp|\
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
mzk-dp150n|\
mzk-w300nh2|\
nbg-419n|\
ramips: add support for Zyxel NBG-419N2 (WAP3205v2) applied bb-final-ramips-add-zyxel-nbg-419n2.patch from 123serge123, found at https://yadi.sk/d/1ZV0lKJwbTE65; see https://forum.openwrt.org/viewtopic.php?pid=246905#p246905, modified slightly to fit to CC release and to new lede build system: image/rt305x.mk include file is used now changed NBG-419N2.dts format to fit style of other dts files Signed-off-by: Klaus <k-laus@quantentunnel.de>
2016-07-24 15:37:52 +00:00
nbg-419n2|\
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
pwh2004|\
ramips: add support for Netgear R6220 This patch adds support for the Netgear R6220, aka Netgear AC1200 and R6220-100NAS. Specification: - SoC: MediaTek MT7621ST (880 MHz) - Falsh: 128 MiB (Macronix MX30LF1G08AA-TI) - RAM: 128 MiB (Nanya NT5CB64M16FP-DH) - Wireless: MediaTek MT7603EN b/g/n , MediaTek MT7612EN an+ac - LAN speed: 10/100/1000 - LAN ports: 4 - WAN speed: 10/100/1000 - WAN ports: 1 - Serial baud rate of Bootloader and factory firmware: 57600 Installation through telnet: - Copy kernel.bin and rootfs.bin to a USB flash disk, plug to usb port on the router. - Enable telnet with link: http://192.168.1.1/setup.cgi?todo=debug (login if required, default: admin password) - You will see "Debug Enabled!" - Telnet 192.168.1.1 and login with "root" - ls /mnt/shares/ to find out path of your USB disk. 'myUdisk' for example. - cd /mnt/shares/myUdisk - mtd_write write rootfs.bin Rootfs - mtd_write write kernel.bin Kernel - reboot nmrpflash can be used to recover to the netgear firmware if a broken image was flashed. Signed-off-by: Hanqing Wong <hquu@outlook.com>
2017-03-11 07:44:33 +00:00
r6220|\
ramips: add support for TP-Link TL-WR840N v4 and TL-WR841N v13 TP-Link TL-WR840N v4 and TL-WR841N v13 are simple N300 routers with 5-port FE switch and non-detachable antennas. Both are very similar and are based on MediaTek MT7628NN (aka MT7628N) WiSoC. The difference between these two models is in number of available LEDs, buttons and power input switch. This work is partially based on GitHub PR#974. Specification: - MT7628N/N (580 MHz) - 64 MB of RAM (DDR2) - 8 MB of FLASH - 2T2R 2.4 GHz - 5x 10/100 Mbps Ethernet - 2x external, non-detachable antennas - UART (J1) header on PCB (115200 8n1) - TL-WR840N v4: 5x LED (GPIO-controlled), 1x button - TL-WR841N v13: 8x LED (GPIO-controlled*), 2x button, power input switch * WAN LED in TL-WR841N v13 is a dual-color, dual-leads type which isn't (fully) supported by gpio-leds driver. This type of LED requires both GPIOs state change at the same time to select color or turn it off. For now, we support/use only the green part of the LED. Factory image notes: These devices use version 3 of TP-Link header, fortunately without RSA signature (at least in case of devices sold in Europe). The difference lays in the requirement for a non-zero value in "Additional Hardware Version" field. Ideally, it should match the value stored in vendor firmware header on device ("0x4"/"0x13" for these devices) but it seems that anything other than "0" is correct. We are able to prepare factory firwmare file which is accepted and (almost) correctly flashed from the vendor GUI. As it turned out, it accepts files without U-Boot image with second header at the beginning but due to some kind of bug in upgrade routine, flashed image gets corrupted before it's written to flash. Tests showed that the GUI upgrade routine copies value of "Additional Hardware Version" from existing firmware into offset "0x2023c" in provided file, _before_ storing it in flash. In case of vendor firmware upgrade files (which all include U-Boot image and two headers), this offset points to the matching field in kernel+rootfs firmware part header. Unfortunately, in case of LEDE factory image file which contains only one header, it points to the offset "0x2023c" in kernel image. This leads to a corrupted kernel and ends up with a "soft-bricked" device. The good news is that U-Boot in these devices contains well known tftp recovery mode, which can be triggered with "reset" button. What's more, in comparison to some of older MediaTek based TP-Link devices, this recovery mode doesn't write whole file at offset "0x0" in flash, without verifying provided file in advance. In case of recovery mode in these devices, first "0x20000" bytes are always skipped and "0x7a0000" bytes from rest of the file are stored in flash at offset "0x20000". Flash instruction: Until (if at all) TP-Link fixes described problem, the only way to flash LEDE image in these devices is to use tftp recovery mode in U-Boot: 1. Configure PC with static IP 192.168.0.66/24 and tftp server. 2. Rename "lede-ramips-mt7628-tl-wr84...-squashfs-tftp-recovery.bin" to "tp_recovery.bin" and place it in tftp server directory. 3. Connect PC with one of LAN ports, press the reset button, power up the router and keep button pressed for around 6-7 seconds, until device starts downloading the file. 4. Router will download file from server, write it to flash and reboot. To access U-Boot CLI, keep pressed "4" key during boot. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2017-06-21 12:16:15 +00:00
tl-wr840n-v4|\
tl-wr841n-v13|\
ramips: add support for Planex VR500. SOC: MT7621A RAM: 256MiB NOR: MX25L51245G Non Wireless Router. Issue: soft reboot problem. SPI Flash do not exit 4byte address mode. Signed-off-by: Yuhei Okawa <tochiro.srchack@gmail.com>
2016-10-10 01:24:42 +00:00
vr500|\
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
wnce2001|\
ramips: Add support for the Netgear WNDR3700v5 https://wiki.openwrt.org/toh/netgear/wndr3700 wndr3700v5 uses the single-core dual thread MediaTek MT7621S SoC. Signed-off-by: L. D. Pinney <ldpinney@gmail.com> SVN-Revision: 49247
2016-04-26 11:43:53 +00:00
wndr3700v5|\
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
x5|\
x8|\
ramips: cleanup EX2700 and WN3000RPv3 LEDs This patch cleans up the WN3000RPv3 and EX2700 setup, bringing it in line with other similar devices: The power led is a bicolor one. The bootloader brings the red side on at powerup. Instead of blinking the red side in diag.sh and need to forcefully turn it off in 01_leds, this patch simplifies the setup by relying on the default off state of the gpio-led driver for the red side and blinking the green side as with other devices. Signed-off-by: Thibaut VARENE <hacks@slashdirt.org>
2017-07-30 13:42:38 +00:00
xdxrn502j|\
wn3000rpv3)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
status_led="$board:green:power"
ramips: add asiarf awapn2403 support Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 41177
2014-06-13 09:16:15 +00:00
;;
ramips: improve edimax 6200n/nl support Assign the reset functionality to the wps/reset buttons. Use the wlan switch of the 6200n to enable/disable wlan. Add the internet led of the 6200nl and use the led for boot status indication Signed-off-by: Mathias Kresin <dev@kresin.me>
2016-09-27 05:16:16 +00:00
3g-6200nl)
status_led="$board:green:internet"
;;
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
a5-v11|\
ramips: add support for Planex CS-QR10 CS-QR10 is MT7620A based IP Camera. the camera and sound does not work with kernel 4.4. - camera chip is sn9c291. - sound chip is wm8960. Signed-off-by: YuheiOKAWA <tochiro.srchack@gmail.com> SVN-Revision: 49234
2016-04-26 11:43:01 +00:00
cs-qr10|\
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
d105|\
dcs-930l-b1|\
hlk-rm04|\
ramips: Add JCG routers to base-files This patch adds support for JHR-N805R, JHR-N825R and JHR-N926R to various scripts in the base-files directory. Signed-off-by: Reinhard Max <reinhard@m4x.de> Reviewed-by: Torsten Duwe <duwe@lst.de> SVN-Revision: 48905
2016-03-04 08:33:09 +00:00
jhr-n825r|\
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
mpr-a1|\
ramips: add support for Planex MZK-EX750NP. add support for Planex MZK-EX750NP. MZK-EX750NP is MT7620A and MT7610E based 11ac wifi repeater. Built-in power supply. 64MiB RAM, 8MiB SPI Flash, non Wired Ethernet. Signed-off-by: YuheiOKAWA <tochiro.srchack@gmail.com> SVN-Revision: 49268
2016-04-29 11:34:56 +00:00
mpr-a2|\
ramips: cleanup EX2700 and WN3000RPv3 LEDs This patch cleans up the WN3000RPv3 and EX2700 setup, bringing it in line with other similar devices: The power led is a bicolor one. The bootloader brings the red side on at powerup. Instead of blinking the red side in diag.sh and need to forcefully turn it off in 01_leds, this patch simplifies the setup by relying on the default off state of the gpio-led driver for the red side and blinking the green side as with other devices. Signed-off-by: Thibaut VARENE <hacks@slashdirt.org>
2017-07-30 13:42:38 +00:00
mzk-ex750np)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
status_led="$board:red:power"
ramips: scripts updates In this patch: * rename Argus leds to avoid underscores * rename Belkin F5D8235 v1 leds from f5d8234 to f5d8235 * remove Belkin F5D8235 v1 status led defined as storage led (it was defined as usb led earlier, just in wrong place) - it should have router led as in v2 * add Argus, Sparklan and Belkin F5D8235 v2 status leds * add Belkin F5D8235 v1 and v2 usb leds * fix Belkin F5D8235 v2 network config generation and mac address axtraction * fix Sparklan board identification * add Sparklan usb led (this board doesn't have usb connector by default and the led is hidden also but if you are going to solder the connector then you'll see the led too) * add Sparklan network config generation and mac address extraction * fix empty string test in network script and... * ...sort case entries by the first board in the list Signed-off-by: Roman Yeryomin <roman@advem.lv> SVN-Revision: 29871
2012-01-23 10:23:32 +00:00
;;
ramips: rename Digineo AC1200 Pro to ZBT-WG3526 32MB The Digineo AC1200 Pro is the 32MB flash variant of the ZBT-WG3526 with unpopulated/exposed sdhci slot. Rename to board to the OEM/ODM name and add the sdhci kernel module to use it for multiple clones. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-01 08:46:44 +00:00
ai-br100|\
ht-tm02)
status_led="$board:blue:wlan"
;;
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
all0239-3g|\
dcs-930|\
dir-300-b1|\
dir-300-b7|\
dir-320-b1|\
dir-600-b1|\
dir-610-a1|\
dir-615-d|\
dir-615-h1|\
dir-620-a1|\
dir-620-d1|\
ramips: Add device DLINK DWR-512-B The Dlink DWR-512-B modem is a ralink 5350 processor based embedding a 3G mini-pcie router. The oem JBOOT bootloader has to be replaced by a RT5350 SDK U-Boot such as https://github.com/stevenylai/ralink_sdk - U-Boot configured for the RT5350 256MiB SDR. Main reason to change the bootloader is the encrypted header used to store the kernel image. In this way an image can only be generated using the propietary binboy tool (included in the GPL distribution from Dlink). The binboy tool doesn't allow to modify the kernel/rootfs partition scheme. This is considered a big constraint (limited kernel size and inefficient usage of flash space). For interested people I pubblished the details of my investigation about the encrypted firmware header here: http://lists.infradead.org/pipermail/lede-dev/2016-October/003435.html Signed-off-by: Giuseppe Lippolis <giu.lippolis@gmail.com>
2016-11-13 22:36:00 +00:00
dwr-512-b|\
ramips: add support for the GnuBee Personal Cloud One The GnuBee Personal Cloud One crowdfunded on https://www.crowdsupply.com It is a low-cost, low-power, network-attached storage device. Specifications: - SoC: MediaTek MT7621AT - RAM: DDR3 512 MB - Flash: 32 MB - Six SATA ports for 2.5" Drives - One micro SDcard - One USB 3.0 - Two USB 2.0 - Gigabit Ethernet: 1 x WAN and 1 x LAN - UART 3.5mm Audio Jack or 3 pin header - 57600 8N1 - Four GPIOs available on a pin header Flash instructions: The GnuBee Personal Cloud One ships with libreCMC installed. libreCMC is a Free Software Foundation approved fork of LEDE/OpenWrt. As such one can upgrade using the webinterface or sysupgrade. Das U-Boot has multiple options for recovery or updates including : - USB - http - tftp Signed-off-by: L. D. Pinney <ldpinney@gmail.com> [use switchdev led trigger, all interfaces are in vlan1; rename leds according to board.d setting; remove ge2 group from the pinmux, this group doesn't exist in the driver] Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-07-22 01:15:56 +00:00
gb-pc1|\
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
hpm|\
hw550-3g|\
ramips: add support for Mercury MAC1200R v2 MT7628AN + MT7612E, 8MB SPI flash, 64MB DDR RAM reset button GPIO is still missing (anyone?) bootloader password is 'slp' Signed-off-by: Daniel Golle <daniel@makrotopia.org>
2016-09-08 22:57:31 +00:00
mac1200rv2|\
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
miniembwifi|\
mofi3500-3gn|\
rut5xx|\
v11st-fe|\
ramips: add support for ZBT WG2626 Signed-off-by: Daniel Golle <daniel@makrotopia.org> SVN-Revision: 47351
2015-11-02 10:18:19 +00:00
wmr-300|\
ramips: prepare ZBT-WG3526 for hardware variants The ZBT-WG3526 is available with 16 or 32 MByte of flash. Rename the current supported 16MByte version to indicate which flash size variant is supported. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-07 21:52:27 +00:00
zbt-wg2626)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
status_led="$board:green:status"
ramips: use consistent naming scheme for LEDs The upstream LED naming convention is "device:color:led-name", but it seems that many of supported boards in OpenWrt don't follow this approach. The following patch fixes this inconsistency in dts{,i} files and updates base-files scripts for ramips target: * fixes wrong indentation * keeps case statements structure in same convention as in other scripts (no empty line after ";;", no indentation for case...esac body) * fixes wrong LED names for some of boards (makes them the same as in dts{,i} files) * combines boards with same configuration (ex. set_wifi_led "rt2800pci-phy0::radio" in 01_leds) Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46664
2015-08-17 06:24:34 +00:00
;;
ramips: dont replace the board name Use fixed led names and add each board variant instead of manipulating the board name. It makes the ramips board name function less different to the one used in other targets and allows to merge them with a common function. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-07 22:34:48 +00:00
asl26555-8M|\
asl26555-16M)
status_led="asl26555:green:power"
;;
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
atp-52b|\
ramips: add support for Afoundry EW-1200 This device features both a 2.4 and 5Ghz radio, and supports 802.11a/b/g/n/ac modes. It has 5 Gb-Ethernet ports and a USB 3.0 host port. It is powered by the Mediatek MT7621 SoC, and the MT7602E and MT7612E wifi chipsets, together with 128MB of RAM and 16 MB of SPI Flash. The stock firmware is in fact based on some openwrt barrier breaker, with a mediatek SDK kernel, and an afoundry custom made web interface (not LuCI based). Firmware update page on the stock web interface can not accept sysupgrade images, it bricks the device. At this point, the only working solution I found was to connect to the serial console port (available on J4 header) and to use opkg to install dropbear. Then scp the sysupgrade file in the device's /tmp and run sysupgrade from console without preserving configuration files. Signed-off-by: Francois Goudal <francois@goudal.net>
2017-02-27 20:59:50 +00:00
ew1200|\
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
ip2202)
status_led="$board:green:run"
ramips: Add Alpha ASL-26555 support. This board uses a TrendChip SOC with its own RAM/Flash for ADSL support. We know both SOCs are connected through ethernet and use some kind of protocol for UART communication, but due to the lack of GPL sources we couldn't get it to work. For this reason the network is configured only for LAN. There are two versions (Chile 8MB and Spain 16MB). Wiki: http://wiki.openwrt.org/toh/alpha/asl26555 Signed-off-by: Esteban Benito <estebanjbs@gmail.com> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> Patchwork: http://patchwork.openwrt.org/patch/3571/ Acked-by: John Crispin <blogic@openwrt.org> SVN-Revision: 36433
2013-04-25 19:02:53 +00:00
;;
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
awapn2403|\
ramips: add support for ELECOM WRH-300CR ELECOM WRH-300CR is MT7620N based very small Wi-Fi router with 64MiB DDR2 SDRAM, 16MiB SPI Flash, one fast ethernet port, and (internal but easy-to-access) UART. it also has internal USB hub and USB card reader which provide one USB port, one SD card slot, and one microSD card slot. Signed-off-by: YuheiOKAWA <tochiro.srchack@gmail.com> Signed-off-by: FUKAUMI Naoki <naobsd@gmail.com> SVN-Revision: 49211
2016-04-21 19:46:59 +00:00
dir-645|\
ramips: add initial support for SamKnows SK-WB8 Signed-off-by: Andrew Yong <me@ndoo.sg>
2016-05-10 16:17:54 +00:00
sk-wb8|\
ramips: add support for ELECOM WRH-300CR ELECOM WRH-300CR is MT7620N based very small Wi-Fi router with 64MiB DDR2 SDRAM, 16MiB SPI Flash, one fast ethernet port, and (internal but easy-to-access) UART. it also has internal USB hub and USB card reader which provide one USB port, one SD card slot, and one microSD card slot. Signed-off-by: YuheiOKAWA <tochiro.srchack@gmail.com> Signed-off-by: FUKAUMI Naoki <naobsd@gmail.com> SVN-Revision: 49211
2016-04-21 19:46:59 +00:00
wrh-300cr)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
status_led="$board:green:wps"
ramips: add userspace support for the Edimax BR-6425 [juhosg: remove sysupgrade changes] Signed-off-by: Yuval Adam <yuv.adm@gmail.com> Signed-off-by: Gabor Juhos <juhosg@openwrt.org> SVN-Revision: 35463
2013-02-02 17:01:50 +00:00
;;
ramips: add support for the HNET C108 The HNET C108 (http://www.szhwtech88.com/Product-product-cid-100-id-4374.html) is a mifi based on MT7602A, which has the following specifications: * CPU: MT7620A * 1x 10/100Mbps Ethernet. * 16 MB Flash. * 64 MB RAM. * 1x USB 2.0 port. Only power is connected, this port is meant for charging other devices. * 1x mini-PCIe slots. * 1x SIM slots. * 1x 2.4Ghz WIFI. * 1x button. * 6000 mAh battery. * 5x controllable LEDs. Works: * Wifi. * Switch. * mini-PCIe slot. Only tested with a USB device (a modem). * SIM slot. * Sysupgrade. * Button (reset). Not working (also applies to the factory firmware): * Wifi LED. It is always switched on, there is no relation to the up/down state or activity of the wireless interface. Not tested: * SD card reader. Notes: * The C108 has no dedicated status LED. I therefore set the LAN LED as status LED. Installation: The router comes pre-installed with OpenWRT, including a variant of Luci. The initial firmware install can be done through this UI, following normal procedure. I.e., access the UI and update the firmware using the sysupgrade-image. Remember to select that you do not want to keep existing settings. Recovery: If you brick the device, the C108 supports recovery using TFTP. Keep the reset button pressed for ~5sec when booting to trigger TFTP. Set the address of the network interface on your machine to 10.10.10.3/24, and rename your image file to Kernal.bin. Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
2017-09-06 09:14:16 +00:00
c108)
status_led="$board:green:lan"
;;
ramips: Add support for Phicomm PSG1208 This patch adds support for Phicomm PSG1208.This is a router with MT7620A SoC with 8M flash and 64M ram. The WPS led is uesd as status_led because the power light can't be controlled with GPIO. It seems that the 5g wifi led is connected to MT7612E and it can't be controlled with GPIO too. Signed-off-by: Chuanhong Guo <gch981213@gmail.com> SVN-Revision: 48721
2016-02-15 18:45:22 +00:00
cf-wr800n|\
psg1208)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
status_led="$board:white:wps"
ramips: use consistent naming scheme for LEDs The upstream LED naming convention is "device:color:led-name", but it seems that many of supported boards in OpenWrt don't follow this approach. The following patch fixes this inconsistency in dts{,i} files and updates base-files scripts for ramips target: * fixes wrong indentation * keeps case statements structure in same convention as in other scripts (no empty line after ";;", no indentation for case...esac body) * fixes wrong LED names for some of boards (makes them the same as in dts{,i} files) * combines boards with same configuration (ex. set_wifi_led "rt2800pci-phy0::radio" in 01_leds) Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46664
2015-08-17 06:24:34 +00:00
;;
ramips: rename PSG1218 to match label Fix previous commit to be less ambigous: PSG1218 rev.A = 5 ports, external PA, heatsinks PSG1218 rev.B = 4 ports, internal PA, no heatsinks Signed-off-by: Daniel Golle <daniel@makrotopia.org>
2017-04-21 00:47:44 +00:00
psg1218a|\
psg1218b)
ramips: fix PSG1218 LEDs Signed-off-by: Xuefu Lin <xuefulin@gmail.com>
2016-10-21 09:06:39 +00:00
status_led="$board:yellow:status"
ramips: Add support for Phicomm K2 PSG1218 - CPU: MT7620A 580MHz - Flash: 8MB - RAM: 64MB - External PA+LNA on both WLAN2.4 and WLAN5 - 4x LAN ethernet and 1x WAN ethernet Signed-off-by: Xuefu Lin <xuefulin@gmail.com>
2016-09-30 11:41:12 +00:00
;;
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
cy-swr1100|\
w502u)
status_led="$board:blue:wps"
;;
ramips: add support for TP-Link Archer C20 v1 TP-Link Archer C20 v1 is a router with 5-port FE switch and non-detachable antennas. It's very similiar to TP-Link Archer C50. Also it's based on MediaTek MT7620A+MT7610EN. Specification: - MediaTek MT7620A (580 Mhz) - 64 MB of RAM - 8 MB of FLASH - 2T2R 2.4 GHz and 1T1R 5 GHz - 5x 10/100 Mbps Ethernet - 2x external, non-detachable antennas - UART (J1) header on PCB (115200 8n1) - 8x LED (GPIO-controlled*), 2x button, power input switch - 1 x USB 2.0 port * WAN LED in this devices is a dual-color, dual-leads type which isn't (fully) supported by gpio-leds driver. This type of LED requires both GPIOs state change at the same time to select color or turn it off. For now, we support/use only the blue part of the LED. * MT7610EN ac chip isn't not supported by LEDE. Therefore 5Ghz won't work. Factory image notes: These devices use version 3 of TP-Link header, fortunately without RSA signature (at least in case of devices sold in Europe). The difference lays in the requirement for a non-zero value in "Additional Hardware Version" field. Ideally, it should match the value stored in vendor firmware header on device. We are able to prepare factory firwmare file which is accepted and (almost) correctly flashed from the vendor GUI. As it turned out, it accepts files without U-Boot image with second header at the beginning but due to some kind of bug in upgrade routine, flashed image gets corrupted before it's written to flash. So, to flash this device we must to prepare image using original firmware from tp-link site with uboot. Flash instruction: Until (if at all) TP-Link fixes described problem, the only way to flash LEDE image in these devices is to use tftp recovery mode in U-Boot. There are two ways to flash the device to LEDE: 1) Using tftp mode with UART connection and original LEDE image - Place lede-ramips-mt7620-ArcherC20-squashfs-factory.bin in tftp server directory - Configure PC with static IP 192.168.0.66/24 and tftp server. - Connect PC with one of LAN ports, power up the router and press key "4" to access U-Boot CLI. - Use the following commands to update the device to LEDE: setenv serverip 192.168.0.66 tftp 0x80060000 lede-ramips-mt7620-ArcherC20-squashfs-factory.bin erase tplink 0x20000 0x7a0000 cp.b 0x80060000 0x20000 0x7a0000 reset - After that the device will reboot and boot to LEDE 2) Using tftp mode without UART connection but require some manipulations with target image - Download and unpack TP-Link Archer C20 v1 firmware from original web site - Split uboot.bin from original firmware by this command (example): dd if=Archer_C20v1_0.9.1_4.0_up_boot(160427)_2016-04-27_13.53.59.bin of=uboot.bin bs=512 count=256 skip=1 - Create ArcherC20V1_tp_recovery.bin using this command: cat uboot.bin lede-ramips-mt7620-ArcherC20-squashfs-factory.bin > ArcherC20V1_tp_recovery.bin - Place ArcherC20V1_tp_recovery.bin in tftp server directory. - Configure PC with static IP 192.168.0.66/24 and tftp server. - Connect PC with one of LAN ports, press the reset button, power up the router and keep button pressed for around 6-7 seconds, until device starts downloading the file. - Router will download file from server, write it to flash and reboot. Signed-off-by: Maxim Anisimov <maxim.anisimov.ua@gmail.com>
2017-09-08 09:39:17 +00:00
c20|\
ramips: add support for Sanlinking D240 The Sanlinking Technologies D240 (http://www.sanlinking.com/en/29-dual-4g-wifi-router.html) is basically the same device as the ZBT WE826, so adding support for it in LEDE is straight forward. The differences is that the D240 has two mini-PCIe slots (instead of one), blue LEDs and supports PoE. Specification: * CPU: MT7620A * 1x 10/100Mbps POE (802.3af/802.3at) Ethernet, 4x 10/100Mbps. * 16 MB Flash. * 128 MB RAM. * 1x USB 2.0 port. * 2x mini-PCIe slots. * 2x SIM slots. * 1x 2.4Ghz WIFI. * 1x button. Wifi, USB, switch and both mini-PCIe slots are working. I have not been able to test the SD card reader. The device comes pre-installed with an older version of OpenWRT, including Luci. In order to install LEDE, you need to follow the existing procedure for updating OpenWRT/LEDE using Luci. I.e., you need to access the UI and update the firmware using the sysupgrade-image. Remember to select that you do not want to keep existing settings. The default router address is 192.168.10.1 and username/password admin/root (at least on my devices). If you brick the device, the procedure for recovery is the same as for the WE826. Please see the wiki page for that device for instructions. Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
2017-02-04 20:28:52 +00:00
d240|\
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
dap-1350|\
na930|\
ramips: Fix support for PBR-M1 board The PBR-M1 support in current OpenWrt is for the early demo board and it doesn't work on the final board.This patch fixes the support for it. The LED called pbr-m1:buzzer is a beeper connected to GPIO26 so I used gpio-beeper instead of gpio-leds. Signed-off-by: 郭传鈜 <gch981213@gmail.com> SVN-Revision: 47844
2015-12-11 15:03:50 +00:00
pbr-m1|\
ramips: add support for TP-Link RE350 The TP-Link RE350 is a wall-wart AC1200 range extender/access point with a single gigabit ethernet port and two non-detachable antennas, based on the MT7621A SoC with MT7603E and MT7612E radios. Firmware wise it is very similar to the QCA based RE450. SoC: MediaTek MT7621A (880MHz) Flash: 8MiB (Winbond W25Q64) RAM: 64MiB (DDR2) Ethernet: 1x 1Gbit Wireless: 2T2R 2.4Ghz (MT7603E) and 5GHz (MT7612E) LEDs: Power, 2.4G, 5G (blue), WPS (red and blue), ethernet link/act (green) Buttons: On/off, LED, reset, WPS Serial header at J1, 57600 8n1: Pin 1 TX Pin 2 RX Pin 3 GND Pin 4 3.3V Factory image can be uploaded directly through the stock UI. Signed-off-by: Alex Maclean <monkeh@monkeh.net>
2017-07-23 19:06:44 +00:00
re350-v1|\
ramips: add support for Asus RT-AC51U Specification: - SoC: MediaTek MT7620A (580 MHz) - RAM: 64 MiB (Winbond W9751G6JB-25) - Flash: 16 MiB (Spansion S25FL128SAIF00) - LAN: x4 100M - WAN: x1 100M - Others: USB 2.0, reset button, wps button and 9 LEDs Issues: - 5 GHz band is not functional (missing driver support) Installation: Asus windows recovery tool: - install the Asus firmware restoration utility - unplug the router, hold the reset button while powering it on - release when the power LED flashes slowly - specify a static IP on your computer: IP address: 192.168.1.75; Subnet mask 255.255.255.0 - Start the Asus firmware restoration utility, specify the sysupgrade image, and press upload TFTP Recovery method: - set computer to a static ip, 192.168.1.75 - connect computer to the LAN 1 port of the router - hold the reset button while powering on the router for a few seconds - send firmware image using a tftp client; i.e from linux: $ tftp tftp> binary tftp> connect 192.168.1.1 tftp> put lede-ramips-mt7620-rt-ac51u-squashfs-sysupgrade.bin tftp> quit Signed-off-by: Ørjan Malde <foxyred333@gmail.com>
2017-05-05 15:54:26 +00:00
rt-ac51u|\
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
rt-n13u|\
rt-n14u|\
rt-n15|\
rt-n56u|\
wl-330n|\
wl-330n3g|\
wli-tx4-ag300n|\
y1|\
y1s)
status_led="$board:blue:power"
add support for the Linksys E1700 SVN-Revision: 43186
2014-11-05 14:37:13 +00:00
;;
ramips: add support for Planex DB-WRT01 This patch add support for Planex DB-WRT01. DANBOARD route on the MT7620A SoC with two Ethernet port and a 802.11n 2.4 GHz radio. DANBOARD is Cartoon character. Signed-off-by: YuheiOKAWA <tochiro.srchack@gmail.com> SVN-Revision: 46918
2015-09-14 20:08:55 +00:00
db-wrt01|\
ramips : add support for PandoraBox D1 Signed-off-by: BangLang Huang <banglang.huang@foxmail.com>
2016-09-27 06:23:27 +00:00
esr-9753|\
pbr-d1)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
status_led="$board:orange:power"
ramips: add support for the Senao/EnGenius ESR-9753 board Signed-off-by: Artur Wronowski <arteqw@gmail.com> SVN-Revision: 29603
2011-12-23 14:27:10 +00:00
;;
ramips: improve F5D8235 V1 support This fixes the partition name for the firmware splitter, the cfi address and adds the mtd-eeprom address for wmac. It adds additional LEDs and make use of them in diag.sh and 01_leds. Please note that the ":blue:wired" LED is used because the ":blue:router" behaviour is unpredictable for failsafe indication. The issue with the router LED is that you have two states only. "off" is steady on and "on" blinks. Therefore the wired LED is more suitable. Furthermore it reuses the correct switch configuration definition to reflect the device ports and numbering. Additionally fixes the issue that the default configuration is not applied as no port 6 exists on this device. Signed-off-by: Tobias Wolf <github-NTEO@vplace.de>
2016-12-01 14:08:22 +00:00
f5d8235-v1)
status_led="$board:blue:wired"
;;
ramips: scripts updates In this patch: * rename Argus leds to avoid underscores * rename Belkin F5D8235 v1 leds from f5d8234 to f5d8235 * remove Belkin F5D8235 v1 status led defined as storage led (it was defined as usb led earlier, just in wrong place) - it should have router led as in v2 * add Argus, Sparklan and Belkin F5D8235 v2 status leds * add Belkin F5D8235 v1 and v2 usb leds * fix Belkin F5D8235 v2 network config generation and mac address axtraction * fix Sparklan board identification * add Sparklan usb led (this board doesn't have usb connector by default and the led is hidden also but if you are going to solder the connector then you'll see the led too) * add Sparklan network config generation and mac address extraction * fix empty string test in network script and... * ...sort case entries by the first board in the list Signed-off-by: Roman Yeryomin <roman@advem.lv> SVN-Revision: 29871
2012-01-23 10:23:32 +00:00
f5d8235-v2)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
status_led="$board:blue:router"
ramips: use consistent naming scheme for LEDs The upstream LED naming convention is "device:color:led-name", but it seems that many of supported boards in OpenWrt don't follow this approach. The following patch fixes this inconsistency in dts{,i} files and updates base-files scripts for ramips target: * fixes wrong indentation * keeps case statements structure in same convention as in other scripts (no empty line after ";;", no indentation for case...esac body) * fixes wrong LED names for some of boards (makes them the same as in dts{,i} files) * combines boards with same configuration (ex. set_wifi_led "rt2800pci-phy0::radio" in 01_leds) Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46664
2015-08-17 06:24:34 +00:00
;;
ramips: Add support for Thunder Timecloud Thunder Timecloud is a small NAS with MT7621A. It has 1 USB port and an SD Card slot. There is no wireless cards. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
2016-08-10 00:18:32 +00:00
f7c027|\
timecloud)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
status_led="$board:orange:status"
ramips: use consistent naming scheme for LEDs The upstream LED naming convention is "device:color:led-name", but it seems that many of supported boards in OpenWrt don't follow this approach. The following patch fixes this inconsistency in dts{,i} files and updates base-files scripts for ramips target: * fixes wrong indentation * keeps case statements structure in same convention as in other scripts (no empty line after ";;", no indentation for case...esac body) * fixes wrong LED names for some of boards (makes them the same as in dts{,i} files) * combines boards with same configuration (ex. set_wifi_led "rt2800pci-phy0::radio" in 01_leds) Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46664
2015-08-17 06:24:34 +00:00
;;
ramips: Add base-files for HiWiFi HC5x61 models HiWiFi HC5661/5761/5861 models are manufactured by http://www.hiwifi.com. These models have similar hardware specs(MT7620A + 128M DDR2 + 16M flash). This patch adds support for them. The original author is Justin Liu (rssnsj@gmail.com). I ported the patch to trunk and submitted it here with his approval. v3 fix 1: Fixed model order 2: Remove manufacturer name from model name 3: Use a hacky but prettier way to get mac address. Signed-off-by: Xiaoning Kang <kangxn@163.com> SVN-Revision: 47111
2015-10-05 10:25:47 +00:00
hc5*61|\
ramips: add support for HiWiFi HC5661A HC5661A is almost the same as HC5661 but MT7628AN is used instead of MT7620A. - MT7628AN - 128 MiB DDR2 RAM (W971GG6KB-25) - 16 MiB SPI NOR flash (W25Q128) - SD slot (not work yet) - 1+4 x 100M Ethernet - 802.11 b/g/n Wi-Fi - 3 x LED - 1 x button - UART pad on PCB (JP1: TX, RX, GND, 3.3V) The factory flash layout seems different from HC5661. "hwf_config" is renamed to "oem" and its size changes to 0x20000. It is modified accordingly in the dts file. 0x000000000000-0x000000030000 : "u-boot" 0x000000030000-0x000000040000 : "hw_panic" 0x000000040000-0x000000050000 : "Factory" 0x000000050000-0x000000160000 : "kernel" 0x000000160000-0x000000fc0000 : "rootfs" 0x000000bb0000-0x000000fc0000 : "rootfs_data" 0x000000fc0000-0x000000fe0000 : "oem" 0x000000fe0000-0x000000ff0000 : "bdinfo" 0x000000ff0000-0x000001000000 : "backup" 0x000000050000-0x000000fc0000 : "firmware" To install LEDE, enabled the "developer mode", which will *void your warranty* and open the SSH server at port 1022. sysupgrade -n -F lede-ramips-mt7628-hc5661a-squashfs-sysupgrade.bin SD slot: - Tried to add modules kmod-sdhci kmod-sdhci-mt7620, and corresponding dts block. - It will block WAN + 3xLAN ports, only one LAN works. - I'm not sure why, everything else works fine. Signed-off-by: Wang JiaWei <buaawjw@gmail.com>
2017-02-24 23:19:15 +00:00
hc5661a|\
ramips: Add JCG routers to base-files This patch adds support for JHR-N805R, JHR-N825R and JHR-N926R to various scripts in the base-files directory. Signed-off-by: Reinhard Max <reinhard@m4x.de> Reviewed-by: Torsten Duwe <duwe@lst.de> SVN-Revision: 48905
2016-03-04 08:33:09 +00:00
jhr-n805r|\
jhr-n926r|\
ramips: Add base-files for HiWiFi HC5x61 models HiWiFi HC5661/5761/5861 models are manufactured by http://www.hiwifi.com. These models have similar hardware specs(MT7620A + 128M DDR2 + 16M flash). This patch adds support for them. The original author is Justin Liu (rssnsj@gmail.com). I ported the patch to trunk and submitted it here with his approval. v3 fix 1: Fixed model order 2: Remove manufacturer name from model name 3: Use a hacky but prettier way to get mac address. Signed-off-by: Xiaoning Kang <kangxn@163.com> SVN-Revision: 47111
2015-10-05 10:25:47 +00:00
mlw221|\
mlwg2)
status_led="$board:blue:system"
;;
ramips: add support for HiWiFi HC5962 This patch adds supports for the HiWiFi HC5962(gee4) http://www.hiwifi.com Short specification: - MT7621AT + MT7612EN + 7603EN - 256MB DDR3 RAM - 128MB NAND flash - 1+3 x 1000M Ethernet - 1x USB 2.0 port. 1x USB 3.0 port. - reset button - UART pad on PCB (JP3: TX, RX, GND, 3.3V) Flash instruction: 1, Download lede-ramips-mt7621-hc5962-squashfs-factory.bin 2, Login as root via SSH on 192.168.199.1 and then copy factory.bin(using wget or nc or...) to /tmp/ 3, use the following commands: $ mtd write /tmp/lede-ramips-mt7621-hc5962-squashfs-factory.bin firmware $ mtd erase firmware_backup && reboot After reboot you should be able to login as root via SSH on 192.168.1.1 Signed-off-by: ZengFei Zhang <zhangzengfei@kunteng.org>
2017-02-22 12:47:22 +00:00
hc5962)
status_led="$board:white:status"
;;
ramips: add support for Phicomm K2P It uses one MT7615D radio chip with DBDC mode enabled. This mode allows this single chip act as an 2x2 11n radio and an 2x2 11ac radio at the same time. However mt76 doesn't support it currently so there is no wireless available. Specification: - SoC: MediaTek MT7621AT - Flash: 16 MB - RAM: 128 MB - Ethernet: 1 x WAN (10/100/1000Mbps) and 4 x LAN (10/100/1000 Mbps) - Wireless radio: MT7615D on PCIE0 - UART: 1 x UART on PCB - 57600 8N1 Issue: - Wireless radio doesn't work due to the lack of driver. Flash instruction: Using UART: 1. Configure PC with a static IP address and setup an TFTP server. 2. Put the firmware into the tftp directory. 3. Connect the UART line as described on the PCB. 4. Power up the device and press 2,then follow the instruction to set device and tftp server IP address and input the firmware file name.U-boot will then load the firmware and write it into the flash. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
2017-07-18 05:02:51 +00:00
k2p|\
m3|\
miwifi-nano)
status_led="$board:blue:status"
;;
ramips: add feature to blink led on sysupgrade Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 47373
2015-11-03 13:32:02 +00:00
linkits7688| \
linkits7688d)
[ "$1" = "upgrade" ] && status_led="mediatek:orange:wifi"
;;
ramips: add support for Intenso Memory 2 Move USB 3.0 This adds support for a rt5350-based "portable nas" solution from Intenso. The board comes with 32M RAM and 8M Flash, the built-in HDD is connected/accessible via a usb3.0<->sata bridge VLI VL701. The device has 1 Ethernet port (100M/10M), 1 micro b usb 3.0 socket (for charging the battery, or accessing the hdd directly). Wireless connectivity is provided by the rt5350 SoC [i.e.: 802.11n 1x1 2.4 GHz with a pcb antenna.] Serial, leds, wifi, ethernet and usb are tested and as far as I can tell: they are working fine (tm). Signed-off-by: Christian Lamparter <chunkeey@googlemail.com> SVN-Revision: 44001
2015-01-17 14:06:13 +00:00
m2m)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
status_led="$board:blue:wifi"
ramips: add Poray M3 support Signed-off-by: Felix Kaechele <heffer@fedoraproject.org> SVN-Revision: 37636
2013-08-01 14:30:53 +00:00
;;
ramips: add support for GL-inet GL-MT300N-V2 This patch adds supports for the GL-inet GL-MT300N-V2. Specification: - SoC: MediaTek MT7628AN - Flash: 16 MiB (W25Q128FVSG) - RAM: 128 MiB DDR - Ethernet: 1 x WAN (100 Mbps) and 1 x LAN (100 Mbps) - USB: 1 x USB 2.0 port - Button: 1 x switch button, 1 x reset button - LED: 3 x LEDS (system power led is not GPIO controller) - UART: 1 x UART on PCB (JP1: 3.3V, RX, TX, GND) Installation through Luci: - The original firmware is LEDE, so both LuCI or sysupgrade can be used. - Do not keep settings, for sysupgrade please use the -n option. Installation through bootloader webserver: - Plug power and hold reset button until red LED blink to bright. - Install sysupgrade image using web interface on 192.168.1.1. Signed-off-by: Kyson Lok <kysonlok@gmail.com> [match maximum image size with firmware partition] Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-05-17 10:18:45 +00:00
gl-mt300n-v2)
status_led="$board:red:wlan"
;;
ramips: dont replace the board name Use fixed led names and add each board variant instead of manipulating the board name. It makes the ramips board name function less different to the one used in other targets and allows to merge them with a common function. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-07 22:34:48 +00:00
m4-4M|\
m4-8M)
status_led="m4:blue:status"
;;
ramips: add Xiaomi Mi Router 3G support This commit adds support for Xiaomi Mi WiFi Router 3G. Short specification: - MT7621AT + MT7603EN + 7612EN - 256MB DDR3 RAM - 128MB NAND flash - 1+2 x 1000M Ethernet - 1x USB 3.0 port - reset button - yellow, blue, red leds Installation through telnet/ssh: - copy lede-ramips-mt7621-mir3g-squashfs-kernel1.bin and lede-ramips-mt7621-mir3g-squashfs-rootfs0.bin to usb disk or wget it from LEDE download site to /tmp - switch to /extdisks/sda1/ (if copied to USB drive) or to /tmp if wgetted from LEDE download site - run: mtd write lede-ramips-mt7621-mir3g-squashfs-kernel1.bin kernel1 - run: mtd write lede-ramips-mt7621-mir3g-squashfs-rootfs0.bin rootfs0 - run: mtd erase kernel0 - run: reboot Originally stock firmware has following partitions: - ... - kernel0 (primary kernel image) - kernel1 (secondary kernel image, used by u-boot in failsafe routine) - rootfs0 (primary rootfs) - rootfs1 (secondary rootfs in case primary fails) - overlay (used as ubi overlay) This commit squashes rootfs0, rootfs1 and overlay partitions into 1, so it can be used by LEDE fully for package installation, resulting in 117,5MiB. This device lacks hw watchdog, so adding softdog instead (stock does the same). Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
2017-08-12 14:56:11 +00:00
mir3g)
status_led="$board:yellow:status"
;;
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
miwifi-mini|\
zte-q7)
status_led="$board:red:status"
ramips: use consistent naming scheme for LEDs The upstream LED naming convention is "device:color:led-name", but it seems that many of supported boards in OpenWrt don't follow this approach. The following patch fixes this inconsistency in dts{,i} files and updates base-files scripts for ramips target: * fixes wrong indentation * keeps case statements structure in same convention as in other scripts (no empty line after ";;", no indentation for case...esac body) * fixes wrong LED names for some of boards (makes them the same as in dts{,i} files) * combines boards with same configuration (ex. set_wifi_led "rt2800pci-phy0::radio" in 01_leds) Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46664
2015-08-17 06:24:34 +00:00
;;
ramips: Adding support for AXIMCom MR-102N 3G/4G Travel Mobile Router MR-102N is a RT3050F based wireless router(32M RAM + 8M NOR flash) with 1 USB and 1 ethernet port. The original product information can be found at: http://www.aximcom.com/en/MR-102N Signed-off-by: Tai-hwa Liang <atliang@gmail.com> SVN-Revision: 45724
2015-05-23 15:27:05 +00:00
mr-102n)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
status_led="$board:amber:status"
ramips: rt305x: add support for the ZyXEL NBG-419N board SVN-Revision: 28078
2011-08-22 20:41:49 +00:00
;;
ramips: Add support to TP-Link Archer MR200 CPU: MT7620N 580MHz Flash: 8MB RAM: 64MB build-in modem 3G/4G four ethernet port 10/100Mbps Signed-off-by: Henryk Heisig <hyniu@o2.pl>
2016-09-24 19:41:43 +00:00
mr200)
status_led="$board:white:power"
;;
ramips: rt305x: add support for the Netcore NW718 board SVN-Revision: 27813
2011-07-28 10:56:32 +00:00
nw718)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
status_led="$board:amber:cpu"
ramips: rt305x: add support for the Netcore NW718 board SVN-Revision: 27813
2011-07-28 10:56:32 +00:00
;;
ramips : add support for Newifi D1 Signed-off-by: BangLang Huang <banglang.huang@foxmail.com>
2016-09-27 06:25:04 +00:00
newifi-d1)
status_led="$board:blue:status"
;;
ramips: Added Onion Omega2 and Omega2+ This patch adds support for the Onion Omega2 and Omega2+ (https://onion.io) Specifications: - SoC: MediaTek MT7688AN (580MHz, ramips) - Omega2 - RAM: 64MB DDR - Storage: 16MB NOR SPI flash onboard - Omega2+ - RAM: 128MB DDR - Storage: 32MB NOR SPI flash onboard + microSD slot - Wireless: Built into MT7688AN (mt76) with onboard 1x chip antenna and u.FL connecter - Ethernet: 1x100M pins on Omega2 & Omega2+, can use Ethernet Expansion and an Omega Dock to get a physical Ethernet port - Strongly recommend using the Omega2 & Omega2+ with a Dock (Expansion Dock, Power Dock, Arduino Dock 2, Mini Dock) - All Docks Provide: - Micro-USB port to provide power to the Omega - On the Expansion and Mini Docks, can also access the terminal (UART0) via serial - USB 2.0 socket connected to Omega - Just the Expansion Dock, Power Dock, and Arduino Dock 2 provide: - Omega GPIO breakout - Allows for connection of Omega Expansions: - Ethernet Expansion - Relay Expansion - PWM Expansion - OLED Expansion - Ethernet Expansion - Proto Expansion - Cellular Expansion Signed-off-by: Lazar Demin <lazar@onion.io>
2017-01-09 19:59:56 +00:00
omega2| \
omega2p)
status_led="$board:amber:system"
;;
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
oy-0001|\
ramips: add ZBT-WE826 32MB variant The ZBT-WG826 is available with 16 or 32 MByte of flash. Split the device tree source file, rename the currently supported 16 MByte version and add the 32 MByte variant. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-12 05:53:56 +00:00
sl-r7205)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
status_led="$board:green:wifi"
ramips: add support for Omnima MiniEMBWiFi board This patch adds support for the Omnima MiniEMBWiFi Ralink RT3050F based board. Based on a patch by Ivan Ignjatic <ivan at omnima.co.uk> SVN-Revision: 29533
2011-12-14 20:51:26 +00:00
;;
ramips: rt305x: add support for the Petatel PSR-680W Wireless CDMA Router This patch adds support for the Korean made Petatel PSR-680W Wireless CDMA Router. The platform is based on Ralink RT3052. http://wiki.openwrt.org/toh/petatel/psr-680w Signed-off-by: Dmitry Shmygov <shmygov at rambler.ru> SVN-Revision: 32450
2012-06-19 09:52:15 +00:00
psr-680w)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
status_led="$board:red:wan"
ramips: use consistent naming scheme for LEDs The upstream LED naming convention is "device:color:led-name", but it seems that many of supported boards in OpenWrt don't follow this approach. The following patch fixes this inconsistency in dts{,i} files and updates base-files scripts for ramips target: * fixes wrong indentation * keeps case statements structure in same convention as in other scripts (no empty line after ";;", no indentation for case...esac body) * fixes wrong LED names for some of boards (makes them the same as in dts{,i} files) * combines boards with same configuration (ex. set_wifi_led "rt2800pci-phy0::radio" in 01_leds) Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46664
2015-08-17 06:24:34 +00:00
;;
ramips: dont replace the board name Use fixed led names and add each board variant instead of manipulating the board name. It makes the ramips board name function less different to the one used in other targets and allows to merge them with a common function. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-07 22:34:48 +00:00
px-4885-4M|\
px-4885-8M)
status_led="px-4885:orange:wifi"
;;
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
re6500|\
whr-1166d|\
ramips: add Widora-NEO board support The Widora board is similar to the Linkit 7688 but features a larger flash capacity. Signed-off-by: Yuan Chenmang <771992497@qq.com> [Jo-Philipp Wich: Reword commit message, cleanup initial PR] Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2016-05-28 10:04:17 +00:00
whr-600d|\
widora-neo)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
status_led="$board:orange:wifi"
ramips: add preliminary support for the Asus RT-N56U board SVN-Revision: 30498
2012-02-13 15:18:04 +00:00
;;
ramips: add support for Planex MZK-EX300NP MZK-EX300NP is MT7620A based wifi repeater. Built-in power supply. 64MiB RAM, 8MiB SPI Flash, non Wired Ethernet. Signed-off-by: YuheiOKAWA <tochiro.srchack@gmail.com> SVN-Revision: 49235
2016-04-26 11:43:06 +00:00
mzk-ex300np|\
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
rt-n10-plus|\
ramips: add support for TRENDnet TEW-638APB V2 This patch add support for the TRENDnet TEW-638APB V2. Specification: - SoC: Ralink SoC RT3052F - Flash: 4MB - RAM: 32MB - Ethernet: 1x LAN (100 Mbps) - Wireless: 2.4GHz b/g/n, 2x external antenna - Buttons: 1x Reset, 1x WPS - LEDs: Power (green), Ethernet (green), WPS (green and orange), Wireless (green) - UART: 1x UART on PCB (3.3V, GND, RX, TX) - 57600 8N1 Installation via vendor firmware: - upload sysupgrade.bin image via TFTP: - stop uboot into tftp-load into option "2" - upload sysupgrade.bin image Signed-off-by: Pavlo Samko <bulldozerbsg@gmail.com>
2017-06-09 11:02:56 +00:00
tew-638apb-v2|\
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
tew-691gr|\
tew-692gr|\
ur-326n4g|\
ur-336un|\
ramips: dont replace the board name Use fixed led names and add each board variant instead of manipulating the board name. It makes the ramips board name function less different to the one used in other targets and allows to merge them with a common function. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-07 22:34:48 +00:00
wf-2881)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
status_led="$board:green:wps"
ramips: Support for Teltonika RUT5XX Hi Hartmut, Thanks for your feedback, I have reformated the patch accordingly. Added support for Teltonika RUT5XX hardware. Signed-off-by: Steffen Weinreich <steve@weinreich.org> SVN-Revision: 40907
2014-06-02 12:42:48 +00:00
;;
ramips: add support for MikroTik hEX v3 (RB750Gr3) The MikroTik hEX v3 (RB750Gr3) is a MT7621AT board which is similar to most MT7621 reference designs, it can be easily supported by this patch; however, the stock RouterBOOT bootloader has to be replaced by a MT7621 SDK U-Boot such as https://github.com/ndoo/RB750Gr3-U-Boot - U-Boot configured for the RB750Gr3 (16MiB SPI flash, 256MiB DDR3 RAM at 1200MHz). RouterBOOT, the stock bootloader, does not initialize the UART and boots silently, making it preferable to replace it with a MT7621 SDK U-Boot with UART (57600 8N1) that supports HTTP, TFTP or serial upload of sysupgrade firmware and U-Boot. Furthermore, RouterOS, the stock firmware, is contained in a proprietary modification of SquashFS without GPL sources; UART is also disabled in stock firmware. The combination of LEDE firmware generated by this PR and MT7621 SDK U-Boot expects the printed MAC address to reside at offset `0xe000` of the factory partition (absolute offset is `0x4e000`); this is similar to the factory MAC address offset for several other MT7621 devices. A 16MiB flash dump suitable for use with flashrom will be provided if/once this patch is accepted and binaries are built by LEDE buildbot. Alternatively, writing the U-Boot to the SPI flash starting at 0x0 offset and booting the board with serial console attached will allow TFTP, HTTP or serial upload of sysupgrade firmware. Signed-off-by: Andrew Yong <me@ndoo.sg>
2016-10-18 20:05:32 +00:00
rb750gr3)
ramips: RB750Gr3: Add pwr LED and buzzer to DTS use pwr LED in diag.sh Expose unused pinmux pins as GPIOs export power LED and buzzer pins Use rb750gr3:blue:pwr LED in diag.sh for boot status instead of rb750gr3:green:usr Signed-off-by: Andrew Yong <me@ndoo.sg>
2016-11-26 14:15:21 +00:00
status_led="$board:blue:pwr"
ramips: add support for MikroTik hEX v3 (RB750Gr3) The MikroTik hEX v3 (RB750Gr3) is a MT7621AT board which is similar to most MT7621 reference designs, it can be easily supported by this patch; however, the stock RouterBOOT bootloader has to be replaced by a MT7621 SDK U-Boot such as https://github.com/ndoo/RB750Gr3-U-Boot - U-Boot configured for the RB750Gr3 (16MiB SPI flash, 256MiB DDR3 RAM at 1200MHz). RouterBOOT, the stock bootloader, does not initialize the UART and boots silently, making it preferable to replace it with a MT7621 SDK U-Boot with UART (57600 8N1) that supports HTTP, TFTP or serial upload of sysupgrade firmware and U-Boot. Furthermore, RouterOS, the stock firmware, is contained in a proprietary modification of SquashFS without GPL sources; UART is also disabled in stock firmware. The combination of LEDE firmware generated by this PR and MT7621 SDK U-Boot expects the printed MAC address to reside at offset `0xe000` of the factory partition (absolute offset is `0x4e000`); this is similar to the factory MAC address offset for several other MT7621 devices. A 16MiB flash dump suitable for use with flashrom will be provided if/once this patch is accepted and binaries are built by LEDE buildbot. Alternatively, writing the U-Boot to the SPI flash starting at 0x0 offset and booting the board with serial console attached will allow TFTP, HTTP or serial upload of sysupgrade firmware. Signed-off-by: Andrew Yong <me@ndoo.sg>
2016-10-18 20:05:32 +00:00
;;
ramips: add support for STORYLiNK SAP-G3200U3 STORYLiNK SAP-G3200U3 is an AC1200 router based on MT7621AT+MT7602EN+MT7612EN. It has 128MB DDR3, 8MB NOR FLASH, 5-port Gbps switch and 1x USB 3.0. The following patch adds support for this device. Tested and working: * ethernet * both WiFi radios * USB 3.0 * buttons * ethernet switch and USB diag LEDs * UART * GPIOs Tested and not working: * LEDs for WiFi radios (connected with WiFi chips, not supported in mt76?) * failsafe mode (known problem, needs workaround like other MTK based devices) More information in Wiki: http://wiki.openwrt.org/toh/storylink/sap-g3200u3 Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46454
2015-07-24 09:09:22 +00:00
sap-g3200u3)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
status_led="$board:green:usb"
add Ralink V11ST-FE board support This board is equipped with: - 4MB of NOR Flash - 32MB of SDRAM - IC+ IP175C switch - one Mini-PCI slot SVN-Revision: 30561
2012-02-15 21:13:11 +00:00
;;
ramips: add diag support for RT-N15 and PWH2004 Also sort the board names alphabetically. SVN-Revision: 27478
2011-07-06 08:05:00 +00:00
v22rw-2x2)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
status_led="$board:green:security"
ramips: Buffalo WZR-AGL300NH target support I got work with this patch. Ethernet switch (includes VLAN), WiFi connected via PCIe, LEDs, buttons. In mtd partion map of DTS file, I renamed Linux firmware regions (kernel + root squashfs) to “firmware”because it allows kernel to split kernel and roots and rootfsdata. signed-off-by: ngc@ff.iij4u.or.jp —— —— SVN-Revision: 44470
2015-02-16 21:19:18 +00:00
;;
ramips: dont replace the board name Use fixed led names and add each board variant instead of manipulating the board name. It makes the ramips board name function less different to the one used in other targets and allows to merge them with a common function. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-07 22:34:48 +00:00
vocore-8M|\
vocore-16M)
status_led="vocore:green:status"
;;
ramips: add support for VoCore2 This patch adds support for the VoCore VoCore2 and its complementary "ultimate" dock. Specifications: - SoC: MediaTek MT7628AN (580MHz, ramips) - RAM: 128MB DDR2 166MHz - Storage: 16MB NOR SPI flash onboard + microSD slot on dock - Wireless: Built into MT7628AN (mt76) with 1T1R firmware on VoCore2 boards with onboard 1x chip antenna - Ethernet: 1x100M (port0) on dock, 1x100M (port2) on PCB header - Dock hardware: - USB 2.0 socket - MicroSD socket - 100Mbps Ethernet x1 - 3.5mm headphone jack (TRRS) connected to Everest Semi ES8388 I2S DAC/ADC (support WIP) - Micro USB for power and console (UART2) Initial installation: - VoCore2 comes preinstalled with a fork of OpenWrt CC and AP on SSID "VoCore2" - Connect to VoCore2 by Ethernet or Wi-Fi - `ssh root@192.168.1.1` (password is "vocore") - scp/wget/etc. LEDE sysupgrade.bin to VoCore2 - `sysupgrade -n <your image>.bin` (don't keep old config, as the original firmware uses Ralink SDK Wi-Fi drivers and not mt76+mac80211) - after sysupgrade completes, Wi-Fi will be disabled by default so use Ethernet or the micro USB console to configure Wi-Fi again Signed-off-by: Andrew Yong <me@ndoo.sg>
2017-01-08 06:30:10 +00:00
vocore2)
status_led="$board:fuchsia:status"
;;
ramips: add support for the VoCore2 Lite The VoCore2 Lite uses the same PCB as the Vocore2. This patch moves the common VoCore2 parts into dtsi. Removed memory node in the device tree source file. Memory is detected automatically. http://vocore.io/ http://vonger.net/ http://vonger.cn/ Specifications: - SoC: MediaTek MT7688AN - RAM: 64MB DDR2 EtronTech EM68B16CWQH-25H - Flash: 8MB NOR SPI Flash GigaDevice GD25Q64CWIG - Wireless: Built into MT7688AN with onboard IPEX connector Firmware installation: - VoCore2-Lite ships with firmware forked from OpenWrt. - Installation from the bootloader is recommended. - If using luci/sysupgrade use the -n option (do not keep settings) original firmware uses a modified proprietary MediaTek wireless driver. - The wireless is disabled by default in LEDE. - If reverting to factory firmware using the bootloader is recommended. Signed-off-by: L. D. Pinney <ldpinney@gmail.com> Tested by: Noble Pepper <noblepepper@gmail.com>
2017-08-03 20:09:06 +00:00
vocore2lite)
status_led="$board:green:status"
;;
ramips: Fix support for PBR-M1 board The PBR-M1 support in current OpenWrt is for the early demo board and it doesn't work on the final board.This patch fixes the support for it. The LED called pbr-m1:buzzer is a beeper connected to GPIO26 so I used gpio-beeper instead of gpio-leds. Signed-off-by: 郭传鈜 <gch981213@gmail.com> SVN-Revision: 47844
2015-12-11 15:03:50 +00:00
w306r-v20|\
ramips: add additional support for MQmaker WiTi board The board is based on mt7621AT cpu, and has 16mb nor flash, 256mb of ram, 2 sata ports, microsd card slot, 1 USB 3.0 port and at least one 2.4 and one 5 ghz antenna. This is the 6th submission that adds support for XHCI in the device tree file, along with switching the location of the 2 radio's and addition of the kmod-i2c-mt7621 in the default packages of the profile. Signed-off-by: Sebastian Careba <nitroshift@yahoo.com> SVN-Revision: 47845
2015-12-11 15:04:13 +00:00
witi|\
ramips: Fix support for PBR-M1 board The PBR-M1 support in current OpenWrt is for the early demo board and it doesn't work on the final board.This patch fixes the support for it. The LED called pbr-m1:buzzer is a beeper connected to GPIO26 so I used gpio-beeper instead of gpio-leds. Signed-off-by: 郭传鈜 <gch981213@gmail.com> SVN-Revision: 47844
2015-12-11 15:03:50 +00:00
zbt-wr8305rt)
status_led="$board:green:sys"
;;
ramips: add support for Buffalo WCR-1166DS Buffalo WCR-1166DS is a small wireless router with - MT7628AN + MT7612E - 64MiB DDR2 SDRAM - 16MiB SPI flash - 2T2R 11ac/a/b/g/n Wi-Fi - 2x 10/100M ethernet switch - 8x programmable LED - 3x button - UART pad on PCB (J2: 3.3V, GND, TX, RX) factory image can be installed via stock web UI. due to the "dual image" function in the bootloader, the second half of the SPI flash ("firmware2" partition) cannot be used as a part of the file system. Signed-off-by: FUKAUMI Naoki <naobsd@gmail.com>
2017-01-28 16:05:56 +00:00
wcr-1166ds|\
whr-300hp2|\
wsr-1166|\
wsr-600)
status_led="$board:green:power"
;;
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
wcr-150gn|\
ramips: initial support for Sitecom WL-351 v1 002 This add support for the Sitecom WL-351 v1 002. In principle the Engenius ESR9850 should also work with this, but I don't have the hardware to test it. Since an external gigabit switch (RTL8366RB) is used, I had to modify the ramips_esw driver to add a 'bypass' mode, which just configures it to not filter the vlan tags. Also two initialization words (FCT2 and FPA2) are set to different values by u-boot than what the driver is using and it only seems to work correctly when they not overridden by the driver, so I added them to the platform specific data as reg_initval_fct2 and reg_initval_fpa2. With this wired lan works as expected, however I'm still having some trouble with the wireless lan: It only works after I rmmod & re-insmod rt2800pci and then reconfigure it in the webinterface, but not directly after rebooting. The symptom of this is wpad saying: Dec 20 15:45:09 OpenWrt daemon.info hostapd: wlan1: STA <notebookmac> IEEE 802.11: associated (aid 1) Dec 20 15:45:09 OpenWrt daemon.info hostapd: wlan1: STA <notebookmac> WPA: pairwise key handshake completed (RSN) Dec 20 15:45:22 OpenWrt daemon.info hostapd: wlan1: STA <notebookmac> IEEE 802.11: authenticated But wpa_supplicant on the client saying: Authentication with <wl351mac> timed out. Signed-off-by: Tobias Diedrich <ranma+openwrt@tdiedrich.de> SVN-Revision: 29604
2011-12-23 14:27:16 +00:00
wl-351)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
status_led="$board:amber:power"
ramips: use consistent naming scheme for LEDs The upstream LED naming convention is "device:color:led-name", but it seems that many of supported boards in OpenWrt don't follow this approach. The following patch fixes this inconsistency in dts{,i} files and updates base-files scripts for ramips target: * fixes wrong indentation * keeps case statements structure in same convention as in other scripts (no empty line after ";;", no indentation for case...esac body) * fixes wrong LED names for some of boards (makes them the same as in dts{,i} files) * combines boards with same configuration (ex. set_wifi_led "rt2800pci-phy0::radio" in 01_leds) Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46664
2015-08-17 06:24:34 +00:00
;;
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
whr-g300n|\
ramips: add support for Zbtlink ZBT-WE2026 This patch adds support for the Zbtlink ZBT-WE2026. Specification: - SoC: MediaTek MT7620N (580MHz) - RAM: 64 MiB - Flash: 8 MiB SPI - LAN: 4x100M - WAN: 1x100M Installation through bootloader webserver: - With the power unplugged press and hold reset button. - Plug power and hold reset button until LED starts to blink. - Install sysupgrade image using web interface on 192.168.1.1. Signed-off-by: Vaclav Svoboda <svoboda@neng.cz>
2017-03-15 08:37:05 +00:00
wlr-6000|\
zbt-we2026)
ramips: add support for Sitecom WLR-6000 The Sitecom firmware upgrade file has SENAO_FIRMWARE_TYPE 2 set. This looks rather wrong since SENAO_FIRMWARE_TYPE 2 is kernel only but the file is way to big for only including a kernel. The factory image need to have the dlf file extension. Otherwise the Sitecom firmware rejects the file. The stock firmware uses the following mac addresses: LAN: 00:0C:F6:AA:BB:D8 (u-boot env: ethaddr) 2,4: 00:0C:F6:AA:BB:D8 (EEPROM) 5: 00:0C:F6:AA:BB:DC (EEPROM) WAN: 00:0C:F6:AA:C8:43 (u-boot env: wanaddr) Assuming the mac address range :D8 to :DC is reserved for this device, the MAC addresses were reorder to have a unique MAC address for each interface: 2.4GHz: 00:0C:F6:AA:BB:D8 LAN: 00:0C:F6:AA:BB:D9 WAN: 00:0C:F6:AA:BB:DA 5 GHz: 00:0C:F6:AA:BB:DC The first MAC is assigned to the 2.4GHz WiFi interface to keep compatibility with the SSIDs printed on the case, which have the last three sextets of the MAC address appended. There are still issues with the rt2x00 driver. It is not possible to use both wireless interfaces at the same time. The 2.4 GHz wireless (PCIe) only works if the internal 5GHz wireless is/has been enabled or used for scanning. The internal 5GHz wireless only works if the 2.4GHz wireless (PCIe) was never enabled. Disabling the 2.4Ghz after it was enabled will result in stations seeing the 5Ghz AP but are unable to connect. Due to the not optimal working wifi the manufacture, backup and storage partitions of the OEM firmware are kept for now to allow an easy switch back to the Sitecom firmware. Signed-off-by: Jasper Scholte <NightNL@outlook.com> Signed-off-by: Mathias Kresin <dev@kresin.me>
2016-08-14 21:30:44 +00:00
status_led="$board:red:power"
;;
ramips: use consistent naming scheme for LEDs The upstream LED naming convention is "device:color:led-name", but it seems that many of supported boards in OpenWrt don't follow this approach. The following patch fixes this inconsistency in dts{,i} files and updates base-files scripts for ramips target: * fixes wrong indentation * keeps case statements structure in same convention as in other scripts (no empty line after ";;", no indentation for case...esac body) * fixes wrong LED names for some of boards (makes them the same as in dts{,i} files) * combines boards with same configuration (ex. set_wifi_led "rt2800pci-phy0::radio" in 01_leds) Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46664
2015-08-17 06:24:34 +00:00
wzr-agl300nh)
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts Instead of using board name provided explicitly as text in LED name, ex.: [...] mlwg2) status_led="mlwg2:blue:system" [...] use $board variable, which allows to combine together multiple boards with same color and LED names, ex: [...] mlw221|\ mlwg2) status_led="$board:blue:system" [...] The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically. One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name"). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46665
2015-08-17 06:24:47 +00:00
status_led="$board:green:router"
ralink: add support for na930 Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 39611
2014-02-18 13:33:25 +00:00
;;
ramips: Added WIZnet WizFi630A Platform based on Ralink RT5350 This patch is to add the WIZnet WizFi630A board as a new platform. The board is in mini pci express form factor. Signed-off-by: Tobias Welz <tw@wiznet.eu> SVN-Revision: 46921
2015-09-14 20:09:31 +00:00
wizfi630a)
status_led="$board::run"
;;
ramips: dont replace the board name Use fixed led names and add each board variant instead of manipulating the board name. It makes the ramips board name function less different to the one used in other targets and allows to merge them with a common function. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-07 22:34:48 +00:00
wr512-3gn-4M|\
wr512-3gn-8M)
status_led="wr512-3gn:green:wps"
;;
ralink: add WRTnode2 platform and led support Signed-off-by: xzmu <xzmu@wrtnode.com> SVN-Revision: 48049
2016-01-01 21:19:50 +00:00
wrtnode2r | \
wrtnode2p | \
wrtnode)
status_led="wrtnode:blue:indicator"
;;
ramips: dont replace the board name Use fixed led names and add each board variant instead of manipulating the board name. It makes the ramips board name function less different to the one used in other targets and allows to merge them with a common function. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-07 22:34:48 +00:00
wt3020-4M|\
wt3020-8M)
status_led="wt3020:blue:power"
;;
ramips: Add support for ZBT-CPE102 - CPU: MT7620N 580MHz - Flash: 8MB - RAM: 64MB - build-in minipcie slot for modem 3G/4G - one ethernet port 10/100Mbps Signed-off-by: Cezary Jackiewicz <cezary@eko.one.pl>
2016-09-25 19:09:31 +00:00
zbt-cpe102)
status_led="$board:green:4g-0"
;;
ramips: add ZBT-WE826 32MB variant The ZBT-WG826 is available with 16 or 32 MByte of flash. Split the device tree source file, rename the currently supported 16 MByte version and add the 32 MByte variant. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-12 05:53:56 +00:00
zbt-we826-16M|\
zbt-we826-32M)
ramips: use the ZBT-WE826 power LED for status indication Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-12 05:56:40 +00:00
status_led="zbt-we826:green:power"
ramips: add ZBT-WE826 32MB variant The ZBT-WG826 is available with 16 or 32 MByte of flash. Split the device tree source file, rename the currently supported 16 MByte version and add the 32 MByte variant. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-12 05:53:56 +00:00
;;
ramips: rename Digineo AC1200 Pro to ZBT-WG3526 32MB The Digineo AC1200 Pro is the 32MB flash variant of the ZBT-WG3526 with unpopulated/exposed sdhci slot. Rename to board to the OEM/ODM name and add the sdhci kernel module to use it for multiple clones. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-01 08:46:44 +00:00
zbt-wg3526-16M|\
zbt-wg3526-32M)
ramips: prepare ZBT-WG3526 for hardware variants The ZBT-WG3526 is available with 16 or 32 MByte of flash. Rename the current supported 16MByte version to indicate which flash size variant is supported. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-04-07 21:52:27 +00:00
status_led="zbt-wg3526:green:status"
;;
ramips: add sysupgrade and status LED support for HW550-3G This patch adds sysupgrade and status LED support for the Aztech HW550-3G. Some LED GPIOs were changed for clarity. Signed-off-by: Layne Edwards <ledwards76@gmail.com> SVN-Revision: 26320
2011-03-27 19:19:40 +00:00
esac
ramips: add diag support SVN-Revision: 20799
2010-04-11 17:47:23 +00:00
}
set_state() {
ramips: add feature to blink led on sysupgrade Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 47373
2015-11-03 13:32:02 +00:00
get_status_led $1
ramips: add diag support SVN-Revision: 20799
2010-04-11 17:47:23 +00:00
case "$1" in
preinit)
ramips: migrate to common led helper functions [juhosg: migrate to status_led_blink_{preinit,failsafe} helpers] Signed-off-by: Michael Heimpold <mhei@heimpold.de> Signed-off-by: Gabor Juhos <juhosg@openwrt.org> SVN-Revision: 35652
2013-02-18 09:56:29 +00:00
status_led_blink_preinit
ramips: add diag support SVN-Revision: 20799
2010-04-11 17:47:23 +00:00
;;
failsafe)
ramips: migrate to common led helper functions [juhosg: migrate to status_led_blink_{preinit,failsafe} helpers] Signed-off-by: Michael Heimpold <mhei@heimpold.de> Signed-off-by: Gabor Juhos <juhosg@openwrt.org> SVN-Revision: 35652
2013-02-18 09:56:29 +00:00
status_led_blink_failsafe
ramips: add diag support SVN-Revision: 20799
2010-04-11 17:47:23 +00:00
;;
ramips: add feature to blink led on sysupgrade Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 47373
2015-11-03 13:32:02 +00:00
upgrade | \
add "preinit_regular" diag.sh set_state argument This new argument is used right after starting regular preinit (which happens if failsafe wasn't triggered). The main purpose of "preinit" argument is to indicate that failsafe can be triggered, however we were missing a way to inform user that we don't wait for a trigger anymore. With this change it's clear when failsafe mode can be triggered. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 43715
2014-12-15 10:37:00 +00:00
preinit_regular)
status_led_blink_preinit_regular
;;
ramips: add diag support SVN-Revision: 20799
2010-04-11 17:47:23 +00:00
done)
status_led_on
;;
esac
}
Reference in a new issue Copy permalink