From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>,
linux-wireless@vger.kernel.org,
mathias.kretschmer@fokus.fraunhofer.de,
Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
Subject: Re: [PATCH] mac80211: fix recalc_radar hwconf sync problem
Date: Thu, 04 Apr 2013 15:38:33 +0200 [thread overview]
Message-ID: <515D8259.1030208@neratec.com> (raw)
In-Reply-To: <1364993200.8351.35.camel@jlt4.sipsolutions.net>
On 04/03/2013 02:46 PM, Johannes Berg wrote:
> On Tue, 2013-04-02 at 18:39 +0200, Simon Wunderlich wrote:
>> local->hw.conf maybe not be synced when recalcing whether radar is
>> enabled, sometimes leaving radar enabled even if it's not neccesary
>> anymore.
>
> I don't really see how, can you explain more?
>
> johannes
>
You seem to be right, the patch does not resolve the observed problem.
I am not deep enough in the DFS master code and its integration to resolve it
myself. What I see is that ath9k_config() is called with a non-DFS channel but
with ieee80211_hw->conf.radar_enabled set. For ath9k that's no problem at all
(radar pulse detection can be enabled on any channel), but indicates a problem in
the channel context handling for DFS.
To reproduce, start an AP on a DFS channel, wait until CAC is finished and fire a
radar. hostapd will switch to a non-DFS channel with the radar_enabled flag set.
next prev parent reply other threads:[~2013-04-04 13:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 16:39 [PATCH] mac80211: fix recalc_radar hwconf sync problem Simon Wunderlich
2013-04-03 12:46 ` Johannes Berg
2013-04-04 13:38 ` Zefir Kurtisi [this message]
2013-04-04 18:22 ` Simon Wunderlich
2013-04-05 10:08 ` Zefir Kurtisi
2013-04-05 10:11 ` Zefir Kurtisi
2013-04-05 11:29 ` Simon Wunderlich
2013-04-05 12:11 ` Zefir Kurtisi
2013-04-05 11:22 ` Johannes Berg
2013-04-05 12:16 ` Simon Wunderlich
2013-04-05 12:36 ` Johannes Berg
2013-04-08 11:51 ` Simon Wunderlich
2013-04-08 12:09 ` [PATCHv2] " Simon Wunderlich
2013-04-08 14:17 ` Zefir Kurtisi
2013-04-08 14:29 ` Johannes Berg
2013-04-08 17:04 ` [PATCHv3] " Simon Wunderlich
2013-04-08 17:53 ` Antonio Quartulli
2013-04-08 20:43 ` [PATCHv4] " Simon Wunderlich
2013-04-09 9:50 ` Johannes Berg
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=515D8259.1030208@neratec.com \
--to=zefir.kurtisi@neratec.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mathias.kretschmer@fokus.fraunhofer.de \
--cc=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=siwu@hrz.tu-chemnitz.de \
/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.