linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: <linux-sunxi@googlegroups.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [linux-sunxi] Firmware for Bluetooth (and wifi)
Date: Fri, 6 Dec 2013 10:00:47 +0100	[thread overview]
Message-ID: <52A1923F.40806@broadcom.com> (raw)
In-Reply-To: <CAGRGNgWBgWqoPUdHSm2OXGb8r-ca5NX2z4_v0eG6oOMgJRd3HQ@mail.gmail.com>

On 12/05/2013 10:46 PM, Julian Calaby wrote:
> Hi Arend,
>
> I watch the linux-sunxi list where we're trying to support a certain
> family of ARM chips and the boards they're on with open source,
> community maintained kernels. They're at the cheaper end of the
> spectrum so they usually end up with chipsets which are bought for
> their price point and Android compatibility, not their ease of use by
> people doing "generic" Linux.
>
> On Fri, Dec 6, 2013 at 2:27 AM, Olliver Schinagl
> <oliver+list@schinagl.nl> wrote:
>> On 05-12-13 14:25, Neal Peacock wrote:
>>>
>>>
>>> On Dec 5, 2013 4:02 AM, "Olliver Schinagl" <oliver+list@schinagl.nl
>>> <mailto:oliver%2Blist@schinagl.nl>> wrote:
>>>   >
>>>   > Hey Benn,
>>>   >
>>>   > it appears as if the bluetooth module requires specific firmware to
>>> operate, it's likly the FM module requires it too?
>>>   >
>>>   > Can you confirm this or wether the firmware for the wifi module also
>>> contains the BT and FM firmwares?
>>>   >
>>> Which WiFi chip is this for?
>>
>> Wifi is mostly handled by extracting it from the broadcom drivers I belive
>> via a script, but BT we are in the dark for.
>
> So, the AMPAK AP6210 Wifi+BT combo device contains one of:
> 1. BCM43362 / BCM20710
> 2. BCM4330 / BCM40183
> 3. BCM4329 / BCM40181
>
> Depending on who you talk to. I can only find one reference for
> options #1 and #3, so I suspect it's the BCM4330 based chipset,
> however I don't have one of these I can crack open so I'm not sure.

All these options are SDIO, right?

> Firstly, are there any plans to support the BCM43362 chipset with the
> brcmfmac driver in the near future?

We had someone from the community asking about that earlier and it 
looked trivial to add it. I will get back on this.

> Secondly, is there an upstream driver for the bluetooth parts of these
> chipsets, and if so, do we need firmware and where can we get it from?
> If there isn't, are there any plans to add support for them?

The BT part is done by another group within broadcom so I have no idea 
about their plans. I suspect they can be supported by generic btsdio 
driver, but I may be totally mistaken.

Gr. AvS

  reply	other threads:[~2013-12-06  9:10 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <52A040CE.5040706@schinagl.nl>
     [not found] ` <CAFXj5xjJ0DTa0Qo1avLboQF-e3TFv3aEr_jjkuZjinwuTzXykQ@mail.gmail.com>
     [not found]   ` <52A09B5B.70800@schinagl.nl>
2013-12-05 21:46     ` [linux-sunxi] Firmware for Bluetooth (and wifi) Julian Calaby
2013-12-06  9:00       ` Arend van Spriel [this message]
2013-12-18 10:31       ` Arend van Spriel
2013-12-18 13:12         ` Hans de Goede
2013-12-18 16:16           ` Arend van Spriel
2013-12-18 16:39             ` Chen-Yu Tsai
2013-12-19 10:12               ` Chen-Yu Tsai
2013-12-26 16:13                 ` Chen-Yu Tsai
2013-12-26 20:29                   ` Hans de Goede
2013-12-27 11:47                   ` Arend van Spriel
2013-12-27 12:36                     ` Chen-Yu Tsai
2014-01-02 13:59                       ` Arend van Spriel
2014-01-02 17:09                         ` Chen-Yu Tsai
     [not found]                           ` <5ce9ab14-5794-4c0d-a859-7a158655f58e@googlegroups.com>
2014-01-02 19:26                             ` Michal Suchanek
2014-01-02 20:29                             ` Arend van Spriel
2014-01-02 21:03                           ` Arend van Spriel
2014-01-03  3:02                             ` Chen-Yu Tsai
2014-01-08  8:56                       ` Arend van Spriel
2014-01-08  9:23                         ` Chen-Yu Tsai
2014-01-08  9:33                           ` Arend van Spriel
2014-01-08 10:17                             ` Chen-Yu Tsai
2014-01-23 22:39                           ` Hans de Goede
2014-01-24 10:25                             ` Arend van Spriel
2014-01-24 16:34                               ` Hans de Goede
2014-01-26  8:53                                 ` Arend van Spriel
2014-01-26  8:56                                   ` Arend van Spriel
2014-01-26 10:23                                   ` Hans de Goede
2014-01-26 12:58                                     ` Arend van Spriel
2014-01-26 13:19                                       ` Hans de Goede
2014-01-26 12:07                                   ` Hans de Goede
2014-01-26 15:49                                   ` Hans de Goede
2014-01-26 11:04                                 ` Arend van Spriel
2014-01-26 12:09                                   ` Hans de Goede
2014-01-26 12:50                                     ` Arend van Spriel
2014-01-02 16:52                 ` Michal Suchanek
2014-01-02 17:11                   ` Chen-Yu Tsai

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=52A1923F.40806@broadcom.com \
    --to=arend@broadcom.com \
    --cc=julian.calaby@gmail.com \
    --cc=linux-sunxi@googlegroups.com \
    --cc=linux-wireless@vger.kernel.org \
    /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).