From: Simon Wunderlich <sw@simonwunderlich.de>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Janusz Dziedzic <janusz.dziedzic@tieto.com>,
Jouni Malinen <j@w1.fi>,
sunitb@qca.qualcomm.com, rsunki@qca.qualcomm.com,
"linux-wireless" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC 4/5] cfg80211: add DFS region capability support
Date: Thu, 14 Nov 2013 17:13:59 +0100 [thread overview]
Message-ID: <201311141714.00098.sw@simonwunderlich.de> (raw)
In-Reply-To: <CAB=NE6WX9JV-Lx11iiPHPinDCxy7u-Q--ucQ-9Mjy-nndKTeqQ@mail.gmail.com>
> On Thu, Nov 14, 2013 at 4:29 PM, Johannes Berg
>
> <johannes@sipsolutions.net> wrote:
> > On Thu, 2013-11-14 at 07:33 -0800, Luis R. Rodriguez wrote:
> >> > Still doesn't make sense - HANDLE_DFS means "I'll react to radar
> >> > detection events and will do the CSA". It has absolutely nothing to do
> >> > with DFS regions. Please keep those things separate.
> >>
> >> How you deal with radar detection is completely dependent on the DFS
> >> region, no?
> >
> > You're missing *my* point :-)
> >
> > Radar *detection* is region-dependent.
> >
> > What happens *after* that (announce a channel switch, etc.) isn't at
> > all.
>
> Sorry, I misread the documentation then, so HANDLE_DFS *does* not mean
> userspace will implement the radar detection in userspace?
>
Right, it does not mean userspace implements radar detection/pattern
matching/etc.
HANDLE_DFS only means that userspace lets the kernel know that it will react
to nl80211-dfs-radar events (these only contain "i detected a radar on freq
XXX" [1] and similar) and that it will do a channel switch (CSA) in this case
to move away.
We still assume that the radar detection/pattern matching/etc, which is indeed
region-specific, is done in the drivers (as done for ath9k now) or by other
means independent of this HANDLE_DFS attribute.
Cheers,
Simon
[1] http://lxr.free-electrons.com/source/include/uapi/linux/nl80211.h#L3836
next prev parent reply other threads:[~2013-11-14 16:14 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
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 [this message]
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=201311141714.00098.sw@simonwunderlich.de \
--to=sw@simonwunderlich.de \
--cc=j@w1.fi \
--cc=janusz.dziedzic@tieto.com \
--cc=johannes@sipsolutions.net \
--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).