From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: John Keeping <john@metanate.com>
Cc: Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
SHA-cyfmac-dev-list@infineon.com, linux-firmware@kernel.org
Subject: Re: brcm: brcmfmac4339 firmware in linux-firmware
Date: Thu, 26 Jan 2023 11:41:53 +0100 [thread overview]
Message-ID: <a08ccf64-652e-7ca1-2470-01514aab09ec@broadcom.com> (raw)
In-Reply-To: <7ffbf116-3252-8347-a621-ca9ef120e263@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
On 1/26/2023 11:15 AM, Arend van Spriel wrote:
> On 1/10/2023 8:40 PM, John Keeping wrote:
>> That was a follow-up to commit 04f71fe ("cypress: add Cypress firmware
>> and clm_blob files") which provides cypress/cyfmac4339-sdio.bin and
>> links it (via WHENCE) to brcm/brcmfmac4339-sdio.bin and has version:
>
> Looking into this now, but how does this work. What does that (via
> WHENCE)? Guess I missed something fundamental here.
Assuming the copy-firmware.sh is taking care of the links. I guess it
accommodates brcmfmac for older kernels, but I feel an itch to change
the brcmfmac driver and directly refer to the cypress firmware files.
Regards,
Arend
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4219 bytes --]
next prev parent reply other threads:[~2023-01-26 10:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 19:40 brcm: brcmfmac4339 firmware in linux-firmware John Keeping
2023-01-15 19:44 ` Arend van Spriel
2023-01-26 10:15 ` Arend van Spriel
2023-01-26 10:41 ` Arend van Spriel [this message]
2023-01-26 10:49 ` John Keeping
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=a08ccf64-652e-7ca1-2470-01514aab09ec@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=john@metanate.com \
--cc=linux-firmware@kernel.org \
--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.