From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot: enable lib/firmware/brcm for rpi0w
Date: Wed, 24 Mar 2021 23:27:03 +0100 [thread overview]
Message-ID: <20210324232703.46b691fe@gmx.net> (raw)
In-Reply-To: <75b24e8f6fe588935be2f1320d172d68@umbiko.net>
Hello Laurentiu-Cristian, Andreas,
On Wed, 24 Mar 2021 06:37:23 +0000, Andreas Ziegler <br015@umbiko.net> wrote:
> Hello Laurentiu-Cristian,
>
> > Subject: [Buildroot] Buildroot: enable lib/firmware/brcm for rpi0w
>
> > output/target/lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi-rpi.txt
>
> The nvram file with 'raspberrypi' in its name is not present in the
> rpi-wifi-firmware blob; you need to create it yourself. As an example,
> this is what I use in a post-build script for a RPi4:
>
> ### create missing nvram file for Raspberry Pi 4
> _TARGET_DIR="${TARGET_DIR}/lib/firmware"
> src_file=brcm/brcmfmac43455-sdio.txt
> dst_file=brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt
> if [ -f ${_TARGET_DIR}/${src_file} ] && ! [ -h
> ${_TARGET_DIR}/${dst_file} ]; then
> ln -rs ${_TARGET_DIR}/${src_file} ${_TARGET_DIR}/${dst_file}
> fi
Or use BR2_PACKAGE_LINUX_FIRMWARE/BR2_PACKAGE_LINUX_FIRMWARE_BRCM_BCM43XXX
already containing the file brcmfmac43455-sdio.raspberrypi,4-model-b.txt
([1], but according to [2],[3],[4] the linux-firmware provided files are
'older than that used by the Raspbian distribution, and has (in certain situations)
significantly worse performance than it (and indeed with some APs, will not
associate at all).')?
Did not (yet) compare the various provided firmware files:
- http://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
- github,LibreELEC,brcmfmac_sdio-firmware-rpi
- https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm
Regards,
Peter
[1] https://git.buildroot.net/buildroot/tree/package/linux-firmware/linux-firmware.mk#n602
[2] https://forums.gentoo.org/viewtopic-t-1108138-start-0.html
[3] https://forums.gentoo.org/viewtopic-p-8398532.html#8398532
[4] https://forum.manjaro.org/t/significant-wifi-speed-increase-with-latest-firmware/43607
>
> Kind regards,
> Andreas
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-03-24 22:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.13.1616500803.19462.buildroot@busybox.net>
2021-03-24 6:37 ` [Buildroot] Buildroot: enable lib/firmware/brcm for rpi0w Andreas Ziegler
2021-03-24 22:27 ` Peter Seiderer [this message]
2021-03-25 9:45 ` Andreas Ziegler
2021-03-25 21:20 ` Peter Seiderer
2021-03-26 12:47 ` Andreas Ziegler
2021-03-29 18:49 ` Peter Seiderer
2021-03-30 8:20 ` Andreas Ziegler
2021-03-30 18:32 ` Peter Seiderer
2021-03-23 10:26 Laurentiu-Cristian Duca
2021-03-23 19:46 ` Peter Seiderer
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=20210324232703.46b691fe@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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