Thanks a lot. It's really helpful. BTW, I really think ath5k need more documentation for those who hasn't touched madwifi or device driver development before.
On Fri, Feb 26, 2010 at 6:57 PM, Bob Copeland <m...@bobcopeland.com> wrote: > On Thu, Feb 25, 2010 at 04:27:13PM -0700, Xingang Zhang wrote: >> seqnum and tstamp is easy to interpret. For ts_status, I can tell if >> it's 0x0, then TX is successful. But what does it mean >> "AR5K_TXERR_XRETRY" for 0x01, and "AR5K_TXERR_FILT" for 0x02, >> "AR5K_TXERR_FIFO" for 0x04? I have several 0x01 errors, what does that mean? > > See desc.c... > "AR5K_TXERR_XRETRY" - excessive retries (with no ack) > "AR5K_TXERR_FILT" - the frame was filtered by matching a destination > mask - I don't think we use this tx filter > "AR5K_TXERR_FIFO" - couldn't DMA the frame to hardware fast enough > >> Also, could somebody help decipher the ts_rate[4] (rate code) for >> AR5414? I can't find any clue from ath5k.h. > > See RATE DEFINITIONS in ath5k.h - I think it's fairly well > documented. > >> my last question is ts_final_idx, what does this parameter means? > > The rate for which transmission actually succeeded. > > -- > Bob Copeland %% www.bobcopeland.com > > _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
