On Fri, 2014-10-03 at 14:58 -0700, Kyeyoon Park wrote: > From: Peng Xu <pxu@xxxxxxxxxxxxxxxx> > > Add support for offloading ACS functionality to the driver. A new > feature flag NL80211_FEATURE_AP_ACS_OFFLOAD was added to support > ACS (Automatic Channel Selection) offload functionality. This flag > allows the driver to advertise its ACS capability. > > When hostapd starts with the "channel" configuration set to 0, it will > check whether the driver has the capability of doing the ACS on its own. > If the driver has such capability, then the channel selection will be > done in the driver. The kernel will skip the channel information > validation since it would initially be NULL when this feature is > enabled. After the channel is selected by the driver, a channel > change event will be sent from the driver to the kernel which updates > the channel information it maintains. This event is in turn sent to > hostapd and the channel information in hostapd will get updated as well. Is this design required? That seems a bit strange because you'd start the AP with ... invalid beacon information? Invalid probe response, and all that? Even an invalid channel reported to other userspace. I'd much prefer offloading this as a separate operation, with the device reporting back the best channel (configuration) to use, and hostapd then using that to start up its operation. johannes -- 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
