From: Gautam Iyer <gi1242+vger@stanford.edu>
To: linux-wireless@vger.kernel.org
Subject: 2.6.26 b43 speed issue (redux) and new firmware drivers
Date: Tue, 22 Jul 2008 12:36:37 -0700 [thread overview]
Message-ID: <20080722193637.GC19885@stanford.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
Hi All,
I'm writing to inquire about a "new" firmware drivers for Broadcom 43xx:
On April 6, 2008 it looks like broadcom-wl-4.150.10.5.2.tar.bz2 appeared
on http://mirror2.openwrt.org/sources/. The install guide for b43
recommends you use b43-fwcutter-011 and broadcom-wl-4.150.10.5.tar.bz2
I tried to use broadcom-wl-4.150.10.5.2.tar.bz2 with b43-fwcutter-011,
but it complained that the md5 sum was not recognized :). Just wondering
if there is any way to use this new firmware?
Thanks in advance,
GI
PS: The main reason I ask is for "performance": A while ago I reported
that my Broadcom 4312 gave 2/3 the speed under b43 (2.6.25), when
compared to ndiswrapper. (I tested by running ttcp, and measuring
the throughput. I got roughly 3MB/s with ndiswrapper, and
2 MB/s with b43).
I just upgraded to 2.6.26, and found that my b43 speed *increased*
to 2.4MB/s :). So thanks to whomever is responsible! I was also
hoping that if I upgrade even the firmware I would be able to
"toast" ndiswrapper. (I transfer large files on my home network
often, which is why I care about the speed so much.)
--
'Cigarette' -- A pinch of tobacco, wrapped in paper, fire at one end,
fool at the other.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-07-22 19:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 19:36 Gautam Iyer [this message]
2008-07-23 15:22 ` 2.6.26 b43 speed issue (redux) and new firmware drivers Larry Finger
2008-07-23 20:32 ` Gautam Iyer
2008-07-23 20:40 ` Gautam Iyer
2008-07-23 21:21 ` 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=20080722193637.GC19885@stanford.edu \
--to=gi1242+vger@stanford.edu \
--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).