From: Johannes Berg <johannes@sipsolutions.net>
To: "Peer, Ilan" <ilan.peer@intel.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"wireless-regdb@lists.infradead.org"
<wireless-regdb@lists.infradead.org>
Subject: Re: [PATCH v3 3/6] cfg80211: Enable GO operation on additional channels
Date: Mon, 03 Feb 2014 13:46:52 +0100 [thread overview]
Message-ID: <1391431612.4488.13.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CB3B3D4774441E42AA3EA0E1BA8230A0333705C1@HASMSX106.ger.corp.intel.com>
On Sun, 2014-02-02 at 19:20 +0000, Peer, Ilan wrote:
> I do not think that this will be needed, as current wpa_supplicant
> logic is not aware of the GO_CONCURRENT and INDOOR_ONLY flags (leaving
> them ignored) and does not allow instantiating an AP/GO on channels
> marked with NO_IR. In addition as this feature must be enabled under
> CONFIG_ONUS, I expect that whoever uses it uses know what's is doing.
Ok, thanks for the clarification. I wasn't sure how existing wpa_s
versions would treat this.
> Such logic might be needed if kernel enforces regulatory compliance
> after the GO_CONCURRENT relaxation conditions are no longer met
> (station interface leaves the channel), where if such a case is true,
> it would be appropriate to add an indication to the kernel telling it
> that user space knows what it's doing, so the kernel will not do any
> quiescing logic (similar to what Luis suggested).
I'm not convinced that is necessary - the "quiescing" would be good I
suppose, but there should be plenty of time before it for userspace to
request an appropriate CSA so I don't think any additional flag is
needed.
Assuming we're talking about the same scenario? I guess it should be
like this:
- STA connected to AP on an "additional" channel
- GO operating on the same channel
- AP starts to advertise CSA
- wpa_s will request CSA for GO as well
- all will be fine
If wpa_s is broken, then at the time that the CSA actually kicks in the
GO would be stopped, since it didn't switch channel, but I don't think
there's a need for any additional flags.
johannes
next prev parent reply other threads:[~2014-02-03 12:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 10:21 [PATCH v3 0/6] Enable additional channels for use Ilan Peer
2014-01-27 10:21 ` [PATCH v3 1/6] cfg80211: Add indoor only and GO concurrent channel attributes Ilan Peer
2014-02-18 22:49 ` Luis R. Rodriguez
2014-02-19 14:44 ` Peer, Ilan
2014-01-27 10:21 ` [PATCH v3 2/6] cfg80211: Add Kconfig option for cellular BS hints Ilan Peer
2014-02-18 22:59 ` Luis R. Rodriguez
2014-01-27 10:21 ` [PATCH v3 3/6] cfg80211: Enable GO operation on additional channels Ilan Peer
2014-01-31 14:11 ` Johannes Berg
2014-02-02 19:20 ` Peer, Ilan
2014-02-03 12:46 ` Johannes Berg [this message]
2014-02-03 13:24 ` Peer, Ilan
2014-02-18 23:38 ` Luis R. Rodriguez
2014-02-19 14:52 ` Peer, Ilan
2014-02-19 15:47 ` Luis R. Rodriguez
2014-02-20 7:31 ` Peer, Ilan
2014-01-27 10:21 ` [PATCH v3 4/6] cfg80211: Add an option to hint indoor operation Ilan Peer
2014-01-31 14:13 ` Johannes Berg
2014-02-03 11:14 ` Ilan Peer
2014-02-19 0:07 ` Luis R. Rodriguez
2014-02-19 15:18 ` Peer, Ilan
2014-01-27 10:21 ` [PATCH v3 5/6] cfg80211: Enable GO operation on indoor channels Ilan Peer
2014-02-19 0:10 ` Luis R. Rodriguez
2014-01-27 10:21 ` [PATCH v3 6/6] mac80211: Enable initiating radiation " Ilan Peer
2014-02-19 0:15 ` Luis R. Rodriguez
2014-02-19 15:28 ` Peer, Ilan
2014-02-19 16:03 ` Luis R. Rodriguez
2014-02-20 7:58 ` Peer, Ilan
2014-02-21 23:31 ` Luis R. Rodriguez
2014-02-22 18:55 ` Peer, Ilan
2014-02-22 20:22 ` Luis R. Rodriguez
2014-02-23 7:23 ` Peer, Ilan
2014-02-23 9:43 ` Luis R. Rodriguez
2014-01-27 10:24 ` [PATCH v3 0/6] Enable additional channels for use Peer, Ilan
2014-02-09 16:06 ` Peer, Ilan
2014-02-18 22:17 ` Luis R. Rodriguez
2014-02-18 22:18 ` Luis R. Rodriguez
-- strict thread matches above, loose matches on Subject: below --
2013-12-03 19:16 [PATCH v2 3/6] cfg80211: Enable GO operation on additional channels Ilan Peer
2013-12-05 13:57 ` [PATCH v3 " Ilan Peer
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=1391431612.4488.13.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ilan.peer@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wireless-regdb@lists.infradead.org \
/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).