On Tue, Aug 23, 2011 at 6:55 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Tue, 23 Aug 2011 18:50:44 +0300, Eliad Peller wrote: >> >> basically these params come from the supplicant on sta addition. >> if the ap wasn't configured with uapsd, there won't be >> NL80211_ATTR_STA_WME attribute, and these fields will be 0. >> >> devices with no uapsd support will ignore these fields. >> am i missing something? > > Well, so, how will the user know whether the device supports uAPSD? Or, if > the user asks hostapd to enable uAPSD, how will hostapd know if the device > supports it or not? > Currently, hostapd just looks for the uapsd_advertisement_enabled config param. i guess we can add and require ap_uapsd capability (on a different patch?). but won't it break environments that use new supplicant with old drivers? Eliad. -- 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
