Re: [ath5k-devel] [ath5k] Incorrect value for ACK_TIMEOUT

2010-09-15 Thread Kalle Valo
Jonathan Guerin writes: > Any chance we can 'acquire' those test plans? ;-) Most probably you need to pay kilo dollars to get access to them. -- Kalle Valo ___ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listi

Re: [ath5k-devel] [ath5k] Incorrect value for ACK_TIMEOUT

2010-09-15 Thread Kalle Valo
Jonathan Guerin writes: >> the thing is, like bob said, that we don't really know much about what the HW >> expects in some of these registers, so unless you can prove your changes to >> be >> correct - e.g. by measurements which fit the theoretical model better, or by >> better thruput, it's ha

Re: [ath5k-devel] [ath5k] Incorrect value for ACK_TIMEOUT

2010-09-15 Thread Kalle Valo
Jonathan Guerin writes: > So, we would prefer to match the spec for an out-of-the-box build, > even tho it would appear to be a worse-performing driving to users? If "an out-of-the-box build" means correctly working 802.11 device then my opinion is yes, we should strive to match the spec even if

Re: [ath5k-devel] [ath5k] Incorrect value for ACK_TIMEOUT

2010-09-15 Thread Jonathan Guerin
Any chance we can 'acquire' those test plans? ;-) -- Jonathan Guerin On Wed, Sep 15, 2010 at 5:36 PM, Kalle Valo wrote: > Jonathan Guerin writes: > >> So, we would prefer to match the spec for an out-of-the-box build, >> even tho it would appear to be a worse-performing driving to users? > > I

Re: [ath5k-devel] [ath5k] Incorrect value for ACK_TIMEOUT

2010-09-15 Thread Bruno Randolf
On Wed September 15 2010 16:27:01 Jonathan Guerin wrote: > So, we would prefer to match the spec for an out-of-the-box build, > even tho it would appear to be a worse-performing driving to users? sure, we need to comply to the specs. bruno > -- > Jonathan Guerin > > On Wed, Sep 15, 2010 at 5:17

Re: [ath5k-devel] [ath5k] Incorrect value for ACK_TIMEOUT

2010-09-15 Thread Jonathan Guerin
So, we would prefer to match the spec for an out-of-the-box build, even tho it would appear to be a worse-performing driving to users? -- Jonathan Guerin On Wed, Sep 15, 2010 at 5:17 PM, Kalle Valo wrote: > Jonathan Guerin writes: > >>> the thing is, like bob said, that we don't really know m

Re: [ath5k-devel] [ath5k] Incorrect value for ACK_TIMEOUT

2010-09-14 Thread Jonathan Guerin
On Wed, Sep 15, 2010 at 1:45 PM, Bruno Randolf wrote: > On Wed September 15 2010 12:28:36 Jonathan Guerin wrote: >> >> Should all of the init be changed to use these functions, along with >> >> #define init values? >> > >> > i think it would be best if we could remove the initvals alltoghether and

Re: [ath5k-devel] [ath5k] Incorrect value for ACK_TIMEOUT

2010-09-14 Thread Bruno Randolf
On Wed September 15 2010 12:28:36 Jonathan Guerin wrote: > >> Should all of the init be changed to use these functions, along with > >> #define init values? > > > > i think it would be best if we could remove the initvals alltoghether and > > use the function to set the ack timeout. but i'm not su

Re: [ath5k-devel] [ath5k] Incorrect value for ACK_TIMEOUT

2010-09-14 Thread Jonathan Guerin
On Wed, Sep 15, 2010 at 1:16 PM, Bruno Randolf wrote: > On Wed September 15 2010 12:01:50 Jonathan Guerin wrote: >> On Wed, Sep 15, 2010 at 12:30 PM, Bruno Randolf wrote: >> > On Wed September 15 2010 10:56:32 Jonathan Guerin wrote: >> >> According to the 802.11-2007 spec document, the ACKTimeout

Re: [ath5k-devel] [ath5k] Incorrect value for ACK_TIMEOUT

2010-09-14 Thread Bruno Randolf
On Wed September 15 2010 12:01:50 Jonathan Guerin wrote: > On Wed, Sep 15, 2010 at 12:30 PM, Bruno Randolf wrote: > > On Wed September 15 2010 10:56:32 Jonathan Guerin wrote: > >> According to the 802.11-2007 spec document, the ACKTimeout value is > >> (Section 9.2.8 ACK procedure): > >> ACKTimeou

Re: [ath5k-devel] [ath5k] Incorrect value for ACK_TIMEOUT

2010-09-14 Thread Jonathan Guerin
On Wed, Sep 15, 2010 at 1:01 PM, Jonathan Guerin wrote: >> >> on 5212 this is 1000 in A mode and 1760 in G mode, which would result in a >> timeout of 25 and 40. > > We have a 5213 chip - does this default to the 5212 branch inside ath5k? > Never mind, I found it... $$ attach.c else if (srev ==

Re: [ath5k-devel] [ath5k] Incorrect value for ACK_TIMEOUT

2010-09-14 Thread Jonathan Guerin
On Wed, Sep 15, 2010 at 12:30 PM, Bruno Randolf wrote: > On Wed September 15 2010 10:56:32 Jonathan Guerin wrote: >> 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 1

Re: [ath5k-devel] [ath5k] Incorrect value for ACK_TIMEOUT

2010-09-14 Thread Bruno Randolf
On Wed September 15 2010 10:56:32 Jonathan Guerin wrote: > 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 = 1

[ath5k-devel] [ath5k] Incorrect value for ACK_TIMEOUT

2010-09-14 Thread Jonathan Guerin
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