On 05/11/2012 17:23, Johannes Berg wrote:
On Thu, 2012-11-01 at 09:54 +0200, Victor Goldenshtein wrote:
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().
Yeah but that probably should change anyway, for channel contexts?
(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?
Because you can't do CAC properly while you're channel-hopping?
I don't see any problems to start CAC on different channels (once we"ll
add this support)
I do see issues with that, but let's not worry about it for now.
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():
MR?
+» if·(chan->cac_started)
+» » return·-EBUSY;
which should block concurrent CAC executions on the same channel.
Yes.
Anyway, the "DFS channel contexts" are not part of this patch series,
and can be added later.
No ... channel contexts are in the kernel now, so you do have to think
about it now.
Well thinking is one thing implementing is another ;)
This whole DFS implementation initially intended for a single channel
mac. I don't might to deal with the channel context stuff but not sure
how much available time I"ll have for it, so it might take awhile.
I know there are people waiting for this, so I'm thinking would you
consider to go first with this single channel DFS support and later to
extend it to work with channel context stuff ?
--
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
