From: Paul Cercueil <paul@crapouillou.net>
To: linux-firmware@kernel.org
Cc: linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
SHA-cyfmac-dev-list@infineon.com, linux-mips@vger.kernel.org,
Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Artur Rojek <contact@artur-rojek.eu>
Subject: Please bump brcm/bcm4330-sdio.bin firmware
Date: Mon, 21 Nov 2022 23:06:57 +0000 [thread overview]
Message-ID: <L70QLR.XAGB8X2431341@crapouillou.net> (raw)
Hello,
As a week-end project I got the BCM4330 chip to work with the mainline
Linux kernel on the MIPS CI20 board. One of the problems I was facing
was the firmware crashing, resulting in timeout errors in the brcmfmac
driver.
It turns out the bcm4330-sdio.bin firmware that's currently in
linux-firmware is not the latest one. Running "strings" on the blob
points out to a version 5.90.125.104 dated 2011-10-25. The firmware
that originally came on the CI20 is version 5.90.195.26 dated
2012-05-09, and the version found in Android [1] is 5.90.195.114 dated
2013-01-23. Only the last two will work on the CI20 board.
My question then, could we bump the firmware available in
linux-firmware to the latest version? Or is there a valid reason why an
older firmware is kept in the tree?
Best regards,
-Paul Cercueil
[1]
https://android.googlesource.com/platform/hardware/broadcom/wlan/+/refs/heads/master/bcmdhd/firmware/bcm4330/fw_bcm4330_bg.bin
next reply other threads:[~2022-11-21 23:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 23:06 Paul Cercueil [this message]
2022-11-22 19:35 ` Please bump brcm/bcm4330-sdio.bin firmware Arend van Spriel
2022-11-23 17:54 ` Paul Cercueil
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=L70QLR.XAGB8X2431341@crapouillou.net \
--to=paul@crapouillou.net \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=contact@artur-rojek.eu \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=linux-firmware@kernel.org \
--cc=linux-mips@vger.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).