linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernhard Schmidt <bernhard.schmidt@saxnet.de>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Luis Rodriguez <Luis.Rodriguez@atheros.com>,
	"nbd@openwrt.org" <nbd@openwrt.org>,
	"dubowoj@neratec.com" <dubowoj@neratec.com>,
	"zefir.kurtisi@neratec.com" <zefir.kurtisi@neratec.com>,
	"simon.wunderlich@saxnet.de" <simon.wunderlich@saxnet.de>
Subject: Re: [PATCH 2/9] [{mac|nl}80211] Add 2 new radar channel flags
Date: Wed, 2 Mar 2011 10:37:33 +0100	[thread overview]
Message-ID: <201103021037.34404.bernhard.schmidt@saxnet.de> (raw)
In-Reply-To: <20110301215412.GD6835@tux>

On Tuesday, March 01, 2011 22:54:12 Luis R. Rodriguez wrote:
> On Mon, Feb 28, 2011 at 08:47:06AM -0800, Bernhard Schmidt wrote:
> > DFS introduces 2 new flags a channel requiring radar detection
> > might take. The interference flag indicates that interference was
> > detected either during CAC or in-service monitoring and the
> > channel is not to be used for the NOP period. The clear flag
> > indicates that during a full CAC no interference was detected and
> > it is allowed to open a BSS on that channel. The case were both
> > flags are set is used to indicate that interference has been
> > detected and we are in progress of closing on that channel.
> 
> What does closing mean?

Channel closing time is the period between radar interference and the
last transmission on a channel. After detected the interferences there
must be short time frame where you can notify stations about switching
to another channel (CSA).

> > Signed-off-by: Bernhard Schmidt <bernhard.schmidt@saxnet.de>
> 
> > ---
> >  include/linux/nl80211.h |    6 ++++++
> >  include/net/cfg80211.h  |   18 ++++++++++++------
> >  net/mac80211/cfg.c      |    6 ++++++
> >  net/mac80211/tx.c       |    6 ++++--
> >  net/wireless/nl80211.c  |    4 ++++
> >  5 files changed, 32 insertions(+), 8 deletions(-)
> > 
> > diff --git a/include/linux/nl80211.h b/include/linux/nl80211.h
> > index e3c9ec7..2282f56 100644
> > --- a/include/linux/nl80211.h
> > +++ b/include/linux/nl80211.h
> > @@ -1371,6 +1371,10 @@ enum nl80211_band_attr {
> >   *	(100 * dBm).
> >   * @NL80211_FREQUENCY_ATTR_MAX: highest frequency attribute number
> >   *	currently defined
> > + * @NL80211_FREQUENCY_ATTR_RADAR_CLEAR: during a full CAC no interference has
> > + *	been detected.
> 
> Why do you need a flag for clear, can you simply count on the
> lack of the flag as the "clear" state?

No. There are 3 states a channel can be in, "usable", "available" and
"unavailable" (as definied in ETSI v1.5.1). On initialization all
channels are "usable", this is indicated by no flag at all. Only after
a full CAC can a channel get "available" (the CLEAR flag) and is now
allowed to be used for beaconing. "unavailable" channels are those
on which interference has been detected, those are marked with
INTERFERENCE, this channel becomes a "usable" (no flag) channel again
after the non-occupancy period.

-- 
Best regards,

Dipl.-Inf. (FH) Bernhard Schmidt (software development)

saxnet GmbH, Willy-Brandt-Ring 1, 08606 Oelsnitz
Tel. +49 (0) 3741 300 6. 100 - Fax +49 (0) 3741 300 6. 101
managing director: Steffen Dreise - county court Chemnitz - HRB 23017
http://www.saxnet.de

  parent reply	other threads:[~2011-03-02  9:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 16:40 [RFC 0/9 v2] DFS/radar state/userspace handling Bernhard Schmidt
2011-02-28 16:46 ` [PATCH 1/9] [mac80211] add method to access oper chan Bernhard Schmidt
2011-03-01 12:11   ` Johannes Berg
2011-02-28 16:47 ` [PATCH 2/9] [{mac|nl}80211] Add 2 new radar channel flags Bernhard Schmidt
2011-03-01 21:54   ` Luis R. Rodriguez
2011-03-02  8:25     ` Johannes Berg
2011-03-02  9:37     ` Bernhard Schmidt [this message]
2011-02-28 16:47 ` [PATCH 3/9] [mac80211] enable radar detection Bernhard Schmidt
2011-03-01 21:56   ` Luis R. Rodriguez
2011-02-28 16:48 ` [PATCH 4/9] [cfg80211] add preliminary radar processing code Bernhard Schmidt
2011-03-01 12:17   ` Johannes Berg
2011-03-01 21:58   ` Luis R. Rodriguez
2011-03-02  7:32     ` Bernhard Schmidt
2011-03-02 16:26       ` Luis R. Rodriguez
2011-02-28 16:49 ` [PATCH 5/9] [cfg80211] channel availability check (CAC) support Bernhard Schmidt
2011-02-28 16:49 ` [PATCH 6/9] [cfg80211] no operation list (NOL) support Bernhard Schmidt
2011-03-01 12:19   ` Johannes Berg
2011-02-28 16:50 ` [PATCH 7/9] [cfg80211] abide channel closing time Bernhard Schmidt
2011-02-28 16:51 ` [PATCH 8/9] [{cfg|nl}80211] announce flag changes to userspace Bernhard Schmidt
2011-02-28 16:51 ` [PATCH 9/9] [cfg80211] interference reporting Bernhard Schmidt
2011-03-01 12:28 ` [RFC 0/9 v2] DFS/radar state/userspace handling Johannes Berg
2011-03-01 13:07   ` Bernhard Schmidt
2011-03-01 13:15     ` Johannes Berg
2011-03-01 13:26       ` Bernhard Schmidt

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=201103021037.34404.bernhard.schmidt@saxnet.de \
    --to=bernhard.schmidt@saxnet.de \
    --cc=Luis.Rodriguez@atheros.com \
    --cc=dubowoj@neratec.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@atheros.com \
    --cc=nbd@openwrt.org \
    --cc=simon.wunderlich@saxnet.de \
    --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 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).