Hi, So on the Atheros NICs, the block-acks are generated by the receiver in hardware and processed by the transmitter in hardware; you then get a bitmap in the TX completion descriptor telling you which frames did succeed/fail.
The TX completion path does check the two 32 bit blockack (ba) fields in the TX descriptor for completion. It doesn't hand-parse a BA frame. -a On 3 February 2014 07:48, Olivier Marce <olivier.ma...@alcatel-lucent.com> wrote: > Hi everybody, > thanks to all of you who share your knowledge and expertise on ath9k. > > I wonder if Ack and Block Ack are processed directly by the HW on > receipt and not the firmware. > > There are several messages that confirm that Ack and Block Ack are > *sent* by HW (http://www.spinics.net/lists/linux-wireless/msg106950.html) > But are they processed (on receipt) also by HW ? I analysed firmware > code and I did not find any Ack/BA processing. > > Is my understanding correct ? > > Best regards > > > -- > Olivier Marcé > Alcatel-Lucent Bell Labs France > _______________________________________________ > ath9k-devel mailing list > ath9k-devel@lists.ath9k.org > https://lists.ath9k.org/mailman/listinfo/ath9k-devel _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
