On 08/19/2015 08:20 AM, Hans de Goede wrote:
Hi,
On 19-08-15 14:07, Robert Moskowitz wrote:
> Hans, I found your earlier message on this, but it does not give ME
> clear instructions on getting the pieces together:
>
> On 08/06/2015 02:19 PM, Hans de Goede wrote:
>> Hi,
>>
>> On 06-08-15 20:08, Clive Messer wrote:
>>> On Thu, 2015-08-06 at 18:04 +0100, Peter Robinson wrote:
>>>
>>>> On Fedora you should just be able to install the appropriate firmware
>>>> for the ap6210 driver and have it work, I don't believe Fedora
>>>> currently has the ability to redistribute it currently otherwise it
>>>> would be in the linux-firmware package which its not.
>>>
>>> Even with the right firmware available, I'm not sure things have
>>> progressed from earlier in the year, where the issues with the
>>> brcmfmac
>>> driver "stopping" on BPi/Cubietruck, with AP6210 hardware, needed
>>> resolution.
>>>
>>> ISTR, some discussion on the sunxi mailing list about this again
>>> recently where they were talking about error recovery on the sdio/mmc
>>> side of things.... Not sure any of this made it upstream to the kernel
>>> yet.
>>>
>>> Hans would probably be able to say what should be working now. ;)
>>
>> When dropping the right nvram file into place, and adding this:
>>
>>
https://github.com/jwrdegoede/linux-sunxi/commit/08c7babbb4bd0f9521a67137...
>>
>>
>> patch to the kernel the cubietruck wifi should work reliable.
>>
>> Although this patch fixes things, and is safe, we may end
>> up with a slightly different fix upstream, that is currently
>> being discussed.
>
> Where is the nvram file described and how to put it in place.
http://dl.cubieboard.org/public/Cubieboard/benn/firmware/ap6210/nvram_ap6...
I cannot resolve that fqdn. I have had this problem in the past with
dl.cubieboard.org; for some reason it is just not available over here.
And save it as /lib/firmware/brcm/brcmfmac43362-sdio.txt
Does that URL tell how to do this?
>
> Is this patch still needed for F23? What specific kernel version is
> included? Or do I still have to patch?
Still needed, you still need to manually patch your kernel.
>>> NB. I had both a Cubietruck and BananaPro running F22. Both of those I
>>> ended up disabling the onboard Broadcom wifi and stuck a dongle in a
>>> USB port due to the issues with the brcmfmac driver. Unless Hans can
>>> say that the issues are now resolved, I think this is very much a case
>>> of "suck it and see". ;)
>>
>> The issues are now resolved, the cubietruck nvram file should also
>> work fine on the bananapro. Hint if you use multiple boards with the
>> brcm wifi, edid the MAC in the nvram file, or all systems end up
>> with the same MAC, fixing the MAC issue and a solution for distributing
>> the nvram file as part of linux-firmware are in my sunxi projects list:
>>
>>
https://revspace.nl/KernelDriverProjects
>
> yuck. And you finally got a stable, unique MAC address working for
> the Cubietruck (well, last year, but still).
>
> How do I do this? Where is the instructions.
There are no instructions, these bits are not yet end user ready.
Once they are things should just work without needing to follow
any instructions.
Well for now, there is only the one Cubietruck here in testing on this
subnet. So I can deal with it.
thanks