From: Kalle Valo <kvalo@codeaurora.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Arend van Spriel <arend.vanspriel@broadcom.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Hans de Goede <hdegoede@redhat.com>,
Jelle van der Waa <jelle@vdwaa.nl>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com
Subject: Re: [2/2] brcmfmac: Use separate firmware for revision 0 of the brcm43430 chip
Date: Wed, 21 Jun 2017 15:21:24 +0000 (UTC) [thread overview]
Message-ID: <20170621152125.0735060854@smtp.codeaurora.org> (raw)
In-Reply-To: <20170616131449.12108-2-hdegoede@redhat.com>
Hans de Goede <hdegoede@redhat.com> wrote:
> The brcm43430 chip needs different firmware files for chip revision 0
> and 1. The file currently in linux-firmware is for revision 1 only.
>
> This commit makes brcmfmac request brcmfmac43430a0-sdio.bin instead
> of brcmfmac43430-sdio.bin for revision 0 chips.
>
> Note that the behavior for revision 1 chips is not changed, ideally those
> would load brcmfmac43430a1-sdio.bin, but that will break existing setups.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> Acked-by: Arend van Spriel <arend.vanspriel@broadcom.com>
Patch applied to wireless-drivers-next.git, thanks.
1278bd149839 brcmfmac: Use separate firmware for revision 0 of the brcm43430 chip
--
https://patchwork.kernel.org/patch/9791523/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2017-06-21 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 13:14 [PATCH 1/2] brcmfmac: Log chip id and revision Hans de Goede
2017-06-16 13:14 ` [PATCH 2/2] brcmfmac: Use separate firmware for revision 0 of the brcm43430 chip Hans de Goede
2017-06-16 20:19 ` Arend van Spriel
2017-06-21 15:21 ` Kalle Valo [this message]
2017-08-25 13:55 ` Jörg Krause
2017-08-25 14:03 ` Hans de Goede
2017-08-25 14:49 ` Jörg Krause
2017-08-25 14:53 ` Hans de Goede
2017-08-25 13:55 ` Jörg Krause
2017-06-16 20:18 ` [PATCH 1/2] brcmfmac: Log chip id and revision 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=20170621152125.0735060854@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=hdegoede@redhat.com \
--cc=jelle@vdwaa.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.