All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: "Íñigo Huguet" <ihuguet@redhat.com>
Cc: Sven Eckelmann <sven@narfation.org>,  ath11k@lists.infradead.org
Subject: Re: failed to fetch board data
Date: Fri, 04 Feb 2022 16:37:24 +0200	[thread overview]
Message-ID: <87wniabsuz.fsf@kernel.org> (raw)
In-Reply-To: <CACT4oue1KcYkxnNUM4fJ8w-TR6Tiu5OekWYctaDRoo7md37dtA@mail.gmail.com> ("Íñigo Huguet"'s message of "Fri, 4 Feb 2022 15:04:58 +0100")

Íñ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

      reply	other threads:[~2022-02-04 14:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wniabsuz.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=ihuguet@redhat.com \
    --cc=sven@narfation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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.