From: Larry Finger <Larry.Finger@lwfinger.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: bcm43xx-dev@lists.berlios.de, netdev@vger.kernel.org,
linville@tuxdriver.com
Subject: Re: Please pull bcm43xx-d80211 bugfixes and new features
Date: Tue, 03 Oct 2006 10:07:59 -0500 [thread overview]
Message-ID: <45227CCF.2000704@lwfinger.net> (raw)
In-Reply-To: <200610031648.04932.mb@bu3sch.de>
Michael Buesch wrote:
> On Tuesday 03 October 2006 16:36, Larry Finger wrote:
>> Michael Buesch wrote:
>>>> kernel: bcm43xx_d80211: firmware revision FE84, patchlevel 90B4, date 2000-14-248
>>>> 29:46:18
>>> Uhm, which firmware are you running?
>> The softmac version reports the following (The "loaded" messages are something I'm trying.):
>>
>> kernel: bcm43xx: Firmware: Microcode "bcm43xx_microcode4.fw" loaded.
>> kernel: bcm43xx: Firmware: PCM "bcm43xx_pcm4.fw" loaded.
>> kernel: bcm43xx: Firmware: InitVals0 "bcm43xx_initval01.fw" loaded.
>> kernel: bcm43xx: Microcode rev 0x123, pl 0x21 (2005-01-22 19:48:06)
>
> Well, so now you know where the problem is.
> I can't debug this for you ;)
>
I repulled wireless-dev and rebuilt it to find the same problem, which probably is not in your
recent patches. When I get a chance, I'll see if I can where it goes wrong.
Larry
next prev parent reply other threads:[~2006-10-03 15:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 16:43 Please pull bcm43xx-d80211 bugfixes and new features Michael Buesch
2006-10-03 3:44 ` Larry Finger
2006-10-03 11:58 ` Michael Buesch
[not found] ` <200610031358.33760.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2006-10-03 12:36 ` Martin Langer
2006-10-03 13:05 ` Michael Buesch
2006-10-03 14:36 ` Larry Finger
[not found] ` <45227569.6070901-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-10-03 14:48 ` Michael Buesch
2006-10-03 15:07 ` Larry Finger [this message]
2006-10-03 15:12 ` Martin Langer
2006-10-03 15:14 ` 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=45227CCF.2000704@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--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 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.