On Sat, Jan 15, 2011 at 02:20:00AM +0100, BjÃrn Smedman wrote: > 2011/1/15 Steve Brown <sbrown@xxxxxxxxxxxx>: > > For instance, an ap vif has a ~100ms interval and a mesh vif has a > > ~1000ms interval. I don't see how to avoid a per vif interval. > > I agree. We should fix ath9k so it works correctly even if beacon > interval is different for different vifs (within some reasonable > limits). Yes, up to a limit. Handling something like 100 TU on one vif and 1000 TU on another is fine, but something like 100 TU and 103 TU would need to be forced to use the same interval. I've been thinking of adding some kind of mechanism for the driver to override Beacon interval in such cases (which would need to go back all the way to user space to hostapd in case of AP mode). -- Jouni Malinen PGP id EFC895FA -- 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
