All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <j@w1.fi>
Cc: linux-wireless@vger.kernel.org, Henning Rogge <hrogge@googlemail.com>
Subject: Re: [RFC] mac80211: Add HT rates into RX status reporting
Date: Thu, 11 Dec 2008 20:24:42 +0100	[thread overview]
Message-ID: <1229023482.8081.67.camel@johannes.berg> (raw)
In-Reply-To: <20081211192251.GA5170@jm.kir.nu>

[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]

On Thu, 2008-12-11 at 21:22 +0200, Jouni Malinen wrote:
> On Thu, Dec 11, 2008 at 07:22:48PM +0100, Johannes Berg wrote:
> > On Thu, 2008-12-11 at 20:15 +0200, Jouni Malinen wrote:
> > > Yes. FreeBSD radiotap definition uses 0x80 as a flag in the rate field
> > > for indicating that it is an MCS index, not bitrate.
> 
> > Ugh. Nobody will dissect that properly.
> 
> Actually, wireshark seems to have code to dissect that..

Ok, I stand corrected. Oh well, this is a huge mess...

> Well, yes, I do need it like yesterday. I really want to have a reliable
> sniffer that I can trust on providing correct information about received
> frames. I can obviously handle a personal patch that adds this, but it
> gets more complex when asking others to capture some frames for you..

Right. We'll need A-MPDU stuff too, I guess?

> Anyway, I will move the radiotap parts into a separate patch and leave
> it to others to decide whether that should go in now or not. The best
> option (if John is willing) would likely be to get the first part
> (mac80211 driver API addition and ath9k fix/cleanup) in and pushed
> upstream while the radiotap parts would be maintained only in
> wireless-testing for the time being.

I agree, that seems best.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2008-12-11 19:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11 16:17 [RFC] mac80211: Add HT rates into RX status reporting Jouni Malinen
2008-12-11 17:16 ` Johannes Berg
2008-12-11 18:15   ` Jouni Malinen
2008-12-11 18:22     ` Johannes Berg
2008-12-11 19:22       ` Jouni Malinen
2008-12-11 19:24         ` Johannes Berg [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=1229023482.8081.67.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=hrogge@googlemail.com \
    --cc=j@w1.fi \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.