From: gavron@wetwork.net
To: Michael Buesch <mb@bu3sch.de>
Cc: bcm43xx-dev@lists.berlios.de,
wireless <linux-wireless@vger.kernel.org>,
Peter Stuge <peter@stuge.se>
Subject: Re: [RFC/T] b43: to few loop tries in do_dummy_tx
Date: Tue, 30 Sep 2008 06:46:04 -0700 [thread overview]
Message-ID: <48E22D9C.9090404@wetwork.net> (raw)
In-Reply-To: <200809301528.26304.mb@bu3sch.de>
Michael Buesch wrote:
> On Tuesday 30 September 2008 07:50:34 Peter Stuge wrote:
>
>> Larry Finger wrote:
>>
>>>> Which specs?
>>>>
>>> The ones generated by the reverse engineers. See
>>> http://bcm-v4.sipsolutions.net/.
>>>
>> Nice work, but as it's a spec of another driver implementation rather
>> than hardware (or even the firmware API) I don't think it should be
>> so authoritative. If other values are clearly better why not use
>> them?
>>
>
> What crap are you smoking?
> The b43 and b43-legacy driver are _based_ on these specifications.
> There are no other specs available.
>
>
If I understand him correctly he's suggesting that there could be BETTER
values than those used by the reference driver. In other words, yes,
B43/B43-Legacy are based on the RE of the Windows driver but perhaps
there are better values that improve behavior beyond that of the
original driver.
He didn't say the following but I will: It's also true that there are
edge cases that RE won't catch without repeated arduous testing in
adverse conditions, and there may be code in the reference driver that
will therefore won't end up in the specs. This means that behavioral
improvements and/or performance gains in B43/B43-Legacy that can be
gained without getting into those edge cases are worthy of consideration
(or maybe specially labeled code).
Just my two farthings worth.
E
--
Legal Disclaimer that you are now contractually bound to under all laws with no recourse:
http://attrition.org/security/rants/z/disclaimers.html
next prev parent reply other threads:[~2008-09-30 13:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 18:31 [RFC/T] b43: to few loop tries in do_dummy_tx Larry Finger
2008-09-29 18:38 ` Michael Buesch
2008-09-29 21:16 ` Peter Stuge
2008-09-29 21:28 ` Larry Finger
2008-09-30 5:50 ` Peter Stuge
2008-09-30 13:28 ` Michael Buesch
2008-09-30 13:46 ` gavron [this message]
2008-09-30 13:54 ` Michael Buesch
2008-09-30 14:11 ` Holger Schurig
2008-09-30 14:22 ` Michael Buesch
2008-09-30 14:13 ` Peter Stuge
2008-09-30 14:21 ` Michael Buesch
2008-09-30 13:26 ` Michael Buesch
2008-09-30 16:34 ` Artem Antonov
2008-09-30 20:02 ` Stefanik Gábor
2008-09-30 22:11 ` Larry Finger
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=48E22D9C.9090404@wetwork.net \
--to=gavron@wetwork.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=peter@stuge.se \
/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).