From: Johannes Berg <johannes@sipsolutions.net>
To: Simon Wunderlich <sw@simonwunderlich.de>
Cc: Antonio Quartulli <a@unstable.cc>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 2/2] mac80211: passively scan DFS channels if requested
Date: Mon, 24 Oct 2016 16:38:36 +0200 [thread overview]
Message-ID: <1477319916.4085.29.camel@sipsolutions.net> (raw)
In-Reply-To: <4116422.yZP7iyh9mq@prime>
On Mon, 2016-10-24 at 16:36 +0200, Simon Wunderlich wrote:
> On Monday, October 24, 2016 4:16:02 PM CEST Johannes Berg wrote:
> >
> > On Mon, 2016-10-24 at 15:42 +0200, Simon Wunderlich wrote:
> > >
> > > Otherwise, it would be pretty much impossible to perform CSAs to
> > > another DFS channel.
> >
> > I was told that to do that you'd need another NIC that's pre-
> > CAC'ing another channel.
>
> Here is the portion from ETSI 301 893 v1.8.1 [1] (the most recent one
> to my knowledege), section 4.7.1.4 which describes operation from
> master devices (Access Points):
> [...]
Yeah I'm pretty sure there are differences in ETSI vs. FCC. Perhaps the
information I was told about was for FCC. But perhaps it's all just
completely wrong :)
johannes
next prev parent reply other threads:[~2016-10-24 14:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-14 1:29 [PATCH v2 1/2] nl80211: add flag to force passive scan on DFS channels Antonio Quartulli
2015-11-14 1:29 ` [PATCH v2 2/2] mac80211: passively scan DFS channels if requested Antonio Quartulli
2015-11-20 10:49 ` Johannes Berg
2015-11-20 12:52 ` Antonio Quartulli
2016-10-24 12:11 ` Antonio Quartulli
2016-10-24 13:33 ` Johannes Berg
2016-10-24 13:35 ` Antonio Quartulli
2016-10-24 13:42 ` Simon Wunderlich
2016-10-24 14:07 ` Michal Kazior
2016-10-24 14:16 ` Johannes Berg
2016-10-24 14:36 ` Simon Wunderlich
2016-10-24 14:38 ` Johannes Berg [this message]
2016-10-24 14:53 ` Simon Wunderlich
2016-10-26 12:58 ` Johannes Berg
2016-10-26 13:30 ` Simon Wunderlich
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=1477319916.4085.29.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=a@unstable.cc \
--cc=linux-wireless@vger.kernel.org \
--cc=sw@simonwunderlich.de \
/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).