Sujith wrote: > Sujith wrote: > > What about hardware that doesn't report any kind of TX status information at all ? > > Currently, there is no way to determine whether the frame has actually gone out, > > all that can be known is that it was pushed to the target. > > Am curious how carl9170 gets the TX status ? > Is there a separate endpoint ? I looked a bit into carl9170 and it looks like the TX status is obtained as incoming data through the CMD endpoint, am I correct ? And the cookie is used to match the status information with the approporiate packet ? Though for ath9k_htc this would mean changes in both the host and FW, the host has to queue up packets in some kind of queue and process them on reception of status interrupts. The FW has to be changed to actually deliver the TX status information. :) It does make it a bit neat to have such a mechanism. And for AP mode, I would think that it's kinda essential unless someone comes with an ingenious way of solving the PS race for drivers that don't set IEEE80211_HW_REPORTS_TX_ACK_STATUS. :-) 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
