diff options
| author | Mark Mentovai <mark@mentovai.com> | 2021-10-04 10:48:29 -0400 |
|---|---|---|
| committer | Christian Marangi <ansuelsmth@gmail.com> | 2022-07-18 01:45:47 +0200 |
| commit | 7f54bf6fe2ac331d018cd273bb1abe04493b5457 (patch) | |
| tree | 9739ae0b0023e4e9b478f7b2e2db2ba1e270d743 /target/linux/ipq40xx/base-files/etc | |
| parent | d9ab1e56d8d16182bd292f393c012d7e6873ed89 (diff) | |
| download | upstream-7f54bf6fe2ac331d018cd273bb1abe04493b5457.tar.gz upstream-7f54bf6fe2ac331d018cd273bb1abe04493b5457.tar.bz2 upstream-7f54bf6fe2ac331d018cd273bb1abe04493b5457.zip | |
ipq40xx: add MikroTik wAP ac (RBwAPG-5HacD2HnD) support
The MikroTik wAP ac (RBwAPG-5HacD2HnD) is a dual-band dual-radio
802.11ac wireless access point with integrated antenna and two Ethernet
ports in a weatherproof enclosure. See
https://mikrotik.com/product/wap_ac for more information.
Important: this is the new ipq40xx-based wAP ac, not the older
ath79-based wAP ac (RBwAPG-5HacT2HnD), already supported in OpenWrt.
Specifications:
- SoC: Qualcomm Atheros IPQ4018
- CPU: 4x ARM Cortex A7
- RAM: 128MB
- Storage: 16MB NOR flash
- Wireless
- 2.4GHz: Built-in IPQ4018 (SoC) 802.11b/g/n 2x2:2, 2.5 dBi antennae
- 5GHz: Built-in IPQ4018 (SoC) 802.11a/n/ac 2x2:2, 2.5 dBi antennae
- Ethernet: Built-in IPQ4018 (SoC, QCA8075), 2x 1000/100/10Mb/s ports,
one with 802.3af/at PoE in
Installation:
Boot the initramfs image via TFTP, then flash the sysupgrade image using
sysupgrade. Details at https://openwrt.org/toh/mikrotik/common.
Notes:
This preserves the MAC addresses of the physical Ethernet ports:
- eth0 corresponds to the physical port labeled ETH1 and has the base
MAC address. This port can be used to power the device.
- eth1 corresponds to the physical port labeled ETH2 and has a MAC
address one greater than the base.
MAC addresses are set from /lib/preinit/05_set_iface_mac_ipq40xx.sh
rather than /etc/board.d/02_network so that they are in effect for
preinit. This should likely be done for other MikroTik devices and
possibly other non-MikroTik devices as well.
As this device has 2 physical ports, they are each connected to their
respective PHYs, allowing the link status to be visible to software.
Since they are not marked on the case with any role (such as LAN or
WAN), both are bridged to the lan network by default, although this can
easily be changed if needed.
Signed-off-by: Mark Mentovai <mark@mentovai.com>
Diffstat (limited to 'target/linux/ipq40xx/base-files/etc')
| -rw-r--r-- | target/linux/ipq40xx/base-files/etc/board.d/02_network | 3 | ||||
| -rw-r--r-- | target/linux/ipq40xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata | 12 |
2 files changed, 10 insertions, 5 deletions
diff --git a/target/linux/ipq40xx/base-files/etc/board.d/02_network b/target/linux/ipq40xx/base-files/etc/board.d/02_network index 8e98f5bc25..5843987627 100644 --- a/target/linux/ipq40xx/base-files/etc/board.d/02_network +++ b/target/linux/ipq40xx/base-files/etc/board.d/02_network @@ -90,7 +90,8 @@ ipq40xx_setup_interfaces() ;; compex,wpj419|\ compex,wpj428|\ - engenius,eap2200) + engenius,eap2200|\ + mikrotik,wap-ac) ucidef_set_interface_lan "eth0 eth1" ;; buffalo,wtr-m2133hp) diff --git a/target/linux/ipq40xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata b/target/linux/ipq40xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata index 19ce3faf78..f1c424a28d 100644 --- a/target/linux/ipq40xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata +++ b/target/linux/ipq40xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata @@ -117,7 +117,8 @@ case "$FIRMWARE" in ;; mikrotik,cap-ac |\ mikrotik,hap-ac2 |\ - mikrotik,hap-ac3) + mikrotik,hap-ac3 |\ + mikrotik,wap-ac) wlan_data="/sys/firmware/mikrotik/hard_config/wlan_data" ( [ -f "$wlan_data" ] && caldata_sysfsload_from_file "$wlan_data" 0x0 0x2f20 ) || \ ( [ -d "$wlan_data" ] && caldata_sysfsload_from_file "$wlan_data/data_0" 0x0 0x2f20 ) @@ -199,7 +200,8 @@ case "$FIRMWARE" in mikrotik,cap-ac |\ mikrotik,hap-ac2 |\ mikrotik,hap-ac3 |\ - mikrotik,sxtsq-5-ac) + mikrotik,sxtsq-5-ac |\ + mikrotik,wap-ac) wlan_data="/sys/firmware/mikrotik/hard_config/wlan_data" ( [ -f "$wlan_data" ] && caldata_sysfsload_from_file "$wlan_data" 0x8000 0x2f20 ) || \ ( [ -d "$wlan_data" ] && caldata_sysfsload_from_file "$wlan_data/data_2" 0x0 0x2f20 ) @@ -222,7 +224,8 @@ case "$FIRMWARE" in case "$board" in mikrotik,cap-ac |\ mikrotik,hap-ac2 |\ - mikrotik,hap-ac3) + mikrotik,hap-ac3 |\ + mikrotik,wap-ac) wlan_data="/sys/firmware/mikrotik/hard_config/wlan_data" ( [ -f "$wlan_data" ] && caldata_sysfsload_from_file "$wlan_data" 0x2f20 0x2f20 ) || \ ( [ -d "$wlan_data" ] && caldata_sysfsload_from_file "$wlan_data/data_0" 0x2f20 0x2f20 ) @@ -234,7 +237,8 @@ case "$FIRMWARE" in mikrotik,cap-ac |\ mikrotik,hap-ac2 |\ mikrotik,hap-ac3 |\ - mikrotik,sxtsq-5-ac) + mikrotik,sxtsq-5-ac |\ + mikrotik,wap-ac) wlan_data="/sys/firmware/mikrotik/hard_config/wlan_data" ( [ -f "$wlan_data" ] && caldata_sysfsload_from_file "$wlan_data" 0xaf20 0x2f20 ) || \ ( [ -d "$wlan_data" ] && caldata_sysfsload_from_file "$wlan_data/data_2" 0x2f20 0x2f20 ) |