aboutsummaryrefslogtreecommitdiffstats
path: root/package/kernel/mac80211/patches/ath
Commit message (Collapse)AuthorAgeFilesLines
* mac80211: Update to version 5.2-rc7Hauke Mehrtens2019-07-1839-644/+110
| | | | | | | | | | | | | | This updates mac80211 to version 5.2-rc7, this contains all the changes to the wireless subsystem up to Linux 5.2-rc7. * The removed patches are applied upstream * b43 now uses kmod-lib-cordic * Update the nl80211.h file in iw to match backports version. * Remove the two backports from kernel 4.9, they were needed for mt76, but that can use the version from backports now, otherwise they collide and cause compile errors. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mac80211: ath10k: adjust tx power reduction for US regulatory domainSven Eckelmann2019-06-151-0/+101
| | | | | | | | | | | | | | | | | | | | | | | | FCC allows maximum antenna gain of 6 dBi. 15.247(b)(4): > (4) The conducted output power limit > specified in paragraph (b) of this section > is based on the use of antennas > with directional gains that do not exceed > 6 dBi. Except as shown in paragraph > (c) of this section, if transmitting > antennas of directional gain greater > than 6 dBi are used, the conducted > output power from the intentional radiator > shall be reduced below the stated > values in paragraphs (b)(1), (b)(2), > and (b)(3) of this section, as appropriate, > by the amount in dB that the > directional gain of the antenna exceeds > 6 dBi. https://www.gpo.gov/fdsys/pkg/CFR-2013-title47-vol1/pdf/CFR-2013-title47-vol1-sec15-247.pdf Signed-off-by: Sven Eckelmann <sven@narfation.org>
* mac80211: ath10k: fix max antenna gain unitSven Eckelmann2019-06-151-0/+49
| | | | | | | | | | | | | | | Most of the txpower for the ath10k firmware is stored as twicepower (0.5 dB steps). This isn't the case for max_antenna_gain - which is still expected by the firmware as dB. The firmware is converting it from dB to the internal (twicepower) representation when it calculates the limits of a channel. This can be seen in tpc_stats when configuring "12" as max_antenna_gain. Instead of the expected 12 (6 dB), the tpc_stats shows 24 (12 dB). Tested on QCA9888 and IPQ4019 with firmware 10.4-3.5.3-00057. Signed-off-by: Sven Eckelmann <sven@narfation.org>
* mac80211: ath9k: Increase allowed antenna gain to 6 dBiSven Eckelmann2019-06-151-3/+3
| | | | | | | | | | | | | | | | | | | | | | FCC allows maximum antenna gain of 6 dBi. 15.247(b)(4): > (4) The conducted output power limit > specified in paragraph (b) of this section > is based on the use of antennas > with directional gains that do not exceed > 6 dBi. Except as shown in paragraph > (c) of this section, if transmitting > antennas of directional gain greater > than 6 dBi are used, the conducted > output power from the intentional radiator > shall be reduced below the stated > values in paragraphs (b)(1), (b)(2), > and (b)(3) of this section, as appropriate, > by the amount in dB that the > directional gain of the antenna exceeds > 6 dBi. Signed-off-by: Sven Eckelmann <sven@narfation.org>
* mac80211: update to version 4.19.32-1Hauke Mehrtens2019-04-061-73/+0
| | | | | | | | The removed patches are now integrated in the upstream kernel. Refresh all patches on top of the new backports release. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Tested-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
* mac80211: ath10k: fix incorrect multicast/broadcast rate settingSven Eckelmann2019-02-261-0/+43
| | | | | | | | | If no mcast_rate is set for the wifi-iface then there is no rate_idx (0) set for the bss. This breaks for example 5GHz meshpoint interfaces because 0 maps to a CCK rate (11Mbit/s). Fixes: db90c243a0b9 ("mac80211: update to version based on 4.19-rc4") Signed-off-by: Sven Eckelmann <sven@narfation.org>
* mac80211: update to version 4.19.23-1Hauke Mehrtens2019-02-178-212/+13
| | | | | | | | This updates mac80211 to backports version 4.19.23-1 which includes all the stable fixes from kernel 4.19.23. The removed patches are included in this version. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mac80211: ath10k: support for management rate controlSven Eckelmann2019-02-112-0/+155
| | | | | | | | | | | | | Issues a wmi command to firmware when multicast rate change is received with the new BSS_CHANGED_MCAST_RATE flag. Also fixes the incorrect fixed_rate setting for CCK rates which got introduced with addition of ath10k_rates_rev2 enum. By default the firmware uses 1Mbps and 6Mbps rate for management packets in 2G and 5G bands respectively. But when the user selects different basic rates from the userspace, we need to send the management packets at the lowest basic rate selected by the user. Signed-off-by: Sven Eckelmann <sven@narfation.org>
* mac80211: ath: add extra 'regulatory domains'Oever González2019-01-261-0/+35
| | | | | | | | | | | | This patch adds several country codes to the regd.h and regd_common.h files in order to support devices whose country codes are not present in the original list. Without this patch, all devices whose manufacturer programmed any of these code in their EEPROM will run without wireless interfaces. Signed-off-by: Oever González <notengobattery@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [matched signed-off]
* mac80211: ath10k: remove "ath10k: fix otp failure result" patchChristian Lamparter2019-01-241-11/+0
| | | | | | | | | | | | | | Initially this patch was introduced as a quick fix following the removal of 936-ath10k_skip_otp_check.patch which caused multiple ath10k pcie devices in various ipq806x and ar71xx/ath79 targets to malfunction. Thankfully, the affected devices have been updated to utilize the pre-caldata method. And finally with the switch to ath10k-ct, which never had the patch or any reports of similar issues, I think it's time to remove this patch since it is no longer needed. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ath9k: Avoid OF no-eeprom quirks when no qca,no-eepromDaniel F. Dickinson2018-12-221-0/+73
| | | | | | | | | | | | | | | | | | Based on the process of discovery in https://github.com/openwrt/openwrt/pull/1613, it has become clear that (at least) the PowerCloud System CR5000 was unable to get working 5GHz wireless (PCIe) because AH_USE_EEPROM was unconditionally masked out, not only when qca,noeeprom was in the DTS. This patch moves mask AH_USE_EEPROM into the if ... qca,noeeprom OF test. Thanks to Christian Lampartar (@chunkeey) for the heavy lifting and help. Patch has been prepared for upstream and will be submitted after review by @chunkeey and @xdarklight. Signed-off-by: Daniel F. Dickinson <cshored@thecshore.com>
* mac80211: Update to version 4.19.7-1Hauke Mehrtens2018-12-136-13/+13
| | | | | | | | | | | This updates the backports package used in mac80211 to version 4.19.7-1 which is based on kernel 4.19.7. This integrates all the stable fixes introduces in this kernel version. The deleted patches are not needed any more because they are either included in the upstream Linux kernel 4.19.7 or in backports 4.19.7-1. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ath9k: register GPIO chip for OF targetsMathias Kresin2018-12-122-10/+19
| | | | | | | | | | | | | | | | | This partitialy reverts commit ccab68f2d399. Registering the GPIO chip without a parent device completely breaks the ath9k GPIOs for device tree targets. As long as boards using the devicetree don't have the gpio-controller property set for the ath9k node, the unloading of the driver works as expected. Register the GPIO chip with the ath9k device as parent only for OF targets to find a trade-off between the needs of driver developers and the broken LEDs and buttons seen by users. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ath9k: fix dynack in IBSS modeKoen Vandeputte2018-11-065-0/+309
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, dynack was only tested upstream using AP/STA mode. Testing it on IBSS, showed that late-ack detection was broken. This is caused due to dynack using Association Request/Response frames for late-ack detection, which IBSS does not use. Also allowing Authentication frames here solves this. A second issue also got fixed, which was also seen AP/STA mode: When a station was added, the estimated value would be exponentially averaged using 0 as a starting point. This means that on larger distances, the ack timeout was still not high enough before synchronizing would run out of late-ack's for estimation. Fix this by using the initial estimated value as a baseline and only start averaging in the following estimation rounds. Test setup: - 2x identical devices: RB912UAG-5HPnD + 19dB sector - IBSS - 2x2 802.11an (ar9340), HT20, long GI - RSSI's -70 / -71 - Real distance: 23910 meter Results (60s iperf runs): Fixed coverage class 54 (up to 24300m): * 21.5 Mbits/sec Dynack: * 28.9 Mbits/sec Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* mac80211: Add patches which were added laterHauke Mehrtens2018-09-261-0/+96
| | | | | | | | These patches were added after the new matches structure for the mac80211 package was created. All the deleted patches are already integrated in kernel 4.19-rc4. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mac80211: update to version based on 4.19-rc4Hauke Mehrtens2018-09-2642-518/+132
| | | | | | | | | | | | This updates mac80211 to backports based on kernel 4.19-rc4. I plan to integrate all the patches which are in this tar into upstream backports soon. I used the backports generated from this code: https://github.com/hauke/backports/commits/wip2 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mac80211: rebase ontop of v4.18.5John Crispin2018-09-2660-0/+4860
Signed-off-by: John Crispin <john@phrozen.org>