From: vgarodia@codeaurora.org
To: Stanimir Varbanov <stanimir.varbanov@linaro.org>
Cc: smagar@codeaurora.org, linux-firmware@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org, 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: Thu, 29 Apr 2021 14:05:56 +0530 [thread overview]
Message-ID: <c38ab84b90feddb43b2782fa11ee5189@codeaurora.org> (raw)
In-Reply-To: <9eaaec5d-a7d4-1889-5c92-28944b198adc@linaro.org>
On 2021-04-28 19:18, Stanimir Varbanov wrote:
> On 4/28/21 3:32 PM, smagar@codeaurora.org wrote:
>> Hello Team,
>>
>> Please include updated firmware bins for venus-5.4 and vpu-2.0.
>>
>> I have fixed comment and title updated.
>>
>> Removed 0 byte unwanted bins.
>>
>> 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
>> 6cdef281cd16d967ad89c01af6fdda85529a2d80:
>>
>> qcom: Add venus firmware files for VPU-2.0 (2021-04-28 14:42:48
>> +0530)
>>
>> ----------------------------------------------------------------
>> smagar (2):
>> qcom: update venus firmware files for v5.4
>> qcom: Add venus firmware files for VPU-2.0
>>
>> WHENCE | 34 +++++++++++++++++++++++++++++++++-
>> 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/vpu20_1v.b00 | Bin 0 -> 692 bytes
>> qcom/vpu-2.0/vpu20_1v.b01 | Bin 0 -> 7376 bytes
>> qcom/vpu-2.0/vpu20_1v.b02 | Bin 0 -> 300 bytes
>> qcom/vpu-2.0/vpu20_1v.b03 | Bin 0 -> 20 bytes
>> qcom/vpu-2.0/vpu20_1v.b04 | Bin 0 -> 20 bytes
>> qcom/vpu-2.0/vpu20_1v.b05 | Bin 0 -> 20 bytes
>> qcom/vpu-2.0/vpu20_1v.b06 | Bin 0 -> 20 bytes
>> qcom/vpu-2.0/vpu20_1v.b07 | Bin 0 -> 24 bytes
>> qcom/vpu-2.0/vpu20_1v.b08 | Bin 0 -> 16 bytes
>> qcom/vpu-2.0/vpu20_1v.b09 | Bin 0 -> 939184 bytes
>> qcom/vpu-2.0/vpu20_1v.b10 | Bin 0 -> 42976 bytes
>> qcom/vpu-2.0/vpu20_1v.b19 | 1 +
>> qcom/vpu-2.0/vpu20_1v.mbn | Bin 0 -> 2031188 bytes
>> qcom/vpu-2.0/vpu20_1v.mdt | Bin 0 -> 8068 bytes
Suraj, lets make these as generic names venus.bxx. We could confirm on
hardware
with generic binary names.
>
> Which Venus IP/SoCs use vpu-2.0 firmware? And what is the difference
> with existing vpu-1.0?
This is for sc7280.
vpu-1.0 and vpu-2.0 differs in hardware w.r.t number of hardware
processing pipes.
Thanks,
Vikash
next prev parent reply other threads:[~2021-04-29 8:36 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 [this message]
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
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=c38ab84b90feddb43b2782fa11ee5189@codeaurora.org \
--to=vgarodia@codeaurora.org \
--cc=adhudase@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=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.