From: Bruno Randolf <br1@einfach.org>
To: Arend van Spriel <arend@broadcom.com>
Cc: linux-wireless@vger.kernel.org, frankyl@broadcom.com,
meuleman@broadcom.com, brudley@broadcom.com,
brcm80211-dev-list@broadcom.com, 海藻敬之 <tkaiso@thinktube.com>
Subject: Re: Broadcom brcmfmac vs bcmdhd on Android
Date: Thu, 25 Apr 2013 19:39:34 +0100 [thread overview]
Message-ID: <51797866.9030403@einfach.org> (raw)
In-Reply-To: <5177F7D6.2020800@einfach.org>
On 04/24/2013 04:18 PM, Bruno Randolf wrote:
>>> I succeeded to compile brcmfmac from recent compat-drivers against the
>>> "tuna" (Galaxy Nexus) kernel, the modules load, but no device is
>>> recognized. Has anyone succeeded doing this? Is there any chance it can
>>> work?
>>
>> That is how we did it and with success. What do you mean by 'no device
>> is recognized'? Do you have any traces to look at?
>
> Good to know. What I did is I compiled the "tuna" kernel (3.0.31)
> without bcmdhd, then brcmfmac from compat-drivers, loaded the brcmfmac
> module (+ dependencies), but then nothing happens. It looks like the
> device is not recognized on SDIO. Is there anything special I need to do
> to activate the chip?
I spent some more time tracing the problem, without much success. Still
it simply looks like no SDIO device is detected. Please see below for
what I found, maybe something rings a bell for you?
Enabling tracing in the brcmfmac driver shows me
"brcmfmac: brcmf_sdio_init: Enter", nothing more.
Then, I enabled function tracing, here are the relevant parts:
sdio_register_driver <-brcmf_sdio_init
driver_register <-sdio_register_driver
driver_find <-driver_register
bus_add_driver <-driver_register
driver_attach <-bus_add_driver
bus_for_each_dev <-driver_attach
module_add_driver <-bus_add_driver
The rest is sysfs file registration, nothing more interesting, but I can
send you the full dump if you want... No driver probe functions are called.
I see a strange problem with the brcmf_sdmmc_ids:
{SDIO_DEVICE(SDIO_VENDOR_ID_BROADCOM, SDIO_DEVICE_ID_BROADCOM_43241)},
{SDIO_DEVICE(SDIO_VENDOR_ID_BROADCOM, SDIO_DEVICE_ID_BROADCOM_4329)},
{SDIO_DEVICE(SDIO_VENDOR_ID_BROADCOM, SDIO_DEVICE_ID_BROADCOM_4330)},
{SDIO_DEVICE(SDIO_VENDOR_ID_BROADCOM, SDIO_DEVICE_ID_BROADCOM_4334)},
On the Galaxy Nexus modinfo just shows:
alias: sdio:c*v02D0d4334*
alias: sdio:c*v02D0d4329*
I.e. every second device, while on my host the modinfo list looks OK.
I manually changed the list to only include 4330 and that way modinfo
shows it correctly also on the device, but maybe this is part of the
problem?
How did you get it to work? Which device did you use (Galaxy Nexus?)?
Do I need to activate CONFIG_BRCMFMAC_SDIO_OOB (I tried with no difference)?
Thank you for any hints,
bruno
next prev parent reply other threads:[~2013-04-25 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 15:41 Broadcom brcmfmac vs bcmdhd on Android Bruno Randolf
2013-04-23 21:10 ` Arend van Spriel
2013-04-24 15:18 ` Bruno Randolf
2013-04-25 18:39 ` Bruno Randolf [this message]
2013-04-25 21:12 ` Franky Lin
2013-04-25 21:36 ` Bruno Randolf
2013-05-17 19:10 ` Bruno Randolf
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=51797866.9030403@einfach.org \
--to=br1@einfach.org \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brudley@broadcom.com \
--cc=frankyl@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=meuleman@broadcom.com \
--cc=tkaiso@thinktube.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).