On Donnerstag, 11. Mai 2017 11:39:46 CEST Arend Van Spriel wrote:
[...]
> So you leave VHT as is. Did you check with 11ac device? I am wondering
> if it needs the same change.
VHT MCS rates are reported by drivers with NSS + MCS rates 0-9 [1] as
separated values. So I would say that the code is correct to report them as
separate values. But no, I haven't tested with an 802.11ac capable device
which I can fully trust because I didn't have one in arms reach (and I would
have to compile a new firmware for it). But the output for a second ath10k
based device looks ok'ish:
Station ac:86:74:61:6b:30 (on wlan1)
inactive time: 700 ms
rx bytes: 10741
rx packets: 95
tx bytes: 9886
tx packets: 86
tx retries: 0
tx failed: 0
rx drop misc: 1
signal: -22 dBm
signal avg: -21 dBm
tx bitrate: 780.0 MBit/s VHT-MCS 8 80MHz short GI VHT-NSS 2
rx bitrate: 780.0 MBit/s VHT-MCS 8 80MHz short GI VHT-NSS 2
rx duration: 8172 us
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
DTIM period: 2
beacon interval:100
short slot time:yes
connected time: 106 seconds
Kind regards,
Sven
[1] http://mcsindex.com/
Attachment:
signature.asc
Description: This is a digitally signed message part.
