From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14676] New: BRCMFMAC SDIO firmware doesn't copy to target
Date: Tue, 22 Mar 2022 12:35:05 +0000 [thread overview]
Message-ID: <bug-14676-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=14676
Bug ID: 14676
Summary: BRCMFMAC SDIO firmware doesn't copy to target
Product: buildroot
Version: 2022.02
Hardware: PC
OS: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: dmanlfc@gmail.com
CC: buildroot@uclibc.org
Target Milestone: ---
package BR2_PACKAGE_BRCMFMAC_SDIO_FIRMWARE_RPI doesn't copy the firmware to the
target directory.
My workaround:
config BR2_PACKAGE_BRCMFMAC_SDIO_FIRMWARE_RPI
bool "brcmfmac-sdio-firmware-rpi"
depends on BR2_arm || BR2_aarch64
select BR2_PACKAGE_BRCMFMAC_SDIO_FIRMWARE_RPI_BT # batocera - BR
fix
select BR2_PACKAGE_BRCMFMAC_SDIO_FIRMWARE_RPI_WIFI # batocera - BR
fix
help
Raspberry Broadcom Bluetooth and Wifi firmware.
Alternatively remove the ifeq ($(BR2_PACKAGE_BRCMFMAC_SDIO_FIRMWARE_RPI_BT),y)
& ifeq ($(BR2_PACKAGE_BRCMFMAC_SDIO_FIRMWARE_RPI_WIFI),y) conditionals from the
makefile.
Dan
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-03-22 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 12:35 bugzilla [this message]
2022-03-22 18:55 ` [Buildroot] [Bug 14676] BRCMFMAC SDIO firmware doesn't copy to target bugzilla
2022-03-22 22:34 ` bugzilla
2022-03-23 8:13 ` bugzilla
2022-03-23 18:58 ` bugzilla
2024-06-15 15:00 ` bugzilla
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=bug-14676-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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