From: Gregory Bellier <gregory.bellier@gmail.com>
To: b43-dev@lists.infradead.org
Subject: A small error in b43
Date: Thu, 7 Apr 2011 22:36:19 +0200 [thread overview]
Message-ID: <BANLkTikM6rDsXLZtsucqtm-GnYcG+12eUQ@mail.gmail.com> (raw)
In-Reply-To: <4D9E1C97.3030007@lwfinger.net>
2011/4/7 Larry Finger <Larry.Finger@lwfinger.net>
> On 04/07/2011 03:09 PM, Gregory Bellier wrote:
>
>> Dear list,
>>
>> I would like to test the b43 driver for a BCM4322. I tried with 2.6.38.2
>> and
>> 2.6.39-rc2 but I'm stuck with a firmware error in dmesg :
>> [ 75.922582] b43-phy0 ERROR: Firmware file "b43/ucode16_mimo.fw" not found
>> [ 75.922587] b43-phy0 ERROR: Firmware file "b43-open/ucode16_mimo.fw" not
>> found
>> [ 75.922590] b43-phy0 ERROR: You must go to
>> http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and
>> download the
>> correct firmware for this driver version. Please carefully read all
>> instructions
>> on this website.
>>
>> I have b43-fwcutter v13.
>>
>> # b43-fwcutter -w /lib/firmware/ broadcom-wl-4.178.10.4/linux/wl_apsta.o
>> This file is recognised as:
>> ID : FW15
>> filename : wl_apsta.o
>> version : 478.104
>> MD5 : bb8537e3204a1ea5903fe3e66b5e2763
>> Extracting b43/ucode5.fw
>> Extracting b43/pcm5.fw
>> Extracting b43/b0g0bsinitvals5.fw
>> Extracting b43/a0g0bsinitvals5.fw
>> Extracting b43/b0g0initvals5.fw
>> Extracting b43/a0g1initvals5.fw
>> Extracting b43/a0g0initvals5.fw
>> Extracting b43/a0g1bsinitvals5.fw
>> Extracting b43/ucode9.fw
>> Extracting b43/a0g1initvals9.fw
>> Extracting b43/a0g0bsinitvals9.fw
>> Extracting b43/b0g0bsinitvals9.fw
>> Extracting b43/b0g0initvals9.fw
>> Extracting b43/a0g1bsinitvals9.fw
>> Extracting b43/a0g0initvals9.fw
>> Extracting b43/ucode11.fw
>> Extracting b43/n0bsinitvals11.fw
>> Extracting b43/n0absinitvals11.fw
>> Extracting b43/n0initvals11.fw
>> Extracting b43/ucode13.fw
>> Extracting b43/b0g0initvals13.fw
>> Extracting b43/a0g1bsinitvals13.fw
>> Extracting b43/a0g1initvals13.fw
>> Extracting b43/lp0bsinitvals13.fw
>> Extracting b43/b0g0bsinitvals13.fw
>> Extracting b43/lp0initvals13.fw
>> Extracting b43/ucode14.fw
>> Extracting b43/lp0initvals14.fw
>> Extracting b43/lp0bsinitvals14.fw
>> Extracting b43/ucode15.fw
>> Extracting b43/lp0bsinitvals15.fw
>> Extracting b43/lp0initvals15.fw
>> Extracting b43/ucode16.fw
>> Extracting b43/n0bsinitvals16.fw
>> Extracting b43/sslpn0initvals16.fw
>> Extracting b43/n0initvals16.fw
>> Extracting b43/lp0initvals16.fw
>> Extracting b43/sslpn0bsinitvals16.fw
>> Extracting b43/lp0bsinitvals16.fw
>>
>> Did I miss something ? I promise I read carefully.
>>
>> Sorry, I wrote this email in several times. I finally did a symlink in
>> /lib/firmware/b43 : # sudo ln -s ucode16.fw ucode16_mimo.fw
>> And it worked like this.
>>
>
> I'm not sure if those two firmware files are equivalent or not.
>
> There is a new version of b43-fwcutter in the git repository at git://
> git.bu3sch.de/b43-tools.git that knows how to extract the firmware from
> URL
> http://mirror2.openwrt.org/sources/broadcom-wl-5.10.56.27.3_mipsel.tar.bz2.
> After untarring, the object file is
> broadcom-wl-5.10.56.27.3/driver/wl_apsta/wl_prebuilt.o
>
Yes, it works properly with this one !
Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20110407/e9a5eb4f/attachment-0001.html>
next prev parent reply other threads:[~2011-04-07 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 20:09 A small error in b43 Gregory Bellier
2011-04-07 20:18 ` Rafał Miłecki
2011-04-07 20:20 ` Larry Finger
2011-04-07 20:36 ` Gregory Bellier [this message]
[not found] <alpine.DEB.2.01.1104162313180.18728@trent.utfs.org>
2011-04-17 7:06 ` Rafał Miłecki
[not found] ` <alpine.DEB.2.01.1104170131420.18728@trent.utfs.org>
2011-04-17 10:27 ` Rafał Miłecki
[not found] ` <alpine.DEB.2.01.1104171138421.18728@trent.utfs.org>
2011-04-17 21:34 ` Rafał Miłecki
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=BANLkTikM6rDsXLZtsucqtm-GnYcG+12eUQ@mail.gmail.com \
--to=gregory.bellier@gmail.com \
--cc=b43-dev@lists.infradead.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).