All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jory A. Pratt" <geekypenguin@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Broadcom Linux <bcm43xx-dev@lists.berlios.de>,
	wireless <linux-wireless@vger.kernel.org>,
	Michael Buesch <mb@bu3sch.de>
Subject: Re: RFT bcm43xx: Really _GOOD_ news
Date: Thu, 08 Feb 2007 12:20:30 -0600	[thread overview]
Message-ID: <45CB69EE.4000102@gmail.com> (raw)
In-Reply-To: <45C8E64B.1050605@lwfinger.net>

Larry Finger wrote:
> I have really _GOOD_ news!!!!! While reviewing the latest changes in the V4 specs, I found an
> interchange of the PHY version and PHY revision fields, relative to the current V3 specs. Of the
> three cards that I have, the 4306 had the same value for the PHY version and revision. In addition,
> it was the only card of the 3 thaw would work at 11Mbs. A light went on!
>
> After installing the patch listed below, both my 4318 and my 4311 will now run at 11Mbs. From tests
> with iperf, I now get rates of 6.1 - 6.5 Mbs from all three.
>
> Larry
>
>
> ==========
>
> Index: linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c
> ===================================================================
> --- linux-2.6.orig/drivers/net/wireless/bcm43xx/bcm43xx_main.c
> +++ linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c
> @@ -3707,9 +3707,9 @@ static int bcm43xx_read_phyinfo(struct b
>
>  	value = bcm43xx_read16(bcm, BCM43xx_MMIO_PHY_VER);
>
> -	phy_version = (value & 0xF000) >> 12;
> +	phy_rev = (value & 0xF000) >> 12;
>  	phy_type = (value & 0x0F00) >> 8;
> -	phy_rev = (value & 0x000F);
> +	phy_version = (value & 0x000F);
>
>  	dprintk(KERN_INFO PFX "Detected PHY: Version: %x, Type %x, Revision %x\n",
>  		phy_version, phy_type, phy_rev);
>
>   
I have tested this until I am blue in the face on a 4318. It killed me,
I was getting less then 200k/b a sec on a 5M pipe :(. I reverted the
patch and all is back to working even tho transfering files on the
internal network is still way out there.


  parent reply	other threads:[~2007-02-08 18:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-06 20:34 RFT bcm43xx: Really _GOOD_ news Larry Finger
2007-02-06 21:37 ` Gene Heskett
2007-02-06 22:29   ` Pavel Roskin
2007-02-06 23:48     ` Gene Heskett
2007-02-07  4:40       ` Larry Finger
2007-02-07  8:03         ` Gene Heskett
2007-02-07  8:17           ` Pavel Roskin
2007-02-07 15:21             ` Daniel Gryniewicz
2007-02-07 15:42               ` Larry Finger
2007-02-06 22:18 ` Pavel Roskin
2007-02-06 22:27   ` Rafael J. Wysocki
2007-02-07  1:08     ` Larry Finger
2007-02-08 18:20 ` Jory A. Pratt [this message]
2007-02-09  0:05   ` 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=45CB69EE.4000102@gmail.com \
    --to=geekypenguin@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.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 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.