From: Helmut Schaa <helmut.schaa@googlemail.com>
To: 李刚 <gang.li@watchdata.com>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: Question about IEEE80211_TX_CTL_NO_ACK in ath_9k
Date: Mon, 19 Dec 2011 14:07:56 +0100 [thread overview]
Message-ID: <CAGXE3d9vwwqFUhOW_swJwZjtJVAQuxtnXy1ovcB-Wa+AQeHaNw@mail.gmail.com> (raw)
In-Reply-To: <20111219112845.C748820066@mail.watchdata.com.cn>
2011/12/19 李刚 <gang.li@watchdata.com>:
> My wireless card is AR9280. I set the IEEE80211_TX_CTL_NO_ACK flag before
> send a packet, but found it no use. It still wait for an ACK.
How did you verify that? For unicast frames with IEEE80211_TX_CTL_NO_ACK
set you will still see an ACK on the air (since the peer has to
generate it according
to the 802.11 spec). The only thing this flag does is to advise the hardware to
ignore a missing ACK and hence to not retry the frame in this case ...
Helmut
next prev parent reply other threads:[~2011-12-19 13:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 23:18 Question about TCP Checksum errors Larry Finger
2011-12-17 23:43 ` Eric Dumazet
2011-12-19 11:38 ` Question about IEEE80211_TX_CTL_NO_ACK in ath_9k 李刚
2011-12-19 12:33 ` Mohammed Shafi
2011-12-19 13:03 ` 李刚
2011-12-19 12:33 ` Daniel Smith
2011-12-19 13:00 ` 李刚
2011-12-19 13:43 ` Daniel Smith
2011-12-19 13:43 ` [ath9k-devel] " Daniel Smith
2011-12-30 8:15 ` Question: ieee80211_rx called twice after one ieee80211_subif_start_xmit call 李刚
2011-12-30 8:15 ` [ath9k-devel] " 李刚
2011-12-30 9:30 ` Adrian Chadd
2011-12-30 9:30 ` [ath9k-devel] " Adrian Chadd
2011-12-30 11:13 ` [ath9k-devel] 答复: " 李刚
2012-01-07 2:11 ` Question about duration of data frame in ath9k_htc 李刚
2012-01-07 2:11 ` [ath9k-devel] " 李刚
2012-01-07 5:31 ` Sujith Manoharan
2012-01-07 5:31 ` [ath9k-devel] " Sujith Manoharan
2011-12-19 13:07 ` Helmut Schaa [this message]
2011-12-19 14:42 ` Question about IEEE80211_TX_CTL_NO_ACK in ath_9k Sujith
2011-12-20 5:39 ` 李刚
2011-12-20 15:24 ` Sujith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGXE3d9vwwqFUhOW_swJwZjtJVAQuxtnXy1ovcB-Wa+AQeHaNw@mail.gmail.com \
--to=helmut.schaa@googlemail.com \
--cc=gang.li@watchdata.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.