From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: janusz.dziedzic@tieto.com, j@w1.fi, sunitb@qca.qualcomm.com,
rsunki@qca.qualcomm.com, linux-wireless@vger.kernel.org
Subject: Re: [RFC 3/5] cfg80211: add regulatory quiescing support
Date: Thu, 14 Nov 2013 15:44:46 +0100 [thread overview]
Message-ID: <1384440286.13941.27.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20131114141105.GB19070@garbanzo.do-not-panic.com> (sfid-20131114_150029_534220_D0403B29)
On Thu, 2013-11-14 at 06:11 -0800, Luis R. Rodriguez wrote:
> 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.
Think of the other way around, such as plugging in a stupid USB NIC just
to see if it works - and suddenly finding your 5 GHz connection broken
because that USB NIC said it really needed some stupid country with 2.4
only. I'm not convinced.
johannes
next prev parent reply other threads:[~2013-11-14 14:44 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 18:12 [RFC 0/5] cfg80211: regulatory quiescing and exporting DFS regions Luis R. Rodriguez
2013-11-13 18:12 ` [RFC 1/5] cfg80211: pass the wdev on the country IE regulatory hint Luis R. Rodriguez
2013-11-13 21:20 ` Johannes Berg
2013-11-14 14:05 ` Luis R. Rodriguez
2013-11-14 14:02 ` Johannes Berg
2013-11-14 15:12 ` Luis R. Rodriguez
2013-11-14 15:05 ` Johannes Berg
2013-11-14 15:21 ` Luis R. Rodriguez
2013-11-15 16:28 ` Luis R. Rodriguez
2013-11-13 18:12 ` [RFC 2/5] cfg80211: make cfg80211_leave_all() available outside of sysfs Luis R. Rodriguez
2013-11-13 18:12 ` [RFC 3/5] cfg80211: add regulatory quiescing support Luis R. Rodriguez
2013-11-13 21:22 ` Johannes Berg
2013-11-14 14:11 ` Luis R. Rodriguez
2013-11-14 14:44 ` Johannes Berg [this message]
2013-11-14 15:18 ` Luis R. Rodriguez
2013-11-25 15:59 ` Johannes Berg
2014-01-24 23:35 ` Luis R. Rodriguez
2014-01-24 23:37 ` Johannes Berg
2013-11-25 15:59 ` Johannes Berg
2013-11-13 18:12 ` [RFC 4/5] cfg80211: add DFS region capability support Luis R. Rodriguez
2013-11-13 21:28 ` Johannes Berg
2013-11-14 14:31 ` Luis R. Rodriguez
2013-11-14 14:48 ` Johannes Berg
2013-11-14 15:33 ` Luis R. Rodriguez
2013-11-14 15:29 ` Johannes Berg
2013-11-14 15:34 ` Luis R. Rodriguez
2013-11-14 16:13 ` Simon Wunderlich
2013-11-15 12:05 ` Luis R. Rodriguez
2013-11-13 18:12 ` [RFC 5/5] cfg80211: DFS check dfs_region before usage Luis R. Rodriguez
2013-11-13 21:29 ` Johannes Berg
2013-11-14 10:15 ` Janusz Dziedzic
2013-11-14 11:52 ` Janusz Dziedzic
2013-11-14 14:46 ` Luis R. Rodriguez
2013-11-15 9:37 ` Janusz Dziedzic
2013-11-15 12:01 ` Luis R. Rodriguez
2013-11-14 14:35 ` Luis R. Rodriguez
2013-11-14 14:33 ` Luis R. Rodriguez
2013-11-13 18:48 ` [RFC 0/5] cfg80211: regulatory quiescing and exporting DFS regions Johannes Berg
2013-11-13 18:57 ` Luis R. Rodriguez
2013-11-13 19:12 ` Johannes Berg
2013-11-13 19:13 ` Johannes Berg
2013-11-14 14:49 ` Luis R. Rodriguez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1384440286.13941.27.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=j@w1.fi \
--cc=janusz.dziedzic@tieto.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=rsunki@qca.qualcomm.com \
--cc=sunitb@qca.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).