[ath9k-devel] ath9k in wireless-testing won't work in AP mode

[Felix Fietkau <nbd@openwrt.org>]

On 2010-02-03 1:08 AM, Luis R. Rodriguez wrote:
> We have reviewed this. The 64 value came from interoperability
> tests against another 802.11n device which had increased delayed BlockAcks
> when CTS-to-self was enabled. Although this is a higher value than
> what the standard says to use we recommend to just leave the value as-is
> and actually use the values from the initvals as the minimum possible
> value as those are the values that have been used for a large array
> of tests, including WMM interop tests. We cannot gaurantee proper
> functionality against other devices otherwise.
> 
> Since the issues so far are obaserved on AR9160 and AR9220
> (and not AR9280) and AR9271 (sujith) this might be a bus issue
> and the only way to zero in on the issue would be by getting full
> register dumps to ensure every other register related to ACK Timeout
> is programmed properly (AR_USEC_USEC I think is one) and
> taking it from there. Testing different values are welcomed but
> upstream we should just use what we have tested with until
> we do WMM interop tests with different values and not sure if
> we'll be doing that for a while.
So how should we handle ACK timeout for different coverage class values?
That's my primary concern, since I wrote the patch to support that.
Should I just send a patch that adds an offset of 45? (= 64us - 19us,
based on the diff between calculated and initval)

- Felix