On 06/13/2013 10:30 AM, John W. Linville wrote:
On Wed, Jun 12, 2013 at 12:01:23PM -0700, Bing Zhao wrote:
"iw reg set XX" or "country_code=XX" in hostapd.conf is a *user* hint.
What we need here is a *driver* hint. Furthermore, with a driver
regulatory hint, the passive-scan and no-ibss flags are cleared so we
can start AP with hostapd on 5G band.
So it's a driver hint which is coming from user space via a module
parameter. IMHO you are abusing interfaces here. Is there any better way
to solve your problem?
It would be nice to have some way to do this for ath9k and other NICs
as well. Best I could come up with is a similar hack for ath9k.
I think part of the problem is that this config info needs to be
available very early in the module loading/init logic, so it's
too late to be configured using 'iw' or similar.
Exactly. regulatory_hint () needs to be called right after wiphy registration.
It does seem a bit ugly. But if Marvell wants it, I don't see any
"regulatory" argument to disallow something like this.
Does anyone have a better suggestion for a user interface for such
a feature?
Maybe a global over-ride module-option in cfg80211 module so that
we wouldn't have to have an individual module-option hack for
each driver?
But, then again, maybe we would still want individual driver
config options....
Thanks,
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
