From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: a-MSDU question (bug in debugfs?)
Date: Wed, 26 Oct 2011 12:17:55 -0700 [thread overview]
Message-ID: <4EA85CE3.6030600@candelatech.com> (raw)
In-Reply-To: <1319656123.4229.11.camel@jlt3.sipsolutions.net>
On 10/26/2011 12:08 PM, Johannes Berg wrote:
> On Wed, 2011-10-26 at 12:03 -0700, Ben Greear wrote:
>> This code from net/mac80211/debugfs_sta.c appears to say that
>> if the IEEE80211_HT_CAP_MAX_AMSDU is set, we are at value 3839,
>> but elsewhere on the web it appears the opposite.
>>
>> Anyone know what is correct? I'm having no good luck finding
>> an official document about this...
>>
>> PRINT_HT_CAP((htc->cap& BIT(11)), "Max AMSDU length: "
>> "3839 bytes");
>> PRINT_HT_CAP(!(htc->cap& BIT(11)), "Max AMSDU length: "
>> "7935 bytes");
>
> iw also has the other way around and I probably would have checked
> against 802.11n. If you can't find that google for getieee
Thanks, I found the 802.11n doc. Page 69 (section 7.3.2.56) seems to indicate
this debugfs code is reversed. I'll post a patch when I
get the rest of my tree sorted out, if no one beats me to it.
Thanks,
Ben
>
> johannes
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2011-10-26 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 19:03 a-MSDU question (bug in debugfs?) Ben Greear
2011-10-26 19:08 ` Johannes Berg
2011-10-26 19:17 ` Ben Greear [this message]
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=4EA85CE3.6030600@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.