* failed to fetch board data
@ 2022-02-03 14:56 Íñigo Huguet
2022-02-03 18:34 ` Sven Eckelmann
0 siblings, 1 reply; 4+ messages in thread
From: Íñigo Huguet @ 2022-02-03 14:56 UTC (permalink / raw)
To: ath11k
Hi, I'm getting the following error with v5.17-rc2 kernel and a WCN6855 card:
chip_id 0x2 chip_family 0xb board_id 0xff soc_id 0x400c0200
failed to fetch board data for
bus=pci,vendor=17cb,device=1103,subsystem-vendor=105b,subsystem-device=e0b8,qmi-chip-id=2,qmi-board-id=255
from ath11k/WCN6855/hw2.0/board-2.bin
However, I have another card working fine with this data:
lspci:
Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01)
Subsystem: Foxconn International, Inc. Device [105b:e0ce]
dmesg:
chip_id 0x2 chip_family 0xb board_id 0xff soc_id 0x400c0210
Apparently, only subsystem ID is different.
I'm using this firmware for both, most recent commit:
https://github.com/kvalo/ath11k-firmware
Is the first card still unsupported or is this an error?
Since it seems that there might be many variants that need to be known
in the board-2.bin file, is it possible to know which ones are
supported and which ones are not?
Thanks
--
Íñigo Huguet
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: failed to fetch board data
2022-02-03 14:56 failed to fetch board data Íñigo Huguet
@ 2022-02-03 18:34 ` Sven Eckelmann
2022-02-04 14:04 ` Íñigo Huguet
0 siblings, 1 reply; 4+ messages in thread
From: Sven Eckelmann @ 2022-02-03 18:34 UTC (permalink / raw)
To: ath11k; +Cc: Íñigo Huguet
[-- Attachment #1.1: Type: text/plain, Size: 3386 bytes --]
On Thursday, 3 February 2022 15:56:29 CET Íñigo Huguet wrote:
> Since it seems that there might be many variants that need to be known
> in the board-2.bin file, is it possible to know which ones are
> supported and which ones are not?
git clone https://github.com/kvalo/ath11k-firmware
git clone https://github.com/qca/qca-swiss-army-knife
./qca-swiss-army-knife/tools/scripts/ath11k/ath11k-bdencoder -i ath11k-firmware/WCN6855/hw2.0/board-2.bin|grep BoardName
Which returns following list:
BoardNames[0]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=3374,qmi-chip-id=2,qmi-board-id=262'
BoardNames[1]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=3374,qmi-chip-id=2,qmi-board-id=266'
BoardNames[2]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=3374,qmi-chip-id=18,qmi-board-id=266'
BoardNames[3]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=14cd,subsystem-device=9409,qmi-chip-id=18,qmi-board-id=255'
BoardNames[4]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=14cd,subsystem-device=9409,qmi-chip-id=2,qmi-board-id=255'
BoardNames[5]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108,qmi-chip-id=18,qmi-board-id=255'
BoardNames[6]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108,qmi-chip-id=2,qmi-board-id=255'
BoardNames[7]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=105b,subsystem-device=e0ce,qmi-chip-id=2,qmi-board-id=255'
BoardNames[8]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=105b,subsystem-device=e0ce,qmi-chip-id=18,qmi-board-id=255'
BoardNames[9]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=14cd,subsystem-device=9308,qmi-chip-id=2,qmi-board-id=255'
BoardNames[10]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17aa,subsystem-device=9308,qmi-chip-id=2,qmi-board-id=255'
BoardNames[11]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17aa,subsystem-device=9309,qmi-chip-id=2,qmi-board-id=255'
BoardNames[12]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17aa,subsystem-device=9309,qmi-chip-id=18,qmi-board-id=255'
BoardNames[13]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17aa,subsystem-device=e0be,qmi-chip-id=2,qmi-board-id=255'
BoardNames[14]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=105b,subsystem-device=e0bb,qmi-chip-id=2,qmi-board-id=255'
BoardNames[15]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=105b,subsystem-device=e0c4,qmi-chip-id=2,qmi-board-id=255'
BoardNames[16]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=105b,subsystem-device=e0c4,qmi-chip-id=18,qmi-board-id=255'
BoardNames[17]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=3374,qmi-chip-id=2,qmi-board-id=771'
BoardNames[18]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=3374,qmi-chip-id=18,qmi-board-id=771'
Keep in mind, that there can also be multiple supported values per line (aka
"per BDF"/board.bin). This doesn't seem to be the case because there is no
extra entry (see placeholder "foobar") like in following example :
BoardNames[XXXX]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=14cd,subsystem-device=9409,qmi-chip-id=18,qmi-board-id=255','foobar'
Kind regards,
Sven
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 102 bytes --]
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: failed to fetch board data
2022-02-03 18:34 ` Sven Eckelmann
@ 2022-02-04 14:04 ` Íñigo Huguet
2022-02-04 14:37 ` Kalle Valo
0 siblings, 1 reply; 4+ messages in thread
From: Íñigo Huguet @ 2022-02-04 14:04 UTC (permalink / raw)
To: Sven Eckelmann; +Cc: ath11k
Hi,
On Thu, Feb 3, 2022 at 7:42 PM Sven Eckelmann <sven@narfation.org> wrote:
>
> On Thursday, 3 February 2022 15:56:29 CET Íñigo Huguet wrote:
> > Since it seems that there might be many variants that need to be known
> > in the board-2.bin file, is it possible to know which ones are
> > supported and which ones are not?
>
> git clone https://github.com/kvalo/ath11k-firmware
> git clone https://github.com/qca/qca-swiss-army-knife
>
> ./qca-swiss-army-knife/tools/scripts/ath11k/ath11k-bdencoder -i ath11k-firmware/WCN6855/hw2.0/board-2.bin|grep BoardName
>
> Which returns following list:
>
> BoardNames[0]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=3374,qmi-chip-id=2,qmi-board-id=262'
> BoardNames[1]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=3374,qmi-chip-id=2,qmi-board-id=266'
> BoardNames[2]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=3374,qmi-chip-id=18,qmi-board-id=266'
> BoardNames[3]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=14cd,subsystem-device=9409,qmi-chip-id=18,qmi-board-id=255'
> BoardNames[4]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=14cd,subsystem-device=9409,qmi-chip-id=2,qmi-board-id=255'
> BoardNames[5]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108,qmi-chip-id=18,qmi-board-id=255'
> BoardNames[6]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108,qmi-chip-id=2,qmi-board-id=255'
> BoardNames[7]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=105b,subsystem-device=e0ce,qmi-chip-id=2,qmi-board-id=255'
> BoardNames[8]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=105b,subsystem-device=e0ce,qmi-chip-id=18,qmi-board-id=255'
> BoardNames[9]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=14cd,subsystem-device=9308,qmi-chip-id=2,qmi-board-id=255'
> BoardNames[10]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17aa,subsystem-device=9308,qmi-chip-id=2,qmi-board-id=255'
> BoardNames[11]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17aa,subsystem-device=9309,qmi-chip-id=2,qmi-board-id=255'
> BoardNames[12]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17aa,subsystem-device=9309,qmi-chip-id=18,qmi-board-id=255'
> BoardNames[13]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17aa,subsystem-device=e0be,qmi-chip-id=2,qmi-board-id=255'
> BoardNames[14]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=105b,subsystem-device=e0bb,qmi-chip-id=2,qmi-board-id=255'
> BoardNames[15]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=105b,subsystem-device=e0c4,qmi-chip-id=2,qmi-board-id=255'
> BoardNames[16]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=105b,subsystem-device=e0c4,qmi-chip-id=18,qmi-board-id=255'
> BoardNames[17]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=3374,qmi-chip-id=2,qmi-board-id=771'
> BoardNames[18]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=3374,qmi-chip-id=18,qmi-board-id=771'
>
> Keep in mind, that there can also be multiple supported values per line (aka
> "per BDF"/board.bin). This doesn't seem to be the case because there is no
> extra entry (see placeholder "foobar") like in following example :
>
>
> BoardNames[XXXX]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=14cd,subsystem-device=9409,qmi-chip-id=18,qmi-board-id=255','foobar'
>
> Kind regards,
> Sven
Thanks for this info, it's really useful.
I assume that to get the card supported I can only wait it to be added
in kvalo firmware repo, right?
--
Íñigo Huguet
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: failed to fetch board data
2022-02-04 14:04 ` Íñigo Huguet
@ 2022-02-04 14:37 ` Kalle Valo
0 siblings, 0 replies; 4+ messages in thread
From: Kalle Valo @ 2022-02-04 14:37 UTC (permalink / raw)
To: Íñigo Huguet; +Cc: Sven Eckelmann, ath11k
Íñigo Huguet <ihuguet@redhat.com> writes:
> Hi,
>
> On Thu, Feb 3, 2022 at 7:42 PM Sven Eckelmann <sven@narfation.org> wrote:
>>
>> On Thursday, 3 February 2022 15:56:29 CET Íñigo Huguet wrote:
>> > Since it seems that there might be many variants that need to be known
>> > in the board-2.bin file, is it possible to know which ones are
>> > supported and which ones are not?
>>
>> git clone https://github.com/kvalo/ath11k-firmware
>> git clone https://github.com/qca/qca-swiss-army-knife
>>
>> ./qca-swiss-army-knife/tools/scripts/ath11k/ath11k-bdencoder -i ath11k-firmware/WCN6855/hw2.0/board-2.bin|grep BoardName
>>
>> Which returns following list:
>>
>> BoardNames[0]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=3374,qmi-chip-id=2,qmi-board-id=262'
>> BoardNames[1]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=3374,qmi-chip-id=2,qmi-board-id=266'
>> BoardNames[2]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=3374,qmi-chip-id=18,qmi-board-id=266'
>> BoardNames[3]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=14cd,subsystem-device=9409,qmi-chip-id=18,qmi-board-id=255'
>> BoardNames[4]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=14cd,subsystem-device=9409,qmi-chip-id=2,qmi-board-id=255'
>> BoardNames[5]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108,qmi-chip-id=18,qmi-board-id=255'
>> BoardNames[6]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108,qmi-chip-id=2,qmi-board-id=255'
>> BoardNames[7]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=105b,subsystem-device=e0ce,qmi-chip-id=2,qmi-board-id=255'
>> BoardNames[8]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=105b,subsystem-device=e0ce,qmi-chip-id=18,qmi-board-id=255'
>> BoardNames[9]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=14cd,subsystem-device=9308,qmi-chip-id=2,qmi-board-id=255'
>> BoardNames[10]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17aa,subsystem-device=9308,qmi-chip-id=2,qmi-board-id=255'
>> BoardNames[11]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17aa,subsystem-device=9309,qmi-chip-id=2,qmi-board-id=255'
>> BoardNames[12]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17aa,subsystem-device=9309,qmi-chip-id=18,qmi-board-id=255'
>> BoardNames[13]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17aa,subsystem-device=e0be,qmi-chip-id=2,qmi-board-id=255'
>> BoardNames[14]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=105b,subsystem-device=e0bb,qmi-chip-id=2,qmi-board-id=255'
>> BoardNames[15]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=105b,subsystem-device=e0c4,qmi-chip-id=2,qmi-board-id=255'
>> BoardNames[16]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=105b,subsystem-device=e0c4,qmi-chip-id=18,qmi-board-id=255'
>> BoardNames[17]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=3374,qmi-chip-id=2,qmi-board-id=771'
>> BoardNames[18]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=3374,qmi-chip-id=18,qmi-board-id=771'
>>
>> Keep in mind, that there can also be multiple supported values per line (aka
>> "per BDF"/board.bin). This doesn't seem to be the case because there is no
>> extra entry (see placeholder "foobar") like in following example :
>>
>>
>> BoardNames[XXXX]: 'bus=pci,vendor=17cb,device=1103,subsystem-vendor=14cd,subsystem-device=9409,qmi-chip-id=18,qmi-board-id=255','foobar'
>>
>> Kind regards,
>> Sven
>
> Thanks for this info, it's really useful.
>
> I assume that to get the card supported I can only wait it to be added
> in kvalo firmware repo, right?
We need to find the correct board file for your hardware. Can you
describe more what hardware you have?
And for easier tracking I recommend filing this missing board file to
bugzilla:
https://wireless.wiki.kernel.org/en/users/drivers/ath11k/bugreport
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2022-02-04 14:37 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-03 14:56 failed to fetch board data Íñigo Huguet
2022-02-03 18:34 ` Sven Eckelmann
2022-02-04 14:04 ` Íñigo Huguet
2022-02-04 14:37 ` Kalle Valo
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.