From: Alfred B. M. Cordero <otto-pilot@hushmail.com>
To: b43-dev@lists.infradead.org
Subject: b43 -- 4312 and built-in/static kernel
Date: Fri, 29 Apr 2011 18:27:06 -0700 [thread overview]
Message-ID: <20110430012706.7ABA9E671D@smtp.hushmail.com> (raw)
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.
next reply other threads:[~2011-04-30 1:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 1:27 Alfred B. M. Cordero [this message]
2011-04-30 2:07 ` b43 -- 4312 and built-in/static kernel Rafał Miłecki
2011-04-30 5:20 ` Larry Finger
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=20110430012706.7ABA9E671D@smtp.hushmail.com \
--to=otto-pilot@hushmail.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