From: Rostislav Lisovy <lisovy@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Michal Sojka <sojkam1@fel.cvut.cz>,
s.sander@nordsys.de, jan-niklas.meier@volkswagen.de,
Rostislav Lisovy <rostislav.lisovy@fel.cvut.cz>
Subject: Re: [PATCH] mac80211: Parse IEEE80211_RADIOTAP_RATE on TX
Date: Mon, 25 Aug 2014 09:52:38 +0200 [thread overview]
Message-ID: <1408953158.8665.15.camel@umadbro> (raw)
In-Reply-To: <1405938028.32255.17.camel@jlt4.sipsolutions.net>
On Mon, 2014-07-21 at 12:20 +0200, Johannes Berg wrote:
> On Thu, 2014-07-10 at 14:27 +0200, Rostislav Lisovy wrote:
> > Add support for parsing radiotap field IEEE80211_RADIOTAP_RATE
> > for transmitted frames. Use the provided datarate value in
> > info->control.rates[] array so it will be used for transmission.
> >
> > Signed-off-by: Rostislav Lisovy <rostislav.lisovy@fel.cvut.cz>
> > ---
> > This feature is essential for Transmit Datarate Control (TDC)
> > in future implementation of IEEE 802.11-2012 "Wireless Access
> > for the Vehicular Environment" support.
>
> It seems like an extremely bad idea to base your implementation of WAVE
> on monitor mode with injection.
>
> Why can't you add a proper datapath?
>
You are right. I was overthinking the per-packet datarate setting a
little bit.
If I am not mistaken it is not possible to say that this feature may be
useful as the general method for monitor-mode injection with datarate
until there is some user-space utility really using/needing it?
Best regards;
Rostislav
next prev parent reply other threads:[~2014-08-25 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 12:27 [PATCH] mac80211: Parse IEEE80211_RADIOTAP_RATE on TX Rostislav Lisovy
2014-07-21 10:20 ` Johannes Berg
2014-08-25 7:52 ` Rostislav Lisovy [this message]
2014-08-29 11:12 ` 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=1408953158.8665.15.camel@umadbro \
--to=lisovy@gmail.com \
--cc=jan-niklas.meier@volkswagen.de \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rostislav.lisovy@fel.cvut.cz \
--cc=s.sander@nordsys.de \
--cc=sojkam1@fel.cvut.cz \
/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