nils/gluon
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
55da2a7b0e
gluon/docs/user/supported_devices.rst

388 lines
4.8 KiB
ReStructuredText
Raw Normal View History

docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
Supported Devices & Architectures
=================================
ath79-generic: add support for TP-Link Archer C6v2 Hardware specification: - SOC: Qualcomm QCA9563 @ 775MHz - Flash: GigaDevice GD25Q64CSIG (8MiB) - RAM: Zentel A3R1GE40JBF (128 MiB DDR2) - Ethernet: Qualcomm QCA8337N: 4x 1Gbps LAN + 1x 1Gbps WAN - Wireless: - 2.4GHz (bgn) QCA9563 integrated (3x3) - 5GHz (ac) Qualcomm QCA9886 (2x2) - Button: 1x power, 1x reset, 1x wps - LED: 6x LEDs: power, wlan2g, wlan5g, lan, wan, wps - UART: There's no UART header on the board
2019-10-31 13:13:43 +00:00
ath79-generic
--------------
ath79-generic: (re)add AVM Fritz!WLAN Repeater 450e (#2420) Gone due to commit 45c84a117bf8 ("ar71xx: drop target")
2022-03-23 19:14:51 +00:00
* AVM
- Fritz!WLAN Repeater 450E [#avmflash]_
ath79-generic: add support for devolo WiFi pro 1200i (#1871)
2019-11-20 12:39:22 +00:00
* devolo
docs: clarify WAN port on LAN-only devices At the December 2019 review day, the behavior for LAN only devices was defined. Such devices will use each LAN port as WAN.
2019-12-03 18:19:39 +00:00
- WiFi pro 1200e [#lan_as_wan]_
ath79-generic: add support for devolo WiFi pro 1200i (#1871)
2019-11-20 12:39:22 +00:00
- WiFi pro 1200i
ath79-generic: add support for devolo WiFi pro 1750c (#1875)
2019-11-22 00:45:00 +00:00
- WiFi pro 1750c
docs: clarify WAN port on LAN-only devices At the December 2019 review day, the behavior for LAN only devices was defined. Such devices will use each LAN port as WAN.
2019-12-03 18:19:39 +00:00
- WiFi pro 1750e [#lan_as_wan]_
ath79-generic: add support for devolo WiFi pro 1750i
2019-11-20 13:20:27 +00:00
- WiFi pro 1750i
ath79-generic: add support for devolo WiFi pro 1750x
2019-11-21 09:30:56 +00:00
- WiFi pro 1750x
ath79-generic: add support for devolo WiFi pro 1200i (#1871)
2019-11-20 12:39:22 +00:00
ath79-generic: add support for D-Link DAP-2660 A1 (#2414) Signed-off-by: Sebastian Schaper <openwrt@sebastianschaper.net>
2022-03-23 22:35:39 +00:00
* D-Link
ath79: migrate D-Link DAP-1330 and DIR-550 from ar71xx (#2417) also add DAP-1365, which is a different case variant of DAP-1330 Signed-off-by: Sebastian Schaper <openwrt@sebastianschaper.net>
2022-03-25 21:23:55 +00:00
- DAP-1330 A1 [#lan_as_wan]_
- DAP-1365 A1 [#lan_as_wan]_
ath79-generic: add support for D-Link DAP-2660 A1 (#2414) Signed-off-by: Sebastian Schaper <openwrt@sebastianschaper.net>
2022-03-23 22:35:39 +00:00
- DAP-2660 A1 [#lan_as_wan]_
ath79: migrate D-Link DAP-1330 and DIR-550 from ar71xx (#2417) also add DAP-1365, which is a different case variant of DAP-1330 Signed-off-by: Sebastian Schaper <openwrt@sebastianschaper.net>
2022-03-25 21:23:55 +00:00
- DIR-505 A1 [#lan_as_wan]_
- DIR-505 A2 [#lan_as_wan]_
ath79-generic: add support for D-Link DAP-2660 A1 (#2414) Signed-off-by: Sebastian Schaper <openwrt@sebastianschaper.net>
2022-03-23 22:35:39 +00:00
ath79-generic: add support for Enterasys WS-AP3705i (#2332)
2021-10-31 23:38:36 +00:00
* Enterasys
- WS-AP3705i
ath79-generic: add support for GL.iNet GL-AR300M-Lite
2020-01-28 23:47:43 +00:00
* GL.iNet
- GL-AR300M-Lite
ath79-generic: add support for Joy-IT JT-OR750i (#2282)
2021-07-30 18:16:34 +00:00
* Joy-IT
- JT-OR750i
ath79-generic: add support for GL.iNet GL-AR300M-Lite
2020-01-28 23:47:43 +00:00
* OCEDO
ath79-generic: add support for OCEDO Raccoon (#1869)
2019-11-20 12:46:18 +00:00
- Raccoon
ath79-generic: add support for Onion Omega (#2306) * ath79-generic: add support for Onion Omega support was previously dropped in commit 45c84a117bf8 ("ar71xx: drop target") * fixup! ath79-generic: add support for Onion Omega * fixup! ath79-generic: add support for Onion Omega
2021-09-04 15:42:44 +00:00
* Onion
- Omega [#modular_ethernet]_
ath79-generic: Add support for OpenMesh A60 Device specifications: ====================== * Qualcomm/Atheros QCA9558 ver 1 rev 0 * 720/600/240 MHz (CPU/DDR/AHB) * 128 MB of RAM * 16 MB of SPI NOR flash - 2x 7 MB available; but one of the 7 MB regions is the recovery image * 3T3R 2.4 GHz Wi-Fi (11n) * 3T3R 5 GHz Wi-Fi (11ac) * multi-color LED (controlled via red/green/blue GPIOs) * 1x GPIO-button (reset) * external h/w watchdog (enabled by default)) * TTL pins are on board (arrow points to VCC, then follows: GND, TX, RX) * 2x ethernet - eth0 + Label: Ethernet 1 + AR8035 ethernet PHY (RGMII) + 10/100/1000 Mbps Ethernet + 802.3af POE + used as WAN interface - eth1 + Label: Ethernet 2 + AR8031 ethernet PHY (SGMII) + 10/100/1000 Mbps Ethernet + used as LAN interface * 1x USB * internal antennas Flashing instructions: ====================== Various methods can be used to install the actual image on the flash. Two easy ones are: ap51-flash ---------- The tool ap51-flash (https://github.com/ap51-flash/ap51-flash) should be used to transfer the image to the u-boot when the device boots up. initramfs from TFTP ------------------- The serial console must be used to access the u-boot shell during bootup. It can then be used to first boot up the initramfs image from a TFTP server (here with the IP 192.168.1.21): setenv serverip 192.168.1.21 setenv ipaddr 192.168.1.1 tftpboot 0c00000 <filename-of-initramfs-kernel>.bin && bootm $fileaddr The actual sysupgrade image can then be transferred (on the LAN port) to the device via scp <filename-of-squashfs-sysupgrade>.bin root@192.168.1.1:/tmp/ On the device, the sysupgrade must then be started using sysupgrade -n /tmp/<filename-of-squashfs-sysupgrade>.bin
2021-10-10 15:02:56 +00:00
* OpenMesh
ath79-generic: Add support for OpenMesh A40 Device specifications: ====================== * Qualcomm/Atheros QCA9558 ver 1 rev 0 * 720/600/240 MHz (CPU/DDR/AHB) * 128 MB of RAM * 16 MB of SPI NOR flash - 2x 7 MB available; but one of the 7 MB regions is the recovery image * 2T2R 2.4 GHz Wi-Fi (11n) * 2T2R 5 GHz Wi-Fi (11ac) * multi-color LED (controlled via red/green/blue GPIOs) * 1x GPIO-button (reset) * external h/w watchdog (enabled by default)) * TTL pins are on board (arrow points to VCC, then follows: GND, TX, RX) * 2x ethernet - eth0 + Label: Ethernet 1 + AR8035 ethernet PHY (RGMII) + 10/100/1000 Mbps Ethernet + 802.3af POE + used as WAN interface - eth1 + Label: Ethernet 2 + AR8035 ethernet PHY (SGMII) + 10/100/1000 Mbps Ethernet + used as LAN interface * 1x USB * internal antennas Flashing instructions: ====================== Various methods can be used to install the actual image on the flash. Two easy ones are: ap51-flash ---------- The tool ap51-flash (https://github.com/ap51-flash/ap51-flash) should be used to transfer the image to the u-boot when the device boots up. initramfs from TFTP ------------------- The serial console must be used to access the u-boot shell during bootup. It can then be used to first boot up the initramfs image from a TFTP server (here with the IP 192.168.1.21): setenv serverip 192.168.1.21 setenv ipaddr 192.168.1.1 tftpboot 0c00000 <filename-of-initramfs-kernel>.bin && bootm $fileaddr The actual sysupgrade image can then be transferred (on the LAN port) to the device via scp <filename-of-squashfs-sysupgrade>.bin root@192.168.1.1:/tmp/ On the device, the sysupgrade must then be started using sysupgrade -n /tmp/<filename-of-squashfs-sysupgrade>.bin
2021-10-10 15:04:31 +00:00
- A40
ath79-generic: Add support for OpenMesh A60 Device specifications: ====================== * Qualcomm/Atheros QCA9558 ver 1 rev 0 * 720/600/240 MHz (CPU/DDR/AHB) * 128 MB of RAM * 16 MB of SPI NOR flash - 2x 7 MB available; but one of the 7 MB regions is the recovery image * 3T3R 2.4 GHz Wi-Fi (11n) * 3T3R 5 GHz Wi-Fi (11ac) * multi-color LED (controlled via red/green/blue GPIOs) * 1x GPIO-button (reset) * external h/w watchdog (enabled by default)) * TTL pins are on board (arrow points to VCC, then follows: GND, TX, RX) * 2x ethernet - eth0 + Label: Ethernet 1 + AR8035 ethernet PHY (RGMII) + 10/100/1000 Mbps Ethernet + 802.3af POE + used as WAN interface - eth1 + Label: Ethernet 2 + AR8031 ethernet PHY (SGMII) + 10/100/1000 Mbps Ethernet + used as LAN interface * 1x USB * internal antennas Flashing instructions: ====================== Various methods can be used to install the actual image on the flash. Two easy ones are: ap51-flash ---------- The tool ap51-flash (https://github.com/ap51-flash/ap51-flash) should be used to transfer the image to the u-boot when the device boots up. initramfs from TFTP ------------------- The serial console must be used to access the u-boot shell during bootup. It can then be used to first boot up the initramfs image from a TFTP server (here with the IP 192.168.1.21): setenv serverip 192.168.1.21 setenv ipaddr 192.168.1.1 tftpboot 0c00000 <filename-of-initramfs-kernel>.bin && bootm $fileaddr The actual sysupgrade image can then be transferred (on the LAN port) to the device via scp <filename-of-squashfs-sysupgrade>.bin root@192.168.1.1:/tmp/ On the device, the sysupgrade must then be started using sysupgrade -n /tmp/<filename-of-squashfs-sysupgrade>.bin
2021-10-10 15:02:56 +00:00
- A60
ath79-generic: Add support for OpenMesh MR600 v2 Device specifications: ====================== * Qualcomm/Atheros AR9344 rev 2 * 560/450/225 MHz (CPU/DDR/AHB) * 128 MB of RAM * 16 MB of SPI NOR flash - 2x 7 MB available; but one of the 7 MB regions is the recovery image * 2T2R 2.4 GHz Wi-Fi * 2T2R 5 GHz Wi-Fi * 8x GPIO-LEDs (6x wifi, 1x wps, 1x power) * 1x GPIO-button (reset) * external h/w watchdog (enabled by default)) * TTL pins are on board (arrow points to VCC, then follows: GND, TX, RX) * 1x ethernet - AR8035 ethernet PHY (RGMII) - 10/100/1000 Mbps Ethernet - 802.3af POE - used as LAN interface * 12-24V 1A DC * internal antennas Flashing instructions: ====================== Various methods can be used to install the actual image on the flash. Two easy ones are: ap51-flash ---------- The tool ap51-flash (https://github.com/ap51-flash/ap51-flash) should be used to transfer the image to the u-boot when the device boots up. initramfs from TFTP ------------------- The serial console must be used to access the u-boot shell during bootup. It can then be used to first boot up the initramfs image from a TFTP server (here with the IP 192.168.1.21): setenv serverip 192.168.1.21 setenv ipaddr 192.168.1.1 tftpboot 0c00000 <filename-of-initramfs-kernel>.bin && bootm $fileaddr The actual sysupgrade image can then be transferred (on the LAN port) to the device via scp <filename-of-squashfs-sysupgrade>.bin root@192.168.1.1:/tmp/ On the device, the sysupgrade must then be started using sysupgrade -n /tmp/<filename-of-squashfs-sysupgrade>.bin Gluon image name change ======================= The device had the image name "openmesh-mr600v2" in older versions of Gluon. This had to be changed with the new name in the device trees of the ath79 device tree.
2021-10-10 15:14:16 +00:00
- MR600 (v1, v2)
ath79-generic: Add support for OpenMesh MR900 v2 Device specifications: ====================== * Qualcomm/Atheros QCA9558 ver 1 rev 0 * 720/600/240 MHz (CPU/DDR/AHB) * 128 MB of RAM * 16 MB of SPI NOR flash - 2x 7 MB available; but one of the 7 MB regions is the recovery image * 3T3R 2.4 GHz Wi-Fi * 3T3R 5 GHz Wi-Fi * 6x GPIO-LEDs (2x wifi, 2x status, 1x lan, 1x power) * 1x GPIO-button (reset) * external h/w watchdog (enabled by default)) * TTL pins are on board (arrow points to VCC, then follows: GND, TX, RX) * 1x ethernet - AR8035 ethernet PHY (RGMII) - 10/100/1000 Mbps Ethernet - 802.3af POE - used as LAN interface * 12-24V 1A DC * internal antennas Flashing instructions: ====================== Various methods can be used to install the actual image on the flash. Two easy ones are: ap51-flash ---------- The tool ap51-flash (https://github.com/ap51-flash/ap51-flash) should be used to transfer the image to the u-boot when the device boots up. initramfs from TFTP ------------------- The serial console must be used to access the u-boot shell during bootup. It can then be used to first boot up the initramfs image from a TFTP server (here with the IP 192.168.1.21): setenv serverip 192.168.1.21 setenv ipaddr 192.168.1.1 tftpboot 0c00000 <filename-of-initramfs-kernel>.bin && bootm $fileaddr The actual sysupgrade image can then be transferred (on the LAN port) to the device via scp <filename-of-squashfs-sysupgrade>.bin root@192.168.1.1:/tmp/ On the device, the sysupgrade must then be started using sysupgrade -n /tmp/<filename-of-squashfs-sysupgrade>.bin Gluon image name change ======================= The device had the image name "openmesh-mr900v2" in older versions of Gluon. This had to be changed with the new name in the device trees of the ath79 device tree.
2021-10-10 15:16:51 +00:00
- MR900 (v1, v2)
ath79-generic: Add support for OpenMesh MR1750 v2 Device specifications: ====================== * Qualcomm/Atheros QCA9558 ver 1 rev 0 * 720/600/240 MHz (CPU/DDR/AHB) * 128 MB of RAM * 16 MB of SPI NOR flash - 2x 7 MB available; but one of the 7 MB regions is the recovery image * 3T3R 2.4 GHz Wi-Fi (11n) * 3T3R 5 GHz Wi-Fi (11ac) * 6x GPIO-LEDs (2x wifi, 2x status, 1x lan, 1x power) * 1x GPIO-button (reset) * external h/w watchdog (enabled by default)) * TTL pins are on board (arrow points to VCC, then follows: GND, TX, RX) * 1x ethernet - AR8035 ethernet PHY (RGMII) - 10/100/1000 Mbps Ethernet - 802.3af POE - used as LAN interface * 12-24V 1A DC * internal antennas Flashing instructions: ====================== Various methods can be used to install the actual image on the flash. Two easy ones are: ap51-flash ---------- The tool ap51-flash (https://github.com/ap51-flash/ap51-flash) should be used to transfer the image to the u-boot when the device boots up. initramfs from TFTP ------------------- The serial console must be used to access the u-boot shell during bootup. It can then be used to first boot up the initramfs image from a TFTP server (here with the IP 192.168.1.21): setenv serverip 192.168.1.21 setenv ipaddr 192.168.1.1 tftpboot 0c00000 <filename-of-initramfs-kernel>.bin && bootm $fileaddr The actual sysupgrade image can then be transferred (on the LAN port) to the device via scp <filename-of-squashfs-sysupgrade>.bin root@192.168.1.1:/tmp/ On the device, the sysupgrade must then be started using sysupgrade -n /tmp/<filename-of-squashfs-sysupgrade>.bin Gluon image name change ======================= The device had the image name "openmesh-mr1750v2" in older versions of Gluon. This had to be changed with the new name in the device trees of the ath79 device tree.
2021-10-10 15:19:29 +00:00
- MR1750 (v1, v2)
ath79-generic: Add support for OpenMesh OM2P v4 Device specifications: ====================== * Qualcomm/Atheros QCA9533 v2 * 650/600/217 MHz (CPU/DDR/AHB) * 64 MB of RAM * 16 MB of SPI NOR flash - 2x 7 MB available; but one of the 7 MB regions is the recovery image * 2x 10/100 Mbps Ethernet * 1T1R 2.4 GHz Wi-Fi * 6x GPIO-LEDs (3x wifi, 2x ethernet, 1x power) * 1x GPIO-button (reset) * external h/w watchdog (enabled by default) * TTL pins are on board (arrow points to VCC, then follows: GND, TX, RX) * 2x fast ethernet - eth0 + Label: Ethernet 1 + 24V passive POE (mode B) - eth1 + Label: Ethernet 2 + 802.3af POE + builtin switch port 1 * 12-24V 1A DC * external antenna Flashing instructions: ====================== Various methods can be used to install the actual image on the flash. Two easy ones are: ap51-flash ---------- The tool ap51-flash (https://github.com/ap51-flash/ap51-flash) should be used to transfer the image to the u-boot when the device boots up. initramfs from TFTP ------------------- The serial console must be used to access the u-boot shell during bootup. It can then be used to first boot up the initramfs image from a TFTP server (here with the IP 192.168.1.21): setenv serverip 192.168.1.21 setenv ipaddr 192.168.1.1 tftpboot 0c00000 <filename-of-initramfs-kernel>.bin && bootm $fileaddr The actual sysupgrade image can then be transferred (on the LAN port) to the device via scp <filename-of-squashfs-sysupgrade>.bin root@192.168.1.1:/tmp/ On the device, the sysupgrade must then be started using sysupgrade -n /tmp/<filename-of-squashfs-sysupgrade>.bin Gluon image name change ======================= The device had the image name "openmesh-om2pv4" in older versions of Gluon. This had to be changed with the new name in the device trees of the ath79 device tree.
2021-10-10 15:22:48 +00:00
- OM2P (v1, v2, v4)
ath79-generic: Add support for OpenMesh OM2P-HS v4 Device specifications: ====================== * Qualcomm/Atheros QCA9533 v2 * 650/600/217 MHz (CPU/DDR/AHB) * 64 MB of RAM * 16 MB of SPI NOR flash - 2x 7 MB available; but one of the 7 MB regions is the recovery image * 2x 10/100 Mbps Ethernet * 2T2R 2.4 GHz Wi-Fi * 6x GPIO-LEDs (3x wifi, 2x ethernet, 1x power) * 1x GPIO-button (reset) * external h/w watchdog (enabled by default) * TTL pins are on board (arrow points to VCC, then follows: GND, TX, RX) * 2x fast ethernet - eth0 + 24V passive POE (mode B) + used as WAN interface - eth1 + 802.3af POE + builtin switch port 1 + used as LAN interface * 12-24V 1A DC * internal antennas Flashing instructions: ====================== Various methods can be used to install the actual image on the flash. Two easy ones are: ap51-flash ---------- The tool ap51-flash (https://github.com/ap51-flash/ap51-flash) should be used to transfer the image to the u-boot when the device boots up. initramfs from TFTP ------------------- The serial console must be used to access the u-boot shell during bootup. It can then be used to first boot up the initramfs image from a TFTP server (here with the IP 192.168.1.21): setenv serverip 192.168.1.21 setenv ipaddr 192.168.1.1 tftpboot 0c00000 <filename-of-initramfs-kernel>.bin && bootm $fileaddr The actual sysupgrade image can then be transferred (on the LAN port) to the device via scp <filename-of-squashfs-sysupgrade>.bin root@192.168.1.1:/tmp/ On the device, the sysupgrade must then be started using sysupgrade -n /tmp/<filename-of-squashfs-sysupgrade>.bin Gluon image name change ======================= The device had the image name "openmesh-om2phsv4" in older versions of Gluon. This had to be changed with the new name in the device trees of the ath79 device tree.
2021-10-10 15:25:55 +00:00
- OM2P-HS (v1, v2, v3, v4)
ath79-generic: Add support for OpenMesh OM2P-LC Device specifications: ====================== * Qualcomm/Atheros AR9330 rev 1 * 400/400/200 MHz (CPU/DDR/AHB) * 64 MB of RAM * 16 MB of SPI NOR flash - 2x 7 MB available; but one of the 7 MB regions is the recovery image * 2x 10/100 Mbps Ethernet * 1T1R 2.4 GHz Wi-Fi * 6x GPIO-LEDs (3x wifi, 2x ethernet, 1x power) * 1x GPIO-button (reset) * external h/w watchdog (enabled by default) * TTL pins are on board (arrow points to VCC, then follows: GND, TX, RX) * 2x fast ethernet - eth0 + builtin switch port 1 + used as LAN interface - eth1 + 18-24V passive POE (mode B) + used as WAN interface * 12-24V 1A DC * internal antennas Flashing instructions: ====================== Various methods can be used to install the actual image on the flash. Two easy ones are: ap51-flash ---------- The tool ap51-flash (https://github.com/ap51-flash/ap51-flash) should be used to transfer the image to the u-boot when the device boots up. initramfs from TFTP ------------------- The serial console must be used to access the u-boot shell during bootup. It can then be used to first boot up the initramfs image from a TFTP server (here with the IP 192.168.1.21): setenv serverip 192.168.1.21 setenv ipaddr 192.168.1.1 tftpboot 0c00000 <filename-of-initramfs-kernel>.bin && bootm $fileaddr The actual sysupgrade image can then be transferred (on the LAN port) to the device via scp <filename-of-squashfs-sysupgrade>.bin root@192.168.1.1:/tmp/ On the device, the sysupgrade must then be started using sysupgrade -n /tmp/<filename-of-squashfs-sysupgrade>.bin
2021-10-10 15:26:49 +00:00
- OM2P-LC
ath79-generic: Add support for OpenMesh OM5P Device specifications: ====================== * Qualcomm/Atheros AR9344 rev 2 * 560/450/225 MHz (CPU/DDR/AHB) * 64 MB of RAM * 16 MB of SPI NOR flash - 2x 7 MB available; but one of the 7 MB regions is the recovery image * 2x 10/100 Mbps Ethernet * 2T2R 5 GHz Wi-Fi * 6x GPIO-LEDs (3x wifi, 2x ethernet, 1x power) * 1x GPIO-button (reset) * external h/w watchdog (enabled by default) * TTL pins are on board (arrow points to VCC, then follows: GND, TX, RX) * 2x fast ethernet - eth0 + builtin switch port 1 + used as LAN interface - eth1 + 18-24V passive POE (mode B) + used as WAN interface * 12-24V 1A DC * internal antennas WAN/LAN LEDs appear to be wrong in ar71xx and have been swapped here. Flashing instructions: ====================== Various methods can be used to install the actual image on the flash. Two easy ones are: ap51-flash ---------- The tool ap51-flash (https://github.com/ap51-flash/ap51-flash) should be used to transfer the image to the u-boot when the device boots up. initramfs from TFTP ------------------- The serial console must be used to access the u-boot shell during bootup. It can then be used to first boot up the initramfs image from a TFTP server (here with the IP 192.168.1.21): setenv serverip 192.168.1.21 setenv ipaddr 192.168.1.1 tftpboot 0c00000 <filename-of-initramfs-kernel>.bin && bootm $fileaddr The actual sysupgrade image can then be transferred (on the LAN port) to the device via scp <filename-of-squashfs-sysupgrade>.bin root@192.168.1.1:/tmp/ On the device, the sysupgrade must then be started using sysupgrade -n /tmp/<filename-of-squashfs-sysupgrade>.bin
2021-10-10 15:27:40 +00:00
- OM5P
ath79-generic: Add support for OpenMesh OM5P-AC v2 Device specifications: ====================== * Qualcomm/Atheros QCA9558 ver 1 rev 0 * 720/600/200 MHz (CPU/DDR/AHB) * 128 MB of RAM * 16 MB of SPI NOR flash - 2x 7 MB available; but one of the 7 MB regions is the recovery image * 2T2R 2.4 GHz Wi-Fi (11n) * 2T2R 5 GHz Wi-Fi (11ac) * 4x GPIO-LEDs (3x wifi, 1x power) * 1x GPIO-button (reset) * external h/w watchdog (enabled by default)) * TTL pins are on board (arrow points to VCC, then follows: GND, TX, RX) * TI tmp423 (package kmod-hwmon-tmp421) for temperature monitoring * 2x ethernet - eth0 + AR8035 ethernet PHY (RGMII) + 10/100/1000 Mbps Ethernet + 802.3af POE + used as LAN interface - eth1 + AR8031 ethernet PHY (RGMII) + 10/100/1000 Mbps Ethernet + 18-24V passive POE (mode B) + used as WAN interface * 12-24V 1A DC * internal antennas This device support is based on the partially working stub from commit 53c474abbdfe ("ath79: add new OF only target for QCA MIPS silicon"). Flashing instructions: ====================== Various methods can be used to install the actual image on the flash. Two easy ones are: ap51-flash ---------- The tool ap51-flash (https://github.com/ap51-flash/ap51-flash) should be used to transfer the image to the u-boot when the device boots up. initramfs from TFTP ------------------- The serial console must be used to access the u-boot shell during bootup. It can then be used to first boot up the initramfs image from a TFTP server (here with the IP 192.168.1.21): setenv serverip 192.168.1.21 setenv ipaddr 192.168.1.1 tftpboot 0c00000 <filename-of-initramfs-kernel>.bin && bootm $fileaddr The actual sysupgrade image can then be transferred (on the LAN port) to the device via scp <filename-of-squashfs-sysupgrade>.bin root@192.168.1.1:/tmp/ On the device, the sysupgrade must then be started using sysupgrade -n /tmp/<filename-of-squashfs-sysupgrade>.bin Gluon image name change ======================= The device had the image name "openmesh-om5p-acv2" in older versions of Gluon. This had to be changed with the new name in the device trees of the ath79 device tree.
2021-10-10 15:30:24 +00:00
- OM5P-AC (v1, v2)
ath79-generic: Add support for OpenMesh OM5P-AN Device specifications: ====================== * Qualcomm/Atheros AR9344 rev 2 * 560/450/225 MHz (CPU/DDR/AHB) * 64 MB of RAM * 16 MB of SPI NOR flash - 2x 7 MB available; but one of the 7 MB regions is the recovery image * 1T1R 2.4 GHz Wi-Fi * 2T2R 5 GHz Wi-Fi * 6x GPIO-LEDs (3x wifi, 2x ethernet, 1x power) * 1x GPIO-button (reset) * external h/w watchdog (enabled by default) * TTL pins are on board (arrow points to VCC, then follows: GND, TX, RX) * TI tmp423 (package kmod-hwmon-tmp421) for temperature monitoring * 2x ethernet - eth0 + AR8035 ethernet PHY + 10/100/1000 Mbps Ethernet + 802.3af POE + used as LAN interface - eth1 + 10/100 Mbps Ethernet + builtin switch port 1 + 18-24V passive POE (mode B) + used as WAN interface * 12-24V 1A DC * internal antennas Flashing instructions: ====================== Various methods can be used to install the actual image on the flash. Two easy ones are: ap51-flash ---------- The tool ap51-flash (https://github.com/ap51-flash/ap51-flash) should be used to transfer the image to the u-boot when the device boots up. initramfs from TFTP ------------------- The serial console must be used to access the u-boot shell during bootup. It can then be used to first boot up the initramfs image from a TFTP server (here with the IP 192.168.1.21): setenv serverip 192.168.1.21 setenv ipaddr 192.168.1.1 tftpboot 0c00000 <filename-of-initramfs-kernel>.bin && bootm $fileaddr The actual sysupgrade image can then be transferred (on the LAN port) to the device via scp <filename-of-squashfs-sysupgrade>.bin root@192.168.1.1:/tmp/ On the device, the sysupgrade must then be started using sysupgrade -n /tmp/<filename-of-squashfs-sysupgrade>.bin
2021-10-10 15:28:55 +00:00
- OM5P-AN
ath79-generic: Add support for OpenMesh A60 Device specifications: ====================== * Qualcomm/Atheros QCA9558 ver 1 rev 0 * 720/600/240 MHz (CPU/DDR/AHB) * 128 MB of RAM * 16 MB of SPI NOR flash - 2x 7 MB available; but one of the 7 MB regions is the recovery image * 3T3R 2.4 GHz Wi-Fi (11n) * 3T3R 5 GHz Wi-Fi (11ac) * multi-color LED (controlled via red/green/blue GPIOs) * 1x GPIO-button (reset) * external h/w watchdog (enabled by default)) * TTL pins are on board (arrow points to VCC, then follows: GND, TX, RX) * 2x ethernet - eth0 + Label: Ethernet 1 + AR8035 ethernet PHY (RGMII) + 10/100/1000 Mbps Ethernet + 802.3af POE + used as WAN interface - eth1 + Label: Ethernet 2 + AR8031 ethernet PHY (SGMII) + 10/100/1000 Mbps Ethernet + used as LAN interface * 1x USB * internal antennas Flashing instructions: ====================== Various methods can be used to install the actual image on the flash. Two easy ones are: ap51-flash ---------- The tool ap51-flash (https://github.com/ap51-flash/ap51-flash) should be used to transfer the image to the u-boot when the device boots up. initramfs from TFTP ------------------- The serial console must be used to access the u-boot shell during bootup. It can then be used to first boot up the initramfs image from a TFTP server (here with the IP 192.168.1.21): setenv serverip 192.168.1.21 setenv ipaddr 192.168.1.1 tftpboot 0c00000 <filename-of-initramfs-kernel>.bin && bootm $fileaddr The actual sysupgrade image can then be transferred (on the LAN port) to the device via scp <filename-of-squashfs-sysupgrade>.bin root@192.168.1.1:/tmp/ On the device, the sysupgrade must then be started using sysupgrade -n /tmp/<filename-of-squashfs-sysupgrade>.bin
2021-10-10 15:02:56 +00:00
ath79: add support for Plasma Cloud PA300
2020-11-23 20:19:27 +00:00
* Plasma Cloud
- PA300
ath79: add support for Plasma Cloud PA300E
2020-11-23 20:19:27 +00:00
- PA300E
ath79: add support for Plasma Cloud PA300
2020-11-23 20:19:27 +00:00
ath79-generic: add support for Siemens WS-AP3610
2021-07-06 00:23:04 +00:00
* Siemens
- WS-AP3610
ath79-generic: add support for TP-Link Archer C6v2 Hardware specification: - SOC: Qualcomm QCA9563 @ 775MHz - Flash: GigaDevice GD25Q64CSIG (8MiB) - RAM: Zentel A3R1GE40JBF (128 MiB DDR2) - Ethernet: Qualcomm QCA8337N: 4x 1Gbps LAN + 1x 1Gbps WAN - Wireless: - 2.4GHz (bgn) QCA9563 integrated (3x3) - 5GHz (ac) Qualcomm QCA9886 (2x2) - Button: 1x power, 1x reset, 1x wps - LED: 6x LEDs: power, wlan2g, wlan5g, lan, wan, wps - UART: There's no UART header on the board
2019-10-31 13:13:43 +00:00
* TP-Link
ath79-generic: add support for TP-Link Archer A7 v5 (#2374)
2022-01-14 22:20:22 +00:00
- Archer A7 (v5)
ath79-generic: add support for TP-Link Archer C6v2 Hardware specification: - SOC: Qualcomm QCA9563 @ 775MHz - Flash: GigaDevice GD25Q64CSIG (8MiB) - RAM: Zentel A3R1GE40JBF (128 MiB DDR2) - Ethernet: Qualcomm QCA8337N: 4x 1Gbps LAN + 1x 1Gbps WAN - Wireless: - 2.4GHz (bgn) QCA9563 integrated (3x3) - 5GHz (ac) Qualcomm QCA9886 (2x2) - Button: 1x power, 1x reset, 1x wps - LED: 6x LEDs: power, wlan2g, wlan5g, lan, wan, wps - UART: There's no UART header on the board
2019-10-31 13:13:43 +00:00
- Archer C6 (v2)
ath79-generic: (re)add support for archer-c7-v2 (#2437)
2022-03-29 15:54:08 +00:00
- Archer C7 (v2)
ath79-generic: (re)add support for CPE210 v2.x (#2429) Gone due to commit 45c84a117bf8 ("ar71xx: drop target")
2022-03-25 17:21:24 +00:00
- CPE210 (v1.0, v1.1, v2.0)
ath79-generic: add support for TP-Link CPE220 v3
2020-04-24 05:32:21 +00:00
- CPE220 (v3.0)
ath79-generic: (re)add support for CPE510 v1.x (#2430) Gone due to commit 45c84a117bf8 ("ar71xx: drop target")
2022-03-25 22:39:19 +00:00
- CPE510 (v1.0, v1.1)
Add support for tp-link CPE510 V2 (#2287) Co-authored-by: Michael Wyraz <michael.wyraz@evermind.de>
2021-08-12 15:14:38 +00:00
- CPE510 (v2.0)
Add support for tp-link CPE510 V3 (#2283)
2021-08-11 17:15:37 +00:00
- CPE510 (v3.0)
ath79-generic: add support for TP-Link EAP225-Outdoor v1
2021-08-28 12:29:58 +00:00
- EAP225-Outdoor (v1)
ath79-generic: add support for TP-Link TL-WDR3600/4300 v1
2021-08-07 19:22:09 +00:00
- TL-WDR3600 (v1)
- TL-WDR4300 (v1)
ath79-generic: (re)add support for tl-wr1043nd-v4 Gone due to commit 45c84a117bf8 ("ar71xx: drop target")
2022-03-25 12:33:42 +00:00
- TL-WR1043N/ND (v3, v4)
ath79-generic: add support for TP-Link WBS210 v2 (#2299)
2021-08-27 21:15:04 +00:00
- WBS210 (v2.0)
ath79-generic: add support for TP-Link Archer C6v2 Hardware specification: - SOC: Qualcomm QCA9563 @ 775MHz - Flash: GigaDevice GD25Q64CSIG (8MiB) - RAM: Zentel A3R1GE40JBF (128 MiB DDR2) - Ethernet: Qualcomm QCA8337N: 4x 1Gbps LAN + 1x 1Gbps WAN - Wireless: - 2.4GHz (bgn) QCA9563 integrated (3x3) - 5GHz (ac) Qualcomm QCA9886 (2x2) - Button: 1x power, 1x reset, 1x wps - LED: 6x LEDs: power, wlan2g, wlan5g, lan, wan, wps - UART: There's no UART header on the board
2019-10-31 13:13:43 +00:00
ath79-generic: (re)add support for UniFi AP Gone due to commit 45c84a1 ("ar71xx: drop target")
2022-03-23 16:31:18 +00:00
* Ubiquiti
ath79-generic: (re)add support for UniFi AC Mesh (#2428) Gone due to commit 45c84a117bf8 ("ar71xx: drop target")
2022-03-26 09:52:35 +00:00
- UniFi AC Mesh
ath79-generic: (re)add support for UniFi AP Gone due to commit 45c84a1 ("ar71xx: drop target")
2022-03-23 16:31:18 +00:00
- UniFi AP
ath79-generic: (re)add support for UniFi AP LR Gone due to commit 45c84a1 ("ar71xx: drop target")
2022-03-24 11:08:26 +00:00
- UniFi AP LR
ath79-generic: (re)add support for UniFi AP PRO (#2416) Ubiquiti UniFi AP PRO Gone due to commit 45c84a1 ("ar71xx: drop target")
2022-03-26 10:11:32 +00:00
- UniFi AP PRO
ath79-generic: (re)add support for UniFi AP Gone due to commit 45c84a1 ("ar71xx: drop target")
2022-03-23 16:31:18 +00:00
ath79: move GL.iNet GL-AR750S to NAND subtarget
2020-04-15 21:57:14 +00:00
ath79-nand
----------
* GL.iNet
- GL-AR750S
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
brcm2708-bcm2708
----------------
* RaspberryPi 1
brcm2708-bcm2709
----------------
* RaspberryPi 2
docs: update for reflect dropped IBSS support
2019-11-05 19:50:37 +00:00
ipq40xx-generic
---------------
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
docs: add Aruba AP-303 and Instant On AP11 to supported devices list
2020-04-27 14:56:40 +00:00
* Aruba
- AP-303
ipq40xx: add support for Aruba AP-303H / Instant ON AP11D (#2302) - [x] must be flashable from vendor firmware - [ ] webinterface - [ ] tftp - [x] other: Console port available. Manufacturer specific cable required. Tutorial in OpenWRT commit message https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=c6e972c8772a628a1a2f2e5590d7c6f4acef9ab0 - [x] must support upgrade mechanism - [x] must have working sysupgrade - [x] must keep/forget configuration (if applicable) *think `sysupgrade [-n]` or `firstboot`* - [x] must have working autoupdate root@Aruba-AP-303H:~# lua -e 'print(require("platform_info").get_image_name())' aruba-ap-303h - [x] reset/wps/phone button must return device into config mode - [x] primary mac should match address on device label (or packaging) (https://gluon.readthedocs.io/en/latest/dev/hardware.html#notes) - wired network - [x] should support all network ports on the device - [x] must have correct port assignment (WAN/LAN) - wifi (if applicable) - [x] association with AP must be possible on all radios - [x] association with 802.11s mesh must be working on all radios - [x] ap/mesh mode must work in parallel on all radios - led mapping - power/sys led (_critical, because led definitions are setup on firstboot only_) - [x] lit while the device is on - [x] should display config mode blink sequence (https://gluon.readthedocs.io/en/latest/features/configmode.html) - radio leds - [x] should map to their respective radio - [x] should show activity - switchport leds - [x] should map to their respective port (or switch, if only one led present) - [x] should show link state and activity - outdoor devices only - [ ] added board name to `is_outdoor_device` function in `package/gluon-core/luasrc/usr/lib/lua/gluon/platform.lua` - ToDo (upstream): - enable PoE pass through on interface E3 system.poe_passthrough=gpio_switch system.poe_passthrough.name='PoE Passthrough' system.poe_passthrough.gpio_pin='446' system.poe_passthrough.value='0' (0 is active)
2021-09-01 21:31:01 +00:00
- AP-303H
ipq40xx: add support for Aruba AP-365 / InstantOn AP17 (#2290)
2021-08-10 23:14:30 +00:00
- AP-365
docs: add Aruba AP-303 and Instant On AP11 to supported devices list
2020-04-27 14:56:40 +00:00
- Instant On AP11
ipq40xx: add support for Aruba AP-303H / Instant ON AP11D (#2302) - [x] must be flashable from vendor firmware - [ ] webinterface - [ ] tftp - [x] other: Console port available. Manufacturer specific cable required. Tutorial in OpenWRT commit message https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=c6e972c8772a628a1a2f2e5590d7c6f4acef9ab0 - [x] must support upgrade mechanism - [x] must have working sysupgrade - [x] must keep/forget configuration (if applicable) *think `sysupgrade [-n]` or `firstboot`* - [x] must have working autoupdate root@Aruba-AP-303H:~# lua -e 'print(require("platform_info").get_image_name())' aruba-ap-303h - [x] reset/wps/phone button must return device into config mode - [x] primary mac should match address on device label (or packaging) (https://gluon.readthedocs.io/en/latest/dev/hardware.html#notes) - wired network - [x] should support all network ports on the device - [x] must have correct port assignment (WAN/LAN) - wifi (if applicable) - [x] association with AP must be possible on all radios - [x] association with 802.11s mesh must be working on all radios - [x] ap/mesh mode must work in parallel on all radios - led mapping - power/sys led (_critical, because led definitions are setup on firstboot only_) - [x] lit while the device is on - [x] should display config mode blink sequence (https://gluon.readthedocs.io/en/latest/features/configmode.html) - radio leds - [x] should map to their respective radio - [x] should show activity - switchport leds - [x] should map to their respective port (or switch, if only one led present) - [x] should show link state and activity - outdoor devices only - [ ] added board name to `is_outdoor_device` function in `package/gluon-core/luasrc/usr/lib/lua/gluon/platform.lua` - ToDo (upstream): - enable PoE pass through on interface E3 system.poe_passthrough=gpio_switch system.poe_passthrough.name='PoE Passthrough' system.poe_passthrough.gpio_pin='446' system.poe_passthrough.value='0' (0 is active)
2021-09-01 21:31:01 +00:00
- Instant On AP11D
ipq40xx: add support for Aruba AP-365 / InstantOn AP17 (#2290)
2021-08-10 23:14:30 +00:00
- Instant On AP17
docs: add Aruba AP-303 and Instant On AP11 to supported devices list
2020-04-27 14:56:40 +00:00
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
* AVM
- FRITZ!Box 4040 [#avmflash]_
ipq40xx-generic: add support for AVM FRITZBox 7530 (#2125)
2020-10-06 21:37:41 +00:00
- FRITZ!Box 7530 [#eva_ramboot]_
ipq40xx: add support for AVM FritzRepeater 1200
2019-11-10 19:39:19 +00:00
- FRITZ!Repeater 1200 [#eva_ramboot]_
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
ipq40xx-generic: add support for EnGenius ENS620EXT
2020-03-06 08:32:03 +00:00
* EnGenius
- ENS620EXT
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
* GL.iNet
- GL-B1300
docs: add Linksys EA6350 v3 to supported devices
2020-05-09 02:09:35 +00:00
* Linksys
- EA6350 (v3)
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
* NETGEAR
docs: supported devices: clarify version numbers of Netgear EX61x0
2020-01-28 00:04:18 +00:00
- EX6100 (v2)
- EX6150 (v2)
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
* OpenMesh
- A42
- A62
ipq40xx: add support for Plasma Cloud PA1200
2020-11-22 13:02:32 +00:00
* Plasma Cloud
- PA1200
ipq40xx: add support for Plasma Cloud PA2200 This device is a dual 5GHz device. It is recommended to manually change the radio of the first device to the lower 5GHz channels and the second radio to the upper 5GHz channels
2020-11-22 13:02:32 +00:00
- PA2200
ipq40xx: add support for Plasma Cloud PA1200
2020-11-22 13:02:32 +00:00
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
* ZyXEL
- NBG6617
docs: add device-classes
2019-12-14 18:06:21 +00:00
- WRE6606 [#device-class-tiny]_
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
docs: update for reflect dropped IBSS support
2019-11-05 19:50:37 +00:00
ipq806x-generic
---------------
ipq806x-generic: remove BROKEN flag for target and NETGEAR R7800 This commit removes the broken flag for the ipq806x-generic target, as the first device (NETGEAR R7800) now has full support in Gluon
2019-11-05 08:01:35 +00:00
* NETGEAR
- R7800
lantiq-xrx200: add support for AVM FRITZ!Box 7412 (#1859)
2019-11-18 21:54:50 +00:00
lantiq-xrx200
-------------
* AVM
lantiq-xrx200: add support for AVM FRITZ!Box 7360 (v1, v2) and 7360 SL
2019-12-09 15:14:53 +00:00
- FRITZ!Box 7360 (v1, v2) [#avmflash]_ [#lan_as_wan]_
- FRITZ!Box 7360 SL [#avmflash]_ [#lan_as_wan]_
lantiq-xrx200: add support for AVM FRITZ!Box 7362 SL Flash instructions in the OpenWRT Commit: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=eae6cac6a30b95bef04d033ed8a303b7e35a078b
2019-11-18 22:28:21 +00:00
- FRITZ!Box 7362 SL [#eva_ramboot]_ [#lan_as_wan]_
lantiq-xrx200: add support for AVM FRITZ!Box 7412 (#1859)
2019-11-18 21:54:50 +00:00
- FRITZ!Box 7412 [#eva_ramboot]_
lantiq-xway: add support for AVM FRITZ!Box 7312
2019-11-06 17:00:33 +00:00
lantiq-xway
-----------
* AVM
- FRITZ!Box 7312 [#avmflash]_
lantiq-xway: add support for NETGEAR DGN3500B
2020-03-09 17:30:20 +00:00
* NETGEAR
- DGN3500B [#lan_as_wan]_
mediatek-mt7622: add support for Ubiquiti UniFi 6 LR Signed-off-by: David Bauer <mail@david-bauer.net>
2021-06-28 22:43:31 +00:00
mediatek-mt7622
---------------
* Ubiquiti
- UniFi 6 LR
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
mpc85xx-generic
---------------
mpc85xx-p1010: add Sophos RED 15w rev.1 (#2438) This adds support for the Sophos RED 15w rev.1 gateway. It is a branch-office SD-WAN device based on the P1014 networking SoC. Signed-off-by: David Bauer <mail@david-bauer.net>
2022-03-30 15:19:08 +00:00
* Sophos
- RED 15w Rev.1
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
* TP-Link
- TL-WDR4900 (v1)
mpc85xx-p1020
---------------
* Aerohive
- HiveAP 330
mpc85xx-p1020: add support for Enterasys WS-AP3710i
2019-12-18 22:56:34 +00:00
* Enterasys
- WS-AP3710i
mpc85xx-p1020: add support for OCEDO Panda (#1847)
2019-11-03 17:59:00 +00:00
* OCEDO
- Panda
docs: update for reflect dropped IBSS support
2019-11-05 19:50:37 +00:00
ramips-mt7620
-------------
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
docs: rename vendor to GL.iNet for uniformity
2020-01-31 18:42:12 +00:00
* GL.iNet
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
- GL-MT300A
- GL-MT300N
- GL-MT750
docs: Add Netgear EX3700 and EX3800 (#2126) Fixes #2113
2020-10-06 13:35:43 +00:00
* NETGEAR
- EX3700
- EX3800
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
* Nexx
- WT3020AD/F/H
ramips-mt76x8: add support for TP-Link TL-WA801ND v5
2020-01-14 14:52:03 +00:00
* TP-Link
ramips-mt7620: add support for TP-Link Archer C2 v1
2020-01-05 23:02:44 +00:00
docs: normalize hardware revision references
2020-04-24 19:38:47 +00:00
- Archer C2 (v1)
ramips-mt7620: add support for tp-link archer c20 v1 (#1866) 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
2020-01-20 22:26:04 +00:00
- Archer C20 (v1)
ramips-mt7620: add support for TP-Link Archer C20i
2020-01-07 23:31:19 +00:00
- Archer C20i
docs: normalize hardware revision references
2020-04-24 19:38:47 +00:00
- Archer C50 (v1)
ramips-mt7620: add support for TP-Link Archer C2 v1
2020-01-05 23:02:44 +00:00
docs: supported_devices: fix small typo Just saw a small typo i made in the Xiaomi Mi Wifi Mini PR. This PR Corrects this.
2020-01-06 23:03:08 +00:00
* Xiaomi
ramips-mt7620: remove broken flag for Xiaomi MiWifi Mini WiFi driver is stable now.
2020-01-04 21:39:00 +00:00
- MiWiFi Mini
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
ramips-mt7621
-------------
* ASUS
docs: update for reflect dropped IBSS support
2019-11-05 19:50:37 +00:00
- RT-AC57U
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
* D-Link
docs: update for reflect dropped IBSS support
2019-11-05 19:50:37 +00:00
- DIR-860L (B1)
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
ramips-mt7621: add support for Netgear R6220
2019-11-07 00:40:52 +00:00
* NETGEAR
docs: supported devices: clarify version numbers of Netgear EX61x0
2020-01-28 00:04:18 +00:00
- EX6150 (v1)
ramips-mt7621: add support for Netgear R6220
2019-11-07 00:40:52 +00:00
- R6220
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
* Ubiquiti
- EdgeRouter X
- EdgeRouter X-SFP
ramips-mt7621: add support for Ubiquiti UniFi 6 Lite (#2310) Hardware -------- MediaTek MT7621AT 256M DDR3 32M SPI-NOR MediaTek MT7603 2T2R 802.11n 2.4GHz MediaTek MT7915 2T2R 802.11ax 5GHz Not Working ----------- - Bluetooth (connected to UART3) UART ---- UART is located in the lower left corner of the board. Pinout is 0 - 3V3 (don't connect) 1 - RX 2 - TX 3 - GND Console is 115200 8N1. Boot ---- 1. Connect to the serial console and connect power. 2. Double-press ESC when prompted 3. Set the fdt address $ fdt addr $(fdtcontroladdr) 4. Remove the signature node from the control FDT $ fdt rm /signature 5. Transfer and boot the OpenWrt initramfs image to the device. Make sure to name the file C0A80114.img and have it reachable at 192.168.1.1/24 $ tftpboot; bootm Installation ------------ 1. Connect to the booted device at 192.168.1.20 using username/password "ubnt". 2. Update the bootloader environment. $ fw_setenv devmode TRUE $ fw_setenv boot_openwrt "fdt addr \$(fdtcontroladdr); fdt rm /signature; bootubnt" $ fw_setenv bootcmd "run boot_openwrt" 3. Transfer the OpenWrt sysupgrade image to the device using SCP. 4. Check the mtd partition number for bs / kernel0 / kernel1 $ cat /proc/mtd 5. Set the bootselect flag to boot from kernel0 $ dd if=/dev/zero bs=1 count=1 of=/dev/mtdblock4 6. Write the OpenWrt sysupgrade image to both kernel0 as well as kernel1 $ dd if=openwrt.bin of=/dev/mtdblock6 $ dd if=openwrt.bin of=/dev/mtdblock7 7. Reboot the device. It should boot into OpenWrt.
2021-09-14 22:44:34 +00:00
- UniFi 6 Lite
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
* ZBT
docs: update for reflect dropped IBSS support
2019-11-05 19:50:37 +00:00
- WG3526-16M
- WG3526-32M
ramips-mt76x8: add support for TP-Link RE200 v2 (#2275) TP-Link RE200 v2 is a wireless range extender with Ethernet and 2.4G and 5G WiFi with internal antennas. It's based on MediaTek MT7628AN+MT7610EN. Specifications -------------- - MediaTek MT7628AN (580 Mhz) - 64 MB of RAM - 8 MB of FLASH - 2T2R 2.4 GHz and 1T1R 5 GHz - 1x 10/100 Mbps Ethernet - UART header on PCB (57600 8n1) - 8x LED (GPIO-controlled), 2x button There are 2.4G and 5G LEDs in red and green which are controlled separately. MAC addresses ------------- The MAC address assignment matches stock firmware, i.e.: LAN : *:0D 2.4G: *:0E 5G : *:0F Installation ------------ Web Interface ------------- It is possible to upgrade to OpenWrt via the web interface. Simply flash the -factory.bin from OEM. In contrast to a stock firmware, this will not overwrite U-Boot.
2021-07-29 06:34:51 +00:00
ramips-mt7621: add Xiaomi Mi Router 4A (Gigabit Edition) Specifications: - SoC: MediaTek MT7621 - Flash: 16 MiB NOR SPI - RAM: 128 MiB DDR3 - Ethernet: 3x 10/100/1000 Mbps (switched, 2xLAN + WAN) - WIFI0: MT7603E 2.4GHz 802.11b/g/n - WIFI1: MT7612E 5GHz 802.11ac - Antennas: 4x external (2 per radio), non-detachable - LEDs: Programmable "power" LED (two-coloured, yellow/blue) Non-programmable "internet" LED (shows WAN activity) - Buttons: Reset Installation: Bootloader won't accept any serial input unless "boot_wait" u-boot environment variable is changed to "on". Vendor firmware won't accept any serial input until "uart_en" is set to "1". Using the https://github.com/acecilia/OpenWRTInvasion exploit you can gain access to shell to enable these options: To enable uart keyboard actions - 'nvram set uart_en=1' To make uboot delay boot work - 'nvram set boot_wait=on' Set boot delay to 5 - 'nvram set bootdelay=5' Then run 'nvram commit' to make the changes permanent. Once in the shell (following the OpenWRTInvasion instructions) you can then run the following to flash OpenWrt and then reboot: 'cd /tmp; curl https://downloads.openwrt.org/...-sysupgrade.bin --output firmware.bin; mtd -e OS1 -r write firmware.bin OS1'
2021-06-29 09:02:15 +00:00
* Xiaomi
- Xiaomi Mi Router 4A (Gigabit Edition)
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
docs: update for reflect dropped IBSS support
2019-11-05 19:50:37 +00:00
ramips-mt76x8
-------------
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
ramips-mt76x8: add support for Cudy WR1000 v2 is available on the market, but apparently has no upstream support, yet: https://forum.openwrt.org/t/v2-of-cudy-wr1000/56965
2020-04-24 11:34:17 +00:00
* Cudy
- WR1000 (v1)
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
* GL.iNet
docs: normalize hardware revision references
2020-04-24 19:38:47 +00:00
- GL-MT300N (v2)
ramips-mt76x8: add support for GL.iNet microuter-N300 (#2303)
2021-09-04 15:42:16 +00:00
- microuter-N300
ramips-mt76x8: add support for GL.iNet VIXMINI
2019-10-30 13:37:04 +00:00
- VIXMINI
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
* NETGEAR
- R6120
ramips-mt76x8: add support for RAVPower RP-WD009 (#2265)
2021-07-18 14:41:27 +00:00
* RAVPower
- RP-WD009
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
* TP-Link
docs: normalize hardware revision references
2020-04-24 19:38:47 +00:00
- Archer C50 (v3)
- Archer C50 (v4)
ramips-mt76x8: add support for TP-Link RE200 v2 (#2275) TP-Link RE200 v2 is a wireless range extender with Ethernet and 2.4G and 5G WiFi with internal antennas. It's based on MediaTek MT7628AN+MT7610EN. Specifications -------------- - MediaTek MT7628AN (580 Mhz) - 64 MB of RAM - 8 MB of FLASH - 2T2R 2.4 GHz and 1T1R 5 GHz - 1x 10/100 Mbps Ethernet - UART header on PCB (57600 8n1) - 8x LED (GPIO-controlled), 2x button There are 2.4G and 5G LEDs in red and green which are controlled separately. MAC addresses ------------- The MAC address assignment matches stock firmware, i.e.: LAN : *:0D 2.4G: *:0E 5G : *:0F Installation ------------ Web Interface ------------- It is possible to upgrade to OpenWrt via the web interface. Simply flash the -factory.bin from OEM. In contrast to a stock firmware, this will not overwrite U-Boot.
2021-07-29 06:34:51 +00:00
- RE200 (v2)
docs: normalize hardware revision references
2020-04-24 19:38:47 +00:00
- TL-MR3020 (v3)
- TL-MR3420 (v5)
- TL-WA801ND (v5)
- TL-WR841N (v13)
- TL-WR902AC (v3)
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
* VoCore
- VoCore2
ramips-mt76x8: add Xiaomi Mi Router 4A (100M Edition)
2021-06-15 18:12:35 +00:00
* Xiaomi
- Xiaomi Mi Router 4A (100M Edition)
ramips-mt76x8: add Xiaomi Mi Router 4C Specifications: - CPU: MediaTek MT7628AN (580MHz) - Flash: 16MB - RAM: 64MB DDR2 - 2.4 GHz: IEEE 802.11b/g/n with Integrated LNA and PA - Antennas: 4x external single band antennas - WAN: 1x 10/100M - LAN: 2x 10/100M - LEDs: 2x yellow/blue. Programmable (labelled as power on case) - Non-programmable (shows WAN activity) - Button: Reset How to install: 1- Use OpenWRTInvasion to gain telnet and ftp access. 2- Push openwrt firmware to /tmp/ using ftp. 3- Connect to router using telnet. (IP: 192.168.31.1 - Username: root - No password) 4- Use command "mtd -r write /tmp/firmware.bin OS1" to flash into the router.. 5- It takes around 2 minutes. After that router will restart itself to OpenWrt.
2021-06-29 09:04:11 +00:00
- Xiaomi Mi Router 4C
ramips-mt76x8: add Xiaomi Mi Router 4A (100M Edition)
2021-06-15 18:12:35 +00:00
rockchip-armv8: add FriendlyARM NanoPi R2S
2020-11-14 09:06:54 +00:00
rockchip-armv8
--------------
* FriendlyElec
- NanoPi R2S
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
sunxi-cortexa7
--------------
* LeMaker
- Banana Pi M1
x86-generic
-----------
* x86-generic
* x86-virtualbox
* x86-vmware
See also: :doc:`x86`
x86-geode
---------
* x86-geode
See also: :doc:`x86`
x86-64
------
* x86-64-generic
* x86-64-virtualbox
* x86-64-vmware
See also: :doc:`x86`
Footnotes
---------
docs: add device-classes
2019-12-14 18:06:21 +00:00
.. [#device-class-tiny]
These devices only support a subset of Gluons capabilities due to flash or memory
size constraints. Devices are classified as tiny in they provide less than 7M of usable
flash space or have a low amount of system memory. For more information, see the
developer documentation: :ref:`device-class-definition`.
docs: move supported devices to own page (#1797)
2019-08-21 21:46:08 +00:00
.. [#avmflash]
docs: fix invalid fritztools link
2022-03-16 14:28:49 +00:00
For instructions on how to flash AVM devices, visit https://fritz-tools.readthedocs.io
ipq40xx: add support for AVM FritzRepeater 1200
2019-11-10 19:39:19 +00:00
.. [#eva_ramboot]
For instructions on how to flash AVM NAND devices, see the respective
ath79-generic: add support for devolo WiFi pro 1200i (#1871)
2019-11-20 12:39:22 +00:00
commit which added support in OpenWrt.
docs: clarify WAN port on LAN-only devices At the December 2019 review day, the behavior for LAN only devices was defined. Such devices will use each LAN port as WAN.
2019-12-03 18:19:39 +00:00
.. [#lan_as_wan]
All LAN ports on this device are used as WAN.
ath79-generic: add support for Onion Omega (#2306) * ath79-generic: add support for Onion Omega support was previously dropped in commit 45c84a117bf8 ("ar71xx: drop target") * fixup! ath79-generic: add support for Onion Omega * fixup! ath79-generic: add support for Onion Omega
2021-09-04 15:42:44 +00:00
.. [#modular_ethernet]
These devices follow a modular principle,
which means even basic functionality like ethernet is provided by an expansion-board,
that may not be bundled with the device itself.
Such expansions are recommended for the config mode, but are not strictly necessary,
as exposed serial ports may grant sufficient access as well.
Reference in New Issue Copy Permalink