Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Felix Fietkau <nbd@openwrt.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 3.15] cfg80211: allow restricting supported dfs regions
Date: Mon, 05 May 2014 11:23:40 +0200	[thread overview]
Message-ID: <1399281820.22235.4.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <536757DA.1010205@openwrt.org>

On Mon, 2014-05-05 at 11:20 +0200, Felix Fietkau wrote:

> >> Add a bitmap in the interface combinations, indicating which DFS regions
> >> are supported by the detector.
> > 
> > Does that make sense? It seems unlikely to me that it would be interface
> > combination specific?
> Having it there made about as much sense to me as having the supportede
> channel width there :)
> Got any better suggestions?

Not really, it does make sense to group them, though the only real
reason to do it there originally was to prohibit multi-channel usage
with radar detection, so that made sense ... I have no real problem
doing this here as well.

> > I think it's already questionable to put this in after -rc4, in
> > particular with the userspace advertising part. Can we do anything
> > else? 
> I mostly pushed it for 3.15, because right now you can already enable
> DFS and it will bring it up on a FCC regdomain and it will appear to be
> working (but probably just not recognize any radars).
> 
> However, now that I look at the description of the options that you have
> to enable, it should be clear enough that this is not guaranteed to be
> functional yet, so I guess it can wait for 3.16.

Ok.

johannes


  reply	other threads:[~2014-05-05  9:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-03 20:55 [PATCH 3.15] cfg80211: allow restricting supported dfs regions Felix Fietkau
2014-05-05  7:33 ` Johannes Berg
2014-05-05  9:20   ` Felix Fietkau
2014-05-05  9:23     ` Johannes Berg [this message]
2014-05-05  9:37     ` Janusz Dziedzic

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=1399281820.22235.4.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@openwrt.org \
    /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