Kalle Valo wrote:
> Fixes checkpatch warning:
>
> drivers/net/wireless/ath/ath10k/swap.c:110: Possible unnecessary 'out of
> memory' message
>
> Signed-off-by: Kalle Valo
2 patches applied to ath-next branch of ath.git, thanks.
2189135437d0 ath10k: remove unnecessary 'out of memory'
Kalle Valo wrote:
> Fixes checkpatch warning:
>
> drivers/net/wireless/ath/ath10k/swap.c:110: Possible unnecessary 'out of
> memory' message
>
> Signed-off-by: Kalle Valo
2 patches applied to ath-next branch of ath.git, thanks.
2189135437d0 ath10k: remove unnecessary 'out of memory'
Wen Gong wrote:
> The workqueue need to flush and destory while remove sdio module,
> otherwise it will have thread which is not destory after remove
> sdio modules.
>
> Tested with QCA6174 SDIO with firmware
> WLAN.RMH.4.4.1-7-QCARMSWP-1.
>
> Signed-off-by: Wen Gong
> Signed-off-by:
Wen Gong wrote:
> The workqueue need to flush and destory while remove sdio module,
> otherwise it will have thread which is not destory after remove
> sdio modules.
>
> Tested with QCA6174 SDIO with firmware
> WLAN.RMH.4.4.1-7-QCARMSWP-1.
>
> Signed-off-by: Wen Gong
> Signed-off-by:
Wen Gong wrote:
> ath10k will receive some message with invalid peer id from firmware.
> reason is:
> There are incoming frames to MAC hardware that NOT find relative
> address search table, then peer id is invalid set by MAC hardware,
> it is hardware's logic, so fix it in ath10k will be more
Wen Gong wrote:
> ath10k will receive some message with invalid peer id from firmware.
> reason is:
> There are incoming frames to MAC hardware that NOT find relative
> address search table, then peer id is invalid set by MAC hardware,
> it is hardware's logic, so fix it in ath10k will be more
Dundi Raviteja wrote:
> Currently the memory allocated for qmi handle is
> not being freed during de-init which leads to memory leak.
>
> Free the allocated qmi memory in qmi deinit
> to avoid memory leak.
>
> Tested HW: WCN3990
> Tested FW: WLAN.HL.3.1-01040-QCAHLSWMTPLZ-1
>
> Fixes:
Dundi Raviteja wrote:
> Currently the memory allocated for qmi handle is
> not being freed during de-init which leads to memory leak.
>
> Free the allocated qmi memory in qmi deinit
> to avoid memory leak.
>
> Tested HW: WCN3990
> Tested FW: WLAN.HL.3.1-01040-QCAHLSWMTPLZ-1
>
> Fixes:
Robert Marko writes:
> I am currently working on the Netgear Orbi Pro SRK60 support for
> OpenWrt. This
> AP requires three special BDFs to get the Wi-Fi PHYs working (correctly). The
> bmi-board-id='s would clash with one of the the IPQ401X AP-DK boards because
> QCA doesn't provide special IDs
Jeff Kletsky writes:
> Support for the Linksys EA8300 under OpenWrt is undergoing final
> review. This is a QCA4019-based device with a PCI-attached QCA9888
> supplying a third radio on 5 GHz. The OEM's firmware and source
> suggest that this device is "based on Qualcomm AP DK07.1-c1"
>
>
Jeff Kletsky writes:
> Support for the Linksys EA8300 under OpenWrt is undergoing final
> review. This is a QCA4019-based device with a PCI-attached QCA9888
> supplying a third radio on 5 GHz. The OEM's firmware and source
> suggest that this device is "based on Qualcomm AP DK07.1-c1"
>
>
Robert Marko writes:
> I am currently working on the Netgear Orbi Prok SRK60 support for
> OpenWrt. This
> AP requires three special BDFs to get the Wi-Fi PHYs working (correctly). The
> bmi-board-id='s would clash with one of the the IPQ401X AP-DK boards because
> QCA doesn't provide special
Steve Glennon writes:
> I am adding support for this device to OpenWrt. This AP requires
> two special BDFs to get the Wi-Fi PHYs working (correctly). The bmi-board-
> id='s would clash with one of the the IPQ401X AP-DK boards because QCA
> doesn't
> provide special IDs for customers and
David Bauer writes:
> this is a set of board.bin files for the AVM FRITZ!Repeater 3000 [0],
> which I wish to be added to the ath10k-firmware repository.
>
> As per the current "Submitting board files" guidelines [1]:
>
> * description for what hardware this is:
> - it is a IPQ4019 based board
Oever González writes:
> This is an update to the BDFs sent for the Linksys EA6350v3 device. After
> testing all files from the original firmware, the following files gave
> the best results.
>
> This update contains:
>
> * original files from the OEM firmware known to be the best for the device
David Bauer writes:
> this is a set of board.bin files for the AVM FRITZ!Box 7530 Router [0],
> which I wish to be added to the ath10k-firmware repository.
>
> As per the current "Submitting board files" guidelines [1]:
>
> * description for what hardware this is:
> - it is a IPQ4019 based
Piotr Dymacz writes:
> This is a special BDF for 5 GHz radio inside ALFA Network AP120C-AC
> [0]. In case of 2.4 GHz radio, BDF used by the vendor firmware is the
> same as the one already embedded in the upstream board-2.bin file:
>
> root@AP120C-AC:/# dmesg | grep -i board
> [ 32.198686]
Sven Eckelmann writes:
> The OpenMesh AA2 AP requires two special BDFs to get the Wi-Fi PHYs working
> (correctly). The bmi-board-id='s would clash with one of the the IPQ401X
> AP-DK boards because QCA doesn't provide special IDs for customers and seems
> to use the AP-DK board-ids in the
Sven Eckelmann writes:
> The OpenMesh A62 AP requires three special BDFs to get the Wi-Fi PHYs working
> (correctly). The bmi-board-id='s would clash with one of the the IPQ401X
> AP-DK boards because QCA doesn't provide special IDs for customers and seems
> to use the AP-DK board-ids in the
Sven Eckelmann writes:
> The OpenMesh A62 AP requires three special BDFs to get the Wi-Fi PHYs working
> (correctly). The bmi-board-id='s would clash with one of the the IPQ401X
> AP-DK boards because QCA doesn't provide special IDs for customers and seems
> to use the AP-DK board-ids in the
"Theone" <1805692...@qq.com> writes:
> For the questions from the wiki page:
>
> * description for what hardware this is:
>
> - it is a IPQ4019 based board (AP-DK07-C1)
> - one QCA40xx radio is used as 5 GHz radio
> - one QCA40xx radio is used as 5GHz radio
>
> * origin of the board file
"Theone" <1805692...@qq.com> writes:
> For the questions from the wiki page:
>
> * description for what hardware this is:
>
> - it is a IPQ4018 based board (AP-DK07-C1)
> - one QCA40xx radio is used as 2.4/5 GHz radio
> - one QCA40xx radio is used as 5GHz radio
>
> * origin of the board
"Theone" <1805692...@qq.com> writes:
> * description for what hardware this is:
>
> - it is a IPQ4018 based board (AP-DK07-C1)
> - one QCA40xx radio is used as 2.4/5 GHz radio
> - one QCA40xx radio is used as 5GHz radio
>
> * origin of the board file (did you create it yourself or where you
"张鹏" <1805692...@qq.com> writes:
> Hi,
>
> For the questions from the wiki page:
>
> * description for what hardware this is:
>
> - it is a IPQ4018 based board (AP-DK07-C1)
> - one QCA40xx radio is used as 2.4/5 GHz radio
> - one QCA40xx radio is used as 5GHz radio
>
> * origin of the board
m...@f0wl.cc writes:
> This is a set of board.bin files for the ASUS Lyra MAP-AC2200 Router [0],
> which I wish to be added to the ath10k-firmware repository.
> As per the current "Submitting board files" guidelines [1]:
>
> * description for what hardware this is:
>
> - it is a IPQ4019 based
Oever González writes:
> For the questions from the wiki page:
>
> * description for what hardware this is:
>
> - it is a IPQ4018 based board (AP-DK01.1-C2)
> - one QCA40xx radio is used as 2.4GHz radio
> - one QCA40xx radio is used as 5GHz radio
>
> * origin of the board file (did you
writes:
> The support for this device was added a while ago to OpenWrt. This AP
> requires
> two special BDFs to get the Wi-Fi PHYs working (correctly). The bmi-board-
> id='s would clash with one of the the IPQ401X AP-DK boards because QCA
> doesn't
> provide special IDs for customers and
Hi,
Can you try with this patch ?
https://patchwork.kernel.org/patch/11021495/
Regards,
Balaji.
On 2019-06-01 23:37, Vjaceslavs Klimovs wrote:
Hi Balaji,
Thank you for looking into this.
1) x86_64 AP
2) Compex WLE1216V5-23 or WLE1216V5-20 card with QCA9984
3) any kernel with commit
From: Abhishek Ambure
For all data packets trasmmited, host gets htt tx completion event.
QCA9984 firmware gives data ack rssi values to host through
htt event of data tx completion. Data ack rssi values are valid
if A0 bit is set in HTT rx message.
Tested HW: QCA9984
Tested FW:
29 matches
Mail list logo
