From: smagar@codeaurora.org
To: linux-firmware@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org, mchehab@infradead.org,
stanimir.varbanov@linaro.org, linux-media-owner@vger.kernel.org
Cc: vgarodia@codeaurora.org, dikshita@codeaurora.org,
pbadge@codeaurora.org, adhudase@codeaurora.org,
sampnimm@codeaurora.org, c_mansur@codeaurora.org
Subject: Request to update venus-5.4 FW files
Date: Wed, 21 Apr 2021 11:28:19 +0530 [thread overview]
Message-ID: <f90802a86e80b6d9cc96ea8dd6aef4d8@codeaurora.org> (raw)
Hello Team,
Please include updated firmware bins for venus-5.4.
Snapshot of pull request is as below, let me know if anything is
missing.
The following changes since commit
85286184d9df1b03bb76049edcfd87c39ce46e94:
Merge branch 'for-upstream' of
git://git.chelsio.net/pub/git/linux-firmware into main (2021-04-19
11:34:11 -0400)
are available in the git repository at:
https://github.com/suraj714/linux-firmware-venus.git master
for you to fetch changes up to 5c893c65b862906a627cea238ae8c2d099027dee:
Updated Venus firmware files for v5.10 (2021-04-20 11:48:28 +0530)
----------------------------------------------------------------
smagar (1):
Updated Venus firmware files for v5.10
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 -> 873596 bytes
qcom/venus-5.4/venus.b03 | Bin 33792 -> 33792 bytes
qcom/venus-5.4/venus.mbn | Bin 919792 -> 919708 bytes
qcom/venus-5.4/venus.mdt | Bin 7020 -> 7020 bytes
6 files changed, 0 insertions(+), 0 deletions(-)
Regards,
Suraj Magar
reply other threads:[~2021-04-21 5:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f90802a86e80b6d9cc96ea8dd6aef4d8@codeaurora.org \
--to=smagar@codeaurora.org \
--cc=adhudase@codeaurora.org \
--cc=c_mansur@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=pbadge@codeaurora.org \
--cc=sampnimm@codeaurora.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).