All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Bernhard Schmidt <bernhard.schmidt@saxnet.de>
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 4/9] [cfg80211] add preliminary radar processing code
Date: Wed, 2 Mar 2011 08:26:00 -0800	[thread overview]
Message-ID: <AANLkTinUou54oKDdk04LP3E=TVGE2CNMetrZuKhwgwcS@mail.gmail.com> (raw)
In-Reply-To: <201103020832.17550.bernhard.schmidt@saxnet.de>

On Tue, Mar 1, 2011 at 11:32 PM, Bernhard Schmidt
<bernhard.schmidt@saxnet.de> wrote:
> On Tuesday, March 01, 2011 22:58:56 Luis R. Rodriguez wrote:
>> On Mon, Feb 28, 2011 at 08:48:49AM -0800, Bernhard Schmidt wrote:
>> > --- /dev/null
>> > +++ b/net/wireless/radar.c
>> > @@ -0,0 +1,86 @@
>> > +/*
>> > + * Radar handling
>> > + *
>> > + * Copyright 2011 Bernhard Schmidt <bernhard.schmidt@saxnet.de>
>> > + *
>> > + * This program is free software; you can redistribute it and/or modify
>> > + * it under the terms of the GNU General Public License version 2 as
>> > + * published by the Free Software Foundation.
>> > + */
>> > +
>> > +#include <linux/ieee80211.h>
>> > +#include <net/cfg80211.h>
>> > +#include "radar.h"
>> > +
>> > +static struct radar_parameters regdomain_params[] = {
>> > +   { 60, 1800, 1000 },     /* FCC, correct? */
>> > +   { 60, 1800, 1000 },     /* ETSI */
>> > +   { 60, 1800, 1000 },     /* JP, correct? */
>> > +};
>>
>> If FCC or JP are not supported, I rather code not be present for it, or some
>> sort of flag for now to allow the radar enablement thingy to fail all the
>> time. In fact if FCC / JP regions are not supported you should not even
>> be able to operate in the mode of operation desired if your target channel
>> is a DFS one. If you do enter into an allowed non-DFS channel for that region
>> and you later try to switch to a DFS chanel then we'd hit another failure.
>
> That just means that I hadn't yet looked up the correct values, those
> are not available on the wiki either.

Either way, disable them if not supported yet.

  Luis

  reply	other threads:[~2011-03-02 16:26 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
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 [this message]
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='AANLkTinUou54oKDdk04LP3E=TVGE2CNMetrZuKhwgwcS@mail.gmail.com' \
    --to=lrodriguez@atheros.com \
    --cc=Luis.Rodriguez@atheros.com \
    --cc=bernhard.schmidt@saxnet.de \
    --cc=dubowoj@neratec.com \
    --cc=linux-wireless@vger.kernel.org \
    --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 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.