From: Hauke Mehrtens <hauke@hauke-m.de>
To: Arend van Spriel <arend@broadcom.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Linux Wireless List <linux-wireless@vger.kernel.org>,
Hante Meuleman <meuleman@broadcom.com>
Subject: Re: [PATCH 4/5] brcmfmac: Add 43143 USB support.
Date: Thu, 18 Oct 2012 14:55:57 +0200 [thread overview]
Message-ID: <507FFC5D.7010108@hauke-m.de> (raw)
In-Reply-To: <1346348582-20095-5-git-send-email-arend@broadcom.com>
On 08/30/2012 07:43 PM, Arend van Spriel wrote:
> From: Hante Meuleman <meuleman@broadcom.com>
>
> Added usb device id to list of supported devices. 43143 is a new
> 802.11n single stream device.
>
> Reviewed-by: Arend Van Spriel <arend@broadcom.com>
> Reviewed-by: Pieter-Paul Giesberts <pieterpg@broadcom.com>
> Signed-off-by: Hante Meuleman <meuleman@broadcom.com>
> Signed-off-by: Arend van Spriel <arend@broadcom.com>
> ---
>
> +#define BRCMF_USB_43143_FW_NAME "brcm/brcmfmac43143.bin"
> #define BRCMF_USB_43236_FW_NAME "brcm/brcmfmac43236b.bin"
> #define BRCMF_USB_43242_FW_NAME "brcm/brcmfmac43242a.bin"
>
Hi,
when do you release the firmware for this devices to the public? I can
not find it in linux-firmware or with a quick google search. I haven't
found the brcmfmac43242a.bin firmware either.
Hauke
next prev parent reply other threads:[~2012-10-18 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 17:42 [PATCH 0/5] brcmfmac: add support for new fullmac devices Arend van Spriel
2012-08-30 17:42 ` [PATCH 1/5] brcmfmac: prevent possible race condition on usb rx control Arend van Spriel
2012-08-30 17:42 ` [PATCH 2/5] brcmfmac: add BCM43241 sdio interface driver support Arend van Spriel
2012-08-30 17:43 ` [PATCH 3/5] brcmfmac: Add 43242 USB support Arend van Spriel
2012-08-30 17:43 ` [PATCH 4/5] brcmfmac: Add 43143 " Arend van Spriel
2012-10-18 12:55 ` Hauke Mehrtens [this message]
2012-12-10 8:01 ` Rafał Miłecki
2012-08-30 17:43 ` [PATCH 5/5] brcmfmac: add callback for nl80211 testmode command Arend van Spriel
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=507FFC5D.7010108@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=meuleman@broadcom.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).