> >> "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. Thanks, Bing > > Thanks, > Ben -- 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
