From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Why is wmm_param required for HT40- in mlme.c
Date: Mon, 31 Jan 2011 18:40:59 +0100 [thread overview]
Message-ID: <1296495659.3812.36.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4D46F2E2.3090905@candelatech.com>
On Mon, 2011-01-31 at 09:35 -0800, Ben Greear wrote:
> > No, I got confused. 802.11n says an HT STA is a QoS STA (5.2.9), but in
> > practice WMM is tested/certified instead of QoS.
>
> So maybe we can remove that check for wmm_param, but put in a printk
> to warn users that their AP is probably mis-configured?
Yes, but there are hidden assumptions that WMM is available throughout
the code that we need to hunt down first -- I'm sure there are some in
the aggregation code for example since aggregation can only work when
QoS/WMM is enabled.
johannes
next prev parent reply other threads:[~2011-01-31 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 5:38 Why is wmm_param required for HT40- in mlme.c Ben Greear
2011-01-30 9:36 ` Johannes Berg
2011-01-30 17:34 ` Ben Greear
2011-01-31 11:03 ` Johannes Berg
2011-01-31 17:35 ` Ben Greear
2011-01-31 17:40 ` Johannes Berg [this message]
2011-01-30 17:41 ` Pat Erley
2011-01-31 11:28 ` Jouni Malinen
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=1296495659.3812.36.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--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 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).