I also found that if the wifi is needed for access over SSH, OpenSSH should be paired with haveged for faster random generator initialization. Line ctrl_interface=/var/run/wpa_supplicant at wpa_nf doesn't seem to be valid nor necessary anymore (if it ever even was).rpi-wifi-firmware is renamed to brcmfmac-sdio-firmware-rpi-wifi which can be found under brcmfmac_sdio-firmware-rpi at Hardware Handling.Using the latest buildroot from git:///buildroot it seems that there are some changes: but if not, edit /etc/inittab and modprobe brcmfmac yourself just before the rc scripts are ran.
Actually I recommend this if you're going to connect UBS devices to your RPi. You could Enable WCHAR support (at Toolchain -menu) in order to have eudev as /dev management (at System configuration -menu) which would automatically handle the driver loading.
Pre-up wpa_supplicant -D nl80211 -i wlan0 -c /etc/wpa_nf -BĪnd at /etc/wpa_nf ctrl_interface=/var/run/wpa_supplicantĪnd now we're still missing the secret ingredient: the wifi driver must be loaded before the networking init-scripts kick in. Then at /etc/network/interfaces auto wlan0 Networking applications -> wpa_supplicant - Enable 80211 supportĮverything else that's necessary should already be pre-selected. Networking applications -> wpa_supplicant Then ( make menuconfig and) select following from Target packages: Hardware Handling -> Firmware -> rpi-wifi-firmware Using buildroot 2018.02.2 make raspberrypi0_defconfig Eventhough the original answer was somewhat helpful, it's definitely not the best one so I though it would be worth sharing my own findings: I also tried to find the "bare minimum wireless" for RPi Zero W using buildroot so this Q&A came quite high on the search results.
0 kommentar(er)
