On 22/10/2012 14:56, Johannes Berg wrote:
On Sun, 2012-10-21 at 18:40 +0200, Victor Goldenshtein wrote:
On 16/10/2012 21:07, Johannes Berg wrote:
On Sun, 2012-10-14 at 16:48 +0200, Victor Goldenshtein wrote:
Add ieee80211_ap_process_chanswitch(), to handle a channel switch
request for AP.
Add ieee80211_ap_ch_switch_done() which updates oper_channel
and notifies upper layers about channel switch complete event.
Given channel contexts, how does this patch need to change?
I guess most of the changes would be in the channel switch complete
area, we will need to update the correct vif channel
(ieee80211_assign_vif_chanctx) instead of the local->oper_channel.
Yes, maybe, not sure.
Also wrt. channel contexts, how will CAC/radar check work? The AP isn't
bound to a channel until start_ap(), so somehow you'll have to bind it
As I mentioned in my previous email we do it with __nl80211_set_channel().
(and keep it on that channel!) while the DFS check is running? And also
prohibit using multiple channels at this time...?
Why we need to prohibit multiple channels during CAC?
I don't see any problems to start CAC on different channels (once we"ll
add this support), also lets not forget that CAC is relevant only for
the AP role. Today for the MR single channel scenarios we have this
check in the nl80211_start_radar_detection():
+» if·(chan->cac_started)
+» » return·-EBUSY;
which should block concurrent CAC executions on the same channel.
Anyway, the "DFS channel contexts" are not part of this patch series,
and can be added later.
--
Thanks,
Victor.
--
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
