* wcn7850 issues
[not found] <LO0P123MB4057D6C2F6FEFF335B30EE7CD6BF2@LO0P123MB4057.GBRP123.PROD.OUTLOOK.COM>
@ 2024-08-06 8:06 ` david Atkins
2024-08-13 13:20 ` david Atkins
` (4 more replies)
0 siblings, 5 replies; 28+ messages in thread
From: david Atkins @ 2024-08-06 8:06 UTC (permalink / raw)
To: ath12k@lists.infradead.org
Hi,
I have updated the kernel we use for testing today to main from https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/, the base install is the ubuntu 24.04 desktop release
Kernel reports as
openwrt@wifi7-amd:~$ uname -a
Linux wifi7-amd 6.11.0-rc2-wt-ath+ #2 SMP PREEMPT_DYNAMIC Mon Aug 5 12:02:22 BST 2024 x86_64 x86_64 x86_64 GNU/Linux
Ath12k from Dmesg
mailto:openwrt@wifi7-amd:~/datkins/kalo/ath/.git$ sudo dmesg | grep ath12k
[ 3.823988] ath12k_pci 0000:01:00.0: BAR 0 [mem 0xfc600000-0xfc7fffff 64bit]: assigned
[ 3.824006] ath12k_pci 0000:01:00.0: enabling device (0000 -> 0002)
[ 3.824305] ath12k_pci 0000:01:00.0: MSI vectors: 16
[ 3.824310] ath12k_pci 0000:01:00.0: Hardware name: wcn7850 hw2.0
[ 4.372789] ath12k_pci 0000:01:00.0: chip_id 0x2 chip_family 0x4 board_id 0x10e soc_id 0x40170200
[ 4.372796] ath12k_pci 0000:01:00.0: fw_version 0x100301e1 fw_build_timestamp 2023-12-06 04:05 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3
[ 4.580233] ath12k_pci 0000:01:00.0 wlp1s0: renamed from wlan0
Ip a shows
3: wlp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:03:7f:58:34:42 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.144/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp1s0
valid_lft 82448sec preferred_lft 82448sec
inet6 fd78:4c15:7f9d::2cf/128 scope global dynamic noprefixroute
valid_lft 82450sec preferred_lft 39250sec
inet6 fd78:4c15:7f9d:0:3f2d:65f7:eb00:3928/64 scope global temporary dynamic
valid_lft 600850sec preferred_lft 82358sec
inet6 fd78:4c15:7f9d:0:a184:9d87:7861:846b/64 scope global mngtmpaddr noprefixroute
valid_lft forever preferred_lft forever
inet6 fe80::f662:5464:1669:4fab/64 scope link noprefixroute
valid_lft forever preferred_lft forever
I have set region to GB
sudo iw reg set GB
so we get
mailto:openwrt@wifi7-amd:~/datkins/kalo/ath/.git$ sudo iw reg get
global
country GB: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5730 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5850 @ 80), (N/A, 23), (N/A), NO-OUTDOOR
(5925 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
(57000 - 71000 @ 2160), (N/A, 40), (N/A)
phy#0 (self-managed)
country na: DFS-UNSET
(2402 - 2472 @ 40), (N/A, 20), (N/A)
(2457 - 2482 @ 20), (N/A, 20), (N/A), PASSIVE-SCAN
(5170 - 5330 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(5490 - 5730 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(5735 - 5895 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(5945 - 7125 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(5945 - 7125 @ 320), (N/A, 30), (N/A), AUTO-BW, PASSIVE-SCAN
Station dump gives me
mailto:openwrt@wifi7-amd:~/datkins/kalo/ath/.git$ sudo iw dev wlp1s0 station dump
Station ac:91:9b:b7:05:b0 (on wlp1s0)
inactive time: 1126 ms
rx bytes: 4832450328
rx packets: 3281108
tx bytes: 4592467521
tx packets: 3152967
tx retries: 38
tx failed: 0
beacon loss: 0
beacon rx: 3267
rx drop misc: 1
signal: 0 dBm
beacon signal avg: -24 dBm
tx duration: 0 us
rx bitrate: 3602.9 MBit/s 160MHz HE-MCS 11 HE-NSS 3 HE-GI 0 HE-DCM 0
rx duration: 0 us
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: yes
TDLS peer: no
DTIM period: 2
beacon interval:100
short slot time:yes
connected time: 4038 seconds
associated at [boottime]: 13.805s
associated at: 1722856637791 ms
current time: 1722860675019 ms
and iw dev wlp1s0 link gives me
Connected to ac:91:9b:b7:05:b0 (on wlp1s0)
SSID: EE-CN589H
freq: 6295.0
RX: 537531156 bytes (3281227 packets)
TX: 297500287 bytes (3152968 packets)
signal: 0 dBm
rx bitrate: 3602.9 MBit/s 160MHz HE-MCS 11 HE-NSS 3 HE-GI 0 HE-DCM 0
bss flags: short-slot-time
dtim period: 2
beacon int: 100
Concerned we have a report of "HE-NSS 3", wifi 7 should be eht and we have a wcn7850 which has only 2 antenna ports.
My understanding is that 160MHz HE-MCS 11 @ 160Mhz will give us 1200 Mbit/s so the report of 3602 suggests its assuming it has 3 spatial streams which would be incorrect
The signal level looks wrong
signal: 0 dBm
beacon signal avg: -24 dBm
we would expect that to agree with the beacon level, we see the beacon change but the signal is always 0, I note from recent messages on the thread that this has been fixed, what branch should I use to check this?
I have also seen this in dmesg during association with the AP,
[ 13.049675] wlp1s0: required MCSes not supported, disabling EHT
[ 13.304272] wlp1s0: authenticate with ac:91:9b:b7:05:b0 (local address=00:03:7f:58:34:42)
[ 13.304281] wlp1s0: send auth to ac:91:9b:b7:05:b0 (try 1/3)
[ 13.312345] wlp1s0: authenticate with ac:91:9b:b7:05:b0 (local address=00:03:7f:58:34:42)
[ 13.312352] wlp1s0: send auth to ac:91:9b:b7:05:b0 (try 1/3)
[ 13.314787] wlp1s0: authenticated
[ 13.315249] wlp1s0: associate with ac:91:9b:b7:05:b0 (try 1/3)
[ 13.321883] wlp1s0: RX AssocResp from ac:91:9b:b7:05:b0 (capab=0x1111 status=0 aid=6)
[ 13.334818] wlp1s0: associated
Iw scan shows this for the AP in the 6Ghz band
BSS ac:91:9b:b7:05:b0(on wlp1s0) -- associated
TSF: 56186843682 usec (0d, 15:36:26)
freq: 6135.0
beacon interval: 100 TUs
capability: ESS Privacy SpectrumMgmt RadioMeasure (0x1111)
signal: -28.00 dBm
last seen: 128 ms ago
Information elements from Probe Response frame:
SSID: EE-CN589H
Supported rates: 6.0* 9.0 12.0* 18.0 24.0* 36.0 48.0 54.0
Country: GB Environment: bogus
Extension ID: 201 Regulatory Class: 137 Coverage class: 0 (up to 0m)
Power constraint: 0 dB
Extended supported rates: 61.5*
RSN: * Version: 1
* Group cipher: CCMP
* Pairwise ciphers: CCMP
* Authentication suites: SAE
* Capabilities: 16-PTKSA-RC 1-GTKSA-RC MFP-required MFP-capable (0x00cc)
BSS Load:
* station count: 1
* channel utilisation: 3/255
* available admission capacity: 0 [*32us]
RM enabled capabilities:
Capabilities: 0x72 0x00 0x00 0x00 0x00
Neighbor Report
Beacon Passive Measurement
Beacon Active Measurement
Beacon Table Measurement
Nonoperating Channel Max Measurement Duration: 0
Measurement Pilot Capability: 0
Supported operating classes:
* current operating class: 137
Extended capabilities:
* Extended Channel Switching
* BSS Transition
* Multiple BSSID
* SSID List
* Interworking
* WNM-Notification
* Operating Mode Notification
* TWT Responder Support
* 80
* 83
802.11u Interworking:
Network Options: 0x0
Network Type: 0 (Private)
802.11u Advertisement:
Query Response Info: 0x7f
Query Response Length Limit: 127
ANQP
Transmit Power Envelope:
Transmit Power Envelope:
HE capabilities:
HE MAC Capabilities (0x000d9a181840):
+HTC HE Supported
TWT Responder
Dynamic BA Fragementation Level: 1
BSR
Broadcast TWT
OM Control
Maximum A-MPDU Length Exponent: 3
RX Control Frame to MultiBSS
A-MSDU in A-MPDU
UL 2x996-Tone RU
OM Control UL MU Data Disable RX
HE PHY Capabilities: (0x0c634088fedb831c110c00):
HE40/HE80/5GHz
HE160/5GHz
Punctured Preamble RX: 3
LDPC Coding in Payload
HE SU PPDU with 1x HE-LTF and 0.8us GI
Full Bandwidth UL MU-MIMO
DCM Max Constellation Rx: 1
SU Beamformer
MU Beamformer
Beamformee STS <= 80Mhz: 7
Beamformee STS > 80Mhz: 7
Sounding Dimensions <= 80Mhz: 3
Sounding Dimensions > 80Mhz: 3
Ng = 16 SU Feedback
Ng = 16 MU Feedback
Codebook Size SU Feedback
Codebook Size MU Feedback
PPE Threshold Present
HE SU PPDU & HE PPDU 4x HE-LTF 0.8us GI
Max NC: 3
HE ER SU PPDU 4x HE-LTF 0.8us GI
HE ER SU PPDU 1x HE-LTF 0.8us GI
TX 1024-QAM
RX 1024-QAM
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: MCS 0-11
4 streams: MCS 0-11
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: MCS 0-11
4 streams: MCS 0-11
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE RX MCS and NSS set 160 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: MCS 0-11
4 streams: MCS 0-11
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set 160 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: MCS 0-11
4 streams: MCS 0-11
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
PPE Threshold 0x7b 0x1c 0xc7 0x71 0x1c 0xc7 0x71 0x1c 0xc7 0x71 0x1c 0xc7 0x71
WMM: * Parameter version 1
* u-APSD
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
No support for EHT and therefore no MSC 12 or 13 which fits with the dmesg warning about it not being supported, is this a card firmware issue rather than the driver?
I carried out some iperf tests with a server with 2.5gb ethernet to the AP,
If I run iperf against the access point with one antenna at H and one at V, approx. 1000mm from the access point I see similar performance on up and down stream sessions, with single and multiple parallel streams.
The iperf server is connected by 2.5gb ethernet to the access point and that has been tested to an aggregate of 3.6bit on wifi 7 using other cards.
openwrt@wifi7-amd:~$ iperf3 -c 192.168.1.168 -p 5002
Connecting to host 192.168.1.168, port 5002
[ 5] local 192.168.1.144 port 46802 connected to 192.168.1.168 port 5002
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 142 MBytes 1.19 Gbits/sec 0 2.63 MBytes
[ 5] 1.00-2.00 sec 136 MBytes 1.14 Gbits/sec 0 2.63 MBytes
[ 5] 2.00-3.00 sec 134 MBytes 1.13 Gbits/sec 0 2.63 MBytes
[ 5] 3.00-4.00 sec 132 MBytes 1.10 Gbits/sec 0 2.63 MBytes
[ 5] 4.00-5.00 sec 136 MBytes 1.15 Gbits/sec 0 2.63 MBytes
[ 5] 5.00-6.00 sec 131 MBytes 1.10 Gbits/sec 0 2.63 MBytes
[ 5] 6.00-7.00 sec 130 MBytes 1.09 Gbits/sec 0 2.63 MBytes
[ 5] 7.00-8.00 sec 132 MBytes 1.10 Gbits/sec 0 2.63 MBytes
[ 5] 8.00-9.00 sec 134 MBytes 1.13 Gbits/sec 0 2.63 MBytes
[ 5] 9.00-10.00 sec 132 MBytes 1.11 Gbits/sec 0 2.63 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.31 GBytes 1.12 Gbits/sec 0 sender
[ 5] 0.00-10.01 sec 1.31 GBytes 1.12 Gbits/sec receiver
Happy to run tests as needed to check but need input on what code to use etc.
Should I try another branch, I note that results in this list do show signal levels so assume there may be a more advanced version.
Can I access a more recent firmware build?
Thanks in advance,
David Atkins
^ permalink raw reply [flat|nested] 28+ messages in thread
* RE: wcn7850 issues
2024-08-06 8:06 ` wcn7850 issues david Atkins
@ 2024-08-13 13:20 ` david Atkins
2024-08-14 7:28 ` Kang Yang
` (3 subsequent siblings)
4 siblings, 0 replies; 28+ messages in thread
From: david Atkins @ 2024-08-13 13:20 UTC (permalink / raw)
To: david Atkins, ath12k@lists.infradead.org
Any thoughts on this, keen to at least replicate results that have been posted here
David
> -----Original Message-----
> From: ath12k <ath12k-bounces@lists.infradead.org> On Behalf Of david
> Atkins
> Sent: Tuesday, August 6, 2024 9:06 AM
> To: ath12k@lists.infradead.org
> Subject: wcn7850 issues
>
>
> Hi,
>
> I have updated the kernel we use for testing today to main from
> https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/, the base install
> is the ubuntu 24.04 desktop release
>
> Kernel reports as
>
>
> openwrt@wifi7-amd:~$ uname -a
> Linux wifi7-amd 6.11.0-rc2-wt-ath+ #2 SMP PREEMPT_DYNAMIC Mon Aug 5
> 12:02:22 BST 2024 x86_64 x86_64 x86_64 GNU/Linux
>
> Ath12k from Dmesg
>
> mailto:openwrt@wifi7-amd:~/datkins/kalo/ath/.git$ sudo dmesg | grep
> ath12k [ 3.823988] ath12k_pci 0000:01:00.0: BAR 0 [mem 0xfc600000-
> 0xfc7fffff 64bit]: assigned [ 3.824006] ath12k_pci 0000:01:00.0: enabling
> device (0000 -> 0002) [ 3.824305] ath12k_pci 0000:01:00.0: MSI vectors: 16
> [ 3.824310] ath12k_pci 0000:01:00.0: Hardware name: wcn7850 hw2.0
> [ 4.372789] ath12k_pci 0000:01:00.0: chip_id 0x2 chip_family 0x4 board_id
> 0x10e soc_id 0x40170200 [ 4.372796] ath12k_pci 0000:01:00.0: fw_version
> 0x100301e1 fw_build_timestamp 2023-12-06 04:05 fw_build_id
> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-
> QCAHMTSWPL_V1.0_V2.0_SILICONZ-3
> [ 4.580233] ath12k_pci 0000:01:00.0 wlp1s0: renamed from wlan0
>
> Ip a shows
>
> 3: wlp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
> state UP group default qlen 1000
> link/ether 00:03:7f:58:34:42 brd ff:ff:ff:ff:ff:ff
> inet 192.168.1.144/24 brd 192.168.1.255 scope global dynamic
> noprefixroute wlp1s0
> valid_lft 82448sec preferred_lft 82448sec
> inet6 fd78:4c15:7f9d::2cf/128 scope global dynamic noprefixroute
> valid_lft 82450sec preferred_lft 39250sec
> inet6 fd78:4c15:7f9d:0:3f2d:65f7:eb00:3928/64 scope global temporary
> dynamic
> valid_lft 600850sec preferred_lft 82358sec
> inet6 fd78:4c15:7f9d:0:a184:9d87:7861:846b/64 scope global mngtmpaddr
> noprefixroute
> valid_lft forever preferred_lft forever
> inet6 fe80::f662:5464:1669:4fab/64 scope link noprefixroute
> valid_lft forever preferred_lft forever
>
> I have set region to GB
>
> sudo iw reg set GB
>
> so we get
>
> mailto:openwrt@wifi7-amd:~/datkins/kalo/ath/.git$ sudo iw reg get global
> country GB: DFS-ETSI
> (2400 - 2483 @ 40), (N/A, 20), (N/A)
> (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
> (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
> (5470 - 5730 @ 160), (N/A, 26), (0 ms), DFS
> (5725 - 5850 @ 80), (N/A, 23), (N/A), NO-OUTDOOR
> (5925 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
> (57000 - 71000 @ 2160), (N/A, 40), (N/A)
>
> phy#0 (self-managed)
> country na: DFS-UNSET
> (2402 - 2472 @ 40), (N/A, 20), (N/A)
> (2457 - 2482 @ 20), (N/A, 20), (N/A), PASSIVE-SCAN
> (5170 - 5330 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
> (5490 - 5730 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
> (5735 - 5895 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
> (5945 - 7125 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
> (5945 - 7125 @ 320), (N/A, 30), (N/A), AUTO-BW, PASSIVE-SCAN
>
> Station dump gives me
>
> mailto:openwrt@wifi7-amd:~/datkins/kalo/ath/.git$ sudo iw dev wlp1s0
> station dump Station ac:91:9b:b7:05:b0 (on wlp1s0)
> inactive time: 1126 ms
> rx bytes: 4832450328
> rx packets: 3281108
> tx bytes: 4592467521
> tx packets: 3152967
> tx retries: 38
> tx failed: 0
> beacon loss: 0
> beacon rx: 3267
> rx drop misc: 1
> signal: 0 dBm
> beacon signal avg: -24 dBm
> tx duration: 0 us
> rx bitrate: 3602.9 MBit/s 160MHz HE-MCS 11 HE-NSS 3 HE-GI 0 HE-
> DCM 0
> rx duration: 0 us
> authorized: yes
> authenticated: yes
> associated: yes
> preamble: long
> WMM/WME: yes
> MFP: yes
> TDLS peer: no
> DTIM period: 2
> beacon interval:100
> short slot time:yes
> connected time: 4038 seconds
> associated at [boottime]: 13.805s
> associated at: 1722856637791 ms
> current time: 1722860675019 ms
>
>
> and iw dev wlp1s0 link gives me
>
> Connected to ac:91:9b:b7:05:b0 (on wlp1s0)
> SSID: EE-CN589H
> freq: 6295.0
> RX: 537531156 bytes (3281227 packets)
> TX: 297500287 bytes (3152968 packets)
> signal: 0 dBm
> rx bitrate: 3602.9 MBit/s 160MHz HE-MCS 11 HE-NSS 3 HE-GI 0 HE-DCM 0
> bss flags: short-slot-time
> dtim period: 2
> beacon int: 100
>
> Concerned we have a report of "HE-NSS 3", wifi 7 should be eht and we have
> a wcn7850 which has only 2 antenna ports.
>
> My understanding is that 160MHz HE-MCS 11 @ 160Mhz will give us 1200
> Mbit/s so the report of 3602 suggests its assuming it has 3 spatial streams
> which would be incorrect
>
> The signal level looks wrong
>
> signal: 0 dBm
> beacon signal avg: -24 dBm
>
> we would expect that to agree with the beacon level, we see the beacon
> change but the signal is always 0, I note from recent messages on the thread
> that this has been fixed, what branch should I use to check this?
>
> I have also seen this in dmesg during association with the AP,
>
> [ 13.049675] wlp1s0: required MCSes not supported, disabling EHT
> [ 13.304272] wlp1s0: authenticate with ac:91:9b:b7:05:b0 (local
> address=00:03:7f:58:34:42) [ 13.304281] wlp1s0: send auth to
> ac:91:9b:b7:05:b0 (try 1/3) [ 13.312345] wlp1s0: authenticate with
> ac:91:9b:b7:05:b0 (local address=00:03:7f:58:34:42) [ 13.312352] wlp1s0:
> send auth to ac:91:9b:b7:05:b0 (try 1/3) [ 13.314787] wlp1s0: authenticated
> [ 13.315249] wlp1s0: associate with ac:91:9b:b7:05:b0 (try 1/3)
> [ 13.321883] wlp1s0: RX AssocResp from ac:91:9b:b7:05:b0 (capab=0x1111
> status=0 aid=6) [ 13.334818] wlp1s0: associated
>
> Iw scan shows this for the AP in the 6Ghz band
>
> BSS ac:91:9b:b7:05:b0(on wlp1s0) -- associated
> TSF: 56186843682 usec (0d, 15:36:26)
> freq: 6135.0
> beacon interval: 100 TUs
> capability: ESS Privacy SpectrumMgmt RadioMeasure (0x1111)
> signal: -28.00 dBm
> last seen: 128 ms ago
> Information elements from Probe Response frame:
> SSID: EE-CN589H
> Supported rates: 6.0* 9.0 12.0* 18.0 24.0* 36.0 48.0 54.0
> Country: GB Environment: bogus
> Extension ID: 201 Regulatory Class: 137 Coverage class: 0 (up
> to 0m)
> Power constraint: 0 dB
> Extended supported rates: 61.5*
> RSN: * Version: 1
> * Group cipher: CCMP
> * Pairwise ciphers: CCMP
> * Authentication suites: SAE
> * Capabilities: 16-PTKSA-RC 1-GTKSA-RC MFP-required MFP-
> capable (0x00cc)
> BSS Load:
> * station count: 1
> * channel utilisation: 3/255
> * available admission capacity: 0 [*32us]
> RM enabled capabilities:
> Capabilities: 0x72 0x00 0x00 0x00 0x00
> Neighbor Report
> Beacon Passive Measurement
> Beacon Active Measurement
> Beacon Table Measurement
> Nonoperating Channel Max Measurement Duration: 0
> Measurement Pilot Capability: 0
> Supported operating classes:
> * current operating class: 137
> Extended capabilities:
> * Extended Channel Switching
> * BSS Transition
> * Multiple BSSID
> * SSID List
> * Interworking
> * WNM-Notification
> * Operating Mode Notification
> * TWT Responder Support
> * 80
> * 83
> 802.11u Interworking:
> Network Options: 0x0
> Network Type: 0 (Private)
> 802.11u Advertisement:
> Query Response Info: 0x7f
> Query Response Length Limit: 127
> ANQP
> Transmit Power Envelope:
> Transmit Power Envelope:
> HE capabilities:
> HE MAC Capabilities (0x000d9a181840):
> +HTC HE Supported
> TWT Responder
> Dynamic BA Fragementation Level: 1
> BSR
> Broadcast TWT
> OM Control
> Maximum A-MPDU Length Exponent: 3
> RX Control Frame to MultiBSS
> A-MSDU in A-MPDU
> UL 2x996-Tone RU
> OM Control UL MU Data Disable RX
> HE PHY Capabilities: (0x0c634088fedb831c110c00):
> HE40/HE80/5GHz
> HE160/5GHz
> Punctured Preamble RX: 3
> LDPC Coding in Payload
> HE SU PPDU with 1x HE-LTF and 0.8us GI
> Full Bandwidth UL MU-MIMO
> DCM Max Constellation Rx: 1
> SU Beamformer
> MU Beamformer
> Beamformee STS <= 80Mhz: 7
> Beamformee STS > 80Mhz: 7
> Sounding Dimensions <= 80Mhz: 3
> Sounding Dimensions > 80Mhz: 3
> Ng = 16 SU Feedback
> Ng = 16 MU Feedback
> Codebook Size SU Feedback
> Codebook Size MU Feedback
> PPE Threshold Present
> HE SU PPDU & HE PPDU 4x HE-LTF 0.8us GI
> Max NC: 3
> HE ER SU PPDU 4x HE-LTF 0.8us GI
> HE ER SU PPDU 1x HE-LTF 0.8us GI
> TX 1024-QAM
> RX 1024-QAM
> HE RX MCS and NSS set <= 80 MHz
> 1 streams: MCS 0-11
> 2 streams: MCS 0-11
> 3 streams: MCS 0-11
> 4 streams: MCS 0-11
> 5 streams: not supported
> 6 streams: not supported
> 7 streams: not supported
> 8 streams: not supported
> HE TX MCS and NSS set <= 80 MHz
> 1 streams: MCS 0-11
> 2 streams: MCS 0-11
> 3 streams: MCS 0-11
> 4 streams: MCS 0-11
> 5 streams: not supported
> 6 streams: not supported
> 7 streams: not supported
> 8 streams: not supported
> HE RX MCS and NSS set 160 MHz
> 1 streams: MCS 0-11
> 2 streams: MCS 0-11
> 3 streams: MCS 0-11
> 4 streams: MCS 0-11
> 5 streams: not supported
> 6 streams: not supported
> 7 streams: not supported
> 8 streams: not supported
> HE TX MCS and NSS set 160 MHz
> 1 streams: MCS 0-11
> 2 streams: MCS 0-11
> 3 streams: MCS 0-11
> 4 streams: MCS 0-11
> 5 streams: not supported
> 6 streams: not supported
> 7 streams: not supported
> 8 streams: not supported
> PPE Threshold 0x7b 0x1c 0xc7 0x71 0x1c 0xc7 0x71 0x1c 0xc7
> 0x71 0x1c 0xc7 0x71
> WMM: * Parameter version 1
> * u-APSD
> * BE: CW 15-1023, AIFSN 3
> * BK: CW 15-1023, AIFSN 7
> * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
> * VO: CW 3-7, AIFSN 2, TXOP 1504 usec
>
> No support for EHT and therefore no MSC 12 or 13 which fits with the dmesg
> warning about it not being supported, is this a card firmware issue rather
> than the driver?
>
> I carried out some iperf tests with a server with 2.5gb ethernet to the AP,
>
>
> If I run iperf against the access point with one antenna at H and one at V,
> approx. 1000mm from the access point I see similar performance on up and
> down stream sessions, with single and multiple parallel streams.
>
> The iperf server is connected by 2.5gb ethernet to the access point and that
> has been tested to an aggregate of 3.6bit on wifi 7 using other cards.
>
> openwrt@wifi7-amd:~$ iperf3 -c 192.168.1.168 -p 5002 Connecting to host
> 192.168.1.168, port 5002 [ 5] local 192.168.1.144 port 46802 connected to
> 192.168.1.168 port 5002 [ ID] Interval Transfer Bitrate Retr Cwnd
> [ 5] 0.00-1.00 sec 142 MBytes 1.19 Gbits/sec 0 2.63 MBytes [ 5] 1.00-
> 2.00 sec 136 MBytes 1.14 Gbits/sec 0 2.63 MBytes [ 5] 2.00-
> 3.00 sec 134 MBytes 1.13 Gbits/sec 0 2.63 MBytes [ 5] 3.00-
> 4.00 sec 132 MBytes 1.10 Gbits/sec 0 2.63 MBytes [ 5] 4.00-
> 5.00 sec 136 MBytes 1.15 Gbits/sec 0 2.63 MBytes [ 5] 5.00-
> 6.00 sec 131 MBytes 1.10 Gbits/sec 0 2.63 MBytes [ 5] 6.00-
> 7.00 sec 130 MBytes 1.09 Gbits/sec 0 2.63 MBytes [ 5] 7.00-
> 8.00 sec 132 MBytes 1.10 Gbits/sec 0 2.63 MBytes [ 5] 8.00-
> 9.00 sec 134 MBytes 1.13 Gbits/sec 0 2.63 MBytes [ 5] 9.00-
> 10.00 sec 132 MBytes 1.11 Gbits/sec 0 2.63 MBytes
> - - - - - - - - - - - - - - - - - - - - - - - - - [ ID]
> Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 1.31
> GBytes 1.12 Gbits/sec 0 sender [ 5] 0.00-10.01 sec 1.31
> GBytes 1.12 Gbits/sec receiver
>
> Happy to run tests as needed to check but need input on what code to use
> etc.
>
> Should I try another branch, I note that results in this list do show signal levels
> so assume there may be a more advanced version.
>
> Can I access a more recent firmware build?
>
> Thanks in advance,
>
> David Atkins
>
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: wcn7850 issues
2024-08-06 8:06 ` wcn7850 issues david Atkins
2024-08-13 13:20 ` david Atkins
@ 2024-08-14 7:28 ` Kang Yang
2024-08-14 8:46 ` Lingbo Kong
` (2 subsequent siblings)
4 siblings, 0 replies; 28+ messages in thread
From: Kang Yang @ 2024-08-14 7:28 UTC (permalink / raw)
To: david Atkins, ath12k@lists.infradead.org
On 8/6/2024 4:06 PM, david Atkins wrote:
>
> Hi,
>
> I have updated the kernel we use for testing today to main from https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/, the base install is the ubuntu 24.04 desktop release
>
> Kernel reports as
>
>
……
>
> I have set region to GB
>
> sudo iw reg set GB
>
> so we get
>
> mailto:openwrt@wifi7-amd:~/datkins/kalo/ath/.git$ sudo iw reg get
> global
> country GB: DFS-ETSI
> (2400 - 2483 @ 40), (N/A, 20), (N/A)
> (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
> (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
> (5470 - 5730 @ 160), (N/A, 26), (0 ms), DFS
> (5725 - 5850 @ 80), (N/A, 23), (N/A), NO-OUTDOOR
> (5925 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
> (57000 - 71000 @ 2160), (N/A, 40), (N/A)
>
> phy#0 (self-managed)
> country na: DFS-UNSET
> (2402 - 2472 @ 40), (N/A, 20), (N/A)
> (2457 - 2482 @ 20), (N/A, 20), (N/A), PASSIVE-SCAN
> (5170 - 5330 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
> (5490 - 5730 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
> (5735 - 5895 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
> (5945 - 7125 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
> (5945 - 7125 @ 320), (N/A, 30), (N/A), AUTO-BW, PASSIVE-SCAN
Hi, david:
We have related patch-set, they are currently under review.
With our patch-set, country code could be set successfully.
dmesg(CN->GB):
root@yk-E5440:/home/yk/ath12k-upstream# iw reg get //CN
global
country CN: DFS-FCC
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5350 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW
(5725 - 5850 @ 80), (N/A, 33), (N/A)
(57240 - 59400 @ 2160), (N/A, 28), (N/A)
(59400 - 63720 @ 2160), (N/A, 44), (N/A)
(63720 - 65880 @ 2160), (N/A, 28), (N/A)
phy#2 (self-managed)
country CN: DFS-FCC
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5735 - 5835 @ 80), (N/A, 14), (N/A), AUTO-BW
root@yk-E5440:/home/yk/ath12k-upstream# iw reg set GB
root@yk-E5440:/home/yk/ath12k-upstream# iw reg get //change to GB now
global
country GB: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5730 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5850 @ 80), (N/A, 23), (N/A), NO-OUTDOOR
(5925 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
(57000 - 71000 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country GB: DFS-ETSI
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5490 - 5590 @ 80), (N/A, 30), (0 ms), DFS, AUTO-BW
(5590 - 5650 @ 40), (N/A, 30), (600000 ms), DFS, AUTO-BW
(5650 - 5730 @ 80), (N/A, 30), (0 ms), DFS, AUTO-BW
(5735 - 5875 @ 80), (N/A, 14), (N/A), AUTO-BW
(5855 - 5875 @ 20), (N/A, 14), (N/A), AUTO-BW
(5855 - 5875 @ 20), (N/A, 14), (N/A), AUTO-BW
(5855 - 5875 @ 20), (N/A, 14), (N/A), AUTO-BW
(5945 - 6425 @ 320), (N/A, 24), (N/A), NO-OUTDOOR, AUTO-BW
Other issues will be replied by someone else, Please be patient.
Thanks.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: wcn7850 issues
2024-08-06 8:06 ` wcn7850 issues david Atkins
2024-08-13 13:20 ` david Atkins
2024-08-14 7:28 ` Kang Yang
@ 2024-08-14 8:46 ` Lingbo Kong
2024-08-14 10:33 ` Baochen Qiang
2024-08-14 10:42 ` Baochen Qiang
4 siblings, 0 replies; 28+ messages in thread
From: Lingbo Kong @ 2024-08-14 8:46 UTC (permalink / raw)
To: david Atkins, ath12k@lists.infradead.org
On 2024/8/6 16:06, david Atkins wrote:
>
> Hi,
>
> I have updated the kernel we use for testing today to main from https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/, the base install is the ubuntu 24.04 desktop release
>
...
> and iw dev wlp1s0 link gives me
>
> Connected to ac:91:9b:b7:05:b0 (on wlp1s0)
> SSID: EE-CN589H
> freq: 6295.0
> RX: 537531156 bytes (3281227 packets)
> TX: 297500287 bytes (3152968 packets)
> signal: 0 dBm
> rx bitrate: 3602.9 MBit/s 160MHz HE-MCS 11 HE-NSS 3 HE-GI 0 HE-DCM 0
> bss flags: short-slot-time
> dtim period: 2
> beacon int: 100
>
> Concerned we have a report of "HE-NSS 3", wifi 7 should be eht and we have a wcn7850 which has only 2 antenna ports.
>
> My understanding is that 160MHz HE-MCS 11 @ 160Mhz will give us 1200 Mbit/s so the report of 3602 suggests its assuming it has 3 spatial streams which would be incorrect
>
hi david, thx a lot!
this nss value is indeed incorrect.i'm currently working on resolving
this issue:)
> The signal level looks wrong
>
> signal: 0 dBm
> beacon signal avg: -24 dBm
>
> we would expect that to agree with the beacon level, we see the beacon change but the signal is always 0, I note from recent messages on the thread that this has been fixed, what branch should I use to check this?
>
the patches related to signal are currently in the public review and
have not been merged into any branch yet.
the link to this patch-set is
https://patchwork.kernel.org/project/linux-wireless/cover/20240801112853.85508-1-quic_lingbok@quicinc.com/
/lingbo kong
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: wcn7850 issues
2024-08-06 8:06 ` wcn7850 issues david Atkins
` (2 preceding siblings ...)
2024-08-14 8:46 ` Lingbo Kong
@ 2024-08-14 10:33 ` Baochen Qiang
2024-08-14 16:58 ` david Atkins
2024-08-14 10:42 ` Baochen Qiang
4 siblings, 1 reply; 28+ messages in thread
From: Baochen Qiang @ 2024-08-14 10:33 UTC (permalink / raw)
To: ath12k
On 8/6/2024 4:06 PM, david Atkins wrote:
> I have also seen this in dmesg during association with the AP,
>
> [ 13.049675] wlp1s0: required MCSes not supported, disabling EHT
this is interesting ... this means EHT MCS verification in ieee80211_verify_sta_eht_mcs_support() fails.
if AP IEs contain EHT operation (I guess so) then this means AP requires NSS larger than 2 in its 'Basic EHT-MCS And NSS Set' field, because WCN7850 supports 2 RX/TX streams for all MCSes (0-7, 8-9, 10-11 and 12-13). so can you check/confirm this? you may add some logs in that function or just check air sniffer if possible.
> [ 13.304272] wlp1s0: authenticate with ac:91:9b:b7:05:b0 (local address=00:03:7f:58:34:42)
> [ 13.304281] wlp1s0: send auth to ac:91:9b:b7:05:b0 (try 1/3)
> [ 13.312345] wlp1s0: authenticate with ac:91:9b:b7:05:b0 (local address=00:03:7f:58:34:42)
> [ 13.312352] wlp1s0: send auth to ac:91:9b:b7:05:b0 (try 1/3)
> [ 13.314787] wlp1s0: authenticated
> [ 13.315249] wlp1s0: associate with ac:91:9b:b7:05:b0 (try 1/3)
> [ 13.321883] wlp1s0: RX AssocResp from ac:91:9b:b7:05:b0 (capab=0x1111 status=0 aid=6)
> [ 13.334818] wlp1s0: associated
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: wcn7850 issues
2024-08-06 8:06 ` wcn7850 issues david Atkins
` (3 preceding siblings ...)
2024-08-14 10:33 ` Baochen Qiang
@ 2024-08-14 10:42 ` Baochen Qiang
2024-08-14 17:00 ` david Atkins
2024-08-14 20:38 ` david Atkins
4 siblings, 2 replies; 28+ messages in thread
From: Baochen Qiang @ 2024-08-14 10:42 UTC (permalink / raw)
To: ath12k
On 8/6/2024 4:06 PM, david Atkins wrote:
> No support for EHT and therefore no MSC 12 or 13 which fits with the
> dmesg warning about it not being supported,
did not noted this ... So if AP does not support EHT, above warnings makes sense, like you said.
is this a card firmware
> issue rather than the driver?
did not follow you here, why is it an issue?
^ permalink raw reply [flat|nested] 28+ messages in thread
* RE: wcn7850 issues
2024-08-14 10:33 ` Baochen Qiang
@ 2024-08-14 16:58 ` david Atkins
0 siblings, 0 replies; 28+ messages in thread
From: david Atkins @ 2024-08-14 16:58 UTC (permalink / raw)
To: Baochen Qiang, ath12k@lists.infradead.org
I understand that EHT is working with test gear and Google Pixel 8.
I'll try and a sniff of the traffic.
David
> -----Original Message-----
> From: ath12k <ath12k-bounces@lists.infradead.org> On Behalf Of Baochen
> Qiang
> Sent: Wednesday, August 14, 2024 11:33 AM
> To: ath12k@lists.infradead.org
> Subject: Re: wcn7850 issues
>
>
>
> On 8/6/2024 4:06 PM, david Atkins wrote:
> > I have also seen this in dmesg during association with the AP,
> >
> > [ 13.049675] wlp1s0: required MCSes not supported, disabling EHT
> this is interesting ... this means EHT MCS verification in
> ieee80211_verify_sta_eht_mcs_support() fails.
>
> if AP IEs contain EHT operation (I guess so) then this means AP requires NSS
> larger than 2 in its 'Basic EHT-MCS And NSS Set' field, because WCN7850
> supports 2 RX/TX streams for all MCSes (0-7, 8-9, 10-11 and 12-13). so can
> you check/confirm this? you may add some logs in that function or just check
> air sniffer if possible.
>
> > [ 13.304272] wlp1s0: authenticate with ac:91:9b:b7:05:b0 (local
> > address=00:03:7f:58:34:42) [ 13.304281] wlp1s0: send auth to
> > ac:91:9b:b7:05:b0 (try 1/3) [ 13.312345] wlp1s0: authenticate with
> > ac:91:9b:b7:05:b0 (local address=00:03:7f:58:34:42) [ 13.312352]
> > wlp1s0: send auth to ac:91:9b:b7:05:b0 (try 1/3) [ 13.314787]
> > wlp1s0: authenticated [ 13.315249] wlp1s0: associate with
> > ac:91:9b:b7:05:b0 (try 1/3) [ 13.321883] wlp1s0: RX AssocResp from
> > ac:91:9b:b7:05:b0 (capab=0x1111 status=0 aid=6) [ 13.334818] wlp1s0:
> > associated
^ permalink raw reply [flat|nested] 28+ messages in thread
* RE: wcn7850 issues
2024-08-14 10:42 ` Baochen Qiang
@ 2024-08-14 17:00 ` david Atkins
2024-08-14 20:38 ` david Atkins
1 sibling, 0 replies; 28+ messages in thread
From: david Atkins @ 2024-08-14 17:00 UTC (permalink / raw)
To: Baochen Qiang, ath12k@lists.infradead.org
AP supports EHT, has been confirmed I'm told with Hamilton NIC by Qualcomm with the proprietary driver.
David
> -----Original Message-----
> From: ath12k <ath12k-bounces@lists.infradead.org> On Behalf Of Baochen
> Qiang
> Sent: Wednesday, August 14, 2024 11:42 AM
> To: ath12k@lists.infradead.org
> Subject: Re: wcn7850 issues
>
>
>
> On 8/6/2024 4:06 PM, david Atkins wrote:
> > No support for EHT and therefore no MSC 12 or 13 which fits with the
> > dmesg warning about it not being supported,
> did not noted this ... So if AP does not support EHT, above warnings makes
> sense, like you said.
>
> is this a card firmware
> > issue rather than the driver?
> did not follow you here, why is it an issue?
>
^ permalink raw reply [flat|nested] 28+ messages in thread
* RE: wcn7850 issues
2024-08-14 10:42 ` Baochen Qiang
2024-08-14 17:00 ` david Atkins
@ 2024-08-14 20:38 ` david Atkins
2024-08-15 2:15 ` Baochen Qiang
1 sibling, 1 reply; 28+ messages in thread
From: david Atkins @ 2024-08-14 20:38 UTC (permalink / raw)
To: Baochen Qiang, ath12k@lists.infradead.org
>
> On 8/6/2024 4:06 PM, david Atkins wrote:
> > No support for EHT and therefore no MSC 12 or 13 which fits with the
> > dmesg warning about it not being supported,
> did not noted this ... So if AP does not support EHT, above warnings makes
> sense, like you said.
>
Anseres inline, AP supports EHT
> is this a card firmware
> > issue rather than the driver?
> did not follow you here, why is it an issue?
>
Is the firmware that’s uploaded to the card not supporting EHT?
David
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: wcn7850 issues
2024-08-14 20:38 ` david Atkins
@ 2024-08-15 2:15 ` Baochen Qiang
2024-08-16 12:23 ` david Atkins
0 siblings, 1 reply; 28+ messages in thread
From: Baochen Qiang @ 2024-08-15 2:15 UTC (permalink / raw)
To: david Atkins, ath12k@lists.infradead.org
On 8/15/2024 4:38 AM, david Atkins wrote:
>>
>> On 8/6/2024 4:06 PM, david Atkins wrote:
>>> No support for EHT and therefore no MSC 12 or 13 which fits with the
>>> dmesg warning about it not being supported,
>> did not noted this ... So if AP does not support EHT, above warnings makes
>> sense, like you said.
>>
>
> Anseres inline, AP supports EHT
>
>> is this a card firmware
>>> issue rather than the driver?
>> did not follow you here, why is it an issue?
>>
>
> Is the firmware that’s uploaded to the card not supporting EHT?
>
FW does support EHT.
You are checking scan results, so it is AP not advertising EHT support (actually AP supports EHT, it is missing in scan results because IW does not print it. I don't know your IW, but at least upstream IW does not print it currently), not WCN7850.
> David
>
^ permalink raw reply [flat|nested] 28+ messages in thread
* RE: wcn7850 issues
2024-08-15 2:15 ` Baochen Qiang
@ 2024-08-16 12:23 ` david Atkins
2024-08-19 2:33 ` Baochen Qiang
0 siblings, 1 reply; 28+ messages in thread
From: david Atkins @ 2024-08-16 12:23 UTC (permalink / raw)
To: Baochen Qiang, ath12k@lists.infradead.org
> On 8/15/2024 4:38 AM, david Atkins wrote:
> >>
> >> On 8/6/2024 4:06 PM, david Atkins wrote:
> >>> No support for EHT and therefore no MSC 12 or 13 which fits with the
> >>> dmesg warning about it not being supported,
> >> did not noted this ... So if AP does not support EHT, above warnings
> >> makes sense, like you said.
> >>
> >
> > Anseres inline, AP supports EHT
> >
> >> is this a card firmware
> >>> issue rather than the driver?
> >> did not follow you here, why is it an issue?
> >>
> >
> > Is the firmware that’s uploaded to the card not supporting EHT?
> >
> FW does support EHT.
>
> You are checking scan results, so it is AP not advertising EHT support (actually
> AP supports EHT, it is missing in scan results because IW does not print it. I
> don't know your IW, but at least upstream IW does not print it currently), not
> WCN7850.
I have captured beacon packets from the AP, they show the presence of EHT, this is a snip from the packet decoded, is there something here that would prevent the Hamilton card seeing eht?
Ext Tag: EHT Capabilities (802.11be D3.0)
Ext Tag length: 14 (Tag len: 15)
Ext Tag Number: EHT Capabilities (802.11be D3.0) (108)
EHT MAC Capabilities Information: 0x0017, EPCS Priority Access Support, EHT OM Control Support, Triggered TXOP Sharing Mode 1 Support, Restricted TWT Support, Maximum MPDU Length: 3 895, EHT Link Adaptation Support: No feedback
.... .... .... ...1 = EPCS Priority Access Support: Supported
.... .... .... ..1. = EHT OM Control Support: Supported
.... .... .... .1.. = Triggered TXOP Sharing Mode 1 Support: Supported
.... .... .... 0... = Triggered TXOP Sharing Mode 2 Support: Not supported
.... .... ...1 .... = Restricted TWT Support: Supported
.... .... ..0. .... = SCS Traffic Description Support: Not supported
.... .... 00.. .... = Maximum MPDU Length: 3 895 (0x0)
.... ...0 .... .... = Maximum A-MPDU Length Exponent Extension: 0
.... ..0. .... .... = EHT TRS Support: Not supported
.... .0.. .... .... = TXOP Return Support In TXOP Sharing Mode 2: Not supported
.... 0... .... .... = Two BQRs Support: Not supported
..00 .... .... .... = EHT Link Adaptation Support: No feedback (0)
00.. .... .... .... = Reserved: 0x0
EHT PHY Capabilities Information
EHT PHY Bits 0-15: 0xffe0
.... .... .... ...0 = Reserved: 0x0
.... .... .... ..0. = Support For 320 MHz in 6 GHz: Not supported
.... .... .... .0.. = Support for 242-tone RU in BW Wider than 20 MHz: Not supported
.... .... .... 0... = NDP With 4x EHT-LTF And 3.2 us GI: Not supported
.... .... ...0 .... = Partial Bandwidth UL MU-MIMO: Not supported
.... .... ..1. .... = SU Beamformer: Supported
.... .... .1.. .... = SU Beamformee: Supported
.... ..11 1... .... = Beamformee SS (<= 80 MHz): 0x7
...1 11.. .... .... = Beamformee SS (= 160 MHz): 0x7
111. .... .... .... = Beamformee SS (= 320 MHz): 0x7
EHT PHY Bits 16-31: 0x00db
.... .... .... .011 = Number Of Sounding Dimensions (<= 80 MHz): 0x3
.... .... ..01 1... = Number Of Sounding Dimensions (= 160 MHz): 0x3
.... ...0 11.. .... = Number Of Sounding Dimensions (= 320 MHz): 0x3
.... ..0. .... .... = Ng = 16 SU Feedback: Not supported
.... .0.. .... .... = Ng = 16 MU Feedback: Not supported
.... 0... .... .... = Codebook Size = (4,2) SU Feedback: Not supported
...0 .... .... .... = Codebook Size = (7,5) MU Feedback: Not supported
..0. .... .... .... = Triggered SU Beamforming Feedback: Not supported
.0.. .... .... .... = Triggered MU Beamforming Partial BW Feedback: Not supported
0... .... .... .... = Triggered CQI Feedback: Not supported
EHT PHY Bits 32-39: 0x18
.... ...0 = Partial Bandwidth DL MU-MIMO: Not supported
.... ..0. = EHT PSR-Based SR support: Not supported
.... .0.. = Power Boost Factor Support: Not supported
.... 1... = EHT MU PPDU With 4x EHT-LTF and 0.8 us GI: Supported
0001 .... = Max Nc: 1
EHT PHY Bits 40-63: 0x3ed876
.... .... .... .... .... ...0 = Non-Triggered CQI Feedback: Not supported
.... .... .... .... .... ..1. = Tx 1024-QAM & 4096-QAM < 242-tone RU Support: Supported
.... .... .... .... .... .1.. = Rx 1024-QAM & 4096-QAM < 242-tone-RU Support: Supported
.... .... .... .... .... 0... = PPE Thresholds Present: Not Present
.... .... .... .... ..11 .... = Common Nominal Packet Padding: 3
.... .... .... .000 01.. .... = Maximum Number Of Supported EHT-LTFs: 1
.... .... .101 1... .... .... = Support Of MCS 15: 11
.... .... 1... .... .... .... = Support Of EHT DUP (MCS 14) in 6 GHz: Supported
.... ...0 .... .... .... .... = Support For 20 MHz Operating STA Receiving NDP With Wider BW: Not supported
.... ..1. .... .... .... .... = Non-OFDMA UL MU-MIMO (BW <= 80 MHz): Supported
.... .1.. .... .... .... .... = Non-OFDMA UL MU-MIMO (BW = 160 MHz): Supported
.... 1... .... .... .... .... = Non-OFDMA UL MU-MIMO (BW = 320 MHz): Supported
...1 .... .... .... .... .... = MU Beamformer (BW <= 80 MHz): Supported
..1. .... .... .... .... .... = MU Beamformer (BW = 160 MHz): Supported
.0.. .... .... .... .... .... = MU Beamformer (BW = 320 MHz): Not supported
0... .... .... .... .... .... = TB Sounding Feedback Rate Limit: Not supported
EHT PHY Bits 64-71: 0x444400
.... ...0 = Rx 1024-QAM In Wider Bandwidth DL OFDMA Support: Not supported
.... ..0. = Rx 4096-QAM In Wider Bandwidth DL OFDMA SUpport: Not supported
0000 00.. = Reserved: 0x00
Supported EHT-MCS and NSS Set
EHT-MCS Map (BW <= 80MHz): 0x444444
.... .... .... .... .... 0100 = Rx Max Nss That Supports EHT-MCS 0-9: 4
.... .... .... .... 0100 .... = Tx Max Nss That Supports EHT-MCS 0-9: 4
.... .... .... 0100 .... .... = Rx Max Nss That Supports EHT-MCS 10-11: 4
.... .... 0100 .... .... .... = Tx Max Nss That Supports EHT-MCS 10-11: 4
.... 0100 .... .... .... .... = Rx Max Nss That Supports EHT-MCS 12-13: 4
0100 .... .... .... .... .... = Tx Max Nss That Supports EHT-MCS 12-13: 4
Ext Tag: EHT Operation (802.11be D3.0)
Ext Tag length: 8 (Tag len: 9)
Ext Tag Number: EHT Operation (802.11be D3.0) (106)
EHT Operation Parameters: 0x01, EHT Operation Information Present
.... ...1 = EHT Operation Information Present: True
.... ..0. = Disabled Subchannel Bitmap Present: False
.... .0.. = EHT Default PE Duration: False
.... 0... = Group Addressed BU Indication Limit: False
..00 .... = Group Addressed BU Indication Exponent: 0
00.. .... = Reserved: 0x0
Basic EHT-MCS And Nss Set: 0x44444444
Control: 0x02, Channel Width: 80 MHz EHT BSS bandwidth
.... .010 = Channel Width: 80 MHz EHT BSS bandwidth (2)
0000 0... = Reserved: 0x00
CCFS0: 0x0000006a
CCFS1: 0x00000000
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: wcn7850 issues
2024-08-16 12:23 ` david Atkins
@ 2024-08-19 2:33 ` Baochen Qiang
2024-08-19 10:55 ` david Atkins
0 siblings, 1 reply; 28+ messages in thread
From: Baochen Qiang @ 2024-08-19 2:33 UTC (permalink / raw)
To: david Atkins, ath12k@lists.infradead.org
On 8/16/2024 8:23 PM, david Atkins wrote:
>> On 8/15/2024 4:38 AM, david Atkins wrote:
>>>>
>>>> On 8/6/2024 4:06 PM, david Atkins wrote:
>>>>> No support for EHT and therefore no MSC 12 or 13 which fits with the
>>>>> dmesg warning about it not being supported,
>>>> did not noted this ... So if AP does not support EHT, above warnings
>>>> makes sense, like you said.
>>>>
>>>
>>> Anseres inline, AP supports EHT
>>>
>>>> is this a card firmware
>>>>> issue rather than the driver?
>>>> did not follow you here, why is it an issue?
>>>>
>>>
>>> Is the firmware that’s uploaded to the card not supporting EHT?
>>>
>> FW does support EHT.
>>
>> You are checking scan results, so it is AP not advertising EHT support (actually
>> AP supports EHT, it is missing in scan results because IW does not print it. I
>> don't know your IW, but at least upstream IW does not print it currently), not
>> WCN7850.
>
>
> I have captured beacon packets from the AP, they show the presence of EHT, this is a snip from the packet decoded, is there something here that would prevent the Hamilton card seeing eht?
>
> Ext Tag: EHT Capabilities (802.11be D3.0)
> Ext Tag length: 14 (Tag len: 15)
> Ext Tag Number: EHT Capabilities (802.11be D3.0) (108)
> EHT MAC Capabilities Information: 0x0017, EPCS Priority Access Support, EHT OM Control Support, Triggered TXOP Sharing Mode 1 Support, Restricted TWT Support, Maximum MPDU Length: 3 895, EHT Link Adaptation Support: No feedback
> .... .... .... ...1 = EPCS Priority Access Support: Supported
> .... .... .... ..1. = EHT OM Control Support: Supported
> .... .... .... .1.. = Triggered TXOP Sharing Mode 1 Support: Supported
> .... .... .... 0... = Triggered TXOP Sharing Mode 2 Support: Not supported
> .... .... ...1 .... = Restricted TWT Support: Supported
> .... .... ..0. .... = SCS Traffic Description Support: Not supported
> .... .... 00.. .... = Maximum MPDU Length: 3 895 (0x0)
> .... ...0 .... .... = Maximum A-MPDU Length Exponent Extension: 0
> .... ..0. .... .... = EHT TRS Support: Not supported
> .... .0.. .... .... = TXOP Return Support In TXOP Sharing Mode 2: Not supported
> .... 0... .... .... = Two BQRs Support: Not supported
> ..00 .... .... .... = EHT Link Adaptation Support: No feedback (0)
> 00.. .... .... .... = Reserved: 0x0
> EHT PHY Capabilities Information
> EHT PHY Bits 0-15: 0xffe0
> .... .... .... ...0 = Reserved: 0x0
> .... .... .... ..0. = Support For 320 MHz in 6 GHz: Not supported
> .... .... .... .0.. = Support for 242-tone RU in BW Wider than 20 MHz: Not supported
> .... .... .... 0... = NDP With 4x EHT-LTF And 3.2 us GI: Not supported
> .... .... ...0 .... = Partial Bandwidth UL MU-MIMO: Not supported
> .... .... ..1. .... = SU Beamformer: Supported
> .... .... .1.. .... = SU Beamformee: Supported
> .... ..11 1... .... = Beamformee SS (<= 80 MHz): 0x7
> ...1 11.. .... .... = Beamformee SS (= 160 MHz): 0x7
> 111. .... .... .... = Beamformee SS (= 320 MHz): 0x7
> EHT PHY Bits 16-31: 0x00db
> .... .... .... .011 = Number Of Sounding Dimensions (<= 80 MHz): 0x3
> .... .... ..01 1... = Number Of Sounding Dimensions (= 160 MHz): 0x3
> .... ...0 11.. .... = Number Of Sounding Dimensions (= 320 MHz): 0x3
> .... ..0. .... .... = Ng = 16 SU Feedback: Not supported
> .... .0.. .... .... = Ng = 16 MU Feedback: Not supported
> .... 0... .... .... = Codebook Size = (4,2) SU Feedback: Not supported
> ...0 .... .... .... = Codebook Size = (7,5) MU Feedback: Not supported
> ..0. .... .... .... = Triggered SU Beamforming Feedback: Not supported
> .0.. .... .... .... = Triggered MU Beamforming Partial BW Feedback: Not supported
> 0... .... .... .... = Triggered CQI Feedback: Not supported
> EHT PHY Bits 32-39: 0x18
> .... ...0 = Partial Bandwidth DL MU-MIMO: Not supported
> .... ..0. = EHT PSR-Based SR support: Not supported
> .... .0.. = Power Boost Factor Support: Not supported
> .... 1... = EHT MU PPDU With 4x EHT-LTF and 0.8 us GI: Supported
> 0001 .... = Max Nc: 1
> EHT PHY Bits 40-63: 0x3ed876
> .... .... .... .... .... ...0 = Non-Triggered CQI Feedback: Not supported
> .... .... .... .... .... ..1. = Tx 1024-QAM & 4096-QAM < 242-tone RU Support: Supported
> .... .... .... .... .... .1.. = Rx 1024-QAM & 4096-QAM < 242-tone-RU Support: Supported
> .... .... .... .... .... 0... = PPE Thresholds Present: Not Present
> .... .... .... .... ..11 .... = Common Nominal Packet Padding: 3
> .... .... .... .000 01.. .... = Maximum Number Of Supported EHT-LTFs: 1
> .... .... .101 1... .... .... = Support Of MCS 15: 11
> .... .... 1... .... .... .... = Support Of EHT DUP (MCS 14) in 6 GHz: Supported
> .... ...0 .... .... .... .... = Support For 20 MHz Operating STA Receiving NDP With Wider BW: Not supported
> .... ..1. .... .... .... .... = Non-OFDMA UL MU-MIMO (BW <= 80 MHz): Supported
> .... .1.. .... .... .... .... = Non-OFDMA UL MU-MIMO (BW = 160 MHz): Supported
> .... 1... .... .... .... .... = Non-OFDMA UL MU-MIMO (BW = 320 MHz): Supported
> ...1 .... .... .... .... .... = MU Beamformer (BW <= 80 MHz): Supported
> ..1. .... .... .... .... .... = MU Beamformer (BW = 160 MHz): Supported
> .0.. .... .... .... .... .... = MU Beamformer (BW = 320 MHz): Not supported
> 0... .... .... .... .... .... = TB Sounding Feedback Rate Limit: Not supported
> EHT PHY Bits 64-71: 0x444400
> .... ...0 = Rx 1024-QAM In Wider Bandwidth DL OFDMA Support: Not supported
> .... ..0. = Rx 4096-QAM In Wider Bandwidth DL OFDMA SUpport: Not supported
> 0000 00.. = Reserved: 0x00
> Supported EHT-MCS and NSS Set
> EHT-MCS Map (BW <= 80MHz): 0x444444
> .... .... .... .... .... 0100 = Rx Max Nss That Supports EHT-MCS 0-9: 4
> .... .... .... .... 0100 .... = Tx Max Nss That Supports EHT-MCS 0-9: 4
> .... .... .... 0100 .... .... = Rx Max Nss That Supports EHT-MCS 10-11: 4
> .... .... 0100 .... .... .... = Tx Max Nss That Supports EHT-MCS 10-11: 4
> .... 0100 .... .... .... .... = Rx Max Nss That Supports EHT-MCS 12-13: 4
> 0100 .... .... .... .... .... = Tx Max Nss That Supports EHT-MCS 12-13: 4
> Ext Tag: EHT Operation (802.11be D3.0)
> Ext Tag length: 8 (Tag len: 9)
> Ext Tag Number: EHT Operation (802.11be D3.0) (106)
> EHT Operation Parameters: 0x01, EHT Operation Information Present
> .... ...1 = EHT Operation Information Present: True
> .... ..0. = Disabled Subchannel Bitmap Present: False
> .... .0.. = EHT Default PE Duration: False
> .... 0... = Group Addressed BU Indication Limit: False
> ..00 .... = Group Addressed BU Indication Exponent: 0
> 00.. .... = Reserved: 0x0
> Basic EHT-MCS And Nss Set: 0x44444444
this means AP requires STA NSS to be equal or larger than 4, however WCN7850 only support 2, so connection in EHT is rejected.
> Control: 0x02, Channel Width: 80 MHz EHT BSS bandwidth
> .... .010 = Channel Width: 80 MHz EHT BSS bandwidth (2)
> 0000 0... = Reserved: 0x00
> CCFS0: 0x0000006a
> CCFS1: 0x00000000
>
>
^ permalink raw reply [flat|nested] 28+ messages in thread
* RE: wcn7850 issues
2024-08-19 2:33 ` Baochen Qiang
@ 2024-08-19 10:55 ` david Atkins
2024-08-30 5:55 ` david Atkins
0 siblings, 1 reply; 28+ messages in thread
From: david Atkins @ 2024-08-19 10:55 UTC (permalink / raw)
To: Baochen Qiang, ath12k@lists.infradead.org
> On 8/16/2024 8:23 PM, david Atkins wrote:
> >> On 8/15/2024 4:38 AM, david Atkins wrote:
> >>>>
> >>>> On 8/6/2024 4:06 PM, david Atkins wrote:
> >>>>> No support for EHT and therefore no MSC 12 or 13 which fits with
> >>>>> the dmesg warning about it not being supported,
> >>>> did not noted this ... So if AP does not support EHT, above
> >>>> warnings makes sense, like you said.
> >>>>
> >>>
> >>> Anseres inline, AP supports EHT
> >>>
> >>>> is this a card firmware
> >>>>> issue rather than the driver?
> >>>> did not follow you here, why is it an issue?
> >>>>
> >>>
> >>> Is the firmware that’s uploaded to the card not supporting EHT?
> >>>
> >> FW does support EHT.
> >>
> >> You are checking scan results, so it is AP not advertising EHT
> >> support (actually AP supports EHT, it is missing in scan results
> >> because IW does not print it. I don't know your IW, but at least
> >> upstream IW does not print it currently), not WCN7850.
> >
> >
> > I have captured beacon packets from the AP, they show the presence of EHT,
> this is a snip from the packet decoded, is there something here that would
> prevent the Hamilton card seeing eht?
> >
> > Ext Tag: EHT Capabilities (802.11be D3.0)
> > Ext Tag length: 14 (Tag len: 15)
> > Ext Tag Number: EHT Capabilities (802.11be D3.0) (108)
> > EHT MAC Capabilities Information: 0x0017, EPCS Priority Access
> Support, EHT OM Control Support, Triggered TXOP Sharing Mode 1 Support,
> Restricted TWT Support, Maximum MPDU Length: 3 895, EHT Link Adaptation
> Support: No feedback
> > .... .... .... ...1 = EPCS Priority Access Support: Supported
> > .... .... .... ..1. = EHT OM Control Support: Supported
> > .... .... .... .1.. = Triggered TXOP Sharing Mode 1 Support: Supported
> > .... .... .... 0... = Triggered TXOP Sharing Mode 2 Support: Not
> supported
> > .... .... ...1 .... = Restricted TWT Support: Supported
> > .... .... ..0. .... = SCS Traffic Description Support: Not supported
> > .... .... 00.. .... = Maximum MPDU Length: 3 895 (0x0)
> > .... ...0 .... .... = Maximum A-MPDU Length Exponent Extension: 0
> > .... ..0. .... .... = EHT TRS Support: Not supported
> > .... .0.. .... .... = TXOP Return Support In TXOP Sharing Mode 2: Not
> supported
> > .... 0... .... .... = Two BQRs Support: Not supported
> > ..00 .... .... .... = EHT Link Adaptation Support: No feedback (0)
> > 00.. .... .... .... = Reserved: 0x0
> > EHT PHY Capabilities Information
> > EHT PHY Bits 0-15: 0xffe0
> > .... .... .... ...0 = Reserved: 0x0
> > .... .... .... ..0. = Support For 320 MHz in 6 GHz: Not supported
> > .... .... .... .0.. = Support for 242-tone RU in BW Wider than 20
> MHz: Not supported
> > .... .... .... 0... = NDP With 4x EHT-LTF And 3.2 us GI: Not
> supported
> > .... .... ...0 .... = Partial Bandwidth UL MU-MIMO: Not supported
> > .... .... ..1. .... = SU Beamformer: Supported
> > .... .... .1.. .... = SU Beamformee: Supported
> > .... ..11 1... .... = Beamformee SS (<= 80 MHz): 0x7
> > ...1 11.. .... .... = Beamformee SS (= 160 MHz): 0x7
> > 111. .... .... .... = Beamformee SS (= 320 MHz): 0x7
> > EHT PHY Bits 16-31: 0x00db
> > .... .... .... .011 = Number Of Sounding Dimensions (<= 80 MHz):
> 0x3
> > .... .... ..01 1... = Number Of Sounding Dimensions (= 160 MHz):
> 0x3
> > .... ...0 11.. .... = Number Of Sounding Dimensions (= 320 MHz):
> 0x3
> > .... ..0. .... .... = Ng = 16 SU Feedback: Not supported
> > .... .0.. .... .... = Ng = 16 MU Feedback: Not supported
> > .... 0... .... .... = Codebook Size = (4,2) SU Feedback: Not
> supported
> > ...0 .... .... .... = Codebook Size = (7,5) MU Feedback: Not
> supported
> > ..0. .... .... .... = Triggered SU Beamforming Feedback: Not
> supported
> > .0.. .... .... .... = Triggered MU Beamforming Partial BW Feedback:
> Not supported
> > 0... .... .... .... = Triggered CQI Feedback: Not supported
> > EHT PHY Bits 32-39: 0x18
> > .... ...0 = Partial Bandwidth DL MU-MIMO: Not supported
> > .... ..0. = EHT PSR-Based SR support: Not supported
> > .... .0.. = Power Boost Factor Support: Not supported
> > .... 1... = EHT MU PPDU With 4x EHT-LTF and 0.8 us GI:
> Supported
> > 0001 .... = Max Nc: 1
> > EHT PHY Bits 40-63: 0x3ed876
> > .... .... .... .... .... ...0 = Non-Triggered CQI Feedback: Not
> supported
> > .... .... .... .... .... ..1. = Tx 1024-QAM & 4096-QAM < 242-tone RU
> Support: Supported
> > .... .... .... .... .... .1.. = Rx 1024-QAM & 4096-QAM < 242-tone-RU
> Support: Supported
> > .... .... .... .... .... 0... = PPE Thresholds Present: Not Present
> > .... .... .... .... ..11 .... = Common Nominal Packet Padding: 3
> > .... .... .... .000 01.. .... = Maximum Number Of Supported EHT-
> LTFs: 1
> > .... .... .101 1... .... .... = Support Of MCS 15: 11
> > .... .... 1... .... .... .... = Support Of EHT DUP (MCS 14) in 6 GHz:
> Supported
> > .... ...0 .... .... .... .... = Support For 20 MHz Operating STA
> Receiving NDP With Wider BW: Not supported
> > .... ..1. .... .... .... .... = Non-OFDMA UL MU-MIMO (BW <= 80
> MHz): Supported
> > .... .1.. .... .... .... .... = Non-OFDMA UL MU-MIMO (BW = 160
> MHz): Supported
> > .... 1... .... .... .... .... = Non-OFDMA UL MU-MIMO (BW = 320
> MHz): Supported
> > ...1 .... .... .... .... .... = MU Beamformer (BW <= 80 MHz):
> Supported
> > ..1. .... .... .... .... .... = MU Beamformer (BW = 160 MHz):
> Supported
> > .0.. .... .... .... .... .... = MU Beamformer (BW = 320 MHz): Not
> supported
> > 0... .... .... .... .... .... = TB Sounding Feedback Rate Limit: Not
> supported
> > EHT PHY Bits 64-71: 0x444400
> > .... ...0 = Rx 1024-QAM In Wider Bandwidth DL OFDMA Support:
> Not supported
> > .... ..0. = Rx 4096-QAM In Wider Bandwidth DL OFDMA SUpport:
> Not supported
> > 0000 00.. = Reserved: 0x00
> > Supported EHT-MCS and NSS Set
> > EHT-MCS Map (BW <= 80MHz): 0x444444
> > .... .... .... .... .... 0100 = Rx Max Nss That Supports EHT-MCS 0-9:
> 4
> > .... .... .... .... 0100 .... = Tx Max Nss That Supports EHT-MCS 0-9: 4
> > .... .... .... 0100 .... .... = Rx Max Nss That Supports EHT-MCS 10-
> 11: 4
> > .... .... 0100 .... .... .... = Tx Max Nss That Supports EHT-MCS 10-
> 11: 4
> > .... 0100 .... .... .... .... = Rx Max Nss That Supports EHT-MCS 12-
> 13: 4
> > 0100 .... .... .... .... .... = Tx Max Nss That Supports EHT-MCS 12-
> 13: 4
> > Ext Tag: EHT Operation (802.11be D3.0)
> > Ext Tag length: 8 (Tag len: 9)
> > Ext Tag Number: EHT Operation (802.11be D3.0) (106)
> > EHT Operation Parameters: 0x01, EHT Operation Information Present
> > .... ...1 = EHT Operation Information Present: True
> > .... ..0. = Disabled Subchannel Bitmap Present: False
> > .... .0.. = EHT Default PE Duration: False
> > .... 0... = Group Addressed BU Indication Limit: False
> > ..00 .... = Group Addressed BU Indication Exponent: 0
> > 00.. .... = Reserved: 0x0
> > Basic EHT-MCS And Nss Set: 0x44444444
> this means AP requires STA NSS to be equal or larger than 4, however
> WCN7850 only support 2, so connection in EHT is rejected.
>
The MCS Rx/Tx Max re maximum from my reading of the spec, not minimum's, the driver work out the max it supports in this case 2 and this less than 4 so it should work.
> > Control: 0x02, Channel Width: 80 MHz EHT BSS bandwidth
> > .... .010 = Channel Width: 80 MHz EHT BSS bandwidth (2)
> > 0000 0... = Reserved: 0x00
> > CCFS0: 0x0000006a
> > CCFS1: 0x00000000
> >
> >
^ permalink raw reply [flat|nested] 28+ messages in thread
* RE: wcn7850 issues
2024-08-19 10:55 ` david Atkins
@ 2024-08-30 5:55 ` david Atkins
2024-08-30 7:08 ` Baochen Qiang
0 siblings, 1 reply; 28+ messages in thread
From: david Atkins @ 2024-08-30 5:55 UTC (permalink / raw)
To: david Atkins, Baochen Qiang, ath12k@lists.infradead.org
Any updates on this? We still cannot register a Hamilton card with ath12k driver with a 4x4 AP
> -----Original Message-----
> From: ath12k <ath12k-bounces@lists.infradead.org> On Behalf Of david
> Atkins
> Sent: Monday, August 19, 2024 11:55 AM
> To: Baochen Qiang <quic_bqiang@quicinc.com>; ath12k@lists.infradead.org
> Subject: RE: wcn7850 issues
>
> > On 8/16/2024 8:23 PM, david Atkins wrote:
> > >> On 8/15/2024 4:38 AM, david Atkins wrote:
> > >>>>
> > >>>> On 8/6/2024 4:06 PM, david Atkins wrote:
> > >>>>> No support for EHT and therefore no MSC 12 or 13 which fits with
> > >>>>> the dmesg warning about it not being supported,
> > >>>> did not noted this ... So if AP does not support EHT, above
> > >>>> warnings makes sense, like you said.
> > >>>>
> > >>>
> > >>> Anseres inline, AP supports EHT
> > >>>
> > >>>> is this a card firmware
> > >>>>> issue rather than the driver?
> > >>>> did not follow you here, why is it an issue?
> > >>>>
> > >>>
> > >>> Is the firmware that’s uploaded to the card not supporting EHT?
> > >>>
> > >> FW does support EHT.
> > >>
> > >> You are checking scan results, so it is AP not advertising EHT
> > >> support (actually AP supports EHT, it is missing in scan results
> > >> because IW does not print it. I don't know your IW, but at least
> > >> upstream IW does not print it currently), not WCN7850.
> > >
> > >
> > > I have captured beacon packets from the AP, they show the presence
> > > of EHT,
> > this is a snip from the packet decoded, is there something here that
> > would prevent the Hamilton card seeing eht?
> > >
> > > Ext Tag: EHT Capabilities (802.11be D3.0)
> > > Ext Tag length: 14 (Tag len: 15)
> > > Ext Tag Number: EHT Capabilities (802.11be D3.0) (108)
> > > EHT MAC Capabilities Information: 0x0017, EPCS Priority
> > > Access
> > Support, EHT OM Control Support, Triggered TXOP Sharing Mode 1
> > Support, Restricted TWT Support, Maximum MPDU Length: 3 895, EHT Link
> > Adaptation
> > Support: No feedback
> > > .... .... .... ...1 = EPCS Priority Access Support: Supported
> > > .... .... .... ..1. = EHT OM Control Support: Supported
> > > .... .... .... .1.. = Triggered TXOP Sharing Mode 1 Support:
> Supported
> > > .... .... .... 0... = Triggered TXOP Sharing Mode 2
> > > Support: Not
> > supported
> > > .... .... ...1 .... = Restricted TWT Support: Supported
> > > .... .... ..0. .... = SCS Traffic Description Support: Not supported
> > > .... .... 00.. .... = Maximum MPDU Length: 3 895 (0x0)
> > > .... ...0 .... .... = Maximum A-MPDU Length Exponent Extension: 0
> > > .... ..0. .... .... = EHT TRS Support: Not supported
> > > .... .0.. .... .... = TXOP Return Support In TXOP
> > > Sharing Mode 2: Not
> > supported
> > > .... 0... .... .... = Two BQRs Support: Not supported
> > > ..00 .... .... .... = EHT Link Adaptation Support: No feedback (0)
> > > 00.. .... .... .... = Reserved: 0x0
> > > EHT PHY Capabilities Information
> > > EHT PHY Bits 0-15: 0xffe0
> > > .... .... .... ...0 = Reserved: 0x0
> > > .... .... .... ..0. = Support For 320 MHz in 6 GHz: Not supported
> > > .... .... .... .0.. = Support for 242-tone RU in
> > > BW Wider than 20
> > MHz: Not supported
> > > .... .... .... 0... = NDP With 4x EHT-LTF And
> > > 3.2 us GI: Not
> > supported
> > > .... .... ...0 .... = Partial Bandwidth UL MU-MIMO: Not
> supported
> > > .... .... ..1. .... = SU Beamformer: Supported
> > > .... .... .1.. .... = SU Beamformee: Supported
> > > .... ..11 1... .... = Beamformee SS (<= 80 MHz): 0x7
> > > ...1 11.. .... .... = Beamformee SS (= 160 MHz): 0x7
> > > 111. .... .... .... = Beamformee SS (= 320 MHz): 0x7
> > > EHT PHY Bits 16-31: 0x00db
> > > .... .... .... .011 = Number Of Sounding Dimensions (<= 80 MHz):
> > 0x3
> > > .... .... ..01 1... = Number Of Sounding Dimensions (= 160 MHz):
> > 0x3
> > > .... ...0 11.. .... = Number Of Sounding Dimensions (= 320 MHz):
> > 0x3
> > > .... ..0. .... .... = Ng = 16 SU Feedback: Not supported
> > > .... .0.. .... .... = Ng = 16 MU Feedback: Not supported
> > > .... 0... .... .... = Codebook Size = (4,2) SU
> > > Feedback: Not
> > supported
> > > ...0 .... .... .... = Codebook Size = (7,5) MU
> > > Feedback: Not
> > supported
> > > ..0. .... .... .... = Triggered SU Beamforming
> > > Feedback: Not
> > supported
> > > .0.. .... .... .... = Triggered MU Beamforming Partial BW
> Feedback:
> > Not supported
> > > 0... .... .... .... = Triggered CQI Feedback: Not supported
> > > EHT PHY Bits 32-39: 0x18
> > > .... ...0 = Partial Bandwidth DL MU-MIMO: Not supported
> > > .... ..0. = EHT PSR-Based SR support: Not supported
> > > .... .0.. = Power Boost Factor Support: Not supported
> > > .... 1... = EHT MU PPDU With 4x EHT-LTF and 0.8 us GI:
> > Supported
> > > 0001 .... = Max Nc: 1
> > > EHT PHY Bits 40-63: 0x3ed876
> > > .... .... .... .... .... ...0 = Non-Triggered
> > > CQI Feedback: Not
> > supported
> > > .... .... .... .... .... ..1. = Tx 1024-QAM &
> > > 4096-QAM < 242-tone RU
> > Support: Supported
> > > .... .... .... .... .... .1.. = Rx 1024-QAM &
> > > 4096-QAM < 242-tone-RU
> > Support: Supported
> > > .... .... .... .... .... 0... = PPE Thresholds Present: Not Present
> > > .... .... .... .... ..11 .... = Common Nominal Packet Padding: 3
> > > .... .... .... .000 01.. .... = Maximum Number
> > > Of Supported EHT-
> > LTFs: 1
> > > .... .... .101 1... .... .... = Support Of MCS 15: 11
> > > .... .... 1... .... .... .... = Support Of EHT DUP (MCS 14) in 6 GHz:
> > Supported
> > > .... ...0 .... .... .... .... = Support For 20
> > > MHz Operating STA
> > Receiving NDP With Wider BW: Not supported
> > > .... ..1. .... .... .... .... = Non-OFDMA UL
> > > MU-MIMO (BW <= 80
> > MHz): Supported
> > > .... .1.. .... .... .... .... = Non-OFDMA UL
> > > MU-MIMO (BW = 160
> > MHz): Supported
> > > .... 1... .... .... .... .... = Non-OFDMA UL
> > > MU-MIMO (BW = 320
> > MHz): Supported
> > > ...1 .... .... .... .... .... = MU Beamformer (BW <= 80 MHz):
> > Supported
> > > ..1. .... .... .... .... .... = MU Beamformer (BW = 160 MHz):
> > Supported
> > > .0.. .... .... .... .... .... = MU Beamformer
> > > (BW = 320 MHz): Not
> > supported
> > > 0... .... .... .... .... .... = TB Sounding
> > > Feedback Rate Limit: Not
> > supported
> > > EHT PHY Bits 64-71: 0x444400
> > > .... ...0 = Rx 1024-QAM In Wider Bandwidth DL OFDMA
> Support:
> > Not supported
> > > .... ..0. = Rx 4096-QAM In Wider Bandwidth DL OFDMA
> SUpport:
> > Not supported
> > > 0000 00.. = Reserved: 0x00
> > > Supported EHT-MCS and NSS Set
> > > EHT-MCS Map (BW <= 80MHz): 0x444444
> > > .... .... .... .... .... 0100 = Rx Max Nss That Supports EHT-MCS 0-
> 9:
> > 4
> > > .... .... .... .... 0100 .... = Tx Max Nss That Supports EHT-MCS 0-9:
> 4
> > > .... .... .... 0100 .... .... = Rx Max Nss That
> > > Supports EHT-MCS 10-
> > 11: 4
> > > .... .... 0100 .... .... .... = Tx Max Nss That
> > > Supports EHT-MCS 10-
> > 11: 4
> > > .... 0100 .... .... .... .... = Rx Max Nss That
> > > Supports EHT-MCS 12-
> > 13: 4
> > > 0100 .... .... .... .... .... = Tx Max Nss That
> > > Supports EHT-MCS 12-
> > 13: 4
> > > Ext Tag: EHT Operation (802.11be D3.0)
> > > Ext Tag length: 8 (Tag len: 9)
> > > Ext Tag Number: EHT Operation (802.11be D3.0) (106)
> > > EHT Operation Parameters: 0x01, EHT Operation Information
> Present
> > > .... ...1 = EHT Operation Information Present: True
> > > .... ..0. = Disabled Subchannel Bitmap Present: False
> > > .... .0.. = EHT Default PE Duration: False
> > > .... 0... = Group Addressed BU Indication Limit: False
> > > ..00 .... = Group Addressed BU Indication Exponent: 0
> > > 00.. .... = Reserved: 0x0
> > > Basic EHT-MCS And Nss Set: 0x44444444
> > this means AP requires STA NSS to be equal or larger than 4, however
> > WCN7850 only support 2, so connection in EHT is rejected.
> >
>
> The MCS Rx/Tx Max re maximum from my reading of the spec, not
> minimum's, the driver work out the max it supports in this case 2 and this
> less than 4 so it should work.
>
> > > Control: 0x02, Channel Width: 80 MHz EHT BSS bandwidth
> > > .... .010 = Channel Width: 80 MHz EHT BSS bandwidth (2)
> > > 0000 0... = Reserved: 0x00
> > > CCFS0: 0x0000006a
> > > CCFS1: 0x00000000
> > >
> > >
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: wcn7850 issues
2024-08-30 5:55 ` david Atkins
@ 2024-08-30 7:08 ` Baochen Qiang
2024-09-01 7:39 ` david Atkins
0 siblings, 1 reply; 28+ messages in thread
From: Baochen Qiang @ 2024-08-30 7:08 UTC (permalink / raw)
To: david Atkins, ath12k@lists.infradead.org
On 8/30/2024 1:55 PM, david Atkins wrote:
> Any updates on this? We still cannot register a Hamilton card with ath12k driver with a 4x4 AP
The 'Basic EHT-MCS And Nss Set' indicate the minimal requirement, not the max, see spec:
35.15 EHT BSS operation
35.15.1 Basic EHT BSS operation
An EHT STA has dot11EHTOptionImplemented equal to true.
The basic EHT-MCS and NSS set is the set of <EHT-MCS, NSS> tuples that are supported by all EHT STAs
that are members of an EHT BSS. ...
An EHT STA shall not attempt to join (MLME-JOIN.request primitive) a BSS unless it supports (i.e., is able
to both transmit and receive using) all of the <EHT-MCS, NSS> tuples in the basic EHT-MCS and NSS set.
^ permalink raw reply [flat|nested] 28+ messages in thread
* RE: wcn7850 issues
2024-08-30 7:08 ` Baochen Qiang
@ 2024-09-01 7:39 ` david Atkins
2024-09-02 1:56 ` Baochen Qiang
0 siblings, 1 reply; 28+ messages in thread
From: david Atkins @ 2024-09-01 7:39 UTC (permalink / raw)
To: Baochen Qiang, ath12k@lists.infradead.org
> On 8/30/2024 1:55 PM, david Atkins wrote:
> > Any updates on this? We still cannot register a Hamilton card with
> > ath12k driver with a 4x4 AP
>
> The 'Basic EHT-MCS And Nss Set' indicate the minimal requirement, not the
> max, see spec:
>
> 35.15 EHT BSS operation
> 35.15.1 Basic EHT BSS operation
>
> An EHT STA has dot11EHTOptionImplemented equal to true.
> The basic EHT-MCS and NSS set is the set of <EHT-MCS, NSS> tuples that are
> supported by all EHT STAs that are members of an EHT BSS. ...
>
> An EHT STA shall not attempt to join (MLME-JOIN.request primitive) a BSS
> unless it supports (i.e., is able to both transmit and receive using) all of the
> <EHT-MCS, NSS> tuples in the basic EHT-MCS and NSS set.
I'm unsure what's missing here, this is the beacon data relating to EHT MCS/NSS
Supported EHT-MCS and NSS Set
EHT-MCS Map (BW <= 80MHz): 0x444444
.... .... .... .... .... 0100 = Rx Max Nss That Supports EHT-MCS 0-9: 4
.... .... .... .... 0100 .... = Tx Max Nss That Supports EHT-MCS 0-9: 4
.... .... .... 0100 .... .... = Rx Max Nss That Supports EHT-MCS 10-11: 4
.... .... 0100 .... .... .... = Tx Max Nss That Supports EHT-MCS 10-11: 4
.... 0100 .... .... .... .... = Rx Max Nss That Supports EHT-MCS 12-13: 4
0100 .... .... .... .... .... = Tx Max Nss That Supports EHT-MCS 12-13: 4
Ext Tag: EHT Operation (802.11be D3.0)
Ext Tag length: 8 (Tag len: 9)
Ext Tag Number: EHT Operation (802.11be D3.0) (106)
EHT Operation Parameters: 0x01, EHT Operation Information Present
.... ...1 = EHT Operation Information Present: True
.... ..0. = Disabled Subchannel Bitmap Present: False
.... .0.. = EHT Default PE Duration: False
.... 0... = Group Addressed BU Indication Limit: False
..00 .... = Group Addressed BU Indication Exponent: 0
00.. .... = Reserved: 0x0
Basic EHT-MCS And Nss Set: 0x44444444
Control: 0x02, Channel Width: 80 MHz EHT BSS bandwidth
.... .010 = Channel Width: 80 MHz EHT BSS bandwidth (2)
0000 0... = Reserved: 0x00
Are you saying the ath12k driver does not support these features? If not can you clarify the issue so I can raise with the AP team.
David
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: wcn7850 issues
2024-09-01 7:39 ` david Atkins
@ 2024-09-02 1:56 ` Baochen Qiang
2024-09-02 6:03 ` david Atkins
0 siblings, 1 reply; 28+ messages in thread
From: Baochen Qiang @ 2024-09-02 1:56 UTC (permalink / raw)
To: david Atkins, ath12k@lists.infradead.org
On 9/1/2024 3:39 PM, david Atkins wrote:
>> On 8/30/2024 1:55 PM, david Atkins wrote:
>>> Any updates on this? We still cannot register a Hamilton card with
>>> ath12k driver with a 4x4 AP
>>
>> The 'Basic EHT-MCS And Nss Set' indicate the minimal requirement, not the
>> max, see spec:
>>
>> 35.15 EHT BSS operation
>> 35.15.1 Basic EHT BSS operation
>>
>> An EHT STA has dot11EHTOptionImplemented equal to true.
>> The basic EHT-MCS and NSS set is the set of <EHT-MCS, NSS> tuples that are
>> supported by all EHT STAs that are members of an EHT BSS. ...
>>
>> An EHT STA shall not attempt to join (MLME-JOIN.request primitive) a BSS
>> unless it supports (i.e., is able to both transmit and receive using) all of the
>> <EHT-MCS, NSS> tuples in the basic EHT-MCS and NSS set.
>
> I'm unsure what's missing here, this is the beacon data relating to EHT MCS/NSS
>
> Supported EHT-MCS and NSS Set
> EHT-MCS Map (BW <= 80MHz): 0x444444
> .... .... .... .... .... 0100 = Rx Max Nss That Supports EHT-MCS 0-9: 4
> .... .... .... .... 0100 .... = Tx Max Nss That Supports EHT-MCS 0-9: 4
> .... .... .... 0100 .... .... = Rx Max Nss That Supports EHT-MCS 10-11: 4
> .... .... 0100 .... .... .... = Tx Max Nss That Supports EHT-MCS 10-11: 4
> .... 0100 .... .... .... .... = Rx Max Nss That Supports EHT-MCS 12-13: 4
> 0100 .... .... .... .... .... = Tx Max Nss That Supports EHT-MCS 12-13: 4
> Ext Tag: EHT Operation (802.11be D3.0)
> Ext Tag length: 8 (Tag len: 9)
> Ext Tag Number: EHT Operation (802.11be D3.0) (106)
> EHT Operation Parameters: 0x01, EHT Operation Information Present
> .... ...1 = EHT Operation Information Present: True
> .... ..0. = Disabled Subchannel Bitmap Present: False
> .... .0.. = EHT Default PE Duration: False
> .... 0... = Group Addressed BU Indication Limit: False
> ..00 .... = Group Addressed BU Indication Exponent: 0
> 00.. .... = Reserved: 0x0
> Basic EHT-MCS And Nss Set: 0x44444444
> Control: 0x02, Channel Width: 80 MHz EHT BSS bandwidth
> .... .010 = Channel Width: 80 MHz EHT BSS bandwidth (2)
> 0000 0... = Reserved: 0x00
>
> Are you saying the ath12k driver does not support these features? If not can you clarify the issue so I can raise with the AP team.
>
ath12k/WCN7850 supports EHT, but with NSS only 2. Here the AP requires NSS to be no less than 4, that is why EHT connection was disabled.
> David
>
>
>
^ permalink raw reply [flat|nested] 28+ messages in thread
* RE: wcn7850 issues
2024-09-02 1:56 ` Baochen Qiang
@ 2024-09-02 6:03 ` david Atkins
2024-09-02 6:20 ` Baochen Qiang
0 siblings, 1 reply; 28+ messages in thread
From: david Atkins @ 2024-09-02 6:03 UTC (permalink / raw)
To: Baochen Qiang, ath12k@lists.infradead.org
> On 9/1/2024 3:39 PM, david Atkins wrote:
> >> On 8/30/2024 1:55 PM, david Atkins wrote:
> >>> Any updates on this? We still cannot register a Hamilton card with
> >>> ath12k driver with a 4x4 AP
> >>
> >> The 'Basic EHT-MCS And Nss Set' indicate the minimal requirement, not
> >> the max, see spec:
> >>
> >> 35.15 EHT BSS operation
> >> 35.15.1 Basic EHT BSS operation
> >>
> >> An EHT STA has dot11EHTOptionImplemented equal to true.
> >> The basic EHT-MCS and NSS set is the set of <EHT-MCS, NSS> tuples
> >> that are supported by all EHT STAs that are members of an EHT BSS. ...
> >>
> >> An EHT STA shall not attempt to join (MLME-JOIN.request primitive) a
> >> BSS unless it supports (i.e., is able to both transmit and receive
> >> using) all of the <EHT-MCS, NSS> tuples in the basic EHT-MCS and NSS set.
> >
> > I'm unsure what's missing here, this is the beacon data relating to
> > EHT MCS/NSS
> >
> > Supported EHT-MCS and NSS Set
> > EHT-MCS Map (BW <= 80MHz): 0x444444
> > .... .... .... .... .... 0100 = Rx Max Nss That Supports EHT-MCS 0-9:
> 4
> > .... .... .... .... 0100 .... = Tx Max Nss That Supports EHT-MCS 0-9: 4
> > .... .... .... 0100 .... .... = Rx Max Nss That Supports EHT-MCS 10-
> 11: 4
> > .... .... 0100 .... .... .... = Tx Max Nss That Supports EHT-MCS 10-
> 11: 4
> > .... 0100 .... .... .... .... = Rx Max Nss That Supports EHT-MCS 12-
> 13: 4
> > 0100 .... .... .... .... .... = Tx Max Nss That Supports EHT-MCS 12-
> 13: 4
> > Ext Tag: EHT Operation (802.11be D3.0)
> > Ext Tag length: 8 (Tag len: 9)
> > Ext Tag Number: EHT Operation (802.11be D3.0) (106)
> > EHT Operation Parameters: 0x01, EHT Operation Information Present
> > .... ...1 = EHT Operation Information Present: True
> > .... ..0. = Disabled Subchannel Bitmap Present: False
> > .... .0.. = EHT Default PE Duration: False
> > .... 0... = Group Addressed BU Indication Limit: False
> > ..00 .... = Group Addressed BU Indication Exponent: 0
> > 00.. .... = Reserved: 0x0
> > Basic EHT-MCS And Nss Set: 0x44444444
> > Control: 0x02, Channel Width: 80 MHz EHT BSS bandwidth
> > .... .010 = Channel Width: 80 MHz EHT BSS bandwidth (2)
> > 0000 0... = Reserved: 0x00
> >
> > Are you saying the ath12k driver does not support these features? If not can
> you clarify the issue so I can raise with the AP team.
> >
> ath12k/WCN7850 supports EHT, but with NSS only 2. Here the AP requires NSS
> to be no less than 4, that is why EHT connection was disabled.
Which field is requiring NSS of 4, I'm only seeing a maximum of 4, the Qualcomm windows driver will connect to the same AP, we had assumed that that ath12k would do the same.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: wcn7850 issues
2024-09-02 6:03 ` david Atkins
@ 2024-09-02 6:20 ` Baochen Qiang
2024-09-03 6:29 ` david Atkins
0 siblings, 1 reply; 28+ messages in thread
From: Baochen Qiang @ 2024-09-02 6:20 UTC (permalink / raw)
To: david Atkins, ath12k@lists.infradead.org
On 9/2/2024 2:03 PM, david Atkins wrote:
>> On 9/1/2024 3:39 PM, david Atkins wrote:
>>>> On 8/30/2024 1:55 PM, david Atkins wrote:
>>>>> Any updates on this? We still cannot register a Hamilton card with
>>>>> ath12k driver with a 4x4 AP
>>>>
>>>> The 'Basic EHT-MCS And Nss Set' indicate the minimal requirement, not
>>>> the max, see spec:
>>>>
>>>> 35.15 EHT BSS operation
>>>> 35.15.1 Basic EHT BSS operation
>>>>
>>>> An EHT STA has dot11EHTOptionImplemented equal to true.
>>>> The basic EHT-MCS and NSS set is the set of <EHT-MCS, NSS> tuples
>>>> that are supported by all EHT STAs that are members of an EHT BSS. ...
>>>>
>>>> An EHT STA shall not attempt to join (MLME-JOIN.request primitive) a
>>>> BSS unless it supports (i.e., is able to both transmit and receive
>>>> using) all of the <EHT-MCS, NSS> tuples in the basic EHT-MCS and NSS set.
>>>
>>> I'm unsure what's missing here, this is the beacon data relating to
>>> EHT MCS/NSS
>>>
>>> Supported EHT-MCS and NSS Set
>>> EHT-MCS Map (BW <= 80MHz): 0x444444
>>> .... .... .... .... .... 0100 = Rx Max Nss That Supports EHT-MCS 0-9:
>> 4
>>> .... .... .... .... 0100 .... = Tx Max Nss That Supports EHT-MCS 0-9: 4
>>> .... .... .... 0100 .... .... = Rx Max Nss That Supports EHT-MCS 10-
>> 11: 4
>>> .... .... 0100 .... .... .... = Tx Max Nss That Supports EHT-MCS 10-
>> 11: 4
>>> .... 0100 .... .... .... .... = Rx Max Nss That Supports EHT-MCS 12-
>> 13: 4
>>> 0100 .... .... .... .... .... = Tx Max Nss That Supports EHT-MCS 12-
>> 13: 4
>>> Ext Tag: EHT Operation (802.11be D3.0)
>>> Ext Tag length: 8 (Tag len: 9)
>>> Ext Tag Number: EHT Operation (802.11be D3.0) (106)
>>> EHT Operation Parameters: 0x01, EHT Operation Information Present
>>> .... ...1 = EHT Operation Information Present: True
>>> .... ..0. = Disabled Subchannel Bitmap Present: False
>>> .... .0.. = EHT Default PE Duration: False
>>> .... 0... = Group Addressed BU Indication Limit: False
>>> ..00 .... = Group Addressed BU Indication Exponent: 0
>>> 00.. .... = Reserved: 0x0
>>> Basic EHT-MCS And Nss Set: 0x44444444
>>> Control: 0x02, Channel Width: 80 MHz EHT BSS bandwidth
>>> .... .010 = Channel Width: 80 MHz EHT BSS bandwidth (2)
>>> 0000 0... = Reserved: 0x00
>>>
>>> Are you saying the ath12k driver does not support these features? If not can
>> you clarify the issue so I can raise with the AP team.
>>>
>> ath12k/WCN7850 supports EHT, but with NSS only 2. Here the AP requires NSS
>> to be no less than 4, that is why EHT connection was disabled.
>
> Which field is requiring NSS of 4, I'm only seeing a maximum of 4, the Qualcomm windows driver will connect to the same AP, we had assumed that that ath12k would do the same.
Basic EHT-MCS And Nss Set: 0x44444444
>
>
>
>
^ permalink raw reply [flat|nested] 28+ messages in thread
* RE: wcn7850 issues
2024-09-02 6:20 ` Baochen Qiang
@ 2024-09-03 6:29 ` david Atkins
2024-09-03 7:47 ` Kalle Valo
0 siblings, 1 reply; 28+ messages in thread
From: david Atkins @ 2024-09-03 6:29 UTC (permalink / raw)
To: Baochen Qiang, ath12k@lists.infradead.org
...
> >>> Ext Tag: EHT Operation (802.11be D3.0)
> >>> Ext Tag length: 8 (Tag len: 9)
> >>> Ext Tag Number: EHT Operation (802.11be D3.0) (106)
> >>> EHT Operation Parameters: 0x01, EHT Operation Information
> Present
> >>> .... ...1 = EHT Operation Information Present: True
> >>> .... ..0. = Disabled Subchannel Bitmap Present: False
> >>> .... .0.. = EHT Default PE Duration: False
> >>> .... 0... = Group Addressed BU Indication Limit: False
> >>> ..00 .... = Group Addressed BU Indication Exponent: 0
> >>> 00.. .... = Reserved: 0x0
> >>> Basic EHT-MCS And Nss Set: 0x44444444
> >>> Control: 0x02, Channel Width: 80 MHz EHT BSS bandwidth
> >>> .... .010 = Channel Width: 80 MHz EHT BSS bandwidth (2)
> >>> 0000 0... = Reserved: 0x00
> >>>
> >>> Are you saying the ath12k driver does not support these features? If
> >>> not can
> >> you clarify the issue so I can raise with the AP team.
> >>>
> >> ath12k/WCN7850 supports EHT, but with NSS only 2. Here the AP
> >> requires NSS to be no less than 4, that is why EHT connection was disabled.
> >
> > Which field is requiring NSS of 4, I'm only seeing a maximum of 4, the
> Qualcomm windows driver will connect to the same AP, we had assumed that
> that ath12k would do the same.
> Basic EHT-MCS And Nss Set: 0x44444444
My understanding of the spec is that there are maximum numbers of streams though, are you saying the AP has to advertise 0x22222222 which would then prevent a 4x4 client (say an extender) from connecting with 4 streams? I note that the Qualcomm windows driver for Hamilton works with the AP and an Intel BE200 also works both of which will be in at most 2x2
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: wcn7850 issues
2024-09-03 6:29 ` david Atkins
@ 2024-09-03 7:47 ` Kalle Valo
2024-09-03 9:57 ` Janusz Dziedzic
0 siblings, 1 reply; 28+ messages in thread
From: Kalle Valo @ 2024-09-03 7:47 UTC (permalink / raw)
To: david Atkins; +Cc: Baochen Qiang, ath12k@lists.infradead.org, linux-wireless
+ linux-wireless
david Atkins <david@3adesign.co.uk> writes:
> ...
>> >>> Ext Tag: EHT Operation (802.11be D3.0)
>> >>> Ext Tag length: 8 (Tag len: 9)
>> >>> Ext Tag Number: EHT Operation (802.11be D3.0) (106)
>> >>> EHT Operation Parameters: 0x01, EHT Operation Information
>> Present
>> >>> .... ...1 = EHT Operation Information Present: True
>> >>> .... ..0. = Disabled Subchannel Bitmap Present: False
>> >>> .... .0.. = EHT Default PE Duration: False
>> >>> .... 0... = Group Addressed BU Indication Limit: False
>> >>> ..00 .... = Group Addressed BU Indication Exponent: 0
>> >>> 00.. .... = Reserved: 0x0
>> >>> Basic EHT-MCS And Nss Set: 0x44444444
>> >>> Control: 0x02, Channel Width: 80 MHz EHT BSS bandwidth
>> >>> .... .010 = Channel Width: 80 MHz EHT BSS bandwidth (2)
>> >>> 0000 0... = Reserved: 0x00
>> >>>
>> >>> Are you saying the ath12k driver does not support these features? If
>> >>> not can
>> >> you clarify the issue so I can raise with the AP team.
>> >>>
>> >> ath12k/WCN7850 supports EHT, but with NSS only 2. Here the AP
>> >> requires NSS to be no less than 4, that is why EHT connection was disabled.
>> >
>> > Which field is requiring NSS of 4, I'm only seeing a maximum of 4, the
>> Qualcomm windows driver will connect to the same AP, we had assumed that
>> that ath12k would do the same.
>> Basic EHT-MCS And Nss Set: 0x44444444
>
> My understanding of the spec is that there are maximum numbers of
> streams though, are you saying the AP has to advertise 0x22222222
> which would then prevent a 4x4 client (say an extender) from
> connecting with 4 streams? I note that the Qualcomm windows driver for
> Hamilton works with the AP and an Intel BE200 also works both of which
> will be in at most 2x2
Did you test Intel BE200 with the Windows driver? Johannes mentioned
that ieee80211_verify_sta_eht_mcs_support() in mac80211 checks this so I
would assume that iwlwifi also behaves like ath12k.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
https://docs.kernel.org/process/submitting-patches.html
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: wcn7850 issues
2024-09-03 7:47 ` Kalle Valo
@ 2024-09-03 9:57 ` Janusz Dziedzic
2024-09-03 10:07 ` Johannes Berg
2024-09-03 10:09 ` Kalle Valo
0 siblings, 2 replies; 28+ messages in thread
From: Janusz Dziedzic @ 2024-09-03 9:57 UTC (permalink / raw)
To: Kalle Valo
Cc: david Atkins, Baochen Qiang, ath12k@lists.infradead.org,
linux-wireless
wt., 3 wrz 2024 o 09:47 Kalle Valo <kvalo@kernel.org> napisał(a):
>
> + linux-wireless
>
> david Atkins <david@3adesign.co.uk> writes:
>
> > ...
> >> >>> Ext Tag: EHT Operation (802.11be D3.0)
> >> >>> Ext Tag length: 8 (Tag len: 9)
> >> >>> Ext Tag Number: EHT Operation (802.11be D3.0) (106)
> >> >>> EHT Operation Parameters: 0x01, EHT Operation Information
> >> Present
> >> >>> .... ...1 = EHT Operation Information Present: True
> >> >>> .... ..0. = Disabled Subchannel Bitmap Present: False
> >> >>> .... .0.. = EHT Default PE Duration: False
> >> >>> .... 0... = Group Addressed BU Indication Limit: False
> >> >>> ..00 .... = Group Addressed BU Indication Exponent: 0
> >> >>> 00.. .... = Reserved: 0x0
> >> >>> Basic EHT-MCS And Nss Set: 0x44444444
> >> >>> Control: 0x02, Channel Width: 80 MHz EHT BSS bandwidth
> >> >>> .... .010 = Channel Width: 80 MHz EHT BSS bandwidth (2)
> >> >>> 0000 0... = Reserved: 0x00
> >> >>>
> >> >>> Are you saying the ath12k driver does not support these features? If
> >> >>> not can
> >> >> you clarify the issue so I can raise with the AP team.
> >> >>>
> >> >> ath12k/WCN7850 supports EHT, but with NSS only 2. Here the AP
> >> >> requires NSS to be no less than 4, that is why EHT connection was disabled.
> >> >
> >> > Which field is requiring NSS of 4, I'm only seeing a maximum of 4, the
> >> Qualcomm windows driver will connect to the same AP, we had assumed that
> >> that ath12k would do the same.
> >> Basic EHT-MCS And Nss Set: 0x44444444
> >
> > My understanding of the spec is that there are maximum numbers of
> > streams though, are you saying the AP has to advertise 0x22222222
> > which would then prevent a 4x4 client (say an extender) from
> > connecting with 4 streams? I note that the Qualcomm windows driver for
> > Hamilton works with the AP and an Intel BE200 also works both of which
> > will be in at most 2x2
>
> Did you test Intel BE200 with the Windows driver? Johannes mentioned
> that ieee80211_verify_sta_eht_mcs_support() in mac80211 checks this so I
> would assume that iwlwifi also behaves like ath12k.
>
Yes, this is AP issue - hostapd fix required - advertise 0x11111 ...
In other case station < 4nss will drop to HE only.
BR
Janusz
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: wcn7850 issues
2024-09-03 9:57 ` Janusz Dziedzic
@ 2024-09-03 10:07 ` Johannes Berg
2024-09-03 10:09 ` Kalle Valo
1 sibling, 0 replies; 28+ messages in thread
From: Johannes Berg @ 2024-09-03 10:07 UTC (permalink / raw)
To: Janusz Dziedzic, Kalle Valo
Cc: david Atkins, Baochen Qiang, ath12k@lists.infradead.org,
linux-wireless
>
> Yes, this is AP issue - hostapd fix required - advertise 0x11111 ...
>
You probably don't even want 0x11111111, that would require all MCSes,
which some stations might not support.
Since some things are mandatory, I'm not sure I see a lot of value in
advertising anything non-zero, certainly not by default, and only set it
if specifically want to require something in the BSS that's _not_
already otherwise mandatory.
I mean, maybe you do want to require 4 NSS and all MCSes like the
0x44444444 does, so that regular clients cannot connect ;)
johannes
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: wcn7850 issues
2024-09-03 9:57 ` Janusz Dziedzic
2024-09-03 10:07 ` Johannes Berg
@ 2024-09-03 10:09 ` Kalle Valo
2024-09-03 21:15 ` david Atkins
1 sibling, 1 reply; 28+ messages in thread
From: Kalle Valo @ 2024-09-03 10:09 UTC (permalink / raw)
To: Janusz Dziedzic
Cc: david Atkins, Baochen Qiang, ath12k@lists.infradead.org,
linux-wireless
Janusz Dziedzic <janusz.dziedzic@gmail.com> writes:
> wt., 3 wrz 2024 o 09:47 Kalle Valo <kvalo@kernel.org> napisał(a):
>>
>> + linux-wireless
>>
>> david Atkins <david@3adesign.co.uk> writes:
>>
>> > ...
>> >> >>> Ext Tag: EHT Operation (802.11be D3.0)
>> >> >>> Ext Tag length: 8 (Tag len: 9)
>> >> >>> Ext Tag Number: EHT Operation (802.11be D3.0) (106)
>> >> >>> EHT Operation Parameters: 0x01, EHT Operation Information
>> >> Present
>> >> >>> .... ...1 = EHT Operation Information Present: True
>> >> >>> .... ..0. = Disabled Subchannel Bitmap Present: False
>> >> >>> .... .0.. = EHT Default PE Duration: False
>> >> >>> .... 0... = Group Addressed BU Indication Limit: False
>> >> >>> ..00 .... = Group Addressed BU Indication Exponent: 0
>> >> >>> 00.. .... = Reserved: 0x0
>> >> >>> Basic EHT-MCS And Nss Set: 0x44444444
>> >> >>> Control: 0x02, Channel Width: 80 MHz EHT BSS bandwidth
>> >> >>> .... .010 = Channel Width: 80 MHz EHT BSS bandwidth (2)
>> >> >>> 0000 0... = Reserved: 0x00
>> >> >>>
>> >> >>> Are you saying the ath12k driver does not support these features? If
>> >> >>> not can
>> >> >> you clarify the issue so I can raise with the AP team.
>> >> >>>
>> >> >> ath12k/WCN7850 supports EHT, but with NSS only 2. Here the AP
>> >> >> requires NSS to be no less than 4, that is why EHT connection was disabled.
>> >> >
>> >> > Which field is requiring NSS of 4, I'm only seeing a maximum of 4, the
>> >> Qualcomm windows driver will connect to the same AP, we had assumed that
>> >> that ath12k would do the same.
>> >> Basic EHT-MCS And Nss Set: 0x44444444
>> >
>> > My understanding of the spec is that there are maximum numbers of
>> > streams though, are you saying the AP has to advertise 0x22222222
>> > which would then prevent a 4x4 client (say an extender) from
>> > connecting with 4 streams? I note that the Qualcomm windows driver for
>> > Hamilton works with the AP and an Intel BE200 also works both of which
>> > will be in at most 2x2
>>
>> Did you test Intel BE200 with the Windows driver? Johannes mentioned
>> that ieee80211_verify_sta_eht_mcs_support() in mac80211 checks this so I
>> would assume that iwlwifi also behaves like ath12k.
>
> Yes, this is AP issue - hostapd fix required - advertise 0x11111 ...
> In other case station < 4nss will drop to HE only.
Thanks. And Johannes pointed out that you had even discussed about this
before:
https://lore.kernel.org/linux-wireless/CAFED-jk8pJheJEViESnE54f-K+JgRMiWoiCSa0GBt=RKaCn7sw@mail.gmail.com/
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
https://docs.kernel.org/process/submitting-patches.html
^ permalink raw reply [flat|nested] 28+ messages in thread
* RE: wcn7850 issues
2024-09-03 10:09 ` Kalle Valo
@ 2024-09-03 21:15 ` david Atkins
2024-09-04 5:08 ` Janusz Dziedzic
0 siblings, 1 reply; 28+ messages in thread
From: david Atkins @ 2024-09-03 21:15 UTC (permalink / raw)
To: Kalle Valo, Janusz Dziedzic
Cc: Baochen Qiang, ath12k@lists.infradead.org,
linux-wireless@vger.kernel.org
> > wt., 3 wrz 2024 o 09:47 Kalle Valo <kvalo@kernel.org> napisał(a):
> >>
> >> + linux-wireless
> >>
> >> david Atkins <david@3adesign.co.uk> writes:
> >>
> >> > ...
> >> >> >>> Ext Tag: EHT Operation (802.11be D3.0)
> >> >> >>> Ext Tag length: 8 (Tag len: 9)
> >> >> >>> Ext Tag Number: EHT Operation (802.11be D3.0) (106)
> >> >> >>> EHT Operation Parameters: 0x01, EHT Operation
> >> >> >>> Information
> >> >> Present
> >> >> >>> .... ...1 = EHT Operation Information Present: True
> >> >> >>> .... ..0. = Disabled Subchannel Bitmap Present: False
> >> >> >>> .... .0.. = EHT Default PE Duration: False
> >> >> >>> .... 0... = Group Addressed BU Indication Limit: False
> >> >> >>> ..00 .... = Group Addressed BU Indication Exponent: 0
> >> >> >>> 00.. .... = Reserved: 0x0
> >> >> >>> Basic EHT-MCS And Nss Set: 0x44444444
> >> >> >>> Control: 0x02, Channel Width: 80 MHz EHT BSS bandwidth
> >> >> >>> .... .010 = Channel Width: 80 MHz EHT BSS bandwidth (2)
> >> >> >>> 0000 0... = Reserved: 0x00
> >> >> >>>
> >> >> >>> Are you saying the ath12k driver does not support these
> >> >> >>> features? If not can
> >> >> >> you clarify the issue so I can raise with the AP team.
> >> >> >>>
> >> >> >> ath12k/WCN7850 supports EHT, but with NSS only 2. Here the AP
> >> >> >> requires NSS to be no less than 4, that is why EHT connection was
> disabled.
> >> >> >
> >> >> > Which field is requiring NSS of 4, I'm only seeing a maximum of
> >> >> > 4, the
> >> >> Qualcomm windows driver will connect to the same AP, we had
> >> >> assumed that that ath12k would do the same.
> >> >> Basic EHT-MCS And Nss Set: 0x44444444
> >> >
> >> > My understanding of the spec is that there are maximum numbers of
> >> > streams though, are you saying the AP has to advertise 0x22222222
> >> > which would then prevent a 4x4 client (say an extender) from
> >> > connecting with 4 streams? I note that the Qualcomm windows driver
> >> > for Hamilton works with the AP and an Intel BE200 also works both
> >> > of which will be in at most 2x2
> >>
> >> Did you test Intel BE200 with the Windows driver? Johannes mentioned
> >> that ieee80211_verify_sta_eht_mcs_support() in mac80211 checks this
> >> so I would assume that iwlwifi also behaves like ath12k.
> >
> > Yes, this is AP issue - hostapd fix required - advertise 0x11111 ...
> > In other case station < 4nss will drop to HE only.
>
> Thanks. And Johannes pointed out that you had even discussed about this
> before:
>
> https://lore.kernel.org/linux-wireless/CAFED-jk8pJheJEViESnE54f-
> K+JgRMiWoiCSa0GBt=RKaCn7sw@mail.gmail.com/
>
So this
Basic EHT-MCS And Nss Set: 0x44444444
Should be 0x11111111 ? and it defines the minimum number of streams needed to connect?
This the defines the max streams ?
Supported EHT-MCS and NSS Set
EHT-MCS Map (BW <= 80MHz): 0x444444
.... .... .... .... .... 0100 = Rx Max Nss That Supports EHT-MCS 0-9: 4
.... .... .... .... 0100 .... = Tx Max Nss That Supports EHT-MCS 0-9: 4
.... .... .... 0100 .... .... = Rx Max Nss That Supports EHT-MCS 10-11: 4
.... .... 0100 .... .... .... = Tx Max Nss That Supports EHT-MCS 10-11: 4
.... 0100 .... .... .... .... = Rx Max Nss That Supports EHT-MCS 12-13: 4
0100 .... .... .... .... .... = Tx Max Nss That Supports EHT-MCS 12-13: 4
david
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: wcn7850 issues
2024-09-03 21:15 ` david Atkins
@ 2024-09-04 5:08 ` Janusz Dziedzic
2024-09-04 6:04 ` david Atkins
0 siblings, 1 reply; 28+ messages in thread
From: Janusz Dziedzic @ 2024-09-04 5:08 UTC (permalink / raw)
To: david Atkins
Cc: Kalle Valo, Baochen Qiang, ath12k@lists.infradead.org,
linux-wireless@vger.kernel.org
wt., 3 wrz 2024 o 23:15 david Atkins <david@3adesign.co.uk> napisał(a):
>
> > > wt., 3 wrz 2024 o 09:47 Kalle Valo <kvalo@kernel.org> napisał(a):
> > >>
> > >> + linux-wireless
> > >>
> > >> david Atkins <david@3adesign.co.uk> writes:
> > >>
> > >> > ...
> > >> >> >>> Ext Tag: EHT Operation (802.11be D3.0)
> > >> >> >>> Ext Tag length: 8 (Tag len: 9)
> > >> >> >>> Ext Tag Number: EHT Operation (802.11be D3.0) (106)
> > >> >> >>> EHT Operation Parameters: 0x01, EHT Operation
> > >> >> >>> Information
> > >> >> Present
> > >> >> >>> .... ...1 = EHT Operation Information Present: True
> > >> >> >>> .... ..0. = Disabled Subchannel Bitmap Present: False
> > >> >> >>> .... .0.. = EHT Default PE Duration: False
> > >> >> >>> .... 0... = Group Addressed BU Indication Limit: False
> > >> >> >>> ..00 .... = Group Addressed BU Indication Exponent: 0
> > >> >> >>> 00.. .... = Reserved: 0x0
> > >> >> >>> Basic EHT-MCS And Nss Set: 0x44444444
> > >> >> >>> Control: 0x02, Channel Width: 80 MHz EHT BSS bandwidth
> > >> >> >>> .... .010 = Channel Width: 80 MHz EHT BSS bandwidth (2)
> > >> >> >>> 0000 0... = Reserved: 0x00
> > >> >> >>>
> > >> >> >>> Are you saying the ath12k driver does not support these
> > >> >> >>> features? If not can
> > >> >> >> you clarify the issue so I can raise with the AP team.
> > >> >> >>>
> > >> >> >> ath12k/WCN7850 supports EHT, but with NSS only 2. Here the AP
> > >> >> >> requires NSS to be no less than 4, that is why EHT connection was
> > disabled.
> > >> >> >
> > >> >> > Which field is requiring NSS of 4, I'm only seeing a maximum of
> > >> >> > 4, the
> > >> >> Qualcomm windows driver will connect to the same AP, we had
> > >> >> assumed that that ath12k would do the same.
> > >> >> Basic EHT-MCS And Nss Set: 0x44444444
> > >> >
> > >> > My understanding of the spec is that there are maximum numbers of
> > >> > streams though, are you saying the AP has to advertise 0x22222222
> > >> > which would then prevent a 4x4 client (say an extender) from
> > >> > connecting with 4 streams? I note that the Qualcomm windows driver
> > >> > for Hamilton works with the AP and an Intel BE200 also works both
> > >> > of which will be in at most 2x2
> > >>
> > >> Did you test Intel BE200 with the Windows driver? Johannes mentioned
> > >> that ieee80211_verify_sta_eht_mcs_support() in mac80211 checks this
> > >> so I would assume that iwlwifi also behaves like ath12k.
> > >
> > > Yes, this is AP issue - hostapd fix required - advertise 0x11111 ...
> > > In other case station < 4nss will drop to HE only.
> >
> > Thanks. And Johannes pointed out that you had even discussed about this
> > before:
> >
> > https://lore.kernel.org/linux-wireless/CAFED-jk8pJheJEViESnE54f-
> > K+JgRMiWoiCSa0GBt=RKaCn7sw@mail.gmail.com/
> >
>
> So this
>
> Basic EHT-MCS And Nss Set: 0x44444444
>
> Should be 0x11111111 ? and it defines the minimum number of streams needed to connect?
>
> This the defines the max streams ?
>
> Supported EHT-MCS and NSS Set
> EHT-MCS Map (BW <= 80MHz): 0x444444
> .... .... .... .... .... 0100 = Rx Max Nss That Supports EHT-MCS 0-9: 4
> .... .... .... .... 0100 .... = Tx Max Nss That Supports EHT-MCS 0-9: 4
> .... .... .... 0100 .... .... = Rx Max Nss That Supports EHT-MCS 10-11: 4
> .... .... 0100 .... .... .... = Tx Max Nss That Supports EHT-MCS 10-11: 4
> .... 0100 .... .... .... .... = Rx Max Nss That Supports EHT-MCS 12-13: 4
> 0100 .... .... .... .... .... = Tx Max Nss That Supports EHT-MCS 12-13: 4
>
You mix different things:
Supported EHT-MCS and NSS set vs Basic EHT-MCS And Nss Set
^ permalink raw reply [flat|nested] 28+ messages in thread
* RE: wcn7850 issues
2024-09-04 5:08 ` Janusz Dziedzic
@ 2024-09-04 6:04 ` david Atkins
2024-09-04 7:08 ` Janusz Dziedzic
0 siblings, 1 reply; 28+ messages in thread
From: david Atkins @ 2024-09-04 6:04 UTC (permalink / raw)
To: Janusz Dziedzic
Cc: Kalle Valo, Baochen Qiang, ath12k@lists.infradead.org,
linux-wireless@vger.kernel.org
> > > >> > ...
> > > >> >> >>> Ext Tag: EHT Operation (802.11be D3.0)
> > > >> >> >>> Ext Tag length: 8 (Tag len: 9)
> > > >> >> >>> Ext Tag Number: EHT Operation (802.11be D3.0) (106)
> > > >> >> >>> EHT Operation Parameters: 0x01, EHT Operation
> > > >> >> >>> Information
> > > >> >> Present
> > > >> >> >>> .... ...1 = EHT Operation Information Present: True
> > > >> >> >>> .... ..0. = Disabled Subchannel Bitmap Present: False
> > > >> >> >>> .... .0.. = EHT Default PE Duration: False
> > > >> >> >>> .... 0... = Group Addressed BU Indication Limit: False
> > > >> >> >>> ..00 .... = Group Addressed BU Indication Exponent: 0
> > > >> >> >>> 00.. .... = Reserved: 0x0
> > > >> >> >>> Basic EHT-MCS And Nss Set: 0x44444444
> > > >> >> >>> Control: 0x02, Channel Width: 80 MHz EHT BSS
> bandwidth
> > > >> >> >>> .... .010 = Channel Width: 80 MHz EHT BSS bandwidth
> (2)
> > > >> >> >>> 0000 0... = Reserved: 0x00
> > > >> >> >>>
> > > >> >> >>> Are you saying the ath12k driver does not support these
> > > >> >> >>> features? If not can
> > > >> >> >> you clarify the issue so I can raise with the AP team.
> > > >> >> >>>
> > > >> >> >> ath12k/WCN7850 supports EHT, but with NSS only 2. Here the
> > > >> >> >> AP requires NSS to be no less than 4, that is why EHT
> > > >> >> >> connection was
> > > disabled.
> > > >> >> >
> > > >> >> > Which field is requiring NSS of 4, I'm only seeing a maximum
> > > >> >> > of 4, the
> > > >> >> Qualcomm windows driver will connect to the same AP, we had
> > > >> >> assumed that that ath12k would do the same.
> > > >> >> Basic EHT-MCS And Nss Set: 0x44444444
> > > >> >
> > > >> > My understanding of the spec is that there are maximum numbers
> > > >> > of streams though, are you saying the AP has to advertise
> > > >> > 0x22222222 which would then prevent a 4x4 client (say an
> > > >> > extender) from connecting with 4 streams? I note that the
> > > >> > Qualcomm windows driver for Hamilton works with the AP and an
> > > >> > Intel BE200 also works both of which will be in at most 2x2
> > > >>
> > > >> Did you test Intel BE200 with the Windows driver? Johannes
> > > >> mentioned that ieee80211_verify_sta_eht_mcs_support() in mac80211
> > > >> checks this so I would assume that iwlwifi also behaves like ath12k.
> > > >
> > > > Yes, this is AP issue - hostapd fix required - advertise 0x11111 ...
> > > > In other case station < 4nss will drop to HE only.
> > >
> > > Thanks. And Johannes pointed out that you had even discussed about
> > > this
> > > before:
> > >
> > > https://lore.kernel.org/linux-wireless/CAFED-jk8pJheJEViESnE54f-
> > > K+JgRMiWoiCSa0GBt=RKaCn7sw@mail.gmail.com/
> > >
> >
> > So this
> >
> > Basic EHT-MCS And Nss Set: 0x44444444
> >
> > Should be 0x11111111 ? and it defines the minimum number of streams
> needed to connect?
> >
> > This the defines the max streams ?
> >
> > Supported EHT-MCS and NSS Set
> > EHT-MCS Map (BW <= 80MHz): 0x444444
> > .... .... .... .... .... 0100 = Rx Max Nss That Supports EHT-MCS 0-9:
> 4
> > .... .... .... .... 0100 .... = Tx Max Nss That Supports EHT-MCS 0-9: 4
> > .... .... .... 0100 .... .... = Rx Max Nss That Supports EHT-MCS 10-
> 11: 4
> > .... .... 0100 .... .... .... = Tx Max Nss That Supports EHT-MCS 10-
> 11: 4
> > .... 0100 .... .... .... .... = Rx Max Nss That Supports EHT-MCS 12-
> 13: 4
> > 0100 .... .... .... .... .... = Tx Max Nss That
> > Supports EHT-MCS 12-13: 4
> >
> You mix different things:
>
> Supported EHT-MCS and NSS set vs Basic EHT-MCS And Nss Set
So the basic set is the minimum?
David
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: wcn7850 issues
2024-09-04 6:04 ` david Atkins
@ 2024-09-04 7:08 ` Janusz Dziedzic
0 siblings, 0 replies; 28+ messages in thread
From: Janusz Dziedzic @ 2024-09-04 7:08 UTC (permalink / raw)
To: david Atkins
Cc: Kalle Valo, Baochen Qiang, ath12k@lists.infradead.org,
linux-wireless@vger.kernel.org
śr., 4 wrz 2024 o 08:04 david Atkins <david@3adesign.co.uk> napisał(a):
>
> > > > >> > ...
> > > > >> >> >>> Ext Tag: EHT Operation (802.11be D3.0)
> > > > >> >> >>> Ext Tag length: 8 (Tag len: 9)
> > > > >> >> >>> Ext Tag Number: EHT Operation (802.11be D3.0) (106)
> > > > >> >> >>> EHT Operation Parameters: 0x01, EHT Operation
> > > > >> >> >>> Information
> > > > >> >> Present
> > > > >> >> >>> .... ...1 = EHT Operation Information Present: True
> > > > >> >> >>> .... ..0. = Disabled Subchannel Bitmap Present: False
> > > > >> >> >>> .... .0.. = EHT Default PE Duration: False
> > > > >> >> >>> .... 0... = Group Addressed BU Indication Limit: False
> > > > >> >> >>> ..00 .... = Group Addressed BU Indication Exponent: 0
> > > > >> >> >>> 00.. .... = Reserved: 0x0
> > > > >> >> >>> Basic EHT-MCS And Nss Set: 0x44444444
> > > > >> >> >>> Control: 0x02, Channel Width: 80 MHz EHT BSS
> > bandwidth
> > > > >> >> >>> .... .010 = Channel Width: 80 MHz EHT BSS bandwidth
> > (2)
> > > > >> >> >>> 0000 0... = Reserved: 0x00
> > > > >> >> >>>
> > > > >> >> >>> Are you saying the ath12k driver does not support these
> > > > >> >> >>> features? If not can
> > > > >> >> >> you clarify the issue so I can raise with the AP team.
> > > > >> >> >>>
> > > > >> >> >> ath12k/WCN7850 supports EHT, but with NSS only 2. Here the
> > > > >> >> >> AP requires NSS to be no less than 4, that is why EHT
> > > > >> >> >> connection was
> > > > disabled.
> > > > >> >> >
> > > > >> >> > Which field is requiring NSS of 4, I'm only seeing a maximum
> > > > >> >> > of 4, the
> > > > >> >> Qualcomm windows driver will connect to the same AP, we had
> > > > >> >> assumed that that ath12k would do the same.
> > > > >> >> Basic EHT-MCS And Nss Set: 0x44444444
> > > > >> >
> > > > >> > My understanding of the spec is that there are maximum numbers
> > > > >> > of streams though, are you saying the AP has to advertise
> > > > >> > 0x22222222 which would then prevent a 4x4 client (say an
> > > > >> > extender) from connecting with 4 streams? I note that the
> > > > >> > Qualcomm windows driver for Hamilton works with the AP and an
> > > > >> > Intel BE200 also works both of which will be in at most 2x2
> > > > >>
> > > > >> Did you test Intel BE200 with the Windows driver? Johannes
> > > > >> mentioned that ieee80211_verify_sta_eht_mcs_support() in mac80211
> > > > >> checks this so I would assume that iwlwifi also behaves like ath12k.
> > > > >
> > > > > Yes, this is AP issue - hostapd fix required - advertise 0x11111 ...
> > > > > In other case station < 4nss will drop to HE only.
> > > >
> > > > Thanks. And Johannes pointed out that you had even discussed about
> > > > this
> > > > before:
> > > >
> > > > https://lore.kernel.org/linux-wireless/CAFED-jk8pJheJEViESnE54f-
> > > > K+JgRMiWoiCSa0GBt=RKaCn7sw@mail.gmail.com/
> > > >
> > >
> > > So this
> > >
> > > Basic EHT-MCS And Nss Set: 0x44444444
> > >
> > > Should be 0x11111111 ? and it defines the minimum number of streams
> > needed to connect?
> > >
> > > This the defines the max streams ?
> > >
> > > Supported EHT-MCS and NSS Set
> > > EHT-MCS Map (BW <= 80MHz): 0x444444
> > > .... .... .... .... .... 0100 = Rx Max Nss That Supports EHT-MCS 0-9:
> > 4
> > > .... .... .... .... 0100 .... = Tx Max Nss That Supports EHT-MCS 0-9: 4
> > > .... .... .... 0100 .... .... = Rx Max Nss That Supports EHT-MCS 10-
> > 11: 4
> > > .... .... 0100 .... .... .... = Tx Max Nss That Supports EHT-MCS 10-
> > 11: 4
> > > .... 0100 .... .... .... .... = Rx Max Nss That Supports EHT-MCS 12-
> > 13: 4
> > > 0100 .... .... .... .... .... = Tx Max Nss That
> > > Supports EHT-MCS 12-13: 4
> > >
> > You mix different things:
> >
> > Supported EHT-MCS and NSS set vs Basic EHT-MCS And Nss Set
>
> So the basic set is the minimum?
>
linux mac80211 check it as minimum - if not pass disable client EHT
OS hostapd set is as 0x00000011 but there is some TODO - so maybe
someone else should describe it more :)
https://w1.fi/cgit/hostap/tree/src/ap/ieee802_11_eht.c#n235
So, eg. OpenWrt/main EHT AP on mt7996e use 0x00000011, and Intel
BE200/WCN7850 connect using EHT
BR
Janusz
^ permalink raw reply [flat|nested] 28+ messages in thread
end of thread, other threads:[~2024-09-04 7:09 UTC | newest]
Thread overview: 28+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <LO0P123MB4057D6C2F6FEFF335B30EE7CD6BF2@LO0P123MB4057.GBRP123.PROD.OUTLOOK.COM>
2024-08-06 8:06 ` wcn7850 issues david Atkins
2024-08-13 13:20 ` david Atkins
2024-08-14 7:28 ` Kang Yang
2024-08-14 8:46 ` Lingbo Kong
2024-08-14 10:33 ` Baochen Qiang
2024-08-14 16:58 ` david Atkins
2024-08-14 10:42 ` Baochen Qiang
2024-08-14 17:00 ` david Atkins
2024-08-14 20:38 ` david Atkins
2024-08-15 2:15 ` Baochen Qiang
2024-08-16 12:23 ` david Atkins
2024-08-19 2:33 ` Baochen Qiang
2024-08-19 10:55 ` david Atkins
2024-08-30 5:55 ` david Atkins
2024-08-30 7:08 ` Baochen Qiang
2024-09-01 7:39 ` david Atkins
2024-09-02 1:56 ` Baochen Qiang
2024-09-02 6:03 ` david Atkins
2024-09-02 6:20 ` Baochen Qiang
2024-09-03 6:29 ` david Atkins
2024-09-03 7:47 ` Kalle Valo
2024-09-03 9:57 ` Janusz Dziedzic
2024-09-03 10:07 ` Johannes Berg
2024-09-03 10:09 ` Kalle Valo
2024-09-03 21:15 ` david Atkins
2024-09-04 5:08 ` Janusz Dziedzic
2024-09-04 6:04 ` david Atkins
2024-09-04 7:08 ` Janusz Dziedzic
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox