From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15546] New: raspberry pi zero 2 w no Wi-Fi device
Date: Mon, 17 Apr 2023 15:52:41 +0000 [thread overview]
Message-ID: <bug-15546-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15546
Bug ID: 15546
Summary: raspberry pi zero 2 w no Wi-Fi device
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: glscene2010@gmail.com
CC: buildroot@uclibc.org
Target Milestone: ---
I use raspberry pi zero 2 w. I use master branch Buildroot.
Full steps here https://forums.raspberrypi.com/viewtopic.php?p=2100121#p2100121
Summary my steps:
I add this tree lines in raspberrypizero2w_defconfig
BR2_PACKAGE_BRCMFMAC_SDIO_FIRMWARE_RPI=y
BR2_PACKAGE_BRCMFMAC_SDIO_FIRMWARE_RPI_BT=y
BR2_PACKAGE_BRCMFMAC_SDIO_FIRMWARE_RPI_WIFI=y
And build:
make clean -C buildroot
make -C buildroot raspberrypizero2w_defconfig
make -C buildroot
But there is no Wi-Fi device.
I know how manually enable Wi-Fi in Buildroot for raspberry pi zero 2 w, do:
modprobe brcmfmac
/etc/init.d/S40Network restart
Why Buildroot don't do it by himself?
--
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:[~2023-04-17 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 15:52 bugzilla [this message]
2023-07-31 18:44 ` [Buildroot] [Bug 15546] raspberry pi zero 2 w no Wi-Fi device bugzilla
2023-08-02 21:19 ` bugzilla
2023-09-11 18:25 ` bugzilla
2023-09-13 12:47 ` bugzilla
2023-10-16 9:53 ` bugzilla
2024-06-15 15:08 ` 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-15546-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