From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Stefanik Gábor" <netrolller.3d@gmail.com>
Cc: Artem Antonov <artem.v.antonov@gmail.com>,
wireless <linux-wireless@vger.kernel.org>,
Broadcom Linux <bcm43xx-dev@lists.berlios.de>,
Michael Buesch <mb@bu3sch.de>
Subject: Re: [RFC/T] b43: to few loop tries in do_dummy_tx
Date: Tue, 30 Sep 2008 17:11:41 -0500 [thread overview]
Message-ID: <48E2A41D.9010206@lwfinger.net> (raw)
In-Reply-To: <69e28c910809301302w48b3d982r5ddac62e459a1ca8@mail.gmail.com>
Stefanik G=E1bor wrote:
>=20
> It would be good to know whether the Windows driver also suffers from
> PHY transmission errors... The "hybrid" Linux driver likely does have
> them, possibly even more than us, judging from its poor performance.
>=20
We didn't see the PHY transmission errors in b43 until fairly
recently. Unfortunately, they are too intermittent to tell if it is a
regression, and more importantly, it would be a bitch to bisect the
code as one would need many weeks of testing before saying that a
particular kernel was good.
When I first got 64-bit dma working on a BCM4311/2, there was always
one such error. That was removed when Michael changed the dma code.
Now I do not get any on most runs, but every once in a while (3 times
since July!), I get a storm of these.
Unlike most of you, I have seen the Broadcom code. There is almost no
error checking in their routines, which is good for us - it makes the
code smaller and the decompilation easier. I will never RE the binary
blob of the hybrid driver for a number of reasons; however, I doubt
that their culture has changed. As to why their driver has such poor
performance, your guess is as good as mine.
Larry
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-09-30 22:11 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
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 [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=48E2A41D.9010206@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=artem.v.antonov@gmail.com \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=netrolller.3d@gmail.com \
/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).