Hi, On 06/12/2014 11:16 PM, [email protected] wrote: > On Thu, Jun 12, 2014 at 4:26 PM, Hans de Goede <[email protected]> wrote: >> Hi, >> >> On 06/12/2014 03:21 PM, [email protected] wrote: >>> I added the ap6210.txt file. Now I get... >>> >>> root@linaro-developer:~# dmesg | grep brcm >>> [ 14.656712] brcmfmac: F1 signature read @0x18000000=0x1591a962 >>> [ 15.123388] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = >>> wl0: Apr 22 2013 14:50:00 version 5.90.195.89.6 FWID 01-b30a427d >>> [ 15.208407] brcmfmac: brcmf_fil_cmd_data: Failed err=-23 >>> [ 15.259285] brcmfmac: brcmf_fil_cmd_data: Failed err=-23 >>> [ 15.290611] brcmfmac: brcmf_fil_cmd_data: Failed err=-23 >>> [ 15.330720] brcmfmac: brcmf_fil_cmd_data: Failed err=-23 >>> [ 15.345610] brcmfmac: brcmf_fil_cmd_data: Failed err=-23 >>> [ 15.396557] brcmfmac: brcmf_fil_cmd_data: Failed err=-23 >>> [ 15.440398] usbcore: registered new interface driver brcmfmac >> >> Those are "normal" this is the brcmfmac driver trying to enable some >> features which are not supported on this model wifi chip. > > How is nvram_ap6210.txt, which I renamed to brcmfmac43362-sdio.txt, > going to get distributed? Was that the right file?
Yes it is the right file. As for how this is going to get distributed, the nvram files are board specific, so I plan to write a patch to allow specifying a nvram-filename property in devicetree in the sdio-function devicetree node (which also holds the oob irq info), brcmfmac will then use brcmfmac43362-sdio-%s.txt as nvram txt filename when this property is present. With this patch in place, distributions can simply distribute all nvram files for boards which they support. As for how the distributions are going to get these nvram files, I think adding them to linux-firmware is the best approach. If you've any comments are a better idea to deal with this I'm all ears. 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.
