From: Johannes Berg <johannes@sipsolutions.net>
To: Adrian Chadd <adrian.chadd@gmail.com>
Cc: Victor Goldenshtein <victorg@ti.com>,
Michal Kazior <michal.kazior@tieto.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"kgiori@qca.qualcomm.com" <kgiori@qca.qualcomm.com>,
"mcgrof@frijolero.org" <mcgrof@frijolero.org>,
"zefir.kurtisi@neratec.com" <zefir.kurtisi@neratec.com>,
"j@w1.fi" <j@w1.fi>, "coelho@ti.com" <coelho@ti.com>,
"igalc@ti.com" <igalc@ti.com>, "nbd@nbd.name" <nbd@nbd.name>,
"simon.wunderlich@s2003.tu-chemnitz.de"
<simon.wunderlich@s2003.tu-chemnitz.de>
Subject: Re: [PATCH v4 5/6] nl80211/cfg80211: add ap channel switch command
Date: Thu, 01 Nov 2012 20:32:00 +0100 [thread overview]
Message-ID: <1351798320.17469.1.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CAJ-Vmom5CrnETTCzaf=fw4Unpxh940KCpbh5D=f8PoeTZUXNiA@mail.gmail.com> (sfid-20121101_181601_259924_BD2A03DE)
On Thu, 2012-11-01 at 10:15 -0700, Adrian Chadd wrote:
> On 1 November 2012 00:54, Victor Goldenshtein <victorg@ti.com> wrote:
>
> > If the driver/device supports MR only on a SC - means it doesn't supports
> > channel switch in MR, so basically the radar detection event triggers AP
> > channel switch which fails (with this new check) and the AP shut down.
> > Of course there are possible driver specific workarounds (as you mentioned
> > above) but these are not part of this series.
> >
> > Just for interest's sake, what is the use case having two APs on the same
> > channel?
>
> One interface _just_ doing DFS/spectral/etc, and not hampered by
> trying to do TX/RX.
Or maybe just multi-BSSID use cases?!
johannes
next prev parent reply other threads:[~2012-11-01 19:31 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 14:48 [PATCH v4 0/6] nl/cfg/mac80211: add DFS master ability Victor Goldenshtein
2012-10-14 14:48 ` [PATCH v4 1/6] nl80211/cfg80211: add radar detection command/event Victor Goldenshtein
2012-10-16 19:01 ` Johannes Berg
2012-10-17 16:20 ` Zefir Kurtisi
2012-10-17 16:23 ` Johannes Berg
2012-10-21 16:40 ` Victor Goldenshtein
2012-10-22 12:55 ` Johannes Berg
2012-11-01 7:54 ` Victor Goldenshtein
2012-11-05 15:21 ` Johannes Berg
2012-11-13 15:04 ` Victor Goldenshtein
2012-11-13 18:05 ` Simon Wunderlich
2012-11-20 15:14 ` Victor Goldenshtein
2012-11-26 10:52 ` Johannes Berg
2012-11-14 11:19 ` Johannes Berg
2012-11-20 15:15 ` Victor Goldenshtein
2012-11-14 12:32 ` Michal Kazior
2012-11-14 12:38 ` Johannes Berg
2012-11-20 15:15 ` Victor Goldenshtein
2012-11-26 10:51 ` Johannes Berg
2012-10-14 14:48 ` [PATCH v4 2/6] mac80211: " Victor Goldenshtein
2012-10-14 14:48 ` [PATCH v4 3/6] nl80211/cfg80211: add ability to enable TX on op-channel Victor Goldenshtein
2012-10-14 14:48 ` [PATCH v4 4/6] mac80211: " Victor Goldenshtein
2012-10-16 19:03 ` Johannes Berg
2012-10-21 16:40 ` Victor Goldenshtein
2012-10-14 14:48 ` [PATCH v4 5/6] nl80211/cfg80211: add ap channel switch command Victor Goldenshtein
2012-10-16 19:06 ` Johannes Berg
2012-10-21 16:40 ` Victor Goldenshtein
2012-10-22 12:52 ` Johannes Berg
2012-11-01 7:54 ` Victor Goldenshtein
2012-11-05 15:27 ` Johannes Berg
2012-11-13 15:04 ` Victor Goldenshtein
2012-10-23 6:20 ` Michal Kazior
2012-11-01 7:54 ` Victor Goldenshtein
2012-11-01 17:15 ` Adrian Chadd
2012-11-01 19:32 ` Johannes Berg [this message]
2012-11-05 15:29 ` Johannes Berg
2012-11-13 15:04 ` Victor Goldenshtein
2012-10-14 14:48 ` [PATCH v4 6/6] mac80211: add ap channel switch command/event Victor Goldenshtein
2012-10-16 19:07 ` Johannes Berg
2012-10-21 16:40 ` Victor Goldenshtein
2012-10-22 12:56 ` Johannes Berg
2012-11-01 7:54 ` Victor Goldenshtein
2012-11-05 15:23 ` Johannes Berg
2012-11-13 15:04 ` Victor Goldenshtein
2012-11-14 11:23 ` Johannes Berg
2012-11-14 12:19 ` Michal Kazior
2012-11-14 12:38 ` Johannes Berg
2012-11-20 15:15 ` Victor Goldenshtein
2012-11-26 10:50 ` Johannes Berg
2012-11-20 15:15 ` Victor Goldenshtein
2012-11-26 10:50 ` Johannes Berg
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=1351798320.17469.1.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=adrian.chadd@gmail.com \
--cc=coelho@ti.com \
--cc=igalc@ti.com \
--cc=j@w1.fi \
--cc=kgiori@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@frijolero.org \
--cc=michal.kazior@tieto.com \
--cc=nbd@nbd.name \
--cc=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=victorg@ti.com \
--cc=zefir.kurtisi@neratec.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.