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: Wed, 24 Apr 2013 16:18:46 +0100 [thread overview]
Message-ID: <5177F7D6.2020800@einfach.org> (raw)
In-Reply-To: <5176F8C2.7050502@broadcom.com>
On 04/23/2013 10:10 PM, Arend van Spriel wrote:
> I am working mainly on brcmfmac. IBSS should work, but reading the
> commit message of your patch I guess it may be a firmware issue so using
> brcmfmac will not make a difference.
I would like to try that to confirm it. And from your message I conclude
the brcmfmac is the way to go forward...
>> 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?
Anyhow I'll debug this further and send you more info later.
Thanks,
bruno
next prev parent reply other threads:[~2013-04-24 15:18 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 [this message]
2013-04-25 18:39 ` Bruno Randolf
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=5177F7D6.2020800@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).