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: brcm: brcmfmac4339 firmware in linux-firmware
Date: Tue, 10 Jan 2023 19:40:57 +0000 [thread overview]
Message-ID: <Y72/Sd/8mMOx13lk@donbot> (raw)
Hi Arend & all,
In linux-firmware, commit 0707b2f ("brcm: add/update firmware files for
brcmfmac driver") adds brcm/brcmfmac4339-sdio.bin with version:
Firmware: BCM4339/2 wl0: Feb 17 2016 18:29:33 version 6.37.32.RC23.34.42 (r608406)
This restores the version previously removed by commit 0f0aefd ("brcm:
remove old brcm firmwares that have newer cypress variants").
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:
Firmware: BCM4339/2 wl0: Sep 5 2019 11:05:52 version 6.37.39.113 (r722271 CY)
It looks like the same also applies to a few other firmware, although I
don't have the hardware to check the relevant versions there.
Should part of 0707b2f ("brcm: add/update firmware files for brcmfmac
driver") be reverted in favour of the files in cypress/? (It looks like
these will already be used due to the order of the file so the symlinks
to cypress/... will overwrite files installed from brcm/...)
Thanks,
John
next reply other threads:[~2023-01-10 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 19:40 John Keeping [this message]
2023-01-15 19:44 ` brcm: brcmfmac4339 firmware in linux-firmware 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
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=Y72/Sd/8mMOx13lk@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 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.