All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>,
	linux-wireless@vger.kernel.org, victorg@ti.com,
	linville@tuxdriver.com, kgiori@qca.qualcomm.com,
	zefir.kurtisi@neratec.com, adrian@freebsd.org, j@w1.fi,
	coelho@ti.com, igalc@ti.com, nbd@nbd.name,
	mathias.kretschmer@fokus.fraunhofer.de,
	Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
Subject: Re: [PATCHv7 2/3] mac80211: add radar detection command/event
Date: Tue, 5 Feb 2013 11:03:29 +0100	[thread overview]
Message-ID: <20130205100329.GC7865@pandem0nium> (raw)
In-Reply-To: <1360056900.8376.0.camel@jlt4.sipsolutions.net>

[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]

On Tue, Feb 05, 2013 at 10:35:00AM +0100, Johannes Berg wrote:
> > 
> > Well, yeah the reporting is currently done per interface. Reporting radars
> > for the hw is certainly possible as well - channel contexts are currently
> > not implemented in ath9k (where I test). The latest patchset works the same
> > way, although we can change that if you prefer. For the current implementation
> > (single channel, single vif) it makes no difference, maybe for future implementations.
> > I don't know if there are any weird corner cases though, and we probably need to
> > adjust the mac80211 interface too when to report radars on certain channels only
> > (e.g. extension channel radar).
> 
> It really just seems strange to me to report radar on all/any other
> interfaces to userspace. If we leave it up to the drivers, we'll get all
> kinds of strange behaviour ;-)
> 
> So it seems better to let mac80211 manage that?

I was afraid you'd say that ... :)

I'll include that change in the next iteration (it is a rather small fix). If you
find anything else in the v8 patchset, please let me know so I can include that.

Cheers,
	Simon

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-02-05 10:03 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 12:21 [PATCHv7 0/3] Add DFS master ability Simon Wunderlich
2013-01-29 12:21 ` [PATCHv7 1/3] nl80211/cfg80211: add radar detection command/event Simon Wunderlich
2013-01-29 13:48   ` Zefir Kurtisi
2013-01-29 14:36     ` Simon Wunderlich
2013-01-30 11:51       ` Zefir Kurtisi
2013-01-30 16:25         ` Simon Wunderlich
2013-01-31  8:52           ` Zefir Kurtisi
2013-01-31 17:54             ` Simon Wunderlich
2013-02-01 10:08               ` Zefir Kurtisi
2013-02-13 14:47                 ` Simon Wunderlich
2013-01-31 14:25   ` Johannes Berg
2013-01-31 16:13     ` Simon Wunderlich
2013-01-31 16:46       ` Johannes Berg
2013-01-31 17:44         ` Simon Wunderlich
2013-02-01  9:40           ` Zefir Kurtisi
2013-02-01  9:54           ` Johannes Berg
2013-01-29 12:21 ` [PATCHv7 2/3] mac80211: " Simon Wunderlich
2013-01-29 13:26   ` Zefir Kurtisi
2013-01-29 14:43     ` Simon Wunderlich
2013-01-31 14:44   ` Johannes Berg
2013-01-31 16:31     ` Simon Wunderlich
2013-01-31 16:48       ` Johannes Berg
2013-01-31 17:47         ` Simon Wunderlich
2013-02-01  9:57           ` Johannes Berg
2013-02-02 22:15             ` Simon Wunderlich
2013-02-04 17:32               ` Johannes Berg
2013-02-05  8:44                 ` Simon Wunderlich
2013-02-05  9:35                   ` Johannes Berg
2013-02-05 10:03                     ` Simon Wunderlich [this message]
2013-01-29 12:22 ` [PATCHv7 3/3] nl80211: allow DFS in start_ap Simon Wunderlich
2013-01-29 13:14 ` [PATCHv7 0/3] Add DFS master ability Zefir Kurtisi
2013-01-29 14:52   ` Simon Wunderlich
2013-01-31 16:50 ` Johannes Berg
2013-01-31 17:21   ` 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=20130205100329.GC7865@pandem0nium \
    --to=simon.wunderlich@s2003.tu-chemnitz.de \
    --cc=adrian@freebsd.org \
    --cc=coelho@ti.com \
    --cc=igalc@ti.com \
    --cc=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --cc=kgiori@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mathias.kretschmer@fokus.fraunhofer.de \
    --cc=nbd@nbd.name \
    --cc=siwu@hrz.tu-chemnitz.de \
    --cc=victorg@ti.com \
    --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.