On 8/20/24 12:05 PM, James Prestwood wrote:
Hi,
I'm using the latest firmware for ath11k [1], WCN6855 hw2.1, and so
far I guess we've been lucky that the regdom has always been set to
00, which apparently allows 6ghz. But recently we have seen the regdom
get set to US and it then has 6ghz disabled:
phy#0 (self-managed)
country US: DFS-FCC
(2402 - 2472 @ 40), (6, 30), (N/A)
(5170 - 5250 @ 80), (6, 24), (N/A), AUTO-BW
(5250 - 5330 @ 80), (6, 24), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (6, 24), (0 ms), DFS, AUTO-BW
(5735 - 5855 @ 80), (6, 30), (N/A), AUTO-BW
(5855 - 5925 @ 40), (6, 30), (N/A), NO-OUTDOOR, AUTO-BW
I have updated the regulatory.db from wireless-regdb.git as well, and
updated all the firmware (including regdb.bin) to the latest
available. According to the wireless-regdb tree, US: DFS-FCC _should_
allow 6ghz [2]:
Is there something I'm missing here?
Thanks,
James
[1]
https://git.codelinaro.org/clo/ath-firmware/ath11k-firmware/-/tree/main/WCN6855?ref_type=heads
[2]
https://git.kernel.org/pub/scm/linux/kernel/git/wens/wireless-regdb.git/tree/db.txt#n1895
It appears the issue was actually at the driver level. Updating to
kernel 6.8 seems to reflect the correct regulatory domain rules, at
least with US: DFS-FCC. Might have something to do a commit [1], which
was sent a few months after 6.2 was released, which is what I've been
using prior.
I now see the expected frequency ranges for US: DFS-FCC:
phy#0 (self-managed)
country US: DFS-FCC
(2402 - 2472 @ 40), (6, 30), (N/A)
(5170 - 5250 @ 80), (6, 24), (N/A), AUTO-BW
(5250 - 5330 @ 80), (6, 24), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (6, 24), (0 ms), DFS, AUTO-BW
(5735 - 5855 @ 80), (6, 30), (N/A), AUTO-BW
(5855 - 5925 @ 40), (6, 30), (N/A), NO-OUTDOOR, AUTO-BW
(5925 - 7125 @ 160), (N/A, 24), (N/A), NO-OUTDOOR, AUTO-BW
[1] https://www.spinics.net/lists/linux-wireless/msg236203.html
