On Wed, Nov 13, 2013 at 10:22:18PM +0100, Johannes Berg wrote: > On Wed, 2013-11-13 at 19:12 +0100, Luis R. Rodriguez wrote: > > This quiesces devices when appropriate to ensure that > > regulatory domain updates take effect and avoid having > > devices initiate radiation when they should not. > > I'm not really sure this makes sense. > > If we're staying connected, how can we be moving far enough to go > through regulatory domains to have totally different rules? Don't think of what makes sense, think of the corner cases that could happen here, such as plugging in a card that disagrees with regulatory settings, and creates a conflict on DFS regions. One example might be someone plugging in a USB 802.11 card programmed for JP in say a FR 802.11 AP, assuming the AP had the USB 802.11 driver. Another example may be if a user provides an input with say 'iw reg set JP' on a FR AP. In such cases we want to stop IR, even if the user was dumb, we'd be respecting the regulatory settings, as silly as they may be. Another more resonable case may be one AP creating a secondary wdev as a STA, consider a P2P GO, with a P2P STA on another channel and lets assume the P2P GO is misprogrammed for JP but the STA wdev picks up association with an AP from FR. > (Also, probably best to squash patches 2 and 3, 2 is pointless by itself > and the code move is obvious with this patch) OK. 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
