On Thu, Jun 13, 2013 at 10:33 AM, Paul Stewart <pstew@xxxxxxxxxxxx> wrote: > On Thu, Jun 13, 2013 at 10:30 AM, John W. Linville > <linville@xxxxxxxxxxxxx> 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? > > > The only (slightly) cleaner thing I could think of is a module > parameter to cfg80211 so all drivers in the system would be made aware > of the boot-time regulatory domain. Oh, wait. That exists in the 'ieee80211_regdom' parameter to cfg80211. You should use that. :-) >> >> >> John >> -- >> John W. Linville Someday the world will need a hero, and you >> linville@xxxxxxxxxxxxx might be all we have. Be ready. -- 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
