From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: b43 -- 4312 and built-in/static kernel
Date: Sat, 30 Apr 2011 00:20:10 -0500 [thread overview]
Message-ID: <4DBB9C0A.1070204@lwfinger.net> (raw)
In-Reply-To: <20110430012706.7ABA9E671D@smtp.hushmail.com>
On 04/29/2011 08:27 PM, Alfred B. M. Cordero wrote:
> Hello,
>
> I am building a static kernel. I have gotten the DVB card working
> by adding
> the .fw to linux/firmware and so I am doing the same thing with the
> 4312.
> The kernel builds fine, the 4312 is found and seems fine.
> dmesg reports the card, lspci shows it and so does ifconfig -a.
>
> ip link set dev wlan0 up pretty much hangs and none of the iw*
> commands
> work.
>
>
> The problem may be that at the request_firmware stage there is a
> mismatch
> between what I've compiled into the kernel and what
> request_firmware is
> requesting.
>
> I have ucode5.fw, b0g0bsinit and b0g0init in linux/firmware and
> added those to .config
>
> If anyone knows how to narrow this down it would be great.
What exactly do you mean by 4312? If you mean a PCI ID of 14e4:4312, then the
firmware above is partially correct. The ucode5.fw is correct, but you also need
b0g0initvals5.fw and b0g0initvals5.fw. In addition, you might need
a0g1initvals5.fw or a0g1initvals5. I no longer have one of those devices, thus I
cannot test.
If you mean BCM4312 802.11b/g, then your firmware selection is wrong. This type
of device will have a PCI ID of 14e4:4315 and will require different firmware.
For these LP-PHY devices, b0g0initvals13.fw, lp0initvals13.fw, and ucode13.fw
are probably needed.
Larry
prev parent reply other threads:[~2011-04-30 5:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 1:27 b43 -- 4312 and built-in/static kernel Alfred B. M. Cordero
2011-04-30 2:07 ` Rafał Miłecki
2011-04-30 5:20 ` Larry Finger [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=4DBB9C0A.1070204@lwfinger.net \
--to=larry.finger@lwfinger.net \
--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