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>, <linux-sunxi@googlegroups.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Chen-Yu Tsai <wens@csie.org>
Subject: Re: [linux-sunxi] [PATCH] brcmfmac: add support for bcm43362 device
Date: Wed, 8 Jan 2014 18:40:59 +0100	[thread overview]
Message-ID: <52CD8DAB.8040307@broadcom.com> (raw)
In-Reply-To: <CAGRGNgWySMpEecaPFL0NuynSwCik17xGRPk44z5cw+AAckaBvA@mail.gmail.com>

On 01/08/2014 01:49 PM, Julian Calaby wrote:
> Hi Arend,
> 
> On Wed, Jan 8, 2014 at 8:49 PM, Arend van Spriel <arend@broadcom.com> wrote:
>> This patch adds support for the bcm43362 1x1 11n chipset. This
>> chipset is used in AP6210 wifi module found on Cubieboard [1].
>>
>> [1] http://cubieboard.org/
>>
>> Reviewed-by: Franky Lin <frankyl@broadcom.com>
>> Reviewed-by: Pieter-Paul Giesberts <pieterpg@broadcom.com>
>> Reviewed-by: Hante Meuleman <meuleman@broadcom.com>
>> Signed-off-by: Arend van Spriel <arend@broadcom.com>
>> ---
>> Hi John,
>>
>> Here a straggler for new device support that people
>> playing with Cubieboards have been asking for. Intended
>> for v3.14 kernel.
>>
>> Regards,
>> Arend
>> ---
>>  drivers/net/wireless/brcm80211/brcmfmac/bcmsdh.c   |    1 +
>>  drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c |    5 +++
>>  .../net/wireless/brcm80211/brcmfmac/sdio_chip.c    |   33 ++++++++++++++++++++
>>  .../net/wireless/brcm80211/include/brcm_hw_ids.h   |    1 +
>>  4 files changed, 40 insertions(+)
>>
>> diff --git a/drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c b/drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c
>> index 2bf4757..9c7f08a 100644
>> --- a/drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c
>> +++ b/drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c
>> @@ -509,6 +509,8 @@ enum brcmf_sdio_frmtype {
>>  #define BCM4334_NVRAM_NAME             "brcm/brcmfmac4334-sdio.txt"
>>  #define BCM4335_FIRMWARE_NAME          "brcm/brcmfmac4335-sdio.bin"
>>  #define BCM4335_NVRAM_NAME             "brcm/brcmfmac4335-sdio.txt"
>> +#define BCM43362_FIRMWARE_NAME         "brcm/brcmfmac43362-sdio.bin"
>> +#define BCM43362_NVRAM_NAME            "brcm/brcmfmac43362-sdio.txt"
> 
> I haven't been following the discussion so this may be redundant, but
> is this firmware is presently winging it's way towards Linux-firmware?

Hi Julian,

The patch for that still has to go out. I am looking whether we have a
newer firmware release as the one found on cubieboard.org [1]. So the
firmware did not set sail yet (expect it soon :-) ).

Regards,
Arend

[1] http://dl.cubieboard.org/public/Cubieboard/benn/firmware/ap6210/

  reply	other threads:[~2014-01-08 17:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08  9:49 [PATCH] brcmfmac: add support for bcm43362 device Arend van Spriel
2014-01-08 12:49 ` [linux-sunxi] " Julian Calaby
2014-01-08 17:40   ` Arend van Spriel [this message]
2014-01-09 10:48 ` Rafał Miłecki

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=52CD8DAB.8040307@broadcom.com \
    --to=arend@broadcom.com \
    --cc=julian.calaby@gmail.com \
    --cc=linux-sunxi@googlegroups.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=wens@csie.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).