From: Ben Greear <greearb@candelatech.com>
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: Tue, 28 Jun 2011 12:51:41 -0700 [thread overview]
Message-ID: <4E0A30CD.9030006@candelatech.com> (raw)
In-Reply-To: <4E0A2F8A.8010102@fedoraproject.org>
On 06/28/2011 12:46 PM, 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.
>
> Tested at the internal wireless network of www.cs.fau.de, where 802.11n
> currently only works reliably with Windows clients.
Would be lovely if this could be per VIF, and settable through something
dynamic, even if just debugfs or similar....
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-06-28 19:51 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 [this message]
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
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=4E0A30CD.9030006@candelatech.com \
--to=greearb@candelatech.com \
--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).