From: Rafael Laufer <rlaufer@CS.UCLA.EDU>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Gábor Stefanik" <netrolller.3d@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] Implementation of the IEEE80211_RADIOTAP_RATE option
Date: Sat, 22 Aug 2009 15:03:56 -0700 [thread overview]
Message-ID: <4A906B4C.6010208@cs.ucla.edu> (raw)
In-Reply-To: <1250927308.23605.6.camel@johannes.local>
Johannes Berg wrote:
> On Fri, 2009-08-21 at 11:03 -0700, Rafael Laufer wrote:
>
>
>> + * @IEEE80211_TX_CTL_RATE_RADIOTAP: completely internal to mac80211,
>> + * used to indicate that the rate was defined in the received radiotap
>> + * header and therefore the rate control algorithm should not change it.
>>
>
> This should be an internal flag, the driver doesn't care.
>
right, and where are those set?
>
>> + /* In monitor mode, if the IEEE80211_RADIOTAP_RATE option is set in
>> + * the received radiotap header, do not call the rate control algorithm.
>> + */
>>
>
> coding style
>
>
>> + /* Get the rate parameter from the radiotap header,
>> + * allowing rate selection on a per-packet basis
>> + */
>>
>
> coding style
>
I am a newbie, I am gonna look into the coding style, but I assume you
are talking about the missing blank line in the beginning
>
>> + case IEEE80211_RADIOTAP_RATE:
>> + bitrate = (*iterator.this_arg) * 5;
>> + for (i = 0; i < sband->n_bitrates; i++) {
>> + if (sband->bitrates[i].bitrate == bitrate)
>> + break;
>> + }
>> + if (i != sband->n_bitrates) {
>> + info->control.rates[0].idx = i;
>> + info->flags |= IEEE80211_TX_CTL_RATE_RADIOTAP;
>> + }
>>
>
> You never set the counter, or any other fields.
>
This is a good point and now I see that Gábor pointed this out as well.
There are other fields in the radiotap header that define the RTS and
DATA retries. However, if those fields are not set, there must be a
default value in this case. Are there any?
>
>> /*
>> * Please update the file
>> * Documentation/networking/mac80211-injection.txt
>>
>
> And you even quote the instructions.
>
come on...
Rafael
next prev parent reply other threads:[~2009-08-22 22:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 0:40 [PATCH] Implementation of the IEEE80211_RADIOTAP_RATE option Rafael Laufer
2009-08-21 8:18 ` Johannes Berg
2009-08-21 13:30 ` Gábor Stefanik
2009-08-21 18:03 ` Rafael Laufer
2009-08-21 18:52 ` Gábor Stefanik
2009-08-21 19:06 ` Rafael Laufer
2009-08-21 19:57 ` Gábor Stefanik
2009-08-21 20:21 ` Rafael Laufer
2009-08-21 20:24 ` Rafael Laufer
2009-08-22 7:50 ` Johannes Berg
2009-08-22 22:05 ` Rafael Laufer
2009-08-22 7:48 ` Johannes Berg
2009-08-22 22:03 ` Rafael Laufer [this message]
2009-08-23 8:06 ` Kalle Valo
2009-08-23 9:11 ` 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=4A906B4C.6010208@cs.ucla.edu \
--to=rlaufer@cs.ucla.edu \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netrolller.3d@gmail.com \
/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).