From: "Arend van Spriel" <arend@broadcom.com>
To: "Gottfried Haider" <gottfried.haider@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"Rafał Miłecki" <zajec5@gmail.com>
Subject: Re: brcmsmac and BCM943224HMB (AXI?)
Date: Sun, 15 May 2011 10:38:29 +0200 [thread overview]
Message-ID: <4DCF9105.6010504@broadcom.com> (raw)
In-Reply-To: <BANLkTim78s_5DNateJDc7fF=Kh5bTMSUPw@mail.gmail.com>
On 05/14/2011 04:55 PM, Gottfried Haider wrote:
> Dear Arend,
>
> I am trying to get a BCM943224HMB module (a Half-Mini Card) [1]
> working with the brcmsmac driver.
>
> Broadcom's webpage mentions that the module includes a BCM43224 core
> (in addition to a BCM2070 Bluetooth one), but the device is not
> getting recognized by the driver in -rc7.
>
> Without understanding too much about AXI, I tried both your
> implementation and Rafał's (the latter with the addition of my PCI
> id). Both did not make the device magically work with brcmsmac, but
> with Rafał's code I got the following output, telling me that the
> device indeed makes use of AXI:
There are two modules for this support. One from Rafal called bcma.ko
and I did one called brcmaxi.ko. I did not get combination brcmsmac/bcma
working yet. So the brcmsmac which is in the linux-next tree does not
need either brcmaxi nor bcma. That is work in progress.
> [ 3.651668] bcma-pci-bridge 0000:04:00.0: PCI INT A -> GSI 17
> (level, low) -> IRQ 17
> [ 3.651686] bcma-pci-bridge 0000:04:00.0: setting latency timer to 64
> [ 3.651818] bcma: Core 0 found: ChipCommon (manuf 0x4BF, id 0x800,
> rev 0x22, class 0x0)
> [ 3.651841] bcma: Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812,
> rev 0x17, class 0x0)
> [ 3.651890] bcma: Core 2 found: PCIe (manuf 0x4BF, id 0x820, rev
> 0x0F, class 0x0)
> [ 3.651986] bcma: Switched to core: 0x800
> [ 3.651998] bcma: Found rev 6 PMU (capabilities 0x108C2606)
> [ 3.652020] bcma: Switched to core: 0x820
> [ 3.710315] bcma: Bus registered
>
>
> Since you mentioned that you tested brcmaxi with brcmsmac, can you
> tell me what's missing to get the device working? Is this only a
> question of adding some device IDs to brcmsmac, or does the driver
> need some major changes to talk to the core through bcma/brcmaxi? (Or
> something completely different?)
As said brcmaxi and bcma are not needed for the current brcmsmac.
> thanks for your time,
> Gottfried
>
> [1] 14e4:0576, got this with a ThinkPad x120e .. the closed driver
> detects the device, but insists that it's disabled by a radio switch
> (tested on -rc7)
Let me ask around over here whether adding the device id will work.
Gr. AvS
--
Almost nobody dances sober, unless they happen to be insane.
-- H.P. Lovecraft --
parent reply other threads:[~2011-05-15 8:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <BANLkTim78s_5DNateJDc7fF=Kh5bTMSUPw@mail.gmail.com>]
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=4DCF9105.6010504@broadcom.com \
--to=arend@broadcom.com \
--cc=gottfried.haider@gmail.com \
--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).