aboutsummaryrefslogtreecommitdiffstats
path: root/package/firmware/ath10k-firmware
Commit message (Collapse)AuthorAgeFilesLines
* ath10k-firmware: fix mirror hashDENG Qingfang2020-01-241-1/+1
| | | | | | | | | Fix PKG_MIRROR_HASH hash mismatch. Fixes: 641a93f0f226 ("ath10k-firmware: update wave 1 firmware to 10.2.4-1.0-00047") Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn> [added missing commit description] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath10k-firmware: Add kmod-ath10k-ct-smallbuffers to dependsHauke Mehrtens2019-12-241-6/+6
| | | | | | | Only select ath10k-ct-regular when smallbuffers version was not selected. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ath10k-firmware: update Candela Tech firmware imagesStefan Lippers-Hollmann2019-12-231-20/+20
| | | | | | | | | | | | | | | | | The release notes since last time for wave-1: * No changes to wave-1, but I make a version .014 copy anyway to keep the makefile in sync. The release notes since last time for wave-2: * December 16, 2019: Wave-2 has a fix to make setting txpower work better. Before setting the power was ignored at least some of the time (it also appeared to work mostly, so I guess it was being correctly set in other ways). Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ath10k-firmware: update Candela Tech firmware imagesKoen Vandeputte2019-12-101-24/+24
| | | | | | | | | | | | | | The release notes since last time for wave-1: * November 29, 2019: Fix IBSS merge issue, related to TSF id leakage bug in firmware code. Thanks for Ahmed Zaki @ Mage-Networks for helping to diagnose and test. The release notes since last time for wave-2: * December 6, 2019: Fix 160Mhz problem caused by logic that did not take into account the fact that 160Mhz has only 1/2 of the NSS of lower bandwidths in the rate table. Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ath10k-firmware: update Candela Tech firmware imagesKoen Vandeputte2019-11-051-24/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | The release notes since last time for wave-1: * October 5, 2019: Fix too-short msg caused by invalid use of PayloadLen in receive path. This appears to resolve the issue of getting (and ignoring) too-short commands when we detect loss of CE interrupts and go into polling mode. * October 12, 2019: Fix regression in IBSS mode that caused SWBA overrun issues. Related to regression added during the ct-station logic, specifically TSF allocation. Thanks for Ahmed Zaki @ Mage-Networks for helping to diagnose and test. * October 15, 2019: Only send beacon tx completion events if we can detect CT driver is being used (based on CT_STATS_OK flag being set). This should help CT firmware work better on stock driver. The release notes since last time for wave-2: * October 15, 2019: Only send beacon tx completion events if we can detect CT driver is being used (based on ATH10k_USE_TXCOMPL_TXRATE2 | ATH10k_USE_TXCOMPL_TXRATE1 flags being set). This should help CT firmware work better on stock driver. * October 31, 2019: Compile out peer-ratecode-list-event. ath10k driver ignores the event. * November 1, 2019: Fix rate-ctrl related crash when nss and other things were changed while station stays associated. See bug: https://github.com/greearb/ath10k-ct/issues/96 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ath10k-firmware: update wave 1 firmware to 10.2.4-1.0-00047David Bauer2019-10-271-5/+5
| | | | | | | This fixes frequent crashes observed on a UniFi AC Mesh using OpenWrt master and 19.07. 18.06 seems not affected from our testing. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath10k-firmware: retrieve wave 1 firmware from kvaloDavid Bauer2019-10-271-2/+2
| | | | | | | | | | | | | This commit changes the source of the Wave 1 ath10k-firmware from linux-firmware to Kall Valos ath10k-firmware repository. This is necessary as the firmware selected in linux-firmware produces frequent crashes in some circumstances. This patch can be removed as soon as linux-firmware carries 10.2.4-1.0-00047 firmware. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath10k-firmware: update Candela Tech firmware imagesRobert Marko2019-09-151-20/+20
| | | | | | | This enables a feature flag in the wave-2 firmware wmi-services indicating it can send software-encrypted raw frames. This should in turn allow the AP-VLAN feature to work. Signed-off-by: Robert Marko <robimarko@gmail.com>
* ath10k-firmware: update Candela Tech firmware imagesKoen Vandeputte2019-08-271-24/+24
| | | | | | | | | | | | | | | | | | | | | | | | | This should fix a problem with 1560 MTU, 160Mhz on DFS channels, some other small issues on < 5.2 kernels, and for 5.2 driver, it pulls in some upstream stable fixes. wave-1 firmware changes since last update: * June 24, 2019: Try allocating low-priority WMI msgs if high-prio are not available. * June 24, 2019: Init rate-ctrl to start at lowest rate instead of in the middle. Hoping this helps DHCP when station connects from a long distance. wave-2: * June 24, 2019 Start rate-ctrl at minimal values to help DHCP work better for far-away peers. * July 24, 2019 Fix old regression that made /a (and probably /b/g) perform poorly, at least on diet-compiled images. * Aug 8, 2019 Improve a/b/g rate-ctrl by damping the PER swings caused by the all-or-nothing logic of transmitting non-block-ack frames one at a time. Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ath10k-firmware: Fix mirror hashHauke Mehrtens2019-07-071-1/+1
| | | | | Fixes: 7f79882d44ba ("ath10k-firmware: update board-2.bin for community firmwares") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ath10k-firmware: update board-2.bin for community firmwaresChristian Lamparter2019-07-071-3/+3
| | | | | | | | This patch updates the board-2.bin for the default IPQ4019, QCA9984 and QCA9888 ath10k-firmware-xyz-ct and -ct-htt firmwares. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ath10k-firmware: update Candela Tech firmware imagesKevin Darbyshire-Bryant2019-06-131-24/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | wave-1: 2019-05-09: Tweak rate-ctrl: Ramp PER up faster, down slower. This helps throughput in rate-vs-range test, especially with nss1. 2019-05-20: Disable adaptive-CCA. I am not sure it helps, and it may make it slower to detect noise that should tell the system to stop transmitting. If someone has means to test this properly, I'd be happy to work with them. wave-2: 2019-05-15: Fix problem where rate-ctrl sometimes used rix of 0x0. 2019-05-15: Allow raw-tx of encrypted frame. Requires a patch to the driver to use raw mode when skb has WEP flag enabled AND skb is flagged to not be encrypted. Lightly tested. 2019-05-16: Fix tx-hang that happened when rate-ctrl chose an OFDM rate for 20Mhz and sent that as AMPDU. To fix, limit to (V)HT rates if peer is (V)HT. It seems that MCS0 (V)HT20 should have as good of a chance of being detected as CCK or OFDM. 2019-06-06: Disable TX-BFEE, TX-BFER for IBSS connections. I suspect this is part of the tx-hang issue seen with IBSS between two 9984 radios. 2019-06-12: Fix rx-rate reporting in 'fw_stats' logic. This was at least partly due to regressions I had added earlier when working on some multi-vdev enhancements. 2019-6-12: Fix case where extd peer-stats were not always populated. The stats gathering code did not handle error conditions well. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* ath10k-firmware: update Candela Tech firmware imagesRobert Marko2019-05-111-24/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Release notes since last time: Release notes for wave-1: 2019-04-02: Support some get/set API for eeprom rate power tables. Mostly backported from 10.2 2019-04-02: Support adaptive-CCA, backported from 10.2 2019-04-02: Support adding eeprom configAddr pairs via the set-special API. These configAddrs can be used to change the default register settings for up to 12 registers. 2019-05-03: Fix tx-power settings for 2x2, 3x3 rates. Original logic I put in back in 2016 set 2x2 and 3x3 lower than the needed to be when using most NICs (very high powered NICs would not have been affected I think, not sure any of those exist though.) This improves throughput for 2x2 and 3x3 devices, especially when the signal is weaker. Release notes for wave-2: 2019-04-08: When setting keys, if high bit of high value of key_rsc_counter is set to 0x1, then the lower 48 bits will be used as the PN value. By default, PN is set to 1 each time the key is set. 2019-04-08: Pack PN into un-used 'excretries' aka 'num_pkt_loss_excess_retry' high 16 bits. This lets us report peer PN, but *only* if driver has previously set a PN when setting key (or set-special cmd is used to enable PN reporting). This is done so that we know the driver is recent enough to deal with the PN stat reporting. 2019-04-16: Support specifying tx rate on a per-beacon packet. See ath10k_wmi_op_gen_beacon_dma and ath10k_convert_hw_rate_to_rate_info for API details. Driver needs additional work to actually enable this feature currently. 2019-04-30: Compile out tx-prefetch caching logic. It is full of tricky bugs that cause tx hangs. I fixed at least one, but more remain and I have wasted too much time on this already. 2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5. This significantly helps DHCP happen quickly, probably because the initial rate being too high would take a while to ramp down, especially since there are few packets sent by the time DHCP needs to start. This bug was triggered by me decreasing retries of 0x1e (upstream default) to 0x4. But, I think it is better to start with lower initial MCS instead of always having a very high retry count. Tested on 8devices Jalapeno dev board(IPQ4019) Signed-off-by: Robert Marko <robimarko@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
* ath10k-firmware: update Candela Tech firmware imagesChristian Lamparter2019-03-301-24/+24
| | | | | | | | | | | | | | | | | | | Release notes since last time: Release notes for wave-1 / 10.1: 2019-03-28: Fix sometimes using bad TID for management frames in htt-mgt mode. (Backported from wave2, looks like bug would be the same though.) Release notes for wave-2 / 10.4: 2019-03-28: Fix off-channel scanning while associated in proxy-station mode. 2019-03-29: Fix sometimes sending mgt frames on wrong tid when using htt-mgt. This bug has been around since I first enabled htt-mgt mode. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ath10k-firmware: update Candela Tech firmware imagesChristian Lamparter2019-03-251-24/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Release notes since last time: Release notes for wave-1: - 2019-03-12: Add btcoex feature flag for 2.4Ghz only adapters, backported from upstream 10.2 firmware. - 2019-03-12: Support offloading decrypt of PMF blockack frames to the host. This lets us do blockack with PMF and rx-sw-crypt. Normal hwcrypt scenarios would not need this. Release notes for wave-2: - 2019-03-12: Fix crash when tearing down VI TID when pending frames exist. Could reproduce this while doing rmmod when VI traffic was flowing and PMF was enabled but broken. Bad luck could rarely cause it to happen in more normal config too. - 2019-03-12: Support offloading decrypt of PMF blockack frames to the host. This lets us do blockack with PMF and rx-sw-crypt. Normal hwcrypt scenarios would not need this. - 2019-03-12: Re-work problematic patch that attempted to fix transmit on non-QOS tids. It appears buggy in several ways, hopefully improved now. This was introduced last fall. See github bug 78. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ath10k-firmware: update Candela Tech firmware imagesMichael Yartys2019-03-061-24/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Release notes since last update: wave-1 firmware: * Feb 14, 2019: Remove logic that causes assert when swba logic is not initialized. This was seen when trying to bring up 6 VAP vdevs. A similar fix went into wave-2 firmware some time ago. * Feb 27, 2019: Support up to 32 vAP vdevs, fix stack corruption when driver requests too many vAP. * Feb 28, 2019: Support beacon-tx-wmi callback message. This lets driver properly clean up beacon buffers so we don't crash (somethings the entire OS/system) due to DMA errors. wave-2 firmware: * Feb 27. 2019: Support up to 32 AP vdevs. Previous to this, stack would be corrupted if you went past 16 AP vdevs. * Feb 28, 2019: Support beacon-tx-wmi callback message. This lets driver properly clean up beacon buffers. In wave-1, this could crash the entire OS, but I didn't see the same crashes in wave-2, so maybe it is fixed in some other way. Add the feature regardless as it seems proper. Signed-off-by: Michael Yartys <michael.yartys@gmail.com>
* ath10k-firmware: update Candela Tech firmware imagesChristian Lamparter2019-02-111-16/+16
| | | | | | | | | | | | | | | | | | Release notes since last time: 2019-02-08: Fix rate-ctrl assert related to bad logic that tried to guess that lower bandwidth probes were automatically successful if higher was. The NSS mismatch that can happen here caused the assert. Just comment out the offending code (per comment from original QCA code). This is bug 69. 2019-02-10: Fix bssid mis-alignment that broke 4-addr vlan mode (bug 67). Original buggy commit was commit 2bf89e70ecd1 ("dev-ds: Better packing of wal_vdev struct.") Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ath10k-firmware: update Candela Tech firmware imagesKoen Vandeputte2019-02-041-16/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Jan 2, 2019 Rebase patches to make 9980 bisectable. * Jan 2, 2019 Fix scheduling related assert when wal-peer is deleted with pending tx buffers (bug 54, and others) * Jan 7, 2019: Fix specifying retransmits for AMPDU frames. It was previously ignored since it is a 'software' retransmit instead of a hardware retransmit. * Jan 9, 2019 Fix potential way to get zero rates selected (and then assert) * Jan 18, 2019 pfsched has specific work-around to just return if we find invalid flags AND if we are in an out-of-order situation. Maybe this is last of the pfsched related issues (bug 54 and similar). * Jan 24, 2019 The rcSibUpdate method can be called concurrently with IRQ tx-completion callback, and that could potentially allow the tx-completion callback to see invalid state and assert or otherwise mess up the rate-ctrl logic. So, disable IRQs in rcSibUpdate to prevent this. Related to bug 58. * Jan 28, 2019 Ensure that cached config is applied to ratectrl objects when fetched from the cache. This should fix part of bug 58. * Jan 28, 2019 Ensure that ratectrl objects from cachemgr are always initialized. This fixes another part of bug 58. * Jan 30, 2019 Better use of temporary rate-ctrl object. Make sure it is initialized, simplify code path. This finishes up porting forward similar changes I made for wave-1 firmware long ago, and fixes another potential way to hit bug-58 issues. * Jan 30, 2019 Cachemgr did not have a callback for when memory was logically freed. This means that peers could keep stale references to rate-ctrl objects that were in process of being DMA'd into to load a different peer's rate-ctrl state. This was causing the bugcheck logic to fail early and often, and I suspect it might be a root cause of bug 58 as well. The fix is to add a callback and set any 'deleted' memory references to NULL so that we cannot access it accidentally. Thanks to excellent logs and patience from the bug-58 reporter! Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ath10k-firmware: update Candela Tech firmware imagesJo-Philipp Wich2018-12-201-22/+22
| | | | | | | - Removed an assert from wave-1 firmware images - Fix three recently reported firmware crashes in wave-2 images Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ath10k-firmware: update all CT firmware variantsMichael Yartys2018-12-151-32/+32
| | | | | | | Wave-1 firmware (988x, 9887): bug fixes Wave-2 firmware (4019, 9888, 99x0, 9984): fix protected management frames, rate-ctrl fixes, and performance improvements Signed-off-by: Michael Yartys <michael.yartys@gmail.com>
* ath10k-firmware: Fix mirror hash sum (FS#1983)Christian Lamparter2018-12-091-1/+1
| | | | | | | | This now matches what was generated locally on my PC and the file on the mirror server. Fixes: 575d0240f9593 ("ath10k-firmware: update board-2.bin for community firmwares") Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ath10k-firmware: update board-2.bin for community firmwaresChristian Lamparter2018-11-011-3/+3
| | | | | | | | This patch updates the board-2.bin for the default IPQ4019, QCA9984 and QCA9888 ath10k-firmware-xyz-ct and -ct-htt firmwares. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ath10k-firmware: disable the package and use default linux-firmware packageJohn Crispin2018-09-261-7/+7
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* ath10k-firmware: update both QCA988X CT variantsStijn Tintel2018-08-261-4/+4
| | | | | | This fixes slow performance with 802.11w enabled. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* ath10k: update QCA4019 firmwareMassimo Tum2018-07-301-1/+1
| | | | | | | | | | With AVM Fritz!Box 4040 and OpenWrt 18.06 RC1 there are many kernel warnings kern.warn kernel: [87771.917049] ath10k_ahb a000000.wifi: Invalid VHT mcs 15 peer stats and there are disconnections when the connected clients are many, at the moment I tried with 16 clients on 2.4 GHz and 8 on 5 GHZ. Firmware 10.4-3.5.3-00057 fixes these warnings and the problem of disconnections of some clients. Signed-off-by: Massimo Tum <masnia@tiscali.it>
* ath10k-firmware: Fix two more typosRosen Penev2018-05-301-2/+2
| | | | | | Actually tested with a local build instead of with scp'ing the firmware. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* ath10k-firmware: Fix typo in last commitRosen Penev2018-05-271-2/+0
| | | | Signed-off-by: Rosen Penev <rosenp@gmail.com>
* ath10k-firmware: Fix QCA6174 supportRosen Penev2018-05-271-2/+16
| | | | | | | | | | | | | | Currently when installing the firmware, a bunch of files and directories that the ath10k driver does not look for are created. The package now installs firmware for both hw 2.1 and 3.0 devices. 2.1 is abandonware but may be useful to keep. 3.0 firmware was tested on a Killer 1535 to be relatively stable with 802.11w disabled. 802.11w causes multiple firmware crashes but that's true of other ath10k firmwares as well. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* ath10k-firmware: Fix mirror hash sumHauke Mehrtens2018-05-211-1/+1
| | | | | | | | This now matches what was generated locally on my PC and the file on the mirror server. Fixes: 349fe46103359 ("ath10k-firmware: Update QCA988X firmware to the latest version") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ath10k-firmware: Update QCA988X firmware to the latest versionTimo Sigurdsson2018-05-181-4/+4
| | | | | | | | | | This patch updates the QCA988X firmware to the latest revision firmware-5.bin_10.2.4-1.0-00037 found in the ath10k-firmware and linux-firmware repositories. Tested on TP-Link Archer C7 v2 (ar71xx). Signed-off-by: Timo Sigurdsson <public_timo.s@silentcreek.de>
* firmware: ath10k-firmware: update to 2018-04-19Sven Eckelmann2018-04-231-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * introduces the BDFs in /lib/firmware/ath10k/QCA4019/hw1.0/board-2.bin for: - 8devices Jalapeno - Asus RT-AC58U - AVM FRITZ!Box 4040 - GL.iNet GL-B1300 - Meraki MR33 - Netgear EX6100v2 - Netgear EX6150v2 - OpenMesh A62 * introduces the BDFs in /lib/firmware/ath10k/QCA9888/hw2.0/board-2.bin - OpenMesh A62 * adds new firmware for QCA6174 hw3.0 - firmware-6.bin_RM.4.4.1.c1-00038-QCARMSWP-1 - firmware-6.bin_RM.4.4.1.c1-00041-QCARMSWP-1 * various undocumented BDF updates to: - QCA4019 hw1.0: + bus=ahb,bmi-chip-id=0,bmi-board-id=16 + bus=ahb,bmi-chip-id=0,bmi-board-id=17 + bus=ahb,bmi-chip-id=0,bmi-board-id=19 + bus=ahb,bmi-chip-id=0,bmi-board-id=20 + bus=ahb,bmi-chip-id=0,bmi-board-id=21 + bus=ahb,bmi-chip-id=0,bmi-board-id=29 + bus=ahb,bmi-chip-id=0,bmi-board-id=30 - QCA9888 hw2.0: + bus=pci,bmi-chip-id=0,bmi-board-id=16 + bus=pci,bmi-chip-id=0,bmi-board-id=17 + bus=pci,bmi-chip-id=0,bmi-board-id=18 + bus=pci,bmi-chip-id=0,bmi-board-id=23 + bus=pci,bmi-chip-id=0,bmi-board-id=24 + bus=pci,bmi-chip-id=0,bmi-board-id=25 - QCA9984 hw1.0: + bus=pci,bmi-chip-id=0,bmi-board-id=1 + bus=pci,bmi-chip-id=0,bmi-board-id=3 + bus=pci,bmi-chip-id=0,bmi-board-id=5 + bus=pci,bmi-chip-id=0,bmi-board-id=6 + bus=pci,bmi-chip-id=0,bmi-board-id=7 + bus=pci,bmi-chip-id=0,bmi-board-id=8 Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
* ath10k-ct: Update firmwareBen Greear2018-04-131-24/+24
| | | | | | | | | | | | | | | This firmware has only small changes from the last commit, but it does have an important fix for at least some PTK rekey logic. The old firmware would have issues if the driver managed to set a clear key while encryption was 'enabled'. This new firmware for both wave-1 and wave-2 should not be susceptible to this type of bug any more. And remove mesh-bcast IE flag from wave-2, still need more work before we can enable that flag in ath10k-ct firmware it seems. Signed-off-by: Ben Greear <greearb@candelatech.com>
* ath10k-ct: Update firmware to latest.Ben Greear2018-03-311-29/+29
| | | | | | | | | | | | | | Wave-1 firmware has a fix for 'addba' not finding the peer. Thanks to Hauke for finding and reporting this. Wave-2 firmware has a fix for leaking a peer multicast key when a monitor device is created. And I re-ordered the '4019' firmware images in the Makefile to match the order of the others. No functional change for that reorder. Signed-off-by: Ben Greear <greearb@candelatech.com> Tested-by: Rosen Penev <rosenp@gmail.com>
* ath10k-ct: Add htt-mgt variants of ath10k-ct firmware.Ben Greear2018-03-231-33/+217
| | | | | | | | | | | | | | | | | | The HTT-MGT variants transport management frames over the normal HTT tx path, just like data frames. This saves limitted WMI buffers which can become depleted if lots of management frames become stuck in TX queues due to peer that went away. In addition, at least for the wave-1 firmware, htt-mgt is required in order for 802.11r (fast roaming) authentication to function properly. The htt-mgt firmware requires the use of the ath10k-ct driver. Normal non-htt-mgt ath10k-ct firmware should work with stock drivers. Signed-off-by: Ben Greear <greearb@candelatech.com>
* ath10k-ct: Update wave-1 and wave-2 firmware to latest.Ben Greear2018-03-231-14/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This updates to latest ath10k-ct firmware. Hopefully we are at the end of the development cycle for this firmware release, so these should be stable. wave-1 changes since last release: Release 20 * Allow flushing peer when deleting. Hopefully this will allow the peer delete command to happen in a reasonable amount of time even if the RF environment is busy (or peer has died). To enable this, set the high flag in the mac-addr second word in the ath10k driver near end of the ath10k_wmi_op_gen_peer_delete method: cmd->peer_macaddr.word1 |= __cpu_to_le32(0x80000000); * Attempt to fix crash seen in resmgr-ocs, appearantly due to list corruption. Use a temporary list instead of trying to rely on for-each-safe. * Add flag to tx-descriptor to allow driver to request no-ack on data frames. This is bit 15 on the flag1 field (previously un-used). * Add option to support specifying the tx-rate-code and retry count on a per-packet basis. Only a single series is supported at this time. Useful mainly for radiotap monitor-tx type testing at this point. * Fix crash on startup when chip is at -40 deg C and calibration fails. Instead of asserting, just keep retrying calibration, which appears to start working after a few minutes (when the chip warms up). * Allow reporting per-chain rssi for management frames. We pack the values into empty space in the mgt-frame wmi header. This will only be enabled if the driver requests it, since otherwise the driver is assumed to not understand the new API. ath10k-ct drivers that support this feature will automatically enable it. * A customer reports a case that appears to be the hardware not properly detecting end of AMPDU, so frames were being mis-delivered to the wrong peer. Attempt to work around this, and in doing so, clean up a bunch of void* abuse in the block-ack reordering code (could not ever confirm there was a problem in this area). * Re-work the rx-mem logic to be less complicated and to use less memory. * Attempt to fix crash that appearanty happens because the driver can sometimes delete a vdev in 'up' state. * Attempt to fix hung scan state machine issues. * Fix crash in tx path due to un-initialized memory. wave-2 changes since last release: Release 10 * Fix an assert related to tx scheduling. This hopefully fixes what appears to be a regression that I added some time back. * Enable CSI reporting for 9984, and maybe 9888/9886. Only in non-trimmed builds. * Other stability improvements, including regression fixes from some tricky bugs introduced in earlier releases. * Allow compiling for IPQ4019 chipset. * Firmware will now send txbf frames to the host (driver) if the TXBF (0xF00000001) set-special feature is enabled, or when the radio is in monitor mode. But, if the frame is consumed by the txbf_cv logic, then the pkt cannot be delivered to the host in this manner. Instead, a WMI event will be sent and host can find the txbf_cv data in shared memory. See ath10k_wmi_event_txbf_cv_mesg() in ath10k-ct driver. * Support rx-all-mgt option. When enabled, the firmware will deliver all management frames that it can to the host. No RX filters are changed when this option is enabled. * Fix at least some problems with sending tx-beamforming frames to SU-MIMO peers. Looks like this was a regression in my code. * Fix a crash in rate-ctrl due to nss mismatch. This was something I introduced while trying to fix other bugs in rate-ctrl some time back. * Attempt to fix a sw-peer-key object leak in IBSS mode. The peer key code is very complex, and shares some pointers as union members. I think I fixed at least some of the issues, but would not be surprised if more exist. * Improve ath10k user guide to document CT firmware features: https://www.candelatech.com/ath10k-ug.php * Add ct-special option to configure the txbf sounding time. See ath10k-ug.php * Fix and allow the driver to tell the firmware to send sounding frames. See ath10k-ug.php In further testing, this seems to fail much of the time, and I am not sure why. Disabling this in diet (trimmed) builds. * Fix crashes related to deleting peers while they are in power-save mode. Reported by LEDE user on r7800 with 9984 NIC. * Make rate-ctrl txbf probe work better. If enabled, the rate-ctrl logic will periodically send out probes at an NSS that can to txbf. Previously, txbf probes would not reliably happen if both AP and peer had the same nss (ie, 2x2 talking to 2x2). To enable this feature, you need to enable the fwtest-cmdid number 20. * Report rx-timeout error counters. These were previously un-reported, though the field existed in the wmi struct already. * txbf: Ignore frames not destined for us. If NIC is in promisc mode, it could acquire and process NDPA frames that were not destined for it. Check the dest-MAC and ignore frames not for us (pass them up the stack for monitor mode instead of save them in the peer's rate-ctrl logic.) * Port ping-pong crash handling and othe related features to IPQ4019 target. It should now act similar to 9984 in this regard. * Fix a few asserts related to txbf and tx-seq logic. * Add custom-stats support, for rx-reorder-stats. Similar to what I did for wave-1. * Disable AMSDU for IBSS. This now matches what I did for peregrine. It seems to work better this way, though I did not debug it in detail. * Enable the set-special command to re-enable AMSDU for IBSS if user wants to experiment. * Fix bug where dbglog did not disable IRQs, so if you made dbglog messages from the IRQ handler, it could cause corruption that could crash the firmware and/or corrupt the log message buffers. * Don't assert if there are no buffer descriptors for RX of non-data frame. * Retry any stuck block-ack sessions every 20 seconds instead of just disabling BA for ever when we get too many failures. * Fix SGI flag when reporting tx-rate info. The flag moved since wave-1 days, and I did not notice that when I ported my changes forward to wave-2. * Allow disabling special CCA handling for IBSS txqs. Earlier testing indicated this might improve throughput in some testing on 9984 chips in IBSS mode, but subsequent testing looks about the same without it. Since I do not really understand what this setting exists for, leave it at upstream defaults. A new set-special API command (0x12) can be used to enable this hack for testing. Setting 0x1 bit disables special CCA handling for non-beacon IBSS txqs, setting 0x2 bit disables it for beacon queues as well. * Add MCAST-BCAST feature flag. This tells driver we do not need a monitor interface to do MESH. * When calculating the rx-address filter (affects ACK & BLOCK-ACK, among other things), to not add in monitor interfaces if other interfaces are up. There is no need for a monitor device to ACK frames. Signed-off-by: Ben Greear <greearb@candelatech.com>
* ath10k-ct: Update DEPENDS and PROVIDESBen Greear2018-03-231-0/+8
| | | | | | | | | | Update DEPENDS and PROVIDES so that ath10k-ct firmware and drivers can be used to replace stock firmware and drivers. The -htt firmware variant, which requires ath10k-ct driver now selects ath10k-ct driver when the firmware is selected. Signed-off-by: Ben Greear <greearb@candelatech.com>
* ath10k-firmware: Support CT IPQ4019 firmware.Ben Greear2018-03-221-3/+71
| | | | | | | Initial beta release of the CT IPQ4019 firmware. Features are similar to the CT 9984 firmware Signed-off-by: Ben Greear <greearb@candelatech.com>
* firmware: ath10k-firmware: update QCA9984 firmware to 10.4-3.5.3-00053Henryk Heisig2018-03-091-1/+1
| | | | | | | | | | | | | | | | | | | This patch updates ath10k-firmware to use the firmware-5.bin_10.4-3.5.3-00053 firmware for the QCA9984. The update fixes "ath10k_pci 0001:01:00.0: Invalid VHT mcs 15 peer stats" spamming the kernel ring buffer at very high frequencies, but introduces the new "ath10k_pci 0001:01:00.0: Unknown eventid: 36925". This new warning doesn't appear to cause problems in practice and is only emitted relatively rarely, not causing dmesg to overflow within minutes. Tested on the ZyXEL NBG6817; early feedback also suggests this firmware to work well (with the same fixes and caveats) on the Netgear r7800 as well. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> Signed-off-by: Henryk Heisig <hyniu@o2.pl>
* firmware: ath10k-firmware: update to 2018-02-09Henryk Heisig2018-03-091-4/+4
| | | | | | | This patch updates ath10k-firmware to last commit and use the firmware-5.bin_10.4-3.5.3-00053 firmware for the QCA9888. Signed-off-by: Henryk Heisig <hyniu@o2.pl>
* firmware: ath10k-firmware: update to 2018-01-26Sven Eckelmann2018-02-111-3/+3
| | | | | | | | | * introduces the BDFs for the OpenMesh A42 in /lib/firmware/ath10k/QCA4019/hw1.0/board-2.bin. * adds new firmware firmware-6.bin_RM.4.4.1.c1-00037-QCARMSWP-1 for QCA6174 hw3.0 Signed-off-by: Sven Eckelmann <sven.eckelmann@open-mesh.com>
* firmware: ath10k-firmware: update QCA988x firmware to 10.2.4-1.0-00033Christian Lamparter2018-01-181-1/+1
| | | | | | | This patch updates ath10k-firmware to use the firmware-5.bin_10.2.4-1.0-00033 firmware for the QCA988x. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* firmware: ath10k-firmware: update QCA9887 firmware to 10.2.4-1.0-00033Christian Lamparter2018-01-181-1/+1
| | | | | | | This patch updates ath10k-firmware to use the firmware-5.bin_10.2.4-1.0-00033 firmware for the QCA9887. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* firmware: ath10k-firmware: update QCA9888 firmware to 10.4-3.4-00104Christian Lamparter2018-01-181-1/+1
| | | | | | | This patch updates ath10k-firmware to use the firmware-5.bin_10.4-3.4-00104 firmware for the QCA9888. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* firmware: ath10k-firmware: update QCA9984 firmware to 10.4-3.4-00104Christian Lamparter2018-01-181-1/+1
| | | | | | | This patch updates ath10k-firmware to use the firmware-5.bin_10.4-3.4-00104 firmware for the QCA9984. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* firmware: ath10k-firmware: update QCA4019 firmware to 10.4-3.4-00104Christian Lamparter2018-01-181-1/+1
| | | | | | | This patch updates ath10k-firmware to use the firmware-5.bin_10.4-3.4-00104 firmware for the QCA4019. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* firmware: ath10k-firmware: update to 2017-12-20Christian Lamparter2018-01-181-3/+3
| | | | | | | This update automatically includes a new firmware for the QCA6174: firmware-6.bin_WLAN.RM.4.4.1-00079-QCARMSWPZ-1 Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* firmware: ath10k-firmware: update QCA4019 firmware to 10.4-3.2.1-00058Christian Lamparter2017-12-081-4/+4
| | | | | | | | This patch updates ath10k-firmware to use the firmware-5.bin_10.4-3.2.1-00058 firmware for the QCA4019. Cc: Hauke Mehrtens <hauke@hauke-m.de> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ath10k-firmware: qca9888 firmware: remove board.binHenryk Heisig2017-10-271-3/+0
| | | | Signed-off-by: Henryk Heisig <hyniu@o2.pl>
* ath10k-ct firmware: Tx-hang and EAPOL handling fixes for wave-2 firmware.Ben Greear2017-10-121-10/+10
| | | | | | | | | | | | | | | | | | Changes since last LEDE release include: * Fix key-setting bug that broke sending the EAPOL 2/4 in some cases. This was a bug I introduced some time back while trying to fix .11r and simplify the key handling logic. (Patch to wpa_supplicant fixed the race with sending the 4/4 and setting the key...un-patched supplicant will still have this race and the 4-way auth will not work as reliably.) * Increase amount of active-tids that can be scheduled. This fixes a tx-stall seen with many station vdevs. * Fix bug in upstream code that would cause the maximum peer to never be scheduled for tx. Signed-off-by: Ben Greear <greearb@candelatech.com>
* ath10k-firmware: use firmware from git instead of extra downloadHauke Mehrtens2017-09-181-28/+3
| | | | | | | | Instead of manually downloading the files again we can also take the same files directly from the ath10k-firmware git which was cloned before. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-12 16:13:10 +0000