On Mon, Sep 01, 2025 at 09:16:16AM +0100, Stuart Henderson wrote: > I might be wrong but I think with many of the modern wlan interfaces, > this is controlled by the firmware rather than the net80211 layer.. > > I think _probably_ the table you're looking at is mainly there for > hostap.
The regdomain code is only used by the ath(4) driver. Updating regdomain.c would be an entirely pointless effort without also somehow adding support to the drivers people are actually using today. But even if that work was already done, I doubt anything would be different. Modern devices enforce various restrictions in firmware and don't allow drivers to control any of this at a fine-grained level. We can mostly just tell firmware which country we believe we're in (and usually set this to the "world" domain). Firmware will do its own internal detection and send us an event when it believes it knows which country it is running in. Some devices only load firmware signed by the vendor to avoid attempts at tamparing with any of this. So the question is really what do you hope to gain from having this feature implemented? You have phrased your request in terms of a proposed solution to some unexplained problem. What do you really need?
