From: "John W. Linville" <linville@tuxdriver.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>,
linux-wireless@vger.kernel.org,
Rogerio Luz Coelho <rogluz.news@gmail.com>,
Herton Ronaldo Krzesinski <herton@mandriva.com.br>,
Hin-Tak Leung <hintak.leung@gmail.com>
Subject: Re: [PATCH] rtl8187b: do not do per packet TX AGC
Date: Mon, 30 Aug 2010 10:12:19 -0400 [thread overview]
Message-ID: <20100830141218.GB30864@tuxdriver.com> (raw)
In-Reply-To: <4C798080.8010002@lwfinger.net>
On Sat, Aug 28, 2010 at 04:32:48PM -0500, Larry Finger wrote:
> On 08/28/2010 12:54 AM, Thadeu Lima de Souza Cascardo wrote:
> > The code for rtl8187 does not do per packet TX AGC. Resetting the per
> > packet TX AGC for rtl8187b appears to increase its overall TX power.
> > This allows the device to associate and a connection be established
> > using APs a little further away.
> >
> > Tested-by: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
> > Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
> > Cc: linux-wireless@vger.kernel.org
> > Cc: Larry Finger <Larry.Finger@lwfinger.net>
> > Cc: Rogerio Luz Coelho <rogluz.news@gmail.com>
> > Cc: Herton Ronaldo Krzesinski <herton@mandriva.com.br>
> > Cc: Hin-Tak Leung <hintak.leung@gmail.com>
> > ---
>
> I'm a little confused here. The subject says not to set the per packet TX AGC,
> while the submission text says that setting it helps. I don't have access to any
> documents that describe this register, but I expect that clearing
> RTL818X_TX_AGC_CTL_PERPACKET_GAIN_SHIFT would disable that feature. As a result
> the code change seems to match the subject.
>
> I have not yet tested this code, but I do note that all the Realtek drivers for
> the RTL8187B set this bit.
>
> Until testing, I withhold judgment on the actual code change, but NACK for the
> inconsistency.
Perhaps the word "clearing" rather than "resetting" would be less confusing?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-08-30 14:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-28 5:54 [PATCH] rtl8187b: do not do per packet TX AGC Thadeu Lima de Souza Cascardo
2010-08-28 21:32 ` Larry Finger
2010-08-30 14:12 ` John W. Linville [this message]
2010-08-30 14:48 ` Larry Finger
2010-08-30 15:28 ` Thadeu Lima de Souza Cascardo
2010-10-26 18:03 ` seno
2010-10-26 18:25 ` [PATCH] " Larry Finger
2010-10-26 18:53 ` Thadeu Lima de Souza Cascardo
2010-10-28 21:13 ` Herton Ronaldo Krzesinski
2010-10-28 22:01 ` Thadeu Lima de Souza Cascardo
2010-10-29 13:15 ` Herton Ronaldo Krzesinski
2010-10-28 23:21 ` seno
2010-10-29 13:54 ` Thadeu Lima de Souza Cascardo
2010-10-29 22:31 ` seno
2010-10-30 0:00 ` Larry Finger
2010-10-30 2:12 ` seno
2010-11-01 4:39 ` Herton Ronaldo Krzesinski
2010-11-01 16:24 ` Larry Finger
2010-11-03 3:16 ` Rogerio Luz Coelho
2010-11-04 14:23 ` Hin-Tak Leung
2010-08-30 15:12 ` Thadeu Lima de Souza Cascardo
2010-09-16 18:44 ` John W. Linville
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=20100830141218.GB30864@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Larry.Finger@lwfinger.net \
--cc=cascardo@holoscopio.com \
--cc=herton@mandriva.com.br \
--cc=hintak.leung@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rogluz.news@gmail.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).