* basic rate set / response frame rate
@ 2008-06-26 20:18 Johannes Berg
0 siblings, 0 replies; only message in thread
From: Johannes Berg @ 2008-06-26 20:18 UTC (permalink / raw)
To: Linux Wireless
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
Hi,
How does hardware currently handle the control response (ACK/CTS) frame
rate? In 802.11 clause 9.6 talks about this, and we implement basic rate
handling in mac80211 to calculate the control response duration, but we
never tell drivers what bitrate to transmit control response frames at.
I suspect this is broken in all drivers (except maybe iwlwifi which
probably does it all in firmware.) The problem then is that if the AP
has basic rates higher than your firmware/hardware default, the control
response takes too long and the NAV isn't updated correctly in other
STAs.
How should we fix this?
The most straight-forward way would be to include a map of rate -> basic
rate into ieee80211_bss_conf, but that isn't easy because the size of
the map isn't known.
Another way would be to just give the driver the basic rate set, but
that means it has to calculate the mapping itself, subject to all the
rules in 802.11 clause 9.6.
Therefore, I prefer the former way, or giving the driver a function to
call for each rate on bss_info_changed to calculate the mapping.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-06-26 20:19 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-06-26 20:18 basic rate set / response frame rate Johannes Berg
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox