Not able to set single rate in ath10k (backports-4.14-rc2-1)

Hi, I got the same error while setting single rate in ath10k firmware version : firmware-5.bin_10.2.4.70.66 ath10k version : backports-4.14-rc2-1.tar.xz After running following commands, I got error and rate didn't set. Please see following log for error and help me to resolve it.

Setting single rate in ath10k broken by "reject/clear user rate mask if not usable"

At one point, you could set a single rate using 'iw' and ath10k would convert that to a special firmware API that fixed all data traffic to a particular rate set. (Management frames and broadcast will not be affected by setting the rates when using ath10k). But, with the commit below, a command

Re: ath10k hang on rmmod after fw crash in 4.13.3+ hacks

On 10/10/2017 12:07 PM, Ben Greear wrote: I loaded a crashing firmware (it crashes early since it ran OOM), and then tried to rmmod it. rmmod hangs, with this stack: Looks like this is a hang related to napi, and I had a patch from an older kernel that is probably not needed anymore...maybe

Re: What should setting rate on 'AP' interface mean?

On 10/10/2017 12:09 PM, Adrian Chadd wrote: Hi, IIRC, I think it's the drivers job to determine per-peer fixed rate. From poking at the 10.1 firmware source, seems that setting fixed RC on the vdev should over-ride all of the stations, but it did not appear to be working as expected... While

Re: What should setting rate on 'AP' interface mean?

Hi, IIRC, I think it's the drivers job to determine per-peer fixed rate. -adrian On 10 October 2017 at 11:34, Ben Greear wrote: > I was trying to use 'iw' to set rates on an AP interface, hoping it would > set tx-rates on all of the stations (peers) to the same

What should setting rate on 'AP' interface mean?

I was trying to use 'iw' to set rates on an AP interface, hoping it would set tx-rates on all of the stations (peers) to the same thing. It appears that the ath10k driver will set ratesets on all stations if we specify more than one rate, but if we specify a single rate, it does not iterate

[PATCH V5 5/5] ath10k: Fix TDLS peer TX data failure issue on encryped AP

From: Yingying Tang For WPA encryption, QCA6174 firmware(version: WLAN.RM.4.4) will unblock data when M4 was sent successfully. For other encryption which didn't need 4-way handshake firmware will unblock the data when peer authorized. Since TDLS is 3-way handshake host

[PATCH V5 2/5] ath10k: Enable TDLS peer buffer STA feature

From: Yingying Tang Enable TDLS peer buffer STA feature. QCA6174 firmware(version: WLAN.RM.4.4) support TDLS peer buffer STA, it reports this capability through wmi service map in wmi service ready event. Set related parameter in TDLS WMI command to enable this feature.

[PATCH V5 1/5] mac80211: Enable TDLS peer buffer STA feature

From: Yingying Tang Enable TDLS peer buffer STA feature. Set extended capability bit to enable buffer STA when driver support it. Signed-off-by: Yingying Tang --- include/net/cfg80211.h |3 +++ net/mac80211/tdls.c|5 - 2

[PATCH V5 3/5] ath10k: Enable TDLS peer inactivity detection

From: Yingying Tang Enable TDLS peer inactivity detetion feature. QCA6174 firmware(version: WLAN.RM.4.4) support TDLS link inactivity detecting. Set related parameters in TDLS WMI command to enable this feature. Signed-off-by: Yingying Tang

[PATCH V5 4/5] ath10k: Avoid to set WEP key for TDLS peer

From: Yingying Tang TDLS peer do not need WEP key. Setting WEP key will lead to TDLS setup failure. Add fix to avoid setting WEP key for TDLS peer. Signed-off-by: Yingying Tang --- drivers/net/wireless/ath/ath10k/mac.c |2 +- 1 file

[PATCH V5 0/5] Add TDLS feature for ath10k

From: Yingying Tang This patchset is for Rome PCIE chip, it will not affect other hardware Yingying Tang (5): mac80211: Enable TDLS peer buffer STA feature ath10k: Enable TDLS peer buffer STA feature ath10k: Enable TDLS peer inactivity detection ath10k: Avoid

[PATCH 1/2] ath10k: update tdls teardown state to target

From: Manikanta Pubbisetty It is required to update the teardown state of the peer when a tdls link with that peer is terminated. This information is useful for the target to perform some cleanups wrt the tdls peer. Without proper cleanup, target assumes that the peer

[PATCH 2/2] ath10k: handle tdls peer events

From: Manikanta Pubbisetty Handle tdls peer events from the target. TDLS events for the peer could be discover, teardown, etc. As of now, adding the logic to handle tdls teardown events alone. Teardown due to peer traffic indication(PTR) timeout is one such teardown

[PATCH 0/2] ath10k: more on tdls support for 10.4 firmwares

From: Manikanta Pubbisetty This patchset includes a bug fix and an enhancement of tdls functionality for 10.4 firmwares. First patch in this series is a bug fix, second one is an enhancement. Manikanta Pubbisetty (2): ath10k: update tdls teardown state to target