Return-path: Received: from mail-yw0-f46.google.com ([209.85.213.46]:63233 "EHLO mail-yw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754368Ab2FGRZM (ORCPT ); Thu, 7 Jun 2012 13:25:12 -0400 Received: by yhmm54 with SMTP id m54so618442yhm.19 for ; Thu, 07 Jun 2012 10:25:12 -0700 (PDT) Message-ID: <4FD0E3F3.2060900@lwfinger.net> (sfid-20120607_192518_175465_FDDCD1A1) Date: Thu, 07 Jun 2012 12:25:07 -0500 From: Larry Finger MIME-Version: 1.0 To: Andre Heider CC: =?UTF-8?B?TWljaGFlbCBCw7xzY2g=?= , Johannes Berg , linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org, =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= Subject: Re: chip id 4318 regression: WARN_ON_ONCE(sdata->vif.hw_queue[i] >= n_queues)) References: <1339014959.4523.0.camel@jlt3.sipsolutions.net> <1339053364.4517.0.camel@jlt3.sipsolutions.net> <20120607180325.7752b3c0@milhouse> In-Reply-To: <20120607180325.7752b3c0@milhouse> Content-Type: text/plain; charset=UTF-8; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: On 06/07/2012 11:03 AM, Michael Büsch wrote: > > b43 messes with the queue count at runtime. I guess that's the reason. > I don't know if this can be fixed now, though. The problem is that we > first need to load the firmware before we know the queue count. > There seem to have been some firmware loading changes, but I didn't > track those too closely. So I don't know whether they allow fixing the > situation or not... The only change in firmware loading is that the probe routine places a initiates an item on a work queue with the firmware loading routine as the callback. Previously, the fw load routines were called directly from the probe routine. There is a bug in the new implementation that I am fixing. It results in the inability to load firmware whenever b43 is built in; however, as long as b43 is a module, it works fine. I do not understand what is different about your system than mine. I have a Cardbus version of the BCM4318 running kernel 3.5-rc1 from mainline. The host computer is a PowerBook G4 Titanium (PPC). The chip has four hardware queues and never had the problem that was fixed with a9d3c05. When I had trouble, it was with a BCM4301, which does only have a single queue. Is it possible that Nintendo uses a special version of the BCM4318 that only contains a single transmit queue? I'm building 3.5-rc1 from wireless-testing, but that will take a while. That Mac is not very fast. Larry