All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Franky Lin" <frankyl@broadcom.com>
To: "Renzo Navas" <renzoefra@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [bcm4329] brcmfmac on kernel 2.6.35 (Andorid)
Date: Wed, 25 Jan 2012 12:29:48 -0800	[thread overview]
Message-ID: <4F20663C.3030500@broadcom.com> (raw)
In-Reply-To: <CAD2CPUEu2ha6TeYrQ4WUdXU0-hdSAAJZR5PGWagSguE1DtBSfQ@mail.gmail.com>

Hi Renzo,

First of all, is it really a good choice to use a fullmac dongle to do 
the scan algorithm investigation? For brcmfmac, all scanning 
implementation is in dongle firmware which is not open source. There is 
nothing much you can do with it. A softmac pci nic probably can meet you 
requirement.

On 01/25/2012 10:03 AM, Renzo Navas wrote:
>    * Is it factible to use the brcmfmac driver on a kernel 2.6.35,
> specifically one made for Android (CyanogenMod 7) kernel?

brcmfmac doesn't have any android support for sure(wake lock, bt coex, 
WIFI_CONTROL_FUNC and etc.).

> For the next 4 following months I will be modifying the bcm4329 driver
> for a Nexus S cellphone (aliases: samsung Ccespo, herring),
> particularly the scanning algorithm.
>
> So far all the android kernel versions for android use a deprecated
> driver called the "bcm4329" -which uses WirelessExtensions-:

For ICS we switch to a newer driver bcmdhd which use cfg80211 instead of 
wext. If you want to use cfg80211 instead of wext, this should be a 
better choice.

> On both testimonies seems to conclude that porting "brcmfmac" for
> android has not been successful.

We do have android support on the roadmap but it's not a high priority 
task because of several reasons.

Franky


  reply	other threads:[~2012-01-25 20:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 18:03 [bcm4329] brcmfmac on kernel 2.6.35 (Andorid) Renzo Navas
2012-01-25 20:29 ` Franky Lin [this message]
2012-01-26 16:04   ` Renzo Navas
2012-01-26 18:55     ` Franky Lin
2012-01-26 16:54 ` Denis 'GNUtoo' Carikli

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=4F20663C.3030500@broadcom.com \
    --to=frankyl@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=renzoefra@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.