From: Larry Finger <Larry.Finger@lwfinger.net>
To: gavron@wetwork.net
Cc: Broadcom Wireless <bcm43xx-dev@berlios.de>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: Speed enhancement for BCM4306/2
Date: Sat, 06 Sep 2008 10:29:57 -0500 [thread overview]
Message-ID: <48C2A1F5.6020607@lwfinger.net> (raw)
In-Reply-To: <48C20F64.1000700@wetwork.net>
gavron@wetwork.net wrote:
>
>
>
> Ok, here's try #2.
> E
> /home/2.6.27/rc4-wl/drivers/net/wireless/b43legacy# diff -uN /tmp/phy.c
> phy.c
> --- /tmp/phy.c 2008-09-05 21:56:20.000000000 -0700
> +++ phy.c 2008-09-05 22:03:28.000000000 -0700
For kernel patches, you need to be working in the base directory of
the kernel sources. For your tree, that would be in
/home/2.6.27/rc4-wl. That way the patches will apply with the
effective command of 'patch -p1 < patch_file'. For kernel patches, I
use quilt so that patches are easy to apply and remove.
> @@ -1010,7 +1010,7 @@
> b43legacy_phy_initb5(dev);
> else
> b43legacy_phy_initb6(dev);
> - if (phy->rev >= 2 || phy->gmode)
> + if (phy->rev >= 2 && phy->gmode)
> b43legacy_phy_inita(dev);
>
> if (phy->rev >= 2) {
The above hunk is correct.
> @@ -1027,15 +1027,17 @@
> }
> if (phy->rev >= 2 || phy->gmode) {
This does not match step 7 of the specs. It was not changed recently,
but the code did not match what was on the web site. No, I don't know why.
> tmp = b43legacy_phy_read(dev, 0x0400) & 0xFF;
> - if (tmp == 3 || tmp == 5) {
> + if (tmp == 4 || tmp == 5) {
> b43legacy_phy_write(dev, 0x04C2, 0x1816);
> - b43legacy_phy_write(dev, 0x04C3, 0x8006);
> + b43legacy_phy_write(dev, 0x04C3, 0x8606);
> if (tmp == 5)
> b43legacy_phy_write(dev, 0x04CC,
> (b43legacy_phy_read(dev,
> 0x04CC) & 0x00FF) |
> 0x1F00);
> }
> + }
> + if (phy->rev >= 2)
> b43legacy_phy_write(dev, 0x047E, 0x0078);
> }
> if (phy->radio_rev == 8) {
This hunk does not match the specs. In addition, I think there are too
many right-hand curly braces for it to compile.
Larry
next prev parent reply other threads:[~2008-09-06 15:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 23:02 Speed enhancement for BCM4306/2 Larry Finger
2008-09-06 4:38 ` gavron
2008-09-06 4:49 ` Larry Finger
2008-09-06 5:04 ` gavron
2008-09-06 10:41 ` Michael Buesch
2008-09-06 15:29 ` Larry Finger [this message]
2008-09-06 18:07 ` gavron
2008-09-06 18:11 ` Michael Buesch
2008-09-06 18:30 ` Larry Finger
2008-09-06 22:59 ` gavron
2008-09-06 23:28 ` Larry Finger
2008-09-06 23:46 ` gavron
2008-09-07 0:18 ` Larry Finger
2008-09-07 0:25 ` gavron
2008-09-07 0:35 ` Larry Finger
2008-09-07 0:41 ` gavron
2008-09-07 0:14 ` gavron
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=48C2A1F5.6020607@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@berlios.de \
--cc=gavron@wetwork.net \
--cc=linux-wireless@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).