Johannes Berg wrote: > > Removing all crappy code in ath9k dealing with this and leaving everything > > to mac80211 would certainly be the better option, but we still have to figure > > out how to manage BA windows. > > Can you explain a little what is required? > Managing per-TID state to handle Block ACKs, failed sub-frames, sub-frame retries and other window management stuff. ath9k manages all this internally. > For ampdu_action(), I recently saw something, somewhere, saying > "mac80211 expects us to fill in the seqno variable" or so, but this is > only true if you don't use mac80211's sequence numbers, otherwise it is > fine to leave it at the pre-assigned value. ampdu_action() requires the driver to set the starting sequence number for initiating an ADDBA session, ath9k was filling it incorrectly. This was fixed in the patch, "ath9k: Fix bug in TX aggregation". Sujith -- 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
