linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <larry.finger@lwfinger.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: wireless <linux-wireless@vger.kernel.org>, bcm43xx-dev@lists.berlios.de
Subject: Re: RFT: The real fix for BCM4311 and BCM4312
Date: Wed, 07 Feb 2007 07:53:26 -0600	[thread overview]
Message-ID: <45C9D9D6.2070700@lwfinger.net> (raw)
In-Reply-To: <200702071443.19676.rjw@sisk.pl>

Rafael J. Wysocki wrote:
> On Wednesday, 7 February 2007 07:34, Pavel Roskin wrote:
>> On Wed, 2007-02-07 at 00:02 -0600, Larry Finger wrote:
>>> The patch below will only affect cards with PHY revision 8, which I think are only BCM4311 and
>>> BCM4312. At least those are the only ones in the database.
>> BCM4312, old patch: 1.7M/s
>> no patch: 26k/s
>> no patch, rate 1: 100k/s
>> new patch: 1.7M/s
>> new patch, rate 1: 1.1M/s
>> new patch, rate 2: 1.5M/s
>> new patch, rate 5.5: 1.7M/s
>> new patch, rate 18: 2.2M/s
>> new patch, rate 36: 2.2M/s
>>
>> Yes, it looks like the new patch is as good as the previous one for my card.
> 
> The patch is apparently sufficient for me too.  Moreover, the D-Link APs that
> were previously "invisible" are now listed by "iwlist ... scan" and I can
> connect with them.  Thanks again!

Great - a two-for-one! That must have been a signal strength issue.

Larry

  reply	other threads:[~2007-02-07 13:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-07  6:02 RFT: The real fix for BCM4311 and BCM4312 Larry Finger
2007-02-07  6:34 ` Pavel Roskin
2007-02-07 13:43   ` Rafael J. Wysocki
2007-02-07 13:53     ` Larry Finger [this message]
2007-02-10 23:30       ` Miles Lane
2007-02-10 23:41         ` Larry Finger
2007-02-13 21:13           ` John W. Linville
2007-02-13 22:19             ` Larry Finger
2007-02-13 23:36               ` Stephen Sinclair

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=45C9D9D6.2070700@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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).