Search Linux Wireless

Re: [Madwifi-devel] How to modify acktimeout, ctstimeout and TXOP limits in MadWifi driver?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello Luis,

I'm sorry but I can understand you very well. Some questions:


What's txop?


Is the txoplimit. Is possible to change this parameter in Wmm mode with driver madwifi. but the maximum value of this is 8160 us. You have been talking about registers, but I don't understand about this question very well. The general idea is: acktimeout registers are limiting the acktimeout value. aren't it?. The limitation then is in the SW and not in the HW.

Other question is the next. is 52.8 in milisecons?. How you can obtain this value?.
I have tested that for AR5212 you have the next limitations for acktimeout:

802.11ag: 370
802.11b: 740 (just 370 x 2)

Thanks for all.

We currently do not set these values other than what is set by default
through the initvals per mode for each baseband MAC and per mode. For
ar5211 we set this to:

       /*        a/XR        aTurbo      b           g(OFDM?)
gTurbo (N/A) */
       { AR5K_TIME_OUT,
               { 0x04000400, 0x08000800, 0x20003000, 0x04000400,
0x04000400 } },

For ar5212 we set this to:

       /*        a/XR        aTurbo      b           g (DYN)     gTurbo */
       { AR5K_TIME_OUT,
               { 0x03e803e8, 0x06e006e0, 0x04200420, 0x08400840,
0x06e006e0 } },

The value set seems to have to match the PLL clock. You do this by
using ath5k_hw_htoclock() and to read from it ath5k_hw_clocktoh().

Using this for 802.11g this seems to be set to 0x840 = 2112 (base 10).

2112 / 40 = 52.8

So perhaps this is an upper limit on the ACK timeout. If so what does
this do and what is the difference in behavior between reaching a
timeout with this value than with the specific value in the rate
duration? I am not sure yet. I think one of them must trigger a
retransmit. We do at least match what the HAL current does except
remember we are currently setting the ACK bit rates to lower bit
rates.

These registers are sharply split. ACK and CTS can only use a 0x1fff
mask of the 32 bits, which is 13 bits. For each value it leaves us
with with the 3 Most Significant BIts as either unused or for some
purpose we are not yet sure how to use.

Hope this helps. Also if you end up testing and getting more
information please do let us know.

 Luis



--
Sandra Salmerón Ntutumu    <makevuy@xxxxxxxx>
Tlf. Analog: +34 91 488 8703 / Móvil: + 34 653 574 298
Tlf. IP desde FWD: 656212. Ext: 10 / Tel. IP desde EHAS: 010010
Fundación EHAS: Enlace Hispanoamericano de Salud - www.ehas.org
Telemedicina rural para zonas aisladas de países en desarrollo


-
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

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux