On 07/18/2016 12:14 PM, Johannes Berg wrote:
On Mon, 2016-07-18 at 12:04 -0700, Ben Greear wrote:
On 07/18/2016 11:56 AM, Johannes Berg wrote:
On Mon, 2016-07-18 at 19:23 +0530, Purushottam Kushwaha wrote:
Driver may allow support for different beacon interval on virtual
interfaces.
Allow if such support is advertised by driver. This adds new
ext_feature as NL80211_EXT_FEATURE_DIFF_BEACON_INTERVAL.
We have NL80211_IFACE_COMB_STA_AP_BI_MATCH in interface
combinations,
perhaps it would make sense to also put this flag there?
I was under impression that ath9k had supported this for years,
but I guess I haven't tested it lately....
It may very well have, but if userspace can't rely on it because other
drivers don't then it's pretty pointless.
A flag would be nice, but for backwards compat, it could be a negative
flag. But, if mac80211 has to be patched to make this work, then maybe
the ath9k feature has been disabled/broken for some time and wouldn't matter
anyway.
Also, ath9k had some restrictions about having the timers be certain
multiples of each other so the hardware could properly service beacons
for multiple vdevs. If chip-specific restrictions remain, then it may be almost impossible
to communicate this properly to the hostapd/userspace. At best, the driver
could just fail to start the vdev in case of mismatch?
Thanks,
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
--
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
