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 19:22:48 +0100 [thread overview]
Message-ID: <1229019768.8081.53.camel@johannes.berg> (raw)
In-Reply-To: <20081211181545.GB32500@jm.kir.nu>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
On Thu, 2008-12-11 at 20:15 +0200, Jouni Malinen wrote:
> > Can we just leave off the bitrate for HT for now?
>
> Yes. FreeBSD radiotap definition uses 0x80 as a flag in the rate field
> for indicating that it is an MCS index, not bitrate. That works fine
> here, too, and I'll update my patch to use the same style. No more
> bitrate calculation for HT rates in mac80211 after that..
Ugh. Nobody will dissect that properly. Do you actually need this
information in userland _now_? Otherwise, Dave Young is moving the list
elsewhere and then we can properly define this in radiotap rather than
going with some other set. 0x80 in flags (not rate) is used to indicate
short-GI in wireshark, and it's all very confusing... I'd rather see a
new "HT rate" field added to radiotap.
> I did not want to think about anything for IBSS.. ;-) One should just
> probe the other STA if you want to learn what it can do..
Right. Who cares about IBSS :)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-12-11 18:23 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 [this message]
2008-12-11 19:22 ` Jouni Malinen
2008-12-11 19:24 ` 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:
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=1229019768.8081.53.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox