From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14676] BRCMFMAC SDIO firmware doesn't copy to target
Date: Wed, 23 Mar 2022 08:13:06 +0000 [thread overview]
Message-ID: <bug-14676-163-b1v4WnuqKI@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14676-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14676
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yann.morin.1998@free.fr
--- Comment #3 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Daniel, All,
As Fabrice explained, the goal is for a user to be able to choose either
firmware to install. However, when that the package does nothing by default
is indeed not very nice; it might be good to ensure that at least one of
the firmwares is installed, with something like (elided for brevity):
config BR2_PACKAGE_BRCMFMAC_SDIO_FIRMWARE_RPI
bool "brcmfmac-sdio-firmware-rpi"
select BR2_PACKAGE_BRCMFMAC_SDIO_FIRMWARE_RPI_WIFI \
if !BR2_PACKAGE_BRCMFMAC_SDIO_FIRMWARE_RPI_BT
Care to send a proper patch to the list, please?
--
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 prev parent reply other threads:[~2022-03-23 8:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 12:35 [Buildroot] [Bug 14676] New: BRCMFMAC SDIO firmware doesn't copy to target bugzilla
2022-03-22 18:55 ` [Buildroot] [Bug 14676] " bugzilla
2022-03-22 22:34 ` bugzilla
2022-03-23 8:13 ` bugzilla [this message]
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-b1v4WnuqKI@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