Date: Wed, 09 Jun 2010 10:33:26 -0700 (PDT)
Message-Id: <20100609.103326.189711649.davem@davemloft.net>
To: reinette.chatre@intel.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: iwlagn fails to assoc with nexus one in ad-hoc mode
From: David Miller <davem@davemloft.net>
In-Reply-To: <1276102692.1835.14610.camel@rchatre-DESK>
References: <20100607.214612.26938385.davem@davemloft.net>
	<1276102692.1835.14610.camel@rchatre-DESK>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Sender: linux-wireless-owner@vger.kernel.org

From: reinette chatre <reinette.chatre@intel.com>
Date: Wed, 09 Jun 2010 09:58:12 -0700

> Hi David,
> 
> On Mon, 2010-06-07 at 21:46 -0700, David Miller wrote:
>> When I try to associate the wireless activity light blinks like
>> crazy and I get kernel log dumps like the one at the end of
>> this email.
> 
> Which hardware are you using? This information is needed to decode the
> firmware assert you are posting.

5300

> 
>> 
>> The nexus one uses a Broadcom BCM4328 for wireless.
>> 
>> Windows 7 users report the same problem with Intel wireless, and that
>> upgrading to the Intel wireless windows driver, version 13.1.1.1,
>> fixes the problem.
> 
> Any idea what they upgraded _from_ ?

13.0, and I believe it says this in the report I gave the URL for,
there might be other bits of useful information there :-)