On 11/24/2022 12:04 PM, Andy Green wrote:
>
>
> On 11/24/22 10:49, Arend van Spriel wrote:
>> On 11/24/2022 11:20 AM, Andy Green wrote:
>
>>>> Thanks for the log. Together with the dhd driver sources I could
>>>> make some sense of it. Perhaps you can try the following hack and
>>>> see if we make it over the first hurdle.
>>>
>>> Thanks, I tried it, but although it looks necessary, there's
>>> evidently something else since the result was the same.
>>>
>>>> +
>>>> + entropy_info.signture = cpu_to_le32(BRCMF_SEED_SIGNATURE);
>>>
>>> This should be ... .signature = ...
>>
>> That's what you get if you get too confident... :-(
>
> Just mention it in case anyone following along at home with the patches.
>
>>> I added a log showing it sending the entropy bytes.
>>
>> Ok. Something is off there. Maybe I tried to be to smart. How does
>> that log statement look which you added?
>
> It's inline with the other logs, it seems to be coming before the actual
> NVRAM download part
>
> >> [ 3.694272] brcmfmac: Download NVRAM brcm/fw_bcm43752a2_pcie.txt
> >> [ 3.694895] brcmfmac: brcmf_pcie_write_entropy_bytes: written 6040
> >> entropy bytes
Sorry. I meant how the source code look like. There should be 128 bytes
written. 6040 is length of nvram so I am a bit confused.
Regards,
Arend