From: Kalle Valo <kvalo@codeaurora.org>
To: Sean Lanigan <sean@lano.id.au>
Cc: arend.vanspriel@broadcom.com, franky.lin@broadcom.com,
hante.meuleman@broadcom.com, chi-hsien.lin@cypress.com,
wright.feng@cypress.com, ulf.hansson@linaro.org,
ian@mnementh.co.uk, linux-wireless@vger.kernel.org,
brcm80211-dev-list@cypress.com, linux-mmc@vger.kernel.org,
Sean Lanigan <sean@lano.id.au>
Subject: Re: brcmfmac: Add support for bcm43364 wireless chipset
Date: Wed, 9 May 2018 10:25:11 +0000 (UTC) [thread overview]
Message-ID: <20180509102511.E97F160FA8@smtp.codeaurora.org> (raw)
In-Reply-To: <1525416503-832-1-git-send-email-sean@lano.id.au>
Sean Lanigan <sean@lano.id.au> wrote:
> Add support for the BCM43364 chipset via an SDIO interface, as used in
> e.g. the Murata 1FX module.
>
> The BCM43364 uses the same firmware as the BCM43430 (which is already
> included), the only difference is the omission of Bluetooth.
>
> However, the SDIO_ID for the BCM43364 is 02D0:A9A4, giving it a MODALIAS
> of sdio:c00v02D0dA9A4, which doesn't get recognised and hence doesn't
> load the brcmfmac module. Adding the 'A9A4' ID in the appropriate place
> triggers the brcmfmac driver to load, and then correctly use the
> firmware file 'brcmfmac43430-sdio.bin'.
>
>
> Signed-off-by: Sean Lanigan <sean@lano.id.au>
> Acked-by: Ulf Hansson <ulf.hansson@linaro.org>
Patch applied to wireless-drivers-next.git, thanks.
9c4a121e8263 brcmfmac: Add support for bcm43364 wireless chipset
--
https://patchwork.kernel.org/patch/10380047/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2018-05-09 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 6:48 [PATCH] brcmfmac: Add support for bcm43364 wireless chipset Sean Lanigan
2018-05-08 7:58 ` Ulf Hansson
2018-05-08 12:11 ` Arend van Spriel
2018-05-08 12:51 ` Kalle Valo
2018-05-09 10:25 ` Kalle Valo [this message]
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=20180509102511.E97F160FA8@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=chi-hsien.lin@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=ian@mnementh.co.uk \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sean@lano.id.au \
--cc=ulf.hansson@linaro.org \
--cc=wright.feng@cypress.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).