From: Kalle Valo <kvalo@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
Vinod Koul <vkoul@kernel.org>
Subject: Re: wcn3990 firmware
Date: Wed, 02 Aug 2023 13:28:13 +0300 [thread overview]
Message-ID: <87cz05wxfm.fsf@kernel.org> (raw)
In-Reply-To: <8990bf1c-32c8-e582-7aa1-d207eba7d7d6@linaro.org> (Dmitry Baryshkov's message of "Mon, 24 Jul 2023 23:02:10 +0300")
Dmitry Baryshkov <dmitry.baryshkov@linaro.org> writes:
> On 24/07/2023 22:38, Dmitry Baryshkov wrote:
>> Hello Kalle, colle
>> Yet-another firmware question (I remember the standard answer of not
>> using firmware not coming from your side). I see that for
>> wcn3990/hw1.0 we have wlanmdsp.mbn with the version
>> WLAN.HL.2.0-01387-QCAHLSWMTPLZ-1
>> We have got the newer wlanmdsp.mbn released under
>> redistribution-permissive license (LICENSE.qcom from
>> linux-firmware). The file has the version
>> WLAN.HL.3.3.7.c2-00723-QCAHLSWMTPLZ-1. It was released for the
>> ath10k embedded into Qualcomm QRB2210 / QRB4210 SoCs.
>
> Update: with the current wlanmdsp.mbn I'm getting the following error
> from the DSP:
>
> [ 22.468121] qcom_q6v5_pas 6080000.remoteproc: fatal error received:
> EX:kernel:0x0:SigVerify:0x173:PC=0xc10dd460
>
> The board is not fused, but the signature format was changed (and so
> were some of the fields).
>
> It seems we will have to provide the updated file somehow to
> linux-firmware. What would be the preferred way for us to do so?
I cannot take firmware files from a 3rd party. Also I don't follow the
WCN3990 firmware development so I can't really comment how that firmware
release works with different WCN3990 hardware, board files and/or
calibration data. But if you think that release should be submitted to
linux-firmware that's up to you.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2023-08-02 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 19:38 wcn3990 firmware Dmitry Baryshkov
2023-07-24 20:02 ` Dmitry Baryshkov
2023-08-02 10:28 ` Kalle Valo [this message]
2023-08-02 11:23 ` Dmitry Baryshkov
2023-08-02 16:45 ` Kalle Valo
2023-08-24 11:42 ` Dmitry Baryshkov
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=87cz05wxfm.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=vkoul@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