From: Michael Buesch <mb@bu3sch.de>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: John Linville <linville@tuxdriver.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
Mark Huijgen <mark@huijgen.tk>,
Broadcom Wireless <bcm43xx-dev@lists.berlios.de>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] b43: LP-PHY: Update B2062 radio init with recent spec changes
Date: Sun, 16 Aug 2009 20:09:34 +0200 [thread overview]
Message-ID: <200908162009.34744.mb@bu3sch.de> (raw)
In-Reply-To: <4A884B0D.5000808@gmail.com>
On Sunday 16 August 2009 20:08:13 Gábor Stefanik wrote:
> The spec for initializing the B2062 radio have changed recently,
> update the code to match the changes.
>
> Signed-off-by: Gábor Stefanik <netrolller.3d@gmail.com>
ack
> ---
> drivers/net/wireless/b43/phy_lp.c | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/wireless/b43/phy_lp.c b/drivers/net/wireless/b43/phy_lp.c
> index 5a7b873..34b7910 100644
> --- a/drivers/net/wireless/b43/phy_lp.c
> +++ b/drivers/net/wireless/b43/phy_lp.c
> @@ -539,10 +539,15 @@ static void lpphy_2062_init(struct b43_wldev *dev)
> b43_radio_write(dev, B2062_N_TX_CTL3, 0);
> b43_radio_write(dev, B2062_N_TX_CTL4, 0);
> b43_radio_write(dev, B2062_N_TX_CTL5, 0);
> + b43_radio_write(dev, B2062_N_TX_CTL6, 0);
> b43_radio_write(dev, B2062_N_PDN_CTL0, 0x40);
> b43_radio_write(dev, B2062_N_PDN_CTL0, 0);
> b43_radio_write(dev, B2062_N_CALIB_TS, 0x10);
> b43_radio_write(dev, B2062_N_CALIB_TS, 0);
> + if (dev->phy.rev > 0) {
> + b43_radio_write(dev, B2062_S_BG_CTL1,
> + (b43_radio_read(dev, B2062_N_COMM2) >> 1) | 0x80);
> + }
> if (b43_current_band(dev->wl) == IEEE80211_BAND_2GHZ)
> b43_radio_set(dev, B2062_N_TSSI_CTL0, 0x1);
> else
--
Greetings, Michael.
prev parent reply other threads:[~2009-08-16 18:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-16 18:08 [PATCH] b43: LP-PHY: Update B2062 radio init with recent spec changes Gábor Stefanik
2009-08-16 18:09 ` 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=200908162009.34744.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mark@huijgen.tk \
--cc=netrolller.3d@gmail.com \
/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).