aboutsummaryrefslogtreecommitdiffstats
path: root/package/firmware/ath10k-firmware
Commit message (Collapse)AuthorAgeFilesLines
* 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>
* ath10k-firmware: update qca9887 firmware to 10.2.4-1.0-00029Andreas Ziegler2017-08-231-4/+5
| | | | Signed-off-by: Andreas Ziegler <github@andreas-ziegler.de>
* ath10k-firmware: add qca9888 firmwareJohn Crispin2017-06-271-0/+19
| | | | | | | | | ath10k-firmware: add qca9888 firmware the firmware files for qca9888 were previously not packaged. add the meta information for doing so. Signed-off-by: John Crispin <john@phrozen.org>
* ipq806x: qca99xx: fix wifi calibrationPavel Kubelun2017-06-171-6/+0
| | | | | | | | | | As of now OTP is being correctly parsed and the driver requires to parse pre-caldata to follow corresponding routine. Rename cal file into pre-calfile so the board initialized correctly with API 2 board data (board-2.bin). Also remove the now unneeded for qca9984 board.bin symlink to 5GHz calfile. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
* ath10k-ct-firmware: Add support for QCA9886/QCA9888 firmware.Ben Greear2017-05-181-0/+36
| | | | | | | | | This firmware shoul have the same general feature set as the rest of the 10.4 CT firmware (9984, 9980, etc). Build-tested only in LEDE, but firmware has been tested with ath10k-ct driver on other OSs, so likely works just fine. Signed-off-by: Ben Greear <greearb@candelatech.com>
* ath10k-ct-firmware: Update to latest.Ben Greear2017-05-181-8/+8
| | | | | | | | | | | The 988x and 9887 firmwares include a bugfix for a case where blockack did not work sometimes, and many fixes for compiler warnings detected by newer gcc compilers. The 9980 and 9984 firmware includes a large backport of upstream QCA firmware changes to bring it up to date. Signed-off-by: Ben Greear <greearb@candelatech.com>
* ath10k-firmware: update to latest versionPavel Kubelun2017-04-121-25/+2
| | | | | | Kvalo's repo has a newer version of qca9984 firmware. Use it instead. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
* ath10k-firmware: update the qca988x firmware to 10.2.4-1.0-00029Changmin Jang2017-04-041-4/+4
| | | | | | | | update the qca988x firmware to firmware-5.bin_10.2.4-1.0-00029. According to LEDE Forum, the new firmware supports mesh mode. Also, it seems to have several improvements. Signed-off-by: Changmin Jang <ckdalsdk12@gmail.com>
* ath10k-firmware: do not select the qca988x by defaultMathias Kresin2017-03-241-1/+0
| | | | | | | | Do not select the qca988x by default as soon as kmod-ath10k is selected. We do support more ath10k chips than the qca988x in the meantime, so this dependency doesn't make sense any longer. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ath10k-firmware: firmware package for QCA4019 devicesChristian Lamparter2017-03-221-0/+18
| | | | | | | This patch adds a new firmware package to ath10k-firmware called ath10k-firmware-qca4019. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ath10k-firmware: bump to latest versionChristian Lamparter2017-03-221-3/+3
| | | | Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ath10k-firmware: update qca9984 firmwarePavel Kubelun2017-03-031-3/+3
| | | | | | Bump qca9984 firmware. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
* ath10k-firmware: update qca9984 firmwarePavel Kubelun2017-02-141-3/+3
| | | | | | Bump qca9984 firmware. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
* ath10k-firmware: revert faulty PKG_SOURCE_DATE change from 7cb27b46Felix Fietkau2017-02-011-1/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ath10k-firmware: update qca9984 firmware and board dataPavel Kubelun2017-02-011-5/+5
| | | | | | | | Fixes firmware crash in rare cases and a bug ath10k_pci 0001:01:00.0: received unexpected tx_fetch_ind event: in push mode for those who kept experiencing it after previous firmware update. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
* ath10k-ct: Support ath10k CT firmware for 9887 chipsets.Ben Greear2017-02-011-3/+41
| | | | | | | | | | | And, update support for 9880 chipsets. The new firmware fixes a regression with EAPOL 4/4 packets added in a recent commit. It also fixes a case where the firmware would improperly try to use STBC when configured for 1x1 (as 9887 always is). Signed-off-by: Ben Greear <greearb@candelatech.com>
* ath10k-firmware: Update QCA988X firmware to latest versionTimo Sigurdsson2017-01-151-4/+4
| | | | | | | | | | This patch updates the QCA988X firmware to the latest revision firmware-5.bin_10.2.4-1.0-00016 found in the official ath10k-firmware repository. Tested on TP-Link Archer C7 v2. Signed-off-by: Timo Sigurdsson <public_timo.s@silentcreek.de>
* ath10k-fw: Update to latest CT firmwareBen Greear2017-01-131-7/+7
| | | | | | | | | For 988X, 9980, 9984 CT firmware. This should allow IBSS + RSN on at least the 988X firmware, and includes recent stability fixes for all firmware. Signed-off-by: Ben Greear <greearb@candelatech.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-02 13:38:36 +0000