From: Michael Buesch <mb@bu3sch.de>
To: bcm43xx-dev@lists.berlios.de
Cc: linux-wireless@vger.kernel.org
Subject: b43 open-firmware new snapshot
Date: Sat, 14 Jun 2008 15:53:42 +0200 [thread overview]
Message-ID: <200806141553.42420.mb@bu3sch.de> (raw)
Hi,
Here comes another snapshot of the Opensource firmware for
the b43 wireless core.
http://bu3sch.de/b43/openfw/b43-openfw-20080614.tar.bz2
The firmware does _ONLY_ work in monitor mode. The TX path is not implemented,
so it can not associate or whatever. It can only receive packets.
This firmware does _only_ work on wireless core revisions 5, 6, 7, 8 or 10.
You can see the core revision by turning on SSB debugging.
It will print something like:
ssb: Core X found: IEEE 802.11 (cc 0x812, rev 0x05, vendor 0x4243)
As you can see there's the revision number in hex.
If you want to test this, first get latest wireless-testing.git kernel driver.
Then get the firmware tarball and extract it.
The tarball contains the full sourcecode and a set of prebuilt binaries.
(If you want to rebuild the stuff, you need to get the assembler toolchain
from http://git.bu3sch.de/git/b43-tools.git).
There are binaries with debugging code (in bin-debug subdir) and without
debugging code (in bin subdir). You want to start with the non-debugging
version for testing. You might want to check the debugging version, if
you see any problems. It might print some useful hints in the kernel
driver for what is going wrong.
Simply get the *.fw files from bin/rev5/ in the tarball and copy them
into /lib/firmware/b43-open.
Then load b43 from latest wireless-testing.git with the module
parameter fwpostfix=-open
--
Greetings Michael.
next reply other threads:[~2008-06-14 13:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-14 13:53 Michael Buesch [this message]
2008-06-15 18:20 ` b43 open-firmware new snapshot Stefanik Gábor
2008-06-15 20:03 ` Michael Buesch
2008-06-18 16:02 ` Francesco Gringoli
2008-06-18 18:06 ` Rafał Miłecki
2008-06-18 18:26 ` Michael Buesch
2008-06-18 18:30 ` 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=200806141553.42420.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@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 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).