linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: seno <senada@t-online.de>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rtl8187b: do not do per packet TX AGC
Date: Tue, 26 Oct 2010 16:53:42 -0200	[thread overview]
Message-ID: <20101026185341.GA4608@barata.holoscopio.com> (raw)
In-Reply-To: <4CC71CFF.8050004@lwfinger.net>

[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]

On Tue, Oct 26, 2010 at 01:25:03PM -0500, Larry Finger wrote:
> On 10/26/2010 01:03 PM, seno wrote:
> > I tried that patch on compat-wireless-2010-10-25 (Kernel 2.6.33.7).
> > 
> > Performance improves minimal, but thousands of errors occur in iwconfig output.
> > (Tx excessive retries, Invalid misc, Missed beacon).
> > 
> > The router also shows lots of errors 
> > (for Received (RX) / Transmitted (TX) packets)
> 
> I no longer remember the details of why this patch was abandoned, but I suspect
> you found the answer.
> 

It was because of the bad wording in the commit description. I was
expecting some more testing from my client before posting it again with
the wording fixed. They've been testing it and there is enough
improvement they require the patch. I don't get the thousands of errors
in iwconfig output. I can try to reproduce it here if I get more
details.

Thanks,
Cascardo.

> Larry
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2010-10-26 19:01 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
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 [this message]
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=20101026185341.GA4608@barata.holoscopio.com \
    --to=cascardo@holoscopio.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=senada@t-online.de \
    /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).