PCI trouble on mvebu (Turris Omnia)

[Toke Høiland-Jørgensen]

"™֟☻̭҇ Ѽ ҉ ®" <vtolkm at googlemail.com> writes:

> On 27/10/2020 21:20, Toke Høiland-Jørgensen wrote:
>> Toke Høiland-Jørgensen <toke at redhat.com> writes:
>>
>>>> Note: related issues - workaround compile ath and cfg80211 as modules
>>>>
>>>> (1) https://bugzilla.kernel.org/show_bug.cgi?id=209863
>>>> (2) https://bugzilla.kernel.org/show_bug.cgi?id=209855
>>>> (3) https://bugzilla.kernel.org/show_bug.cgi?id=209853
>>> Yeah, I had noticed the regdb failure but put off debugging that until
>>> the PCI issue was resolved. So guess that's next on my list - thanks for
>>> the pointer (although I'd rather avoid the module approach as booting
>>> the kernel directly from my build box over tftp is quite convenient...
>>> Let's see if there isn't another way to fix this)
>> To follow up on this, everything seems to work just fine (ath10k init at
>> boot + regulatory db load) if I simply set:
>>
>> CONFIG_EXTRA_FIRMWARE="ath10k/QCA988X/hw2.0/board.bin ath10k/QCA988X/hw2.0/firmware-5.bin regulatory.db regulatory.db.p7s"
>>
>> -Toke
>>
>
> That works on my node only for the regulatory files but not the ath10 
> firmware with kconfig:
>
>   Symbol: EXTRA_FIRMWARE_DIR [=/srv/fw]
>   Type  : string
>   Defined at drivers/base/firmware_loader/Kconfig:63
>     Prompt: Firmware blobs root directory
>     Depends on: FW_LOADER [=y] && EXTRA_FIRMWARE [=regulatory.db 
> regulatory.db.p7s board.bin firmware-5.bin]!=
>     Location:
>      -> Device Drivers
>        -> Generic Driver Options
>          -> Firmware loader
>            -> Firmware loading facility (FW_LOADER [=y])
>              -> Build named firmware blobs into the kernel binary 
> (EXTRA_FIRMWARE [=regulatory.db regulatory.db.p7s board.bin 
> firmware-5.bin])

I think that's because you're missing the path prefix
(ath10k/QCA988X/hw2.0/) from board.bin and firmware-5.bin?
request_firmware() uses the full path...

-Toke