radiotap.netbsd.org archive mirror
 help / color / mirror / Atom feed
From: Simon Barber <simon-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
To: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
Cc: radiotap-S783fYmB3Ccdnm+yROfE0A@public.gmane.org
Subject: Re: [RFC] L-SIG field
Date: Mon, 2 Jul 2018 10:45:58 -0700	[thread overview]
Message-ID: <2C890112-D4D8-4764-8A0E-1544E21457A5@superduper.net> (raw)
In-Reply-To: <1530542232.3117.5.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>

I'd love to see this! It would be very useful for the Wireshark timeline, to accurately display aggregate duration when not all the subframes are passed up by the driver.

Simon

> On Jul 2, 2018, at 7:37 AM, Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org> wrote:
> 
> Looks like we need this, any thoughts? Seems like a straight-forward
> extension.
> 
> ---
> title: L-SIG
> categories: [suggested]
> ---
> Bit Number
> : 27 (tentatively assigned, field data may change)
> 
> Structure
>  - u16 data1, data2
> 
> Required Alignment
> : 2
> 
> Unit(s)
> : none
> 
> This field indicates - if known - the contents of the L-SIG.
> 
> ## data1
> 
> | **`0x0001`** | rate known |
> | **`0x0002`** | length known |
> | **`0xfffc`** | (reserved) |
> 
> ## data2
> 
> | **`0x000f`** | rate |
> | **`0xfff0`** | length |
> 

      parent reply	other threads:[~2018-07-02 17:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02 14:37 [RFC] L-SIG field Johannes Berg
     [not found] ` <1530542232.3117.5.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2018-07-02 17:45   ` Simon Barber [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=2C890112-D4D8-4764-8A0E-1544E21457A5@superduper.net \
    --to=simon-vp0mx6+5gkqfx2apin6yfw@public.gmane.org \
    --cc=johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
    --cc=radiotap-S783fYmB3Ccdnm+yROfE0A@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
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).