From: Henning Rogge <hrogge@googlemail.com>
To: Jouni Malinen <j@w1.fi>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
"Stefanik Gábor" <netrolller.3d@gmail.com>,
"Jouni Malinen" <jouni.malinen@atheros.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
"Thomas d'Otreppe" <tdotreppe@aircrack-ng.org>
Subject: Re: [PATCH 3/3] mac80211: Add HT rates into radiotap
Date: Fri, 12 Dec 2008 16:31:51 +0100 [thread overview]
Message-ID: <200812121631.56952.hrogge@googlemail.com> (raw)
In-Reply-To: <20081212151619.GA16981@jm.kir.nu>
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
On Friday 12 December 2008 16:16:19 Jouni Malinen wrote:
> While I'm not against defining something more officially for radiotap,
> I do not agree with the part about this format being that brain-dead.
> Both 40 MHz and short GI are indicated (IEEE80211_CHAN_TURBO and
> IEEE80211_RADIOTAP_F_SHORTGI) and shown in the current wireshark
> release.
Changing the meaning of the old "txrate" field (by putting an index inside) is
a great way to break the userspace interface to any existing program. :(
Just get a new field for the mcs index.
Henning
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-12-12 15:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 12:38 [PATCH 0/3] mac80211: HT rate reporting in RX status Jouni Malinen
2008-12-12 12:38 ` [PATCH 1/3] mac80211: Add HT rates into RX status reporting Jouni Malinen
2008-12-12 15:47 ` Johannes Berg
2008-12-12 12:38 ` [PATCH 2/3] ath9k: Report HT rates in RX status Jouni Malinen
2008-12-12 12:38 ` [PATCH 3/3] mac80211: Add HT rates into radiotap Jouni Malinen
2008-12-12 14:47 ` Stefanik Gábor
2008-12-12 14:48 ` Johannes Berg
2008-12-12 15:16 ` Jouni Malinen
2008-12-12 15:31 ` Henning Rogge [this message]
2008-12-12 16:34 ` Jouni Malinen
2008-12-12 15:50 ` Johannes Berg
2008-12-12 15:49 ` 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=200812121631.56952.hrogge@googlemail.com \
--to=hrogge@googlemail.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=jouni.malinen@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netrolller.3d@gmail.com \
--cc=tdotreppe@aircrack-ng.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.