From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: 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 23:21:39 +0200 [thread overview]
Message-ID: <200807232321.40096.mb@bu3sch.de> (raw)
In-Reply-To: <48874C9D.2050900@lwfinger.net>
On Wednesday 23 July 2008 17:22:05 Larry Finger wrote:
> 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.
Well, there are parts in the b43 code that are subject to optimization.
The power adjustment code, for example. I have a patch in development for this,
but didn't work on it for quite some time.
--
Greetings Michael.
prev parent reply other threads:[~2008-07-23 21: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
2008-07-23 20:32 ` Gautam Iyer
2008-07-23 20:40 ` Gautam Iyer
2008-07-23 21:21 ` Michael Buesch [this message]
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=200807232321.40096.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=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).