update ath5k_beacon_update_timers() for better beacon timer calculation in a
variety of situations. most important is the possibility to call it with the
timestamp of a received beacon, when we detected that a HW merge has happened
and we need to reconfigure the beacon timers based on that.
we
use SWBA (software beacon alert) interrupts to keep track of the next beacon
time und check if a HW merge (automatic TSF update) has happened on every
received beacon with the same BSSID.
this is necessary because the atheros hardware will silently update the local
TSF in IBSS mode, but not its
in 11.1.2.2 Beacon generation in an IBSS the IEEE802.11 standard says, each
STA should... b) Calculate a random delay uniformly distributed in the range
between zero and twice aCWmin × aSlotTime,.
configure cwmin and cwmax of the beacon queue in IBSS mode according to this.
unfortunately beacon
On 01/19/2008 03:49 AM, Bruno Randolf wrote:
* use only one debug level for beacon debugging: unify ATH5K_DEBUG_BEACON and
ATH5K_DEBUG_BEACON_PROC
* remove debug level ATH5K_DEBUG_FATAL. doesn't make sense as a debug level -
if it's fatal it should be logged as an error.
* fancier
+ qi.tqi_cw_max = 2 * ah-ah_cw_min;
Have you checked ath5k_hw_reset_tx_queue ? cw_min/cw_max is
recalculated there, maybe we are doing something wrong there...
--
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
On Jan 18, 2008 7:50 AM, Bruno Randolf [EMAIL PROTECTED] wrote:
always extend the rx timestamp with the local TSF, since this information is
also needed for proper IBSS merging. this is done in the tasklet for now,
maybe
has to be moved to the interrupt handler like in madwifi.
Hi,
On Sat, 19 Jan 2008, Luis R. Rodriguez wrote:
On Jan 18, 2008 7:50 AM, Bruno Randolf [EMAIL PROTECTED] wrote:
+* always extend the mac timestamp, since this information
is
+* also needed for proper IBSS merging.
+*
+
