According to the 802.11-2007 spec document, the ACKTimeout value is (Section 9.2.8 ACK procedure): ACKTimeout = aSIFSTime + aSlotTime + aPHY-RX-START-Delay >From Table 17-15—OFDM PHY characteristics, the values are: aSIFSTime = 16 aSlotTime = 9 aPHY-RX-START-Delay = 25 Therefore, ACKTimeout = 50 In the driver source, this appears to be initialised to: $$ ath5k.h #define AR5K_INIT_ACK_CTS_TIMEOUT 1024 $$ reg.h /* * ACK/CTS timeout register */ #define AR5K_TIME_OUT 0x8014 /* Register Address */ #define AR5K_TIME_OUT_ACK 0x00001fff /* ACK timeout mask */ #define AR5K_TIME_OUT_ACK_S 0 #define AR5K_TIME_OUT_CTS 0x1fff0000 /* CTS timeout mask */ #define AR5K_TIME_OUT_CTS_S 16 Taking the value of the register (1024), masking it with the ACK Timeout Mask (0x1fff) and dividing it by the clock rate (40), we get a much smaller ACK Timeout value: 1024 & 0x1fff = 1024 1024/40 = 25us Am I understanding this right? Is the driver actually setting the ACK Timeout to be much smaller than even a DIFS, let alone matching the spec? Thanks, -- Jonathan Guerin -- 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
