linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jouni Malinen <j@w1.fi>
To: Ilan Peer <ilan.peer@intel.com>
Cc: linux-wireless@vger.kernel.org, mcgrof@do-not-panic.com,
	David Spinadel <david.spinadel@intel.com>
Subject: Re: [PATCH 3/3] [RFC] cfg80211: Enable GO operation on additional channels
Date: Mon, 8 Jul 2013 13:04:18 +0300	[thread overview]
Message-ID: <20130708100418.GA10670@w1.fi> (raw)
In-Reply-To: <1372768095-26053-4-git-send-email-ilan.peer@intel.com>

On Tue, Jul 02, 2013 at 03:28:15PM +0300, Ilan Peer wrote:
> Allow GO operation on a channel marked with
> IEEE80211_CHAN_INDOOR_ONLY or IEEE80211_CHAN_GO_CONCURRENT
> iff there is an active station interface that is associated to
> an AP operating on this channel.
> 
> Note that this is a permissive approach to the FCC definitions,
> that require a clear assessment that either the platform device
> is an indoor device, or the device operating the AP is an indoor
> device, i.e., AC powered.
> It is assumed that these restrictions are enforced by user space.

The introduction in 0/3 mentioned DFS, but I did not see it being
addressed in any of the actual changes. Is this only for indoors vs.
outdoors?

> Furthermore, it is assumed, that if the conditions that allowed for
> the operation of the GO on such a channel change, it is the
> responsibility of user space to evacuate the GO from the channel.

Do you have plans or changes to address this? I'd assume wpa_supplicant
could stop the group on channel list changes, but I don't think it does
that currently.

-- 
Jouni Malinen                                            PGP id EFC895FA

  reply	other threads:[~2013-07-08 10:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02 12:28 [PATCH 0/3] Enable additional channels for GO Ilan Peer
2013-07-02 12:28 ` [PATCH 1/3] [RFC] cfg80211: Add indoor only and GO concurrent channel attributes Ilan Peer
2013-07-08 21:45   ` Luis R. Rodriguez
2013-07-10 10:43     ` Peer, Ilan
2013-07-16 20:43       ` Luis R. Rodriguez
2013-07-17 18:47         ` Peer, Ilan
2013-07-18 23:30           ` Luis R. Rodriguez
2013-07-02 12:28 ` [PATCH 2/3] [RFC] cfg80211: Add Kconfig option for cellular BS hints Ilan Peer
2013-07-02 13:55   ` Arend van Spriel
2013-07-02 14:00     ` Johannes Berg
2013-07-02 14:13       ` Arend van Spriel
2013-07-02 12:28 ` [PATCH 3/3] [RFC] cfg80211: Enable GO operation on additional channels Ilan Peer
2013-07-08 10:04   ` Jouni Malinen [this message]
2013-07-09  5:40     ` Peer, Ilan
2013-07-08 22:04   ` Luis R. Rodriguez
2013-07-10 10:47     ` Peer, Ilan
2013-07-16 20:57       ` Luis R. Rodriguez
2013-07-17 19:15         ` Peer, Ilan
2013-07-18 23:34           ` Luis R. Rodriguez
2013-10-04 17:38             ` Luis R. Rodriguez
2013-10-06 11:28               ` Peer, Ilan

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=20130708100418.GA10670@w1.fi \
    --to=j@w1.fi \
    --cc=david.spinadel@intel.com \
    --cc=ilan.peer@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@do-not-panic.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).