On 22/10/2012 14:52, Johannes Berg wrote:
On Sun, 2012-10-21 at 18:40 +0200, Victor Goldenshtein wrote:
On 16/10/2012 21:06, Johannes Berg wrote:
Hmm, does that really work? I mean, it can do the update when the event
comes in, but is that fast enough, or should it give us the new beacon
already when programming the switching?
Yes it works with our 12xx, in the 12xx the FW (upon channel switch
command) is responsible to decrement the channel switch count in the
beacon CSA IE and to remove the CSA IE from the beacon once device moves
to the new channel (+ to updates the DS).
So ... you've made this kind of behaviour a mandatory part of the
userspace API. Where is it documented then? How will it work with other
devices?
It's should work the same with other devices, each device should
implement AP channel switch op according the spec, the implementation
can be hardware/driver depended. I just mentioned how we do it in our
devices, which I think is the right way without introducing any races
(as you mentioned), So no behavior enforcement here as long as it
according the spec.
--
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
