From: Michael Buesch <mb@bu3sch.de>
To: Pavel Roskin <proski@gnu.org>
Cc: bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: b43 opensource firmware for monitor mode
Date: Thu, 5 Jun 2008 15:35:13 +0200 [thread overview]
Message-ID: <200806051535.14340.mb@bu3sch.de> (raw)
In-Reply-To: <1212633988.26365.42.camel@dv>
On Thursday 05 June 2008 04:46:28 Pavel Roskin wrote:
> On Wed, 2008-06-04 at 17:16 +0200, Michael Buesch wrote:
> > 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.
>
> That's great news! Having distributable firmware would simplify
> installation, placing b43 to the same league as Intel devices. But
> having free firmware would be unique to Broadcom card and extremely
> attractive for research in wireless communications and development of
> novel devices using non-standard protocol extensions.
>
> As a short term goal, maybe bcm4328 could be dumbed down to work with
> b43?
>
> I've tried it with bcm4318 first, and it hung hard on module load. Even
> Alt-SysRq would not work. It turns out it was revision 9 missing in
> your list.
>
> Then I tries a bcm4306 device with rev 5 core. The module loaded. I
> brought it up in managed mode first. Scanning didn't work. I brought
> the device down and set monitor mode. But the system hung when I tried
> to bring the interface back up.
There shouldn't be a reason for a freeze. It might crash, yes, but it always
prints out useful messages first for me.
--
Greetings Michael.
next prev parent reply other threads:[~2008-06-05 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 15:16 b43 opensource firmware for monitor mode Michael Buesch
2008-06-05 2:46 ` Pavel Roskin
2008-06-05 13:35 ` Michael Buesch [this message]
[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=200806051535.14340.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.