From: Jouni Malinen <j@w1.fi>
To: Michel Alexandre Salim <salimma@fedoraproject.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net,
"Luis R. Rodriguez" <lrodriguez@atheros.com>,
Jouni Malinen <jmalinen@atheros.com>,
Vasanthakumar Thiagarajan <vasanth@atheros.com>,
Senthil Balasubramanian <senthilkumar@atheros.com>
Subject: Re: [PATCH] ath9k: add module option for disabling 11n functionality
Date: Wed, 29 Jun 2011 00:57:57 +0300 [thread overview]
Message-ID: <20110628215757.GA14975@jm.kir.nu> (raw)
In-Reply-To: <4E0A2F8A.8010102@fedoraproject.org>
On Tue, Jun 28, 2011 at 09:46:18PM +0200, Michel Alexandre Salim wrote:
> Some wireless base stations implement 802.11n mode in ways that
> open-source drivers cannot handle properly, resulting in very
> unstable connections. This patch introduces an '11n_disable' option
> to the ath9k driver, similar to the same option for the iwlagn
> driver.
What is so special about this that makes it impossible for open source
drivers to handle? The proper approach here would be to figure out what
is causing the interop issue and fix (or more likely, work around) that.
In addition, if this is really needed, why would this be a driver
specific hack rather than providing a shared mechanism in mac80211 to
disable 802.11n support? It would sound strange if there would need to
be a new module parameter in every 802.11n driver to handle something
like this.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2011-06-28 21:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 19:46 [PATCH] ath9k: add module option for disabling 11n functionality Michel Alexandre Salim
2011-06-28 19:51 ` Ben Greear
2011-06-28 20:06 ` [ath9k-devel] " Luis R. Rodriguez
2011-06-28 20:40 ` Ben Greear
2011-06-29 17:50 ` Andreas Hartmann
2011-06-28 21:57 ` Jouni Malinen [this message]
2011-06-29 1:26 ` Adrian Chadd
2011-06-29 8:56 ` Michel Alexandre Salim
2011-06-29 13:09 ` Jouni Malinen
2011-06-29 13:43 ` Michel Alexandre Salim
2011-06-29 13:55 ` Jouni Malinen
2011-06-29 14:06 ` Michel Alexandre Salim
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=20110628215757.GA14975@jm.kir.nu \
--to=j@w1.fi \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=jmalinen@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=salimma@fedoraproject.org \
--cc=senthilkumar@atheros.com \
--cc=vasanth@atheros.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).