> Yes, this is handled by firmware, What is important is to make switch > on beacon edge. > Still our implementation uses also timer in mac rather then some mac > to driver over complicated synchronization. > Other thing is that the firmware enforce the switching, traffic on the > old channel is not allowed after the switch. Yeah, ok. As for enforcing the traffic, true as well. However, I'd like mac80211 to help out with this for those drivers that don't do it all in firmware (all others, I'd assume); it's not overly important that you switch instantly after receiving the switch beacon, if you take a bit longer to do that you'll just potentially miss a few packets. No big deal. > > Also, does your firmware implement full radar detection? Broadcom and > > Atheros hardware seem to only pass information about pulse edges up to > > the driver (in different ways, obviously) and pulse/radar detection > > needs to be done in software, I'd like that to be somehow shareable. > > > iwl drivers were designed for laptop marked mostly unlike like other > vendors that plays in AP market so the radar awareness is in slave > mode. I think the hw actually support radar detection but I'm not sure > it was ever employed in a product. Oh, right, ok. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
