On 03/02/2022 23:30, Johannes Berg wrote:
On Tue, 2021-10-12 at 12:24 +0200, Nicolas Cavallari wrote:
This patch somehow appears to break ath9k's eeprom hints and restrict
it to the world regulatory domain on v5.12.10.
ath9k calls wiphy_apply_custom_regulatory() with its own kind of world
regulatory domain, before it decodes hints from the eeprom and uses
regulatory_hint() to request a specific alpha2.
With this patch, applying the hint fails because wiphy->regd is already set.
If i revert this patch, ath9k works again.
Hm. It stands to reason that perhaps ath9k should call
wiphy_apply_custom_regulatory(NULL) (if that's possible) to reset the
knowledge of having a custom regulatory domain, before requesting the
correct one be applied by cfg80211 (and possibly even crda userspace).
wiphy_apply_custom_regulatory(NULL) is apparently not possible.
The regulatory code is still a black box to me...
