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. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
