From: Stanimir Varbanov <stanimir.varbanov@linaro.org>
To: asitshah@codeaurora.org, linux-firmware@kernel.org,
linux-arm-kernel@lists.infradead.org, mchehab@infradead.org,
linux-media@vger.kernel.org, stanimir.varbanov@linaro.org,
linux-media-owner@vger.kernel.org
Cc: dikshita@codeaurora.org, sampnimm@codeaurora.org,
vgarodia@codeaurora.org
Subject: Re: Update venus firmware files for v5.4 and v5.2
Date: Wed, 25 Nov 2020 18:02:44 +0200 [thread overview]
Message-ID: <c7da805a-65a8-6011-e710-b7ffa29492a3@linaro.org> (raw)
Message-ID: <20201125160244.ug9U7rpcSaCbww7Xr3tBWAoNoWZFdR9-Lg4J4adKHmk@z> (raw)
In-Reply-To: <78c092f9b8d8b3833d7ac4f36253f7d3@codeaurora.org>
Hi Asit,
with 5.2/venus updated firmware I see following errors while loading
venus driver:
Nov 25 15:57:50 linaro-developer kernel: [418683.609209] qcom-venus
aa00000.video-codec: invalid firmware metadata
Nov 25 15:57:50 linaro-developer kernel: [418683.616354] qcom-venus
aa00000.video-codec: fail to load video firmware
Nov 25 15:57:50 linaro-developer kernel: [418683.631439] qcom-venus:
probe of aa00000.video-codec failed with error -22
Please don't merge it in linux-firmware until we are not sure what is
going on here!
On 11/25/20 10:41 AM, asitshah@codeaurora.org wrote:
> Hi Team,
>
> Please include updated Venus Firmware bins for v5.4 and v5.2 .
>
> Snapshot of pull request is as below, let me know if anything is missing.
>
>>>>>>>
>
> The following changes since commit
> b362fd4cb8963ad75517dbcf424974f65a29a60e:
>
> Mellanox: Add new mlxsw_spectrum firmware xx.2008.2018 (2020-11-24
> 09:55:03 -0500)
>
> are available in the git repository at:
>
> https://github.com/shahasit/linux-firmware-video/tree/master
>
> for you to fetch changes up to e6459dce893a5b8dbf684762d5396acc11149186:
>
> qcom : updated venus firmware files for v5.2 (2020-11-25 14:02:10 +0530)
>
> ----------------------------------------------------------------
> Asit Shah (2):
> qcom : updated venus firmware files for v5.4
> qcom : updated venus firmware files for v5.2
>
> qcom/venus-5.2/venus.b00 | Bin 212 -> 212 bytes
> qcom/venus-5.2/venus.b01 | Bin 6600 -> 6808 bytes
> qcom/venus-5.2/venus.b02 | Bin 837304 -> 856432 bytes
> qcom/venus-5.2/venus.b03 | Bin 33640 -> 33648 bytes
> qcom/venus-5.2/venus.mbn | Bin 883264 -> 902400 bytes
> qcom/venus-5.2/venus.mdt | Bin 6812 -> 7020 bytes
> qcom/venus-5.4/venus.b00 | Bin 212 -> 212 bytes
> qcom/venus-5.4/venus.b01 | Bin 6808 -> 6808 bytes
> qcom/venus-5.4/venus.b02 | Bin 873680 -> 873704 bytes
> qcom/venus-5.4/venus.b03 | Bin 33792 -> 33792 bytes
> qcom/venus-5.4/venus.mbn | Bin 919792 -> 919816 bytes
> qcom/venus-5.4/venus.mdt | Bin 7020 -> 7020 bytes
> 12 files changed, 0 insertions(+), 0 deletions(-)
>
> <<<<<<
>
> Regards,
> Asit
--
regards,
Stan
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-25 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 8:41 Update venus firmware files for v5.4 and v5.2 asitshah
2020-11-25 8:41 ` asitshah
2020-11-25 16:02 ` Stanimir Varbanov [this message]
2020-11-25 16:02 ` Stanimir Varbanov
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=c7da805a-65a8-6011-e710-b7ffa29492a3@linaro.org \
--to=stanimir.varbanov@linaro.org \
--cc=asitshah@codeaurora.org \
--cc=dikshita@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-firmware@kernel.org \
--cc=linux-media-owner@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=sampnimm@codeaurora.org \
--cc=vgarodia@codeaurora.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;
as well as URLs for NNTP newsgroup(s).