RadioTap Archive on
 help / color / Atom feed
From: Johannes Berg <>
To: Simon Barber <>,
Subject: Re: [RFA] timestamp field
Date: Thu, 21 Jan 2016 08:40:11 +0100
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, 2016-01-20 at 09:46 -0800, Simon Barber wrote:
> I like this proposal. One aspect that is missing is to define the 
> meaning of the timestamp with aggregates. Should this field be
> present for all subframes, or just the first/last? Should the
> timestamp refer to the subframes, or the whole A-MPDU? Currently what
> I see in different generators is the MACTIME field is either the same
> for all subframes, and always refers to the whole A-MPDU - not
> individual subframes. For one generator the MACTIME was 0 for
> subframes after the 1st. Sometimes the signal strength is only
> present on the last subframe.

Yeah, I had actually noticed this - our device also has the PHY
acquisition timestamp of the A-MPDU, in all the frames. We should
probably elide it in all but the first, but if we somehow lost the
first frame that would be bad. I'm not even sure you can identify that
today at all though.

I don't think we can *standardise* the behaviour, but perhaps providing
flags for the different behaviours would at least help you identify it?

Any thoughts what flags would be useful?

> Macbooks generate radtiotap files with incorrect rate fields for 
> subframes with CRC errors.

That's a bit odd. Talk to Broadcom? ;-)

> If you look in the wireshark gerrit, you will see I have been porting
> my timeline viewer code over to the current devel mainline.

Very nice! :)


  parent reply index

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04 13:41 Johannes Berg
     [not found] ` <>
2016-01-20 12:42   ` Johannes Berg
     [not found]     ` <>
2016-01-20 17:46       ` Simon Barber
     [not found]         ` <>
2016-01-21  7:40           ` Johannes Berg [this message]
     [not found]             ` <>
2016-02-03 22:29               ` Simon Barber
2016-06-02  9:30           ` Johannes Berg
2016-06-02  9:31   ` Johannes Berg

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

RadioTap Archive on

Archives are clonable:
	git clone --mirror 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/ \
	public-inbox-index radiotap

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone