From: Larry Finger <larry.finger@lwfinger.net>
To: Daniel Gryniewicz <dang@fprintf.net>
Cc: Pavel Roskin <proski@gnu.org>,
wireless <linux-wireless@vger.kernel.org>,
bcm43xx-dev@lists.berlios.de
Subject: Re: RFT bcm43xx: Really _GOOD_ news
Date: Wed, 07 Feb 2007 09:42:10 -0600 [thread overview]
Message-ID: <45C9F352.3030706@lwfinger.net> (raw)
In-Reply-To: <1170861665.6964.4.camel@athena.fprintf.net>
Daniel Gryniewicz wrote:
> On Wed, 2007-02-07 at 03:17 -0500, Pavel Roskin wrote:
>> On Wed, 2007-02-07 at 03:03 -0500, Gene Heskett wrote:
>>
>>> And the 4318 is whats in my lappy. What does it break?
>> Oh, please, let's stop such questions. Does it really matter what some
>> knowingly wrong change does to particular hardware? Just don't try the
>> old patch. Just forget that it existed. It's not going to the kernel.
>>
>> Please try the new patch. Ideally, measure speeds for various rates,
>> because it's the speed that the patch is supposed to improve.
>>
>> If you have more questions of this kind, please make sure my personal
>> e-mail is not in CC.
>>esg
>
> Except that the new patch changes nothing for us poor 4318 users, so
> what's the point of trying it?
>
> That said, I'm running the broken patch right now, and my 4318 is
> working better than ever before, so it changed *something* for my card.
Intriguing. Please send me the output of 'dmesg | grep bcm43xx'. Thanks.
Larry
next prev parent reply other threads:[~2007-02-07 15:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 20:34 RFT bcm43xx: Really _GOOD_ news Larry Finger
2007-02-06 21:37 ` Gene Heskett
2007-02-06 22:29 ` Pavel Roskin
2007-02-06 23:48 ` Gene Heskett
2007-02-07 4:40 ` Larry Finger
2007-02-07 8:03 ` Gene Heskett
2007-02-07 8:17 ` Pavel Roskin
2007-02-07 15:21 ` Daniel Gryniewicz
2007-02-07 15:42 ` Larry Finger [this message]
2007-02-06 22:18 ` Pavel Roskin
2007-02-06 22:27 ` Rafael J. Wysocki
2007-02-07 1:08 ` Larry Finger
2007-02-08 18:20 ` Jory A. Pratt
2007-02-09 0:05 ` John W. Linville
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=45C9F352.3030706@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=dang@fprintf.net \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.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).