linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Hauke Mehrtens" <hauke@hauke-m.de>
Subject: Re: bcma-pci-bridge issue with bcm43224
Date: Wed, 11 Jul 2012 17:55:59 +0200	[thread overview]
Message-ID: <4FFDA20F.4000308@broadcom.com> (raw)
In-Reply-To: <CACna6rxf2bmhEKqGPcgP50au=XxeRHUQUvMm1OSidp+oQ6ycuA@mail.gmail.com>

On 07/11/2012 04:32 PM, Rafał Miłecki wrote:
> 2012/7/11 Arend van Spriel <arend@broadcom.com>:
>> Hi Rafal
>>
>> I am testing with BCM43224 in PCIe slot:
>> $ lspci -vns 03:00.0
>> 03:00.0 0280: 14e4:4353 (rev 01)
>>         Subsystem: 1028:000e
>>         Flags: bus master, fast devsel, latency 0, IRQ 17
>>         Memory at e6e00000 (64-bit, non-prefetchable) [size=16K]
>>         Capabilities: <access denied>
>>         Kernel driver in use: bcma-pci-bridge
>>
>> In the log the irq field in the bcma_device structure is printed in
>> brcmsmac probe function and the value seems invalid hence the
>> request_irq() failure. Any clues?
>>
>> Gr. AvS
>>
>> [86629.110723] bcma: bus0: Found chip with id 0xA8D8, rev 0x01 and
>> package 0x0A
>> [86629.110783] bcma: bus0: Core 0 found: ChipCommon (manuf 0x4BF, id
>> 0x800, rev 0x22, class 0x0)
>> [86629.110828] bcma: bus0: Core 1 found: IEEE 802.11 (manuf 0x4BF, id
>> 0x812, rev 0x17, class 0x0)
>> [86629.110939] bcma: bus0: Core 2 found: PCIe (manuf 0x4BF, id 0x820,
>> rev 0x0F, class 0x0)
>> [86629.144286] bcma: bus0: Bus registered
>> [86672.144812] brcmsmac bcma0:0: mfg 4bf core 812 rev 23 class 0 irq
>> -421527552
>> [86672.150745] brcmsmac: Applying 43224B0+ WARs
>> [86672.153155] ieee80211 phy0: wl0: request_irq() failed
>> [86672.153169] brcmsmac: brcms_bcma_probe: brcms_attach failed!
> 
> No idea at the moment. I can setup my machine and give it a try. I'll
> need a day or rather two.
> 
> Are you using wireless-testing?
> 

Yes. My branch is based on

commit 43eec16e655eeaee396fe20ab2e92f0fee5a9440
Merge: bb75604 abb14fc
Author: John W. Linville <linville@tuxdriver.com>
Date:   Fri Jul 6 16:30:45 2012 -0400

Gr. AvS


  reply	other threads:[~2012-07-11 15:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11 13:09 bcma-pci-bridge issue with bcm43224 Arend van Spriel
2012-07-11 14:32 ` Rafał Miłecki
2012-07-11 15:55   ` Arend van Spriel [this message]
2012-07-14  9:48   ` Arend van Spriel
2012-07-15 13:00     ` Hauke Mehrtens
2012-07-21  9:03 ` Rafał Miłecki

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=4FFDA20F.4000308@broadcom.com \
    --to=arend@broadcom.com \
    --cc=hauke@hauke-m.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=zajec5@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).