I used the previous commit scheme (mac80211: Parse legacy and HT rate
in injected frames).
I will rewrite the documentation. Should I send v3 or a different patch?

Regards,
Lorenzo

On Tue, Feb 23, 2016 at 11:10 AM, Johannes Berg
<[email protected]> wrote:
> On Fri, 2016-02-19 at 11:43 +0100, Lorenzo Bianconi wrote:
>> Add VHT radiotap parsing support to ieee80211_parse_tx_radiotap().
>> That capability has been tested using a d-link dir-860l rev b1
>> running
>> OpenWrt trunk and mt76 driver
>>
>> Signed-off-by: Lorenzo Bianconi <[email protected]>
>> ---
>>  Documentation/networking/mac80211-injection.txt | 10 ++++++++
>>  net/mac80211/tx.c                               | 31
>> +++++++++++++++++++++++++
>>  2 files changed, 41 insertions(+)
>>
>> diff --git a/Documentation/networking/mac80211-injection.txt
>> b/Documentation/networking/mac80211-injection.txt
>> index ec8f934..ef57cc0 100644
>> --- a/Documentation/networking/mac80211-injection.txt
>> +++ b/Documentation/networking/mac80211-injection.txt
>> @@ -45,6 +45,16 @@ radiotap headers and used to control injection:
>>     number of retries when either IEEE80211_RADIOTAP_RATE or
>>     IEEE80211_RADIOTAP_MCS was used
>>
>> + * IEEE80211_RADIOTAP_VHT
>> +
>> +   VHT rate for the transmission (only for devices without own rate
>> control).
>> +   Also some flags are parsed
>> +
>> +   IEEE80211_TX_RC_SHORT_GI: use short guard interval
>> +   IEEE80211_TX_RC_40_MHZ_WIDTH: send in HT40 mode
>> +   IEEE80211_TX_RC_80_MHZ_WIDTH: send in HT80 mode
>> +   IEEE80211_TX_RC_160_MHZ_WIDTH: send in HT160 mode
>>
> This makes no sense, those are mac80211 internal flags, should document
> the radiotap flags here, not what they map to internally.
>
> johannes



-- 
UNIX is Sexy: who | grep -i blonde | talk; cd ~; wine; talk; touch;
unzip; touch; strip; gasp; finger; gasp; mount; fsck; more; yes; gasp;
umount; make clean; sleep
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to