linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: rt61 and TSF reporting?
Date: Tue, 1 Jul 2008 13:41:38 +0200	[thread overview]
Message-ID: <200807011341.38815.IvDoorn@gmail.com> (raw)
In-Reply-To: <1214911794.29181.3.camel@johannes.berg>

On Tuesday 01 July 2008, Johannes Berg wrote:
> On Tue, 2008-07-01 at 13:15 +0200, Ivo van Doorn wrote:
> > On Tuesday 01 July 2008, Johannes Berg wrote:
> > > 
> > > > > > Note that these undocumented fields only are present in rt2500pci and rt61pci.
> > > > > 
> > > > > Ok cool, I'll play with that, I should be able to make a patch myself,
> > > > > thanks.
> > > > 
> > > > Oh wait, just found a reference about those RXD words:
> > > > 
> > > >  * The following fields are for DMA block and HOST usage only.
> > > >  * Can't be touched by ASIC MAC block.
> > > > 
> > > > In other words, they are for driver usage only. :S
> > > 
> > > The only ones that are ever non-zero are 0, 1, 4 and 5. Guess not then.
> > 
> > 4 contains data?
> > 2 and 3 I understand since HW crypto is disabled in wireless-testing,
> > but that should mean that 4 should also be 0 unless my estimation about
> > it being the ICV field is wrong...
> > 
> > What data is in there?
> 
> Heh. I was connected to an encrypted AP with a different device and
> monitoring the traffic no that channel, and got the following:
> 
> [139528.433872] rt61pci rx word 4: 0x60483004
> [139528.433882] rt61pci rx word 5: 0x012c30a8
> [139528.468947] rt61pci rx word 4: 0x60483004
> [139528.468956] rt61pci rx word 5: 0x01566138
> [139528.571350] rt61pci rx word 4: 0x60483004
> [139528.571361] rt61pci rx word 5: 0x1dba1048
> [139528.673744] rt61pci rx word 4: 0x60483004
> [139528.673753] rt61pci rx word 5: 0x18e02078
> [139528.776153] rt61pci rx word 4: 0x60483004
> [139528.776165] rt61pci rx word 5: 0x01568018
> [139528.878538] rt61pci rx word 4: 0x60483004
> [139528.878549] rt61pci rx word 5: 0x072a9048
> 
> In fact, through the whole uptime of the card word 4 never changed, so
> maybe it's just bogus data from the disabled hwcrypto engine.

Ok, I'll run some experiments with HW crypto enabled and see if the value
is different for each frame in there.

Ivo


  reply	other threads:[~2008-07-01 11:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01 10:26 rt61 and TSF reporting? Johannes Berg
2008-07-01 10:47 ` Ivo van Doorn
2008-07-01 10:48   ` Johannes Berg
2008-07-01 11:05     ` Ivo van Doorn
2008-07-01 11:06       ` Johannes Berg
2008-07-01 11:15         ` Ivo van Doorn
2008-07-01 11:29           ` Johannes Berg
2008-07-01 11:41             ` Ivo van Doorn [this message]
2008-07-04 11:02 ` Ivo van Doorn
2008-07-04 11:02   ` Johannes Berg
2008-07-04 11:14     ` Ivo van Doorn

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=200807011341.38815.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.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 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).