linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Thu, 25 Oct 2012 17:41:16 -0700	[thread overview]
Message-ID: <20121026004116.GF20609@shredder> (raw)
In-Reply-To: <CAJ-Vmok3+ts43ow_Btj7sG3DfWNeD7O=gNWagJrSGkBWFvyQMQ@mail.gmail.com>

On Thu, Oct 25, 2012 at 03:27:39PM -0700, Adrian Chadd wrote:
> On 25 October 2012 15:25, Thomas Pedersen <thomas@cozybit.com> wrote:
> 
> >> Thomas, is the TSF in the RX status descriptor actually 32 bits, or is
> >> this a printing error?
> >
> > Looking at the printk again, I'm pretty sure I'm just an idiot and the
> > printed value is being truncated to 32 bits. Will test and verify the
> > TSF wraps correctly again.

Yep, the TSF actually wraps to 64 bits correctly :|

[ 4394.156056] got beacon with ts         ABA184D3 from 00:03:7f:10:4e:0a at         FEF0D969, now:         FEF0DC84. offset == -795
[ 4395.723180] got beacon with ts        1020E8597 from 00:03:7f:10:4e:1a at         FF08C20E, now:         FF08C526. offset == -792
[ 4397.771811] got beacon with ts        1022DC649 from 00:03:7f:10:4e:1a at         FF2802BC, now:         FF280671. offset == -949
[ 4406.446193] got beacon with ts         AC5D0568 from 00:03:7f:10:4e:0a at         FFAC5A30, now:         FFAC5D68. offset == -824
[ 4412.109937] got beacon with ts        103088637 from 00:03:7f:10:4e:1a at        10002C292, now:        10002C5F0. offset == -862
[ 4416.205946] got beacon with ts        10347041B from 00:03:7f:10:4e:1a at        100414070, now:        100414376. offset == -774
[ 4418.253827] got beacon with ts        103664224 from 00:03:7f:10:4e:1a at        100607E74, now:        1006081C7. offset == -851
[ 4418.735826] got beacon with ts         AD188414 from 00:03:7f:10:4e:0a at        10067D90F, now:        10067DC4B. offset == -828

Thanks,
Thomas

  reply	other threads:[~2012-10-26  0:41 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
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 [this message]
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=20121026004116.GF20609@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).