All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benoit PAPILLAULT <benoit.papillault@free.fr>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath9k: Avoid acktimeout wraps around at bootstrap
Date: Tue, 27 Apr 2010 21:28:09 +0200	[thread overview]
Message-ID: <4BD73AC9.8070005@free.fr> (raw)
In-Reply-To: <v2mf74418681004270409i80853db1n6cf8bbb2cf68c6c0@mail.gmail.com>

Lorenzo Bianconi a ?crit :
> Hi all,
>
> I am using ath9k/mac80211 on a PC Engines Alix with a Mikrotik R52n
> card (AR9280 chipset), OpenWrt r21030 (kernel 2.6.32.10) and
> compat-wireless-2010-04-21. I am injecting packets using a VAP in
> monitor mode.
> I have a doubt on ath9k_hw_init_defaults() in hw.c. In particular
> during the bootstrap ah->slottime in ath9k_hw_init_defaults() is set
> to " (u32) -1", so after a HW reset (for example as a result of a
> channel change) in the function ath9k_hw_init_global_settings() the
> acktimeout variable wraps around as ah->slottime is 0xFFFFFFFF and
>
> acktimeout = sifstime + ah->slottime + 3 * ah->coverage_class
>
> In this way we obtain that acktimout is set to 15 us (assuming
> ah->coverage_class set to 0) in the 5GHZ band so less than one of its
> summands (sifstime = 16).
> I wrote this simple patch in order to set ah->slottime to standard
> value for OFDM PHY layer during bootstrap.
>   
Does this have any visible effect or is this patch for strict 
compliance? I am asking this since I see very strange stuff regarding 
ACK (delayed, missing, out of order, ...)

Regards,
Benoit

  reply	other threads:[~2010-04-27 19:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27 11:09 [ath9k-devel] [PATCH] ath9k: Avoid acktimeout wraps around at bootstrap Lorenzo Bianconi
2010-04-27 19:28 ` Benoit PAPILLAULT [this message]
2010-04-27 21:46   ` Lorenzo Bianconi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BD73AC9.8070005@free.fr \
    --to=benoit.papillault@free.fr \
    --cc=ath9k-devel@lists.ath9k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.