From: Peter Stuge <peter@stuge.se>
To: Michael Buesch <mb@bu3sch.de>
Cc: bcm43xx-dev@lists.berlios.de, wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC/T] b43: to few loop tries in do_dummy_tx
Date: Tue, 30 Sep 2008 16:13:53 +0200 [thread overview]
Message-ID: <20080930141353.16996.qmail@stuge.se> (raw)
In-Reply-To: <200809301528.26304.mb@bu3sch.de>
Michael Buesch wrote:
> > 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?
Maybe we just miscommunicated, or maybe I misunderstood something
about the reverse engineering process. I am very new to this project.
> The b43 and b43-legacy driver are _based_ on these specifications.
> There are no other specs available.
I know. Allow me to clarify my train of thought:
* Specs are created by reverse engineering of a binary blob.
* After development of b43*, many can happily use the drivers. \o/
* As it turns out, b43* can be made even more reliable by doing
things slightly different than what the specs say. Case in point
looping a little longer.
At this point, if there are only/mostly benefits, I don't see why
deviating from the specs is bad - after all they "only" document
another driver, right?
//Peter
next prev parent reply other threads:[~2008-09-30 14:13 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
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 [this message]
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=20080930141353.16996.qmail@stuge.se \
--to=peter@stuge.se \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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).