From: Johannes Berg <johannes@sipsolutions.net>
To: Roberto Riggio <roberto.riggio@create-net.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Use case for the radiotap rate patch
Date: Mon, 22 Nov 2010 10:01:04 -0800 [thread overview]
Message-ID: <1290448864.5718.3.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4CEAAFB1.1020707@create-net.org>
On Mon, 2010-11-22 at 19:00 +0100, Roberto Riggio wrote:
> Il 22/11/2010 16:39, Johannes Berg ha scritto:
> > radiotap now has a way to specify one attribute multiple times, so that
> > should be used for MRR
> Is there a patch available for the linux kernel that supports this
> new approach to specify the MRR? I can easly modify the click
> radiotap header generation code, but without the support in
> the kernel it would be rather pointless.
The kernel parser will support this, but you'd have to provide the code
to actually use multiple rates as MRR
johannes
prev parent reply other threads:[~2010-11-22 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 10:47 Use case for the radiotap rate patch Roberto Riggio
2010-11-22 15:39 ` Johannes Berg
2010-11-22 18:00 ` Roberto Riggio
2010-11-22 18:01 ` 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=1290448864.5718.3.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=roberto.riggio@create-net.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).