> > > For rt73? IIRC the rate selection algo does not work at all for that > > > device, because we cannot report failed frames. Or have you done > > > anything about that I might have missed, Ivo? If not, the rate is > > > probably fixed at 54Mbit anyway. > > > > Well I didn't do anything new, but this line will report rt2x00lib that the > > frame was succesfully send or failed to send: > > txdesc.status = !urb->status ? TX_SUCCESS : TX_FAIL_RETRY; > > What is missing is the retry count, since that is something that > > the USB drivers cannot report. (Unless I grab the max retry count > > as configured by mac80211 as the number of retries on failure) > > Well, I have just put my rt73 into a metal box. Many frames do fail, > only very few get through pinging my AP. The rate control still keeps > the rate at 54Mbit/s :-) So it seems neither excessive_retries nor the > retry_count in the tx_status struct is set at all. Hmm, perhaps we need some way the driver can inform the rate selection module about statistics. I mean the hardware does measure the number of failed TX frames, and the number of retries, but it doesn't set them in the descriptor but in the hardware. Ivo -- 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
