On Wed, Jun 20, 2012 at 11:46 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > Also, it seems that the value should be reset eventually ... at least on > interface down or so. Otherwise you can start CAC, then bring the > interface down to stop the device, and then bring it back up (CAC check > is no longer running) and then you can use the channel after some time > even though you never really checked for radar... > np, will also reset both the timestamp + new flag during interface down. > And if you start CAC on two different devices on the same channel, but > they happen to share channel structs in the driver then this will all > conflict quite badly. > We can just return EBUSY if the radar detection has already started on this specific channel. Btw, this is another argument why the "radar_detect_timeout" should be per channel. -- 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
