RadioTap Archive on lore.kernel.org
 help / color / Atom feed
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Simon Barber <simon-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
Cc: Thomas Pedersen <thomas-W/OLz77bvjtBDgjK7y7TUQ@public.gmane.org>,
	"radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org"
	<radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org>
Subject: Re: TSFT
Date: Wed, 21 Nov 2012 11:42:32 +0100
Message-ID: <1353494552.10444.18.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <50AC0791.3040005-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>

On Tue, 2012-11-20 at 14:43 -0800, Simon Barber wrote:
> One problem with fixing the calculations is that quite a lot of 
> information is needed to do the calculation correctly. In Intel's case I 
> don't know if Ness information is available, and this makes upto a 16us 
> difference in the PLCP header length.
> 
> Calculating the start of the MPDU from the end accurately requires 
> knowing the FEC scheme, the MCS, the guard interval, the bandwidth. Is 
> the FEC scheme known, or are all current cards only supporting BCC?

Good question, I don't really know.

> Do you know if Intel supports extension spatial streams? If not the 
> number is always 0. And FEC - is it always BCC?

I don't think our devices support extension spatial streams or anything
but BCC.

Overall though, I think there's an argument to be made here for simply
introducing a new radiotap timestamp field that gives the timestamp at
the end of the frame? This could be defined better and would be more
accurate.

I'm not sure I'd want to redefine the existing field in any way since
there are probably a whole bunch of implementations out there that just
stick whatever timestamp they have into the field, without regard for
where it is in the frame, and without regard for aggregation.

johannes

      parent reply index

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-17  6:26 TSFT Simon Barber
     [not found] ` <50A72E17.6070207-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
2012-11-17  6:48   ` TSFT David Young
     [not found]     ` <20121117064848.GO21779-Gq8g4XVd89tWk0Htik3J/w@public.gmane.org>
2012-11-17  8:45       ` TSFT Johannes Berg
     [not found]         ` <1353141950.9543.3.camel-8Nb76shvtaUJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2012-11-17 17:46           ` TSFT David Young
     [not found]             ` <20121117174600.GQ21779-Gq8g4XVd89tWk0Htik3J/w@public.gmane.org>
2012-11-17 18:43               ` TSFT Johannes Berg
2012-11-17 18:56               ` TSFT Guy Harris
2012-11-17 23:26   ` TSFT Thomas Pedersen
2012-11-18  7:20     ` TSFT Simon Barber
     [not found]       ` <50A88C3D.5030809-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
2012-11-18 11:07         ` TSFT Johannes Berg
     [not found]           ` <1353236845.9649.6.camel-8Nb76shvtaUJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2012-11-20 22:43             ` TSFT Simon Barber
     [not found]               ` <50AC0791.3040005-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
2012-11-21 10:42                 ` Johannes Berg [this message]

Reply instructions:

You may reply publically 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=1353494552.10444.18.camel@jlt4.sipsolutions.net \
    --to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
    --cc=radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org \
    --cc=simon-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org \
    --cc=thomas-W/OLz77bvjtBDgjK7y7TUQ@public.gmane.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

RadioTap Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/radiotap/0 radiotap/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 radiotap radiotap/ https://lore.kernel.org/radiotap \
		radiotap@radiotap.org
	public-inbox-index radiotap

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.netbsd.radiotap


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git