On Tue, Jan 5, 2010 at 1:25 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Mon, 2010-01-04 at 11:28 -0500, Luis R. Rodriguez wrote: > >> +/** >> + * regulatory_hint_disconnect - informs all devices have been >> disconneted > > disconnected > >> + * >> + * Regulotory rules can be enhanced further upon scanning and upon > > Regulatory > >> + * connection to an AP. These rules become stale if we disconnect >> + * and go to another country, whether or not we suspend and resume. >> + * If we suspend, go to another country and resume we'll >> automatically >> + * get disconnected shortly after resuming and things will be reset >> as well. >> + * This routine is a helper to restore regulatory settings to how >> they were >> + * prior to our first connect attempt. This includes ignoring country >> IE and >> + * beacon regulatory hints. The ieee80211_regdom module parameter >> will always >> + * be respected but if a user had set the regulatory domain that will >> take >> + * precedence. >> + * >> + * Must be called from process context and hold the cfg80211_mutex. >> + */ > > However, I don't quite understand why we need this function. We already > tell cfg80211 about disconnect events or requests, can't it call some > regulatory update when either of those two happen? Sure, hence the RFC, can you point me to those events? Luis -- 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
