In order to learn more about how the zd1211 works I though I could try implementing a few missing functions in the dscape zd1211 driver. The easiest ones looked to be the statistics functions.
get_stats needs this filled: struct ieee80211_low_level_stats { unsigned int dot11ACKFailureCount; unsigned int dot11RTSFailureCount; unsigned int dot11FCSErrorCount; unsigned int dot11RTSSuccessCount; }; get_tx_stats needs this filled, one per queue: struct ieee80211_tx_queue_stats_data { unsigned int len; /* num packets in queue */ unsigned int limit; /* queue len (soft) limit */ unsigned int count; /* total num frames sent */ }; I've been poking around in the vendor driver amd zd1211rw and don't see an obvious way to collect this data. For example I didn't see where RTS success/failure is tracked. I also haven't located the exact spot to separate FCS (CRC errors) from other classes of errors. -- Jon Smirl [EMAIL PROTECTED] ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs