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 12:47:57 +0200 [thread overview]
Message-ID: <200807011247.57739.IvDoorn@gmail.com> (raw)
In-Reply-To: <1214907990.7763.40.camel@johannes.berg>
Hi,
> Is there any way to get rt61 to report the receive timestamp? That would
> be very useful for monitor mode and good for IBSS.
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. ;)
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.
Neither rt2500usb or rt73usb contain them, which means that they can't report the TSF
based on descriptor information.
Ivo
next prev parent reply other threads:[~2008-07-01 10:43 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 [this message]
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
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=200807011247.57739.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).