From: Kalle Valo <kvalo@kernel.org>
To: "Marek Behún" <kabel@kernel.org>
Cc: ath11k@lists.infradead.org
Subject: Re: board.bin file for IPQ9574
Date: Mon, 09 Sep 2024 12:22:13 +0300 [thread overview]
Message-ID: <87ikv5gp16.fsf@kernel.org> (raw)
In-Reply-To: <t4kb7ljvau3ycvfr66kkidjqy2iim5ln2jobzrv5x6glb5cfwi@ybjrfbrogxwg> ("Marek Behún"'s message of "Sun, 8 Sep 2024 13:00:23 +0200")
Marek Behún <kabel@kernel.org> writes:
> Hi Kalle and linux-wireless,
>
> I am trying to bring up a IPQ9574 prototype board with QCN5124 chip.
>
> I am stuck with the ath11k driver requesting board.bin file, which I
> seem to be unable to find anywhere. There is such a file (board-2.bin)
> for example for the IPQ8074 SoC in linux-firmware [1].
>
> There is IPQ9574 folder in https://github.com/quic/upstream-wifi-fw
> but
We have nothing to do with that repo, the name is very misleading. You
need to contact Qualcomm about that repo.
> it does not contain no board.bin, only other files that kernel
> requested.
>
> What is happening? Why isn't this file available anywhere?
We really should write some documentation about board files but no time
right now. board.bin is part of calibration data and it's product
specific, so finding the correct one for your board is not simple.
What I recommend is to file a bug to bugzilla and explain your product
in detail (where you got it from etc):
https://wireless.wiki.kernel.org/en/users/drivers/ath11k/bugreport
That way it's easier to track this.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2024-09-09 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-08 11:00 board.bin file for IPQ9574 Marek Behún
2024-09-09 9:22 ` 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=87ikv5gp16.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=kabel@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox