On Wed, 2007-12-12 at 18:15 +0100, Johannes Berg wrote: > Hi, > > > rt2x00 devices can't generate rts/cts frames themselves, but rely on the > > driver to generate them. Also, the hardware reports tx status back for > > those frames. Now the question is whether these frames should be > > reported back to mac80211 using ieee80211_tx_status[_irqsafe]. AFAIK, > > this has some subtle effects, e.g. they won't show up on monitor > > interfaces if we don't report them. > > They never show up on monitor interfaces for all other hardware because > there the hardware handles them. How is it that rt2x00 cannot handle > rts? It has to at least know that an RTS was sent and to send the frame > only after the CTS, and that needs to be a MAC function and cannot be > implemented in host software. rt2x00 devices have some flags in the TX descriptor that basically tell the device to send a burst of frames, optionally requesting to wait for an ack (i.e. CTS in the case of an RTS frame) for any of them. > So, I'd think they shouldn't be reported at all. Ok, I'll prepare a patch for rt2x00. Mattias - 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
