[PATCH] Revert "ath: add support for special 0x0 regulatory domain"

Jouni Malinen jkmalinen at gmail.com
Fri Oct 30 03:20:30 EDT 2020

On Thu, Oct 29, 2020 at 4:06 PM Félix Sipma <felix+kernel at gueux.org> wrote:
> I made a detailed report, with dmesg outputs of different
> kernel/firmware-atheros and wireless-regdb combinations at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970679

So the issue is in not being able to operate an AP on the 5 GHz band?
That sounds like the expected behavior for any device that has not
been calibrated and provisioned for a specific country where
regulatory rules allow operation on the 5 GHz band. I understand that
this may look like a regression since the commit removed
functionality, but it feels like a bug fix to me since that
functionality should not have been enabled by default in the first
place. The goal here is to avoid inappropriate operation on the band
without explicit configuration to enable such operation. In AP
devices, the device should have been provisioned for a specific
country to be able to enforce the correct frequency range
restrictions. The safe default for a device that does not have such
explicit configuration within the WLAN component itself is to use the
world roaming mode which prevents initialization of radiation (i.e.,
does not allow AP mode to be started but allows station mode operation
to connect to an already started AP) on the 5 GHz band.

- Jouni

More information about the ath10k mailing list