From: Thomas Pedersen <thomas@cozybit.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: ath9k-devel@lists.ath9k.org,
linux-wireless <linux-wireless@vger.kernel.org>,
Bob Copeland <me@bobcopeland.com>
Subject: Re: [ath9k-devel] ath9k_htc and reported mactime
Date: Wed, 24 Oct 2012 15:08:13 -0700 [thread overview]
Message-ID: <20121024220813.GB6723@shredder> (raw)
In-Reply-To: <CAJ-VmonzYsUsSOyr34Xj9=mTpsHEbGNUS2RoN=BenqthGfakVw@mail.gmail.com>
On Wed, Oct 24, 2012 at 02:26:05PM -0700, Adrian Chadd wrote:
> On 24 October 2012 14:22, Adrian Chadd <adrian@freebsd.org> wrote:
> > Hi,
> >
> > can you please repeat this experiment but dump the TSF32/TSF64 fields
> > there as hexadecimal, rather than decimal?
> >
> > I'd like to see if this is an example of "bad TSF32->TSF64 promotion".
>
> Also, we should check to see whether the MAC is paying attention to
> any beacon frames
How? For mesh mode support we currently just reuse the WDS AP firmware vif
opmode.
> and updating _its_ timestamp using that beacon frame timer. That's
> one of the mesh-and-sta-and-ap-at-the-same-time problems - in
> STA mode, the TSF gets fudged based on the AP TSF. In other modes this
> doesn't necessarily hold.
OK, but the TSF for AP shouldn't be automatically updated on other
beacons, right?
Thanks again,
Thomas
next prev parent reply other threads:[~2012-10-24 22:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAG6hwVP5YkBEN9vZPGGEHbK=9ow2wJJ1x_BvSQbDzUscTiOHTA@mail.gmail.com>
2012-10-21 2:41 ` ath9k_htc and reported mactime Thomas Pedersen
2012-10-22 14:31 ` [ath9k-devel] " Adrian Chadd
2012-10-24 19:45 ` Thomas Pedersen
2012-10-24 21:22 ` Adrian Chadd
2012-10-24 21:26 ` Adrian Chadd
2012-10-24 22:08 ` Thomas Pedersen [this message]
2012-10-24 23:33 ` Adrian Chadd
2012-10-25 1:54 ` Adrian Chadd
2012-10-25 2:13 ` Adrian Chadd
2012-10-25 20:42 ` Adrian Chadd
2012-10-25 22:25 ` Thomas Pedersen
2012-10-25 22:27 ` Adrian Chadd
2012-10-26 0:41 ` Thomas Pedersen
2012-10-26 0:42 ` Adrian Chadd
2012-10-24 22:04 ` Thomas Pedersen
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=20121024220813.GB6723@shredder \
--to=thomas@cozybit.com \
--cc=adrian@freebsd.org \
--cc=ath9k-devel@lists.ath9k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).