Hi, On 07/06/2014 03:02 PM, [email protected] wrote: > On Sun, Jul 6, 2014 at 8:15 AM, Hans de Goede <[email protected]> wrote: >> Hi, >> >> On 07/04/2014 06:50 PM, [email protected] wrote: >>> So is AP6210 support in mainline 3.16-rc1? I don't have a wireless >>> device when I boot it but I do get some log messages at boot.... >>> >>> Can the AP6210 be probed? I don't see anything in the Cubietruck DTS >>> loading the driver. >>> >>> This is on Emilio's DMA tree. >>> http://git.elopez.com.ar/linux/commits/branch/sunxi-dma >>> >>> [ 1.809112] mmc1: new high speed SDIO card at address 0001 >>> [ 1.815717] brcmfmac: F1 signature read @0x18000000=0x1591a962 >>> [ 2.835866] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): >>> clkctl 0x50 >>> [ 3.856501] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): >>> clkctl 0x50 >> >> This happens when your using a wrong nvram file / wrong >> >> brcmfmac43362-sdio.txt >> >> Where did you get yours from? > > It is from cubieboard.org. Where is the correct one?
That is the correct one, looking at: >>> [ 1.809112] mmc1: new high speed SDIO card at address 0001 >>> [ 1.815717] brcmfmac: F1 signature read @0x18000000=0x1591a962 It seems you've the module build in, I'm amazed it can find the firmware in time then, seems like the race between getting the rootfs mounted, and trying to load the firmware ends up favorable in your case. In general having the brcmfmac build in is no a good idea, because /lib/firmware needs to be available before it loads, and there is no way to guarantee this when its build in. Can you try making brcmfmac a module ? Regards, Hans -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
