On 23 May 2014 11:07, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Fri, 2014-05-23 at 10:58 +0200, Michal Kazior wrote: > >> If you keep on beaconing for too long on a DFS channel after detecting >> a radar you risk breaking local law (ETSI and FCC specify quiescing >> periods). > > Yes, this is true. > >> > You could technically just return NULL in this period, but I don't know >> > how well drivers would cope with that (though technically they have to >> > cope with it due to memory allocation failures anyway) >> >> Sounds good to me. >> >> I guess you'd use ieee80211_csa_is_complete (or >> ieee80211_csa_update_counter) for template-based drivers to stop >> beaconing. > > The thing is, I don't see that template based drivers would be able to > stop beaconing :-) > > This whole design that requires it seems a bit fishy to start with, so I > can't really imagine anyone writing firmware that supports it. That > said, ours only supports a single beacon at a time anyway, so we'll > switch immediately and don't have to do that anyway. What if you have AP+STA and STA switches too? It might delay your AP interface switch, no? We could assume userspace always requests us to do The Right Thing, but should we trust it so much? Michał -- 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
