All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Hartmann <andihartmann@01019freenet.de>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Ben Greear <greearb@candelatech.com>,
	Michel Alexandre Salim <salimma@fedoraproject.org>,
	ath9k-devel@venema.h4ckr.net, linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>,
	Jouni Malinen <jmalinen@atheros.com>,
	Senthil Balasubramanian <senthilkumar@atheros.com>,
	Vasanthakumar Thiagarajan <vasanth@atheros.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [ath9k-devel] [PATCH] ath9k: add module option for disabling 11n functionality
Date: Wed, 29 Jun 2011 19:50:25 +0200	[thread overview]
Message-ID: <4E0B65E1.5000707@01019freenet.de> (raw)
In-Reply-To: <BANLkTimRc-SzfeYhiKJ5g9pn3tuUzJM_DQ@mail.gmail.com>

Luis R. Rodriguez schrieb:
> On Tue, Jun 28, 2011 at 12:51 PM, Ben Greear <greearb@candelatech.com> wrote:
>> 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.

This is a joke, isn't it? If there are problems, why don't you fix them
instead of disabling the feature?

I know, there are problems with the 11n mode (not just with atheros
chips) - but they seem to be just ignored by a lot of the developers
here. There is a bug report [1] but it seems to be handled as if it was
sent against /dev/null.

Why don't you fix the problems? Why do you ignore them? Why don't you
support people who are willing to spent time for testing?


Kind regards,
Andreas


[1] http://w1.fi/bugz/show_bug.cgi?id=402

  parent reply	other threads:[~2011-06-29 17:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28 19:46 [ath9k-devel] [PATCH] ath9k: add module option for disabling 11n functionality Michel Alexandre Salim
2011-06-28 19:46 ` Michel Alexandre Salim
2011-06-28 19:51 ` [ath9k-devel] " Ben Greear
2011-06-28 19:51   ` Ben Greear
2011-06-28 20:06   ` [ath9k-devel] " Luis R. Rodriguez
2011-06-28 20:06     ` Luis R. Rodriguez
2011-06-28 20:40     ` Ben Greear
2011-06-28 20:40       ` Ben Greear
2011-06-29 17:50     ` Andreas Hartmann [this message]
2011-06-28 21:57 ` Jouni Malinen
2011-06-28 21:57   ` Jouni Malinen
2011-06-29  1:26   ` [ath9k-devel] " Adrian Chadd
2011-06-29  1:26     ` Adrian Chadd
2011-06-29  8:56   ` [ath9k-devel] " Michel Alexandre Salim
2011-06-29  8:56     ` Michel Alexandre Salim
2011-06-29 13:09     ` [ath9k-devel] " Jouni Malinen
2011-06-29 13:09       ` Jouni Malinen
2011-06-29 13:43       ` [ath9k-devel] " Michel Alexandre Salim
2011-06-29 13:43         ` Michel Alexandre Salim
2011-06-29 13:55         ` [ath9k-devel] " Jouni Malinen
2011-06-29 13:55           ` Jouni Malinen
2011-06-29 14:06           ` [ath9k-devel] " Michel Alexandre Salim
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=4E0B65E1.5000707@01019freenet.de \
    --to=andihartmann@01019freenet.de \
    --cc=ath9k-devel@venema.h4ckr.net \
    --cc=greearb@candelatech.com \
    --cc=jmalinen@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@gmail.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 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.