From: vgarodia@codeaurora.org
To: Josh Boyer <jwboyer@kernel.org>
Cc: smagar@codeaurora.org,
Stanimir Varbanov <stanimir.varbanov@linaro.org>,
Linux Firmware <linux-firmware@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-media-owner@vger.kernel.org, dikshita@codeaurora.org,
adhudase@codeaurora.org, sampnimm@codeaurora.org,
mansur@codeaurora.org
Subject: Re: Update venus firmware files for v5.4 and venus firmware files for VPU-2.0
Date: Mon, 03 May 2021 22:52:58 +0530 [thread overview]
Message-ID: <87a5e5795d06cd8a87315b74b201d693@codeaurora.org> (raw)
In-Reply-To: <CA+5PVA7jSe_Hgtsw80rebBOATDGApQbss1txs__KfQh+o+e3Lg@mail.gmail.com>
Thanks Suraj.
Hi Josh,
On 2021-05-03 19:05, Josh Boyer wrote:
> On Mon, May 3, 2021 at 3:30 AM <smagar@codeaurora.org> wrote:
>> Hi Vikash,
>>
>> As you suggested I did this changes.
>> Below is combined pull request for venus-5.4 and VPU-2.0.
>> Please find snapshot of pull request, 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
>> c7b11ed12b6391097e84babab62802076fd15902:
>>
>> qcom: Add venus firmware files for VPU-2.0 (2021-05-03 12:18:45
>> +0530)
>>
>> ----------------------------------------------------------------
>> smagar (2):
>> qcom: update venus firmware files for v5.4
>> qcom: Add venus firmware files for VPU-2.0
>
> Vikash, does this one look good to you?
Yes, the pull request looks good to go.
> josh
>
>>
>> WHENCE | 19 ++++++++++++++++++-
>> 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
>> qcom/vpu-2.0/venus.b00 | Bin 0 -> 692 bytes
>> qcom/vpu-2.0/venus.b01 | Bin 0 -> 7376 bytes
>> qcom/vpu-2.0/venus.b02 | Bin 0 -> 300 bytes
>> qcom/vpu-2.0/venus.b03 | Bin 0 -> 20 bytes
>> qcom/vpu-2.0/venus.b04 | Bin 0 -> 20 bytes
>> qcom/vpu-2.0/venus.b05 | Bin 0 -> 20 bytes
>> qcom/vpu-2.0/venus.b06 | Bin 0 -> 20 bytes
>> qcom/vpu-2.0/venus.b07 | Bin 0 -> 24 bytes
>> qcom/vpu-2.0/venus.b08 | Bin 0 -> 16 bytes
>> qcom/vpu-2.0/venus.b09 | Bin 0 -> 939184 bytes
>> qcom/vpu-2.0/venus.b10 | Bin 0 -> 42976 bytes
>> qcom/vpu-2.0/venus.b19 | 1 +
>> qcom/vpu-2.0/venus.mbn | Bin 0 -> 2031188 bytes
>> qcom/vpu-2.0/venus.mdt | Bin 0 -> 8068 bytes
>> 21 files changed, 19 insertions(+), 1 deletion(-)
>> create mode 100644 qcom/vpu-2.0/venus.b00
>> create mode 100644 qcom/vpu-2.0/venus.b01
>> create mode 100644 qcom/vpu-2.0/venus.b02
>> create mode 100644 qcom/vpu-2.0/venus.b03
>> create mode 100644 qcom/vpu-2.0/venus.b04
>> create mode 100644 qcom/vpu-2.0/venus.b05
>> create mode 100644 qcom/vpu-2.0/venus.b06
>> create mode 100644 qcom/vpu-2.0/venus.b07
>> create mode 100644 qcom/vpu-2.0/venus.b08
>> create mode 100644 qcom/vpu-2.0/venus.b09
>> create mode 100644 qcom/vpu-2.0/venus.b10
>> create mode 100644 qcom/vpu-2.0/venus.b19
>> create mode 100644 qcom/vpu-2.0/venus.mbn
>> create mode 100644 qcom/vpu-2.0/venus.mdt
Regards,
Vikash
next prev parent reply other threads:[~2021-05-03 17:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 12:32 Update venus firmware files for v5.4 and venus firmware files for VPU-2.0 smagar
2021-04-28 13:48 ` Stanimir Varbanov
2021-04-28 13:48 ` Stanimir Varbanov
2021-04-29 8:35 ` vgarodia
2021-04-29 12:07 ` smagar
2021-04-30 7:39 ` vgarodia
2021-05-03 7:30 ` smagar
2021-05-03 13:35 ` Josh Boyer
2021-05-03 13:35 ` Josh Boyer
2021-05-03 17:22 ` vgarodia [this message]
2021-05-03 23:28 ` Josh Boyer
2021-05-03 23:28 ` 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=87a5e5795d06cd8a87315b74b201d693@codeaurora.org \
--to=vgarodia@codeaurora.org \
--cc=adhudase@codeaurora.org \
--cc=dikshita@codeaurora.org \
--cc=jwboyer@kernel.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=mansur@codeaurora.org \
--cc=mchehab@infradead.org \
--cc=sampnimm@codeaurora.org \
--cc=smagar@codeaurora.org \
--cc=stanimir.varbanov@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.