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: Fri, 4 Jul 2008 13:14:05 +0200 [thread overview]
Message-ID: <200807041314.05908.IvDoorn@gmail.com> (raw)
In-Reply-To: <1215169362.19862.2.camel@johannes.berg>
On Friday 04 July 2008, Johannes Berg wrote:
>
> > I just received an answer from Ralink about this issue,
>
> Cool.
>
> > 1. For 11b/g based chips rt2500, rt2570, rt61, rt73 doesn't implement this.
>
> Oh, too bad.
>
> > 2. For 11n based chips, there is one MAC register have to enable to have this feature.
> > But, Word 2 of RXWI will put the timestamp and the RSSI will put to Word 3.
> > The original Word 3 SNR will disappear and replace by RSSI.
>
> Nice.
>
> > As for the timestamps in 2400 and rt2800, they are both in 32bits, so I am not sure how
> > reliable they will be for IBSS.
>
> Well 32-bits is plenty if you can also read the TSF to extend it to 64,
> b43 only gets 16 by the firmware and we just extend it on packet RX.
Ok, I'll update rt2x00 so rt2400pci can already start reporting the timestamp,
I assume the timestamp reporting is more important then reporting the SNR,
because apparenly for rt2800 we can only get one of those. :S
Ivo
prev parent reply other threads:[~2008-07-04 11:08 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
2008-07-04 11:02 ` Ivo van Doorn
2008-07-04 11:02 ` Johannes Berg
2008-07-04 11:14 ` Ivo van Doorn [this message]
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=200807041314.05908.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).