Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot: enable lib/firmware/brcm for rpi0w
Date: Tue, 23 Mar 2021 20:46:03 +0100	[thread overview]
Message-ID: <20210323204603.60c02d67@gmx.net> (raw)
In-Reply-To: <CAPm8-H4Kq23eCBX0XeZReOdr7hHzQzPymzqZckDDfXCKV1Q_bg@mail.gmail.com>

Hello Laurentiu-Cristian,

On Tue, 23 Mar 2021 12:26:16 +0200, Laurentiu-Cristian Duca <laurentiu.duca@gmail.com> wrote:

> Hello buildroot community,
>
>   Please tell me what option should be enabled
> in buildroot 2020.11 in order to have for raspberry pi zero w:
> output/target/lib/firmware/brcm/brcmfmac43430-sdio.bin
> output/target/lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi-rpi.txt
> output/target/lib/firmware/brcm/brcmfmac43430-sdio.txt
>   These are required by brcmfmac to have wifi working.
> By default they are not installed, even if I do
> make raspberrypi0w_defconfig

Not the buildroot defconfigs are about a minimal starting point (not full featured for
the supported board)....

The option BR2_PACKAGE_RPI_WIFI_FIRMWARE should be the one:
	$ make menuconfig
		--> Target packages
			--> Hardware Handling
				--> Firmware
					--> rpi-wifi-firmware

Regards,
Peter


>
> Thanks
> L-C
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2021-03-23 19:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23 10:26 [Buildroot] Buildroot: enable lib/firmware/brcm for rpi0w Laurentiu-Cristian Duca
2021-03-23 19:46 ` Peter Seiderer [this message]
     [not found] <mailman.13.1616500803.19462.buildroot@busybox.net>
2021-03-24  6:37 ` Andreas Ziegler
2021-03-24 22:27   ` Peter Seiderer
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

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=20210323204603.60c02d67@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