From: John Keeping <john@metanate.com>
To: Arend van Spriel <arend.vanspriel@broadcom.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 10:49:56 +0000 [thread overview]
Message-ID: <Y9Ja1CM5tgkditHK@donbot> (raw)
In-Reply-To: <a08ccf64-652e-7ca1-2470-01514aab09ec@broadcom.com>
On Thu, Jan 26, 2023 at 11:41:53AM +0100, Arend van Spriel wrote:
> 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.
Yes, `make install` calls copy-firmware.sh which reads the Link: lines
from WHENCE and creates the symlinks specified by those lines.
Regards,
John
prev parent reply other threads:[~2023-01-26 10:50 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
2023-01-26 10:49 ` John Keeping [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=Y9Ja1CM5tgkditHK@donbot \
--to=john@metanate.com \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.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 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).