From: "Arend van Spriel" <arend@broadcom.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "Mahesh Palivela" <maheshp@posedge.com>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC v3] cfg80211/mac80211: 802.11ac changes
Date: Thu, 21 Jun 2012 20:34:42 +0200 [thread overview]
Message-ID: <4FE36942.1090801@broadcom.com> (raw)
In-Reply-To: <1340302471.4489.43.camel@jlt3.sipsolutions.net>
On 06/21/2012 08:14 PM, Johannes Berg wrote:
> On Thu, 2012-06-21 at 16:51 +0000, Mahesh Palivela wrote:
>
>> +/* 802.11ac VHT Capabilities */
>> +#define IEEE80211_VHT_CAP_MAX_MPDU_LENGTH_7991 0x00000001
>> +#define IEEE80211_VHT_CAP_MAX_MPDU_LENGTH_11454 0x00000002
>
> I have a feeling there should be a value for 3895, since this isn't
> really a bitfield only (it doesn't make sense to set both of these, in
> fact 3 is reserved)
These are matching the values specified for the VHP Capability Info IE.
3895 is specified as 0. Value 3 is reserved because it is not to be
regarded as a bit field.
Gr. AvS
next prev parent reply other threads:[~2012-06-21 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 16:51 [RFC v3] cfg80211/mac80211: 802.11ac changes Mahesh Palivela
2012-06-21 18:14 ` Johannes Berg
2012-06-21 18:34 ` Arend van Spriel [this message]
2012-06-21 18:39 ` Johannes Berg
2012-06-21 19:02 ` Arend van Spriel
2012-06-22 3:06 ` Mahesh Palivela
2012-06-22 6:33 ` Johannes Berg
2012-06-22 6:47 ` Mahesh Palivela
2012-06-22 6:54 ` 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=4FE36942.1090801@broadcom.com \
--to=arend@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=maheshp@posedge.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).