From: Larry Finger <Larry.Finger@lwfinger.net>
To: LKML <linux-kernel@vger.kernel.org>, Julienne Hill <jmhill@anl.gov>
Subject: Re: [ANNOUNCE] ndiswrapper 1.54 for Linux 2.6.28 Released
Date: Sun, 28 Dec 2008 23:14:15 -0600 [thread overview]
Message-ID: <49585CA7.7020406@lwfinger.net> (raw)
>> On Sat, 27 Dec 2008 12:05:57 MST, jmerkey@xxxxxxxxxxxxxxxxxxxxx said:
> And most, if not all, of the reverse engineered and hacked firmware is
> **SHIT** and does not work properly. My bcml15.sys drivers work great --
> the Linux drivers with the crap firmware which locks up all the time and
> stops receiving packets does not even make the LED wireless display work.
The firmware used by the b43 driver for BCM43XX is _EXACTLY_ the same as used by
the Windows drivers. We are working on reverse-engineering the firmware, but
that is not workiong yet. In fact, the firmware is extracted from the Broadcom
drivers. If the firmware is faulty, it isn't our fault. Of course, our RE is not
perfect, but then we get absolutely no support from the vendor.
Your device may work better with ndiswrapper and bcmwl5.sys than with b43, but I
find that ndiswrapper dies after about 4 hours and cannot be resurrected even by
unloading and reloading the driver. A reboot is needed. On the other hand, b43
just keeps on chugging.
Larry
next reply other threads:[~2008-12-29 5:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 5:14 Larry Finger [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-27 19:05 [ANNOUNCE] ndiswrapper 1.54 for Linux 2.6.28 Released jmerkey
2008-12-27 20:48 ` Valdis.Kletnieks
2008-12-27 22:50 ` jmerkey
[not found] ` <34474.166.70.238.44.1230418240.squirrel@webmail.wolfmountaingroup.com >
2008-12-27 22:53 ` jmerkey
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=49585CA7.7020406@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=jmhill@anl.gov \
--cc=linux-kernel@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