From: Johannes Berg <johannes@sipsolutions.net>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: rt61 and TSF reporting?
Date: Tue, 01 Jul 2008 12:48:34 +0200 [thread overview]
Message-ID: <1214909314.7763.43.camel@johannes.berg> (raw)
In-Reply-To: <200807011247.57739.IvDoorn@gmail.com> (sfid-20080701_124340_925081_6971CC60)
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
Hi,
> The specsheets say nothing about TSF timestamps anywhere else then
> the registers (which is accessed by the get_tsf() callback function).
> To be more exact, the specsheets say _nothing_ about the RXD descriptors at all,
> which means they are not helpful for that. ;)
Heh.
> However there are a few RXD fields which are labeled as "reserved" which could
> mean the field is present, just not documented.
>
> You could try printing the values of those words to see if they contain valid data,
> and to be more exact the TSF data (this can be done in the function rt61pci_fill_rxdone(...))
> The undocumented/reserved words are: 6 to 15
>
> Do you want me to come up with a patch for this?
>
> 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.
> Neither rt2500usb or rt73usb contain them, which means that they can't report the TSF
> based on descriptor information.
So I guess they just don't transfer those reserved fields on USB.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-07-01 10:49 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 [this message]
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
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=1214909314.7763.43.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=ivdoorn@gmail.com \
--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).