From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
Cc: linux-wireless@vger.kernel.org, johannes@sipsolutions.net,
victorg@ti.com, linville@tuxdriver.com, kgiori@qca.qualcomm.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 0/3] Add DFS master ability
Date: Tue, 29 Jan 2013 14:14:26 +0100 [thread overview]
Message-ID: <5107CB32.2070908@neratec.com> (raw)
In-Reply-To: <1359462120-22898-1-git-send-email-siwu@hrz.tu-chemnitz.de>
On 01/29/2013 01:21 PM, Simon Wunderlich wrote:
> [...]
>
> The channel states are now implemented in cfg80211. Shall we inform userspace
> about channel changes? If yes, how should we do that? We could add channel states
> to the channel list, and give "channel list changed" events to userspace as it
> happens now, or define a new kind of event ("channel-available-again-event").
> Suggestions welcome. :)
>
An event whenever a channel state changes is perfect, ideally provided with the
time-stamp when this change happened.
With the centralized channel state handling proposed here, the required
modification to allow managed DFS operation can be minimized to a proprietary (or
even upstreamed but CONFIG_CFG80211_CERTIFICATION_ONUS guarded) function to modify
channel states.
Can't contribute much to code review, but full ACK for the updated concept.
> If you prefer, I can split off the channel state stuff from the radar detect
> patches.
>
> Cheers,
> Simon
>
next prev parent reply other threads:[~2013-01-29 13:14 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
2013-01-29 12:22 ` [PATCHv7 3/3] nl80211: allow DFS in start_ap Simon Wunderlich
2013-01-29 13:14 ` Zefir Kurtisi [this message]
2013-01-29 14:52 ` [PATCHv7 0/3] Add DFS master ability 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=5107CB32.2070908@neratec.com \
--to=zefir.kurtisi@neratec.com \
--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=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=siwu@hrz.tu-chemnitz.de \
--cc=victorg@ti.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.