From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Paul Menzel <paulepanter@users.sourceforge.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Fabien ADAM <id2ndr@crocobox.org>,
linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
Subject: Re: [rt2x00-users] [PATCH 3.11] rt2800: fix wrong TX power compensation
Date: Tue, 27 Aug 2013 10:00:02 +0200 [thread overview]
Message-ID: <20130827080001.GA2609@redhat.com> (raw)
In-Reply-To: <1377548398.4408.4.camel@mattotaupa>
On Mon, Aug 26, 2013 at 10:19:58PM +0200, Paul Menzel wrote:
> Could you please add which ones you have tested?
I checked 2 devices (3071 & 3070) but they have EXTERNAL_TX_ALC bit set.
I assume the fix is correct based on vendor driver and it fixes devices
which have no EXTERNAL_TX_ACL, but I can not tell what chipset that are.
Is possible that the same chipset can be configured with and without
EXTERNAL_TX_ALC.
> Is there a bug report about this?
Fabien reported problem on mailing list, I can add that as reference.
I hope it also fixes bug reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=913631
but I haven't get confirmation about that from users yet.
Stanislaw
next prev parent reply other threads:[~2013-08-27 8:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 13:18 [PATCH 3.11] rt2800: fix wrong TX power compensation Stanislaw Gruszka
2013-08-26 19:04 ` [rt2x00-users] " Gertjan van Wingerde
2013-08-26 20:19 ` Paul Menzel
2013-08-27 8:00 ` Stanislaw Gruszka [this message]
2013-08-27 8:13 ` [PATCH 3.11 v2] " Stanislaw Gruszka
2013-08-27 8:26 ` [rt2x00-users] " Paul Menzel
2013-08-27 9:13 ` Stanislaw Gruszka
2013-08-28 15:10 ` John W. Linville
2013-08-27 8:22 ` [rt2x00-users] [PATCH 3.11] " Daniel Golle
2013-08-27 8:22 ` Paul Menzel
2013-08-27 9:07 ` Stanislaw Gruszka
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=20130827080001.GA2609@redhat.com \
--to=sgruszka@redhat.com \
--cc=id2ndr@crocobox.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=paulepanter@users.sourceforge.net \
--cc=users@rt2x00.serialmonkey.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).