From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14676] BRCMFMAC SDIO firmware doesn't copy to target
Date: Tue, 22 Mar 2022 18:55:11 +0000 [thread overview]
Message-ID: <bug-14676-163-5YHiJzCQS5@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14676-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14676
--- Comment #1 from Fabrice Fontaine <fontaine.fabrice@gmail.com> ---
Hi,
Thanks for your bug report, however this is not a bug but an expected behavior.
With your proposal, the user won't be able to select if we wants to install
bluetooth firmware, wifi firmware or both firmwares. Moreover, the Wifi
firmware can't always be installed as it conflicts with linux-firmware Broadcom
BRCM bcm43xx.
So, I would advise to update the batocera defconfigs (e.g.
https://github.com/batocera-linux/batocera.linux/tree/master/configs) with:
BR2_PACKAGE_BRCMFMAC_SDIO_FIRMWARE_RPI=y
BR2_PACKAGE_BRCMFMAC_SDIO_FIRMWARE_RPI_BT=y
BR2_PACKAGE_BRCMFMAC_SDIO_FIRMWARE_RPI_WIFI=y
Best Regards,
Fabrice
--
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-22 18:55 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 ` bugzilla [this message]
2022-03-22 22:34 ` [Buildroot] [Bug 14676] " 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-5YHiJzCQS5@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