hi! i put up 2 new traces of cardbus cards, both with a 5112A PHY. the curious thing is, the one with the 5213 MAC works with ath5k, but the one with 5213A doesn't. there shouldn't be *that* much difference...
http://br1.einfach.org/ath/5213-5112A-mad-trace.tgz http://br1.einfach.org/ath/5213A-5112A-mad-trace.tgz i'll try to figure out the differences tomorrow, but i'm still a bit overwhelmed with the amount of data. i want to add a --filter option to the ath-reg-decode script to get rid of the uninteresting registers... right now i think we can filter (this is a regex): KEY|AR5K_PCICFG|AR5K_SLEEP|AR5K_INTPEND|AR5K_STA_ID1|AR5K_STA_ID0|AR5K_TSF_| AR5K_PISR|AR5K_RAC_PISR|AR5K_RXDP|AR5K_SIMR|AR5K_PIMR|AR5K_IER maybe BSS_ID|TIMER|AR5K_QUEUE_DFS_SEQNUM|AR5K_QUEUE_TXDP|BEACON and AR5K_RX_FILTER_5211|AR5K_PHY_ERR_FIL|AR5K_PHY_ERR_FIL|AR5K_RXCFG|MCAST_FILTER| AR5K_ACK_FAIL_5211|AR5K_RTS_FAIL_5211|AR5K_FCS_FAIL_5211|AR5K_RTS_OK_5211 too? nick? luis? anyone? can you comment? thanks, bruno _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
