From: Andreas Kemnade <andreas@kemnade.info>
To: linux-firmware@kernel.org, linux-wireless@vger.kernel.org
Subject: brcmfmac nvram files best practices
Date: Wed, 28 Sep 2022 00:34:17 +0200 [thread overview]
Message-ID: <20220928003417.0bc3e5f1@aktux> (raw)
Hi,
I am working on mainlining stuff for several ebook readers (esp.
kobo/tolino ones). I often find a CyberTan WC121 (BCM43362) SDIO WiFi
chip there.
That one requires a nvram file. It can be found in the vendor system
(often an ancient 3.0.35 kernel with bcmdhd driver)
So now, it would be nice to have it installed via package management.
A source for that missing file is (besides of sdcard backups of the original
system):
https://download.pageplace.de/ereader/15.3.2/OS44/update.zip
(linked from here: https://mytolino.de/software-updates-tolino-ereader/)
path system/lib/firmware/wc121/nvram.txt needs to be present at
/lib/firmware/brcm/brcmfmac43362-sdio.kobo,tolino-shine2hd.txt
The only problem is that I do not see a distribution license there. So
I am hesitating to just submit that one to the linux-firmware.git
Are there any best practices to deal with that situation? find any
source which also includes a license (and which hopefully allows
distribution)? or is there any way to reverse-engineer that stuff.
How were things done for the nvram.txt files already present in
linux-firmware.git?
Regards,
Andreas Kemnade
reply other threads:[~2022-09-27 22:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220928003417.0bc3e5f1@aktux \
--to=andreas@kemnade.info \
--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