From: Larry Finger <larry.finger@lwfinger.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: Bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] bcm43xx-mac80211: Fix for tx_bias equal to 0xFF
Date: Sat, 26 May 2007 16:11:34 -0500 [thread overview]
Message-ID: <4658A286.1050204@lwfinger.net> (raw)
In-Reply-To: <200705262206.53388.mb@bu3sch.de>
Michael Buesch wrote:
> On Saturday 26 May 2007 19:55:30 Larry Finger wrote:
>> Michael Buesch wrote:
>>> Ok, on which specification bits is this actually based? :)
>>> txpower_bg still needs a rewrite, and I have a patch for that in
>>> the pipeline, but it's still buggy due to missing specs stuff.
>>>
>> It is not in the V4 specifications that I have found, but the V3 (softmac) driver does this "fixup".
>
> I cannot find this in the sm driver. Can you give me a hint
> where to search?
>
>> With it, my 4311 connects with bcm43xx-mac80211. Without it, no connection.
>
> Ok, nice.
>
My memory was faulty earlier, but it is coming back. V3 differs in that txctl1 (the equivalent of
tx_bias) is not initialized to 0xFF, but is given a value of 0-3 in bcm43xx_default_txctl1. I added
trace code that checked the value being written to radio register 0x52 and dumped the stack when the
value was still 0xFF. On that basis, I made it look like the code in bcm43xx_phy_initg when tx_bias
is 0xFF.
Would you prefer the equivalent of bcm43xx_default_txctl1? That wouldn't be difficult.
Are the txpower adjustment bugs a problem with the specs? Is there anything I can do?
Larry
Larry
next prev parent reply other threads:[~2007-05-26 21:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 17:09 [PATCH] bcm43xx-mac80211: Fix for tx_bias equal to 0xFF Larry Finger
2007-05-26 17:19 ` Michael Buesch
2007-05-26 17:55 ` Larry Finger
2007-05-26 17:56 ` Michael Buesch
2007-05-26 20:06 ` Michael Buesch
2007-05-26 21:11 ` Larry Finger [this message]
2007-05-26 21:13 ` Michael Buesch
2007-05-26 21:41 ` Joseph Jezak
2007-05-26 20:18 ` Michael Buesch
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=4658A286.1050204@lwfinger.net \
--to=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 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).