From: Johannes Berg <johannes@sipsolutions.net>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Jonas Gorski <jogo@openwrt.org>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
Nishant Sarmukadam <nishants@marvell.com>,
Yogesh Ashok Powar <yogeshp@marvell.com>,
Lennert Buytenhek <buytenh@wantstofly.org>
Subject: Re: [RFC/RFT] mwl8k: don't expose non-standard rates
Date: Sat, 13 Apr 2013 18:18:19 +0200 [thread overview]
Message-ID: <1365869899.1089.0.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CAJ-VmokacZUw1Wru_0w1XaVRoZWP6nOMcdKo=1yhP-C9rbifHg@mail.gmail.com> (sfid-20130413_162928_260950_E23BA078)
On Sat, 2013-04-13 at 07:29 -0700, Adrian Chadd wrote:
> Hi,
>
> On 13 April 2013 03:31, Jonas Gorski <jogo@openwrt.org> wrote:
> > Do not advertise the non standard rates 22 Mbps and 72 Mbps to mac80211,
> > they will make it into the probe responses and cause clients checking them
> > to refuse association, e.g. wpa_supplicant says:
>
> Are these "turbo" mode rates? ie, 40MHz wide channels with pre-11n
> rates on them?
22 actually *is* a standard rate, it's just that almost nobody
implements it.
The original problem seems a bit strange though, seems those should just
not be marked basic?
johannes
next prev parent reply other threads:[~2013-04-13 16:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 10:31 [RFC/RFT] mwl8k: don't expose non-standard rates Jonas Gorski
2013-04-13 14:29 ` Adrian Chadd
2013-04-13 16:18 ` Johannes Berg [this message]
2013-04-13 18:59 ` Adrian Chadd
2013-04-13 22:08 ` Felix Fietkau
2013-04-14 10:49 ` Jonas Gorski
2013-04-14 12:11 ` [PATCH] mwl8k: remove nonstandard rate 72 Mbps Jonas Gorski
2013-04-15 6:38 ` Yogesh Ashok Powar
2013-04-15 7:53 ` Jonas Gorski
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=1365869899.1089.0.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=adrian@freebsd.org \
--cc=buytenh@wantstofly.org \
--cc=jogo@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=nishants@marvell.com \
--cc=yogeshp@marvell.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).