bounced on mailing list as my email address changed recently. On 22-03-16 21:36, Arend van Spriel wrote: > On 19-03-16 11:54, Hauke Mehrtens wrote: >> Hi Arend, >> >> could you or someone else from Broadcom pleases add the firmware for the >> BCM43430 SDIO to linux-firmware. This module is used in the Raspberry Pi >> 3 and it would be a lot easer for distributions to have the firmware in >> linux-firmware. > > Oops. I thought it already was available. Will look into this.
The firmware can be found here [1] and there is license file. I am no lawyer but it looks like it allows redistribution of the firmware. Regards, Arend [1] https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm80211 > Regards, > Arend > >> Hauke >> >> On 03/08/2016 11:13 PM, Álvaro Fernández Rojas wrote: >>> I've got WiFi and Bluetooth working: >>> https://github.com/openwrt-es/openwrt/commits/brcm2708-rpi3-wifi >>> https://github.com/openwrt-es/openwrt/commits/brcm2708-rpi3-bt >>> >>> WiFi is working after latest brcmfmac patches backported by Rafał, with >>> some issues like the following: >>> brcmfmac: brcmf_proto_bcdc_hdrpull: wlan0: non-BCDC packet received, >>> flags 0x44 >>> >>> BT is working but only for baud rates <= 115200. I'm still investigating >>> why. >>> In order to setup the bluetooth, the following bluez patches are needed: >>> https://github.com/openwrt/packages/pull/2464 >>> >>> By the way, I won't be submitting any WiFi/BT patches until anyone from >>> either the Raspberry foundation or Broadcom clarifies the license of the >>> firmware files. >>> https://github.com/raspberrypi/linux/issues/1325 >>> >>> Regards, >>> Álvaro. >>> >>> El 04/03/2016 a las 21:06, Álvaro Fernández Rojas escribió: >>>> These patches add basic Raspberry Pi 3 support. >>>> >>>> Bootlog: >>>> https://gist.github.com/Noltari/92f51259c9d18506192b#file-bcm2710_rpi3-log >>>> >>>> >>>> Known issues: >>>> 1) No ARMv8 64 bit support. >>>> More info: >>>> https://github.com/raspberrypi/firmware/issues/550 >>>> 2) UART0 is connected to BCM43430 (Bluetooth), which means that >>>> console relies on UART1. >>>> UART1 clock depends on pll_freq, which changes depending on the core >>>> frequency. >>>> In order to get a proper console through GPIOs 14 & 15, you should >>>> force a fixed frequency instead of the default dynamic one. >>>> You can do that by either setting core_freq=250 on config.txt or >>>> force_turbo=1 (this last option will run your rpi at maximum frequency >>>> so be careful). >>>> The framebuffer console (HDMI) isn't affected so you can use that >>>> one with an external keyboard and USB HID package. >>>> More info: >>>> https://github.com/raspberrypi/firmware/issues/553 >>>> https://github.com/RPi-Distro/repo/issues/22 >>>> 3) No WiFi support. >>>> brcmfmac43430-sdio.bin / brcmfmac43430-sdio.txt firmware files >>>> aren't available on linux-firmware for now. >>>> Downloading those files from >>>> https://github.com/RPi-Distro/firmware-nonfree and trying to enable >>>> BCM43430 SDIO WiFi causes the following kernel exception: >>>> >>>> https://gist.github.com/Noltari/92f51259c9d18506192b#file-bcm2710_rpi3_brcmfmac-log >>>> >>>> 4) No Bluetooth support. >>>> >> _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel