Hi, On Fri, Jan 24, 2014 at 6:56 AM, Hans de Goede <[email protected]> wrote: > Hi, > > > On 01/23/2014 11:39 PM, Hans de Goede wrote: >> >> Hi, >> >> I've been working on updating sunxi-devel to include more >> recent versions if your gmac patches, as well as adding support >> for the wifi + bluetooth found on the cubietruck. >> >> Here is my current work on this: >> >> https://github.com/jwrdegoede/linux-sunxi/commits/sunxi-devel >> >> It is close to working, but unfortunately it does not work, >> here is what I get in dmesg when I modprove the module: >> >> [ 99.700889] brcmfmac_sdio mmc1:0001:1: device tree node not found >> [ 100.020984] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: >> Apr 22 2013 14:50:00 version 5.90.195.89.6 FWID 01-b30a427d >> [ 100.260948] brcmfmac: brcmf_fil_cmd_data: Failed err=-23 >> [ 100.281260] brcmfmac: brcmf_fil_cmd_data: Failed err=-23 >> [ 100.322508] usbcore: registered new interface driver brcmfmac >> [ 160.445215] brcmfmac: brcmf_cfg80211_sched_scan_start: Scanning >> already: status (1) >> [ 203.445404] brcmfmac: brcmf_cfg80211_sched_scan_start: Scanning >> already: status (1) >> [ 256.445140] brcmfmac: brcmf_cfg80211_sched_scan_start: Scanning >> already: status (1) >> ... >> >> This is using the firmware + nvram found here: >> http://dl.cubieboard.org/public/Cubieboard/benn/firmware/ap6210/ >> >> Wens' can you give my tree a try? And which version of the firmware + >> nvram are you using ?
Tested your tree. Works nicely. Perhaps you could check the hardware signature? From what Arend said, there's at least 2 revisions of the chip. Also you mentioned modprobe. I've only used it built-in. My relevant kernel messages: mmc1: queuing unknown CIS tuple 0x80 (2 bytes) mmc1: queuing unknown CIS tuple 0x80 (3 bytes) mmc1: queuing unknown CIS tuple 0x80 (3 bytes) mmc1: queuing unknown CIS tuple 0x80 (7 bytes) mmc1: new high speed SDIO card at address 0001 brcmfmac_sdio mmc1:0001:1: device tree node not found brcmfmac: F1 signature read @0x18000000=0x1591a962 brcmfmac_sdio mmc1:0001:2: Direct firmware load failed with error -2 brcmfmac_sdio mmc1:0001:2: Falling back to user helper brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Apr 22 2013 14:50:00 version 5.90.195.89.6 FWID 01-b30a427d brcmfmac: brcmf_fil_cmd_data: Failed err=-23 brcmfmac: brcmf_fil_cmd_data: Failed err=-23 brcmfmac: brcmf_fil_cmd_data: Failed err=-14 brcmfmac: brcmf_fil_cmd_data: Failed err=-14 > Quick update, I've just tested: > https://github.com/wens/linux/commits/wip/sunxi-next-wifi About this, I would like to move WiFi power control to a regulator, and controlled by sunxi-mci via vmmc-supply (not supported ATM). And I will do a new rfkill patch series. This is mostly cleanup. > And the result is the same. So wrong firmware / nvram ? > > I've used: > http://dl.cubieboard.org/public/Cubieboard/benn/firmware/ap6210/fw_bcm40181a2.bin > http://dl.cubieboard.org/public/Cubieboard/benn/firmware/ap6210/nvram_ap6210.txt I use these as well. > > Regards, > > Hans > > p.s. > > About the oob interrupt stuff not working, AFAIK you should set a pinctrl > function (not input, but a function like mmc is a function) on the pin in > question > for it to work as external interrupt, I believe you're not doing so in your > dts. The pinctrl driver seems to set the function when the interrupt is enabled. Unfortunately we don't have any documentation/examples on how to use them. I will look into that later. Thanks ChenYu P.S. Off topic but, is the USB PHY driver final? I believe there's an issue in the probe error checking code: https://github.com/wens/linux/commit/349b8903e8909455d6f91fbad046fddc2d9326a5 -- 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/groups/opt_out.
