From: Michael Buesch <mb@bu3sch.de>
To: bcm43xx-dev@lists.berlios.de
Cc: linux-wireless@vger.kernel.org
Subject: b43 opensource firmware for monitor mode
Date: Wed, 4 Jun 2008 17:16:53 +0200 [thread overview]
Message-ID: <200806041716.53771.mb@bu3sch.de> (raw)
Release early, release often.
Here's the first testing release of the b43 opensource firmware.
http://bu3sch.de/misc/b43-openfw-20080604.tar.bz2
Currently only the receive path is partially implemented. So that
means we can only run it in monitor mode for now. This firmware is
able to receive packets and push them without special handling (like
decrypting) to the driver.
There are lots of bugs, of course. Sometimes the PLCP header is corrupted.
That will result in a kernel driver warning in xmit.c.
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, please get the 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).
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
Setup monitor mode and see packets coming in. Or not...
--
Greetings Michael.
next reply other threads:[~2008-06-04 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 15:16 Michael Buesch [this message]
2008-06-05 2:46 ` b43 opensource firmware for monitor mode Pavel Roskin
2008-06-05 13:35 ` Michael Buesch
[not found] <22744.201.36.143.231.1212676638.:mail@corporativo.mandic.com.br>
2008-06-05 14:43 ` 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=200806041716.53771.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).