Hi Arend, On Thu, Jul 28, 2016 at 3:37 PM, Arend van Spriel <arend.vanspriel@xxxxxxxxxxxx> wrote: > Hi Fabio, > > So this is another fine example of firmware API not able to deliver. I > think in all these kernels you have the same issue. The problem is that > the order of events upon kernel boot is not predictable. In this case > you have rootfs being mounted and brcmfmac getting probed as the two > competing events. When rootfs is mounted before brcmfmac is being probed > it works, but if brcmfmac is probed before rootfs is mounted the > firmware request will fail. So the only reliable option for built-in > drivers requiring firmware is to built-in the firmware into the kernel > as well. Thanks for your explanation. Tried building brcmfmac as module and after doing 'modprobe brcmfmac' the firmware is correctly loaded from the rootfs in all the kernels I tested. Now I just need it to load brcmfmac module automatically, but this is a a separate issue I will investigate. Thanks a lot for your help! Fabio Estevam -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
