diff options
author | Ivo van Doorn <ivdoorn@gmail.com> | 2007-07-27 15:43:23 +0200 |
---|---|---|
committer | David S. Miller <davem@sunset.davemloft.net> | 2007-10-10 16:47:38 -0700 |
commit | d5d08def9216c445339c5a24a2cdc9cc2c8c13f7 (patch) | |
tree | 323fa9482da42ae8ce28c2030cf12bafd44e3eba /drivers/cdrom | |
parent | 8a69aa93d54cb56017159b08512c80ede2263060 (diff) | |
download | linux-d5d08def9216c445339c5a24a2cdc9cc2c8c13f7.tar.gz linux-d5d08def9216c445339c5a24a2cdc9cc2c8c13f7.tar.bz2 linux-d5d08def9216c445339c5a24a2cdc9cc2c8c13f7.zip |
[MAC80211]: Add LONG_RETRY flag to ieee80211_tx_control
mac80211 informs the driver what the short and long retry values are through
set_retry_limit(), but when packets are being transmitted it did not inform the
driver which of the 2 retry limits should actually be used.
Instead it sends the actual value, but for drivers that can only set the retry limit
and the register and in the descriptor need to indicate which of the limits should
be used this is not really useful.
This patch will add a IEEE80211_TXCTL_LONG_RETRY_LIMIT flag to the
ieee80211_tx_control structure. By default the short retry limit should be
used but if the flag is set the long retry should be used.
This does not prevent the driver to ignore the request for "no retry" packets,
but at least those will be send out with the short retry limit. But there is no
perfect cure for this problem.. :(
Signed-off-by: Ivo van Doorn <IvDoorn@gmail.com>
Signed-off-by: Jiri Benc <jbenc@suse.cz>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'drivers/cdrom')
0 files changed, 0 insertions, 0 deletions