Message-ID: <45C9F352.3030706@lwfinger.net>
Date: Wed, 07 Feb 2007 09:42:10 -0600
From: Larry Finger <larry.finger@lwfinger.net>
MIME-Version: 1.0
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
References: <45C8E64B.1050605@lwfinger.net>	<200702061848.00815.gene.heskett@verizon.net>	<45C95830.6040507@lwfinger.net>	<200702070303.40968.gene.heskett@verizon.net>	<1170836250.11150.116.camel@dv> <1170861665.6964.4.camel@athena.fprintf.net>
In-Reply-To: <1170861665.6964.4.camel@athena.fprintf.net>
Content-Type: text/plain; charset=ISO-8859-1
Sender: linux-wireless-owner@vger.kernel.org

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