From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: John Linville <linville@tuxdriver.com>,
netdev@vger.kernel.org, Bcm43xx-dev@lists.berlios.de,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] bcm43xx: Fix incorrect definition of PHY revision
Date: Wed, 7 Feb 2007 15:14:16 +0100 [thread overview]
Message-ID: <200702071514.17516.mb@bu3sch.de> (raw)
In-Reply-To: <45c94821.qjljSnUzfws7mU7T%Larry.Finger@lwfinger.net>
On Wednesday 07 February 2007 04:31, Larry Finger wrote:
> There is a typographical error in the spefications that interchange the PHY version
> and revision. Fixing this error makes all BCM43xx varieties work at full CCCK rates.
>
> Signed-off-by: Larry Finger<Larry.Finger@lwfinger.net>
> ---
>
> John,
>
> This patch should be put into wireless-2.6 and into 'upstream' as soon as possible.
> I will be sending it to stable for inclusion in 2.6.20.1, and whatever other kernels
> are still being maintained by -stable.
>
> Larry
> ---
>
> Index: wireless-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c
> ===================================================================
> --- wireless-2.6.orig/drivers/net/wireless/bcm43xx/bcm43xx_main.c
> +++ wireless-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c
> @@ -3704,9 +3704,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 don't think this is correct.
>From which part of the specs did you get this?
http://bcm-v4.sipsolutions.net/802.11/PHY is where the PHY_Version
register is explained. "phy_version"=="AnalogType"
Actually it is possible that phy_revision is mask 0xFF, but that's
not too important at the moment, as we don't have revisions>0xF, yet.
But besides that, it's interresting that this "fixes" things for you.
Especially since wireless-2.6 has no support for hw-power-control, which
is needed by cards 4318 and newer.
--
Greetings Michael.
prev parent reply other threads:[~2007-02-07 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 3:31 [PATCH] bcm43xx: Fix incorrect definition of PHY revision Larry Finger
2007-02-07 14:14 ` Michael Buesch [this message]
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=200702071514.17516.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
/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).