linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Gautam Iyer <gi1242+vger@stanford.edu>, linux-wireless@vger.kernel.org
Subject: Re: 2.6.26 b43 speed issue (redux) and new firmware drivers
Date: Wed, 23 Jul 2008 10:22:05 -0500	[thread overview]
Message-ID: <48874C9D.2050900@lwfinger.net> (raw)
In-Reply-To: <20080722193637.GC19885@stanford.edu>

Gautam Iyer wrote:
> 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.)

I do not know what changed between 4.150.10.5 and 4.150.10.2, but I doubt that 
the firmware in the new driver will make any appreciable difference in the 
performance of the BCM4312. My guess is that they found some errors in the 
handling of the N PHY or the LP PHY, which are the two newest devices, and fixed 
them. Of course, we do need to update fwcutter to test my hypothesis. As a 
reverse engineer, I also need to see what changed. What version is the Windows 
driver that you use?

It is a fact of life that this kind of reverse engineering rarely will perform 
better than the original driver. After all, if we make an exact copy, then we 
repeat their mistakes. Any mistakes of ours have a small chance of improving 
performance. Where we do improve on the original is in the error handling.

I get the same performance with my BCM4312 as you do.

Larry

  reply	other threads:[~2008-07-23 15:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22 19:36 2.6.26 b43 speed issue (redux) and new firmware drivers Gautam Iyer
2008-07-23 15:22 ` Larry Finger [this message]
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=48874C9D.2050900@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=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).