From: asitshah@codeaurora.org
To: 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: vgarodia@codeaurora.org, dikshita@codeaurora.org
Subject: Update venus firmware files for v5.4
Date: Fri, 06 Nov 2020 10:40:27 +0530 [thread overview]
Message-ID: <c1bcb5eedc160e99d65576d431816a41@codeaurora.org> (raw)
Message-ID: <20201106051027.xSLGSL03fZAC7EzGNcXuvnfeyZj7WpK1T6z4L9FWTdo@z> (raw)
Hi Team,
Please include updated Venus Firmware bins for v5.4.
Snapshot of pull request is as below, let me know if anything is
missing.
>>>>>>
The following changes since commit
dae4b4cd084102cd49c37aa8b579b208028ab025:
Merge branch 'v1.1.5' of
https://github.com/irui-wang/linux_fw_vpu_v1.1.5 into main (2020-10-23
08:10:37 -0400)
are available in the git repository at:
https://github.com/shahasit/video-linux-firmware/tree/master
for you to fetch changes up to 8a46c32a26b3f22835543b158877aa0b0e01e8d6:
qcom : updated venus firmware files for v5.4 (2020-11-06 10:33:37
+0530)
----------------------------------------------------------------
Asit Shah (1):
qcom : updated venus firmware files for v5.4
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 873100 -> 873680 bytes
qcom/venus-5.4/venus.b03 | Bin 33792 -> 33792 bytes
qcom/venus-5.4/venus.mbn | Bin 919212 -> 919792 bytes
qcom/venus-5.4/venus.mdt | Bin 7020 -> 7020 bytes
6 files changed, 0 insertions(+), 0 deletions(-)
<<<<<<
Regards,
Asit
next reply other threads:[~2020-11-06 5:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 5:10 asitshah [this message]
2020-11-06 5:10 ` Update venus firmware files for v5.4 asitshah
2020-11-06 5:10 ` asitshah
2020-11-13 15:19 ` Josh Boyer
2020-11-13 15:19 ` Josh Boyer
2020-11-13 15:19 ` Josh Boyer
-- strict thread matches above, loose matches on Subject: below --
2020-10-08 9:50 asitshah
2020-10-08 9:50 ` asitshah
2020-10-08 9:50 ` asitshah
2020-10-20 5:47 ` asitshah
2020-10-20 5:47 ` asitshah
2020-10-20 5:47 ` asitshah
2020-10-23 12:05 ` Josh Boyer
2020-10-23 12:05 ` Josh Boyer
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=c1bcb5eedc160e99d65576d431816a41@codeaurora.org \
--to=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=stanimir.varbanov@linaro.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).