From: Kalle Valo <kvalo@codeaurora.org>
To: Mikhail Rudenko <mike.rudenko@gmail.com>
Cc: linux-wireless@vger.kernel.org,
Mikhail Rudenko <mike.rudenko@gmail.com>,
Arend van Spriel <arend.vanspriel@broadcom.com>
Subject: Re: [PATCH v3] brcmfmac: use separate firmware for 43430 revision 2
Date: Sat, 21 Aug 2021 16:58:18 +0000 (UTC) [thread overview]
Message-ID: <20210821165818.5AB80C4360D@smtp.codeaurora.org> (raw)
In-Reply-To: <20210804231308.576071-1-mike.rudenko@gmail.com>
Mikhail Rudenko <mike.rudenko@gmail.com> wrote:
> A separate firmware is needed for Broadcom 43430 revision 2. This
> chip can be found in e.g. certain revisions of Ampak AP6212 wireless
> IC. Original firmware file from IC vendor is named
> 'fw_bcm43436b0.bin', but brcmfmac and also btbcm drivers report chip
> id 43430, so requested firmware file name is
> 'brcmfmac43430b0-sdio.bin' in line with other 43430 revisions.
>
> Reviewed-by: Arend van Spriel <arend.vanspriel@broadcom.com>
> Signed-off-by: Mikhail Rudenko <mike.rudenko@gmail.com>
Patch applied to wireless-drivers-next.git, thanks.
f8d6523891cf brcmfmac: use separate firmware for 43430 revision 2
--
https://patchwork.kernel.org/project/linux-wireless/patch/20210804231308.576071-1-mike.rudenko@gmail.com/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-08-21 16:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-09 23:30 [PATCH] brcmfmac: use separate firmware for 43430 revision 2 Mikhail Rudenko
2021-05-10 8:06 ` Arend van Spriel
2021-05-14 9:41 ` Mikhail Rudenko
2021-05-21 13:22 ` Mikhail Rudenko
2021-06-24 16:39 ` Kalle Valo
2021-06-28 10:11 ` Arend van Spriel
2021-06-28 12:16 ` Arend van Spriel
2021-06-28 14:05 ` Mikhail Rudenko
2021-06-28 14:54 ` [PATCH v2] " Mikhail Rudenko
2021-08-01 10:25 ` Kalle Valo
2021-08-04 23:13 ` [PATCH v3] " Mikhail Rudenko
2021-08-21 16:58 ` Kalle Valo [this message]
2021-08-16 13:59 ` [PATCH v2] " Mikhail Rudenko
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=20210821165818.5AB80C4360D@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mike.rudenko@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 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).