From: Sam Leffler <sam@errno.com>
To: David Young <dyoung@pobox.com>
Cc: Michael Wu <flamingice@sourmilk.net>,
Marcelo Tosatti <marcelo@kvack.org>,
netdev <netdev@vger.kernel.org>, Jeff Garzik <jgarzik@pobox.com>,
Dan Williams <dcbw@redhat.com>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
"John W. Linville" <linville@redhat.com>
Subject: Re: [PATCH] Marvell Libertas 8388 802.11b/g USB driver
Date: Fri, 15 Dec 2006 20:20:06 -0800 [thread overview]
Message-ID: <458373F6.4030105@errno.com> (raw)
In-Reply-To: <45836E3D.1090905@errno.com>
Sam Leffler wrote:
> David Young wrote:
>> On Fri, Dec 15, 2006 at 09:52:20PM -0500, Michael Wu wrote:
>>> On Friday 15 December 2006 17:51, Marcelo Tosatti wrote:
>>>> --- a/include/net/ieee80211_radiotap.h
>>>> +++ b/include/net/ieee80211_radiotap.h
>>>> @@ -168,6 +168,23 @@ struct ieee80211_radiotap_header {
>>>> * Unitless indication of the Rx/Tx antenna for this packet.
>>>> * The first antenna is antenna 0.
>>>> *
>>>> + * IEEE80211_RADIOTAP_RX_FLAGS u_int16_t bitmap
>>>> + *
>>>> + * Properties of received frames. See flags defined below.
>>>> + *
>>>> + * IEEE80211_RADIOTAP_TX_FLAGS u_int16_t bitmap
>>>> + *
>>>> + * Properties of transmitted frames. See flags defined below.
>>>> + *
>>>> + * IEEE80211_RADIOTAP_RTS_RETRIES u_int8_t data
>>>> + *
>>>> + * Number of rts retries a transmitted frame used.
>>>> + *
>>>> + * IEEE80211_RADIOTAP_DATA_RETRIES u_int8_t data
>>>> + *
>>>> + * Number of unicast retries a transmitted frame used.
>>>> + *
>>>> + *
>>>> * IEEE80211_RADIOTAP_FCS u32 data
>>>> *
>>>> * FCS from frame in network byte order.
>>>> @@ -187,7 +204,11 @@ enum ieee80211_radiotap_type {
>>>> IEEE80211_RADIOTAP_ANTENNA = 11,
>>>> IEEE80211_RADIOTAP_DB_ANTSIGNAL = 12,
>>>> IEEE80211_RADIOTAP_DB_ANTNOISE = 13,
>>>> - IEEE80211_RADIOTAP_EXT = 31,
>>>> + IEEE80211_RADIOTAP_RX_FLAGS = 14,
>>>> + IEEE80211_RADIOTAP_TX_FLAGS = 15,
>>>> + IEEE80211_RADIOTAP_RTS_RETRIES = 16,
>>>> + IEEE80211_RADIOTAP_DATA_RETRIES = 17,
>>>> + IEEE80211_RADIOTAP_EXT = 31
>>>> };
>>>>
>>>> /* Channel flags. */
>>> Did you send this part to netbsd also? We really don't want to fork
>>> radiotap. ;) Also, this should be in a separate patch, but I'm guessing it's
>>> all rolled together for convenience.
>> No, especially since NetBSD is where I keep the authoritative definitions.
>>
>> How have you defined RX_FLAGS and TX_FLAGS?
>>
>> BTW, IEEE80211_RADIOTAP_FCS (above) never made it into radiotap. No bit
>> is reserved.
>
> Tell that to everyone that implements it.
>
My mistake. David pointed out correctly that the mechanism for adding
the FCS out-of-line (IEEE80211_RADIOTAP_FCS) was not used. Instead
there is a flag bit that tells whether or not FCS is present (inline) in
the data. This flag bit is what I was thinking of--it's honored by
ethereal (aka wireshark), kismet, tcpdump, etc.
Sam
next prev parent reply other threads:[~2006-12-16 4:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 22:51 [PATCH] Marvell Libertas 8388 802.11b/g USB driver Marcelo Tosatti
2006-12-16 2:52 ` Michael Wu
2006-12-16 3:03 ` David Young
2006-12-16 3:55 ` Sam Leffler
2006-12-16 4:20 ` Sam Leffler [this message]
[not found] ` <20061218195723.GB7260@dmt>
2007-02-06 23:21 ` David Young
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=458373F6.4030105@errno.com \
--to=sam@errno.com \
--cc=arnd@arndb.de \
--cc=dcbw@redhat.com \
--cc=dyoung@pobox.com \
--cc=flamingice@sourmilk.net \
--cc=jgarzik@pobox.com \
--cc=linville@redhat.com \
--cc=marcelo@kvack.org \
--cc=mcgrof@gmail.com \
--cc=netdev@vger.kernel.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).