From: Jonathan Guerin <jonathan@guerin.id.au>
To: Bob Copeland <me@bobcopeland.com>, Nick Kossifidis <mickflemm@gmail.com>
Cc: Bruno Randolf <br1@einfach.org>,
ath5k-devel <ath5k-devel@lists.ath5k.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [ath5k-devel] [support] ath5k contention windows
Date: Wed, 15 Sep 2010 13:20:15 +1000 [thread overview]
Message-ID: <AANLkTi=EhtU-ahDRdP+qqQ5hYcVtMmw_=RiYc95fDAU4@mail.gmail.com> (raw)
In-Reply-To: <20100915030444.GB8429@hash.localnet>
On Wed, Sep 15, 2010 at 1:04 PM, Bob Copeland <me@bobcopeland.com> wrote:
>
> Just a wild guess, driver may include a small fudge factor to account
> for time spent in qcu. At one point I compared all of the initvals
> to those from the HAL; we're at least bug-compatible with it if there
> are errors here.
But, the SIFS and SLOT_TIME values should already account for those times?
>From the spec (Section 9.2.10 DCF timing relations):
aSIFSTime is: aRxRFDelay + aRxPLCPDelay + aMACProcessingDelay +
aRxTxTurnaroundTime.
aSlotTime is: aCCATime + aRxTxTurnaroundTime + aAirPropagationTime +
aMACProcessingDelay.
>
>> By the way, I may be completely wrong about some of these things, I'm
>> just going off the understanding I have regarding the register values.
>
> Well mostly no one has looked at them, so you may well have found
> some problems.
>
> FWIW if you use coverage classes (not default), we appear to use the
> right values there.
I'm going to plead ignorance here and say that I'm not sure what you
mean by coverage classes...
>
> --
> Bob Copeland %% www.bobcopeland.com
>
> _______________________________________________
> ath5k-devel mailing list
> ath5k-devel@lists.ath5k.org
> https://lists.ath5k.org/mailman/listinfo/ath5k-devel
>
prev parent reply other threads:[~2010-09-15 3:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTi=azJS6bn7-=Bbb--ibACaQWqv4ZGLMUpfxynm7@mail.gmail.com>
2010-09-14 5:53 ` [support] ath5k contention windows Jonathan Guerin
2010-09-15 3:40 ` Jonathan Guerin
2010-09-15 3:48 ` [ath5k-devel] " Bruno Randolf
2010-09-14 17:39 ` Bob Copeland
2010-09-14 23:07 ` Jonathan Guerin
2010-09-15 0:44 ` Jonathan Guerin
2010-09-15 1:47 ` Bruno Randolf
2010-09-15 1:58 ` Jonathan Guerin
2010-09-14 22:48 ` Nick Kossifidis
2010-09-14 23:07 ` Jonathan Guerin
2010-09-15 0:58 ` Bruno Randolf
2010-09-15 1:06 ` Jonathan Guerin
2010-09-15 3:04 ` Bob Copeland
2010-09-15 3:20 ` Jonathan Guerin [this message]
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='AANLkTi=EhtU-ahDRdP+qqQ5hYcVtMmw_=RiYc95fDAU4@mail.gmail.com' \
--to=jonathan@guerin.id.au \
--cc=ath5k-devel@lists.ath5k.org \
--cc=br1@einfach.org \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=mickflemm@gmail.com \
/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.