linux-firmware.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@gmail.com>
To: asitshah@codeaurora.org
Cc: dikshita@codeaurora.org,
	Stanimir Varbanov <stanimir.varbanov@linaro.org>,
	Linux Firmware <linux-firmware@kernel.org>,
	linux-media-owner@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	vgarodia@codeaurora.org, linux-arm-kernel@lists.infradead.org,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Update venus firmware files for v5.4
Date: Fri, 13 Nov 2020 10:19:05 -0500	[thread overview]
Message-ID: <CA+5PVA5eWkyWuG6ehcfsO=h_LSOzyOpdB_d3=y0O6m+jeeobEg@mail.gmail.com> (raw)
Message-ID: <20201113151905.OTq88AWnBeXdRP09p8mAJH9_4LGWnoANGrw6d8HiJHc@z> (raw)
In-Reply-To: <c1bcb5eedc160e99d65576d431816a41@codeaurora.org>

Pulled and pushed out.

josh

On Fri, Nov 6, 2020 at 12:10 AM <asitshah@codeaurora.org> wrote:
>
> 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

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2020-11-13 15:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06  5:10 Update venus firmware files for v5.4 asitshah
2020-11-06  5:10 ` asitshah
2020-11-06  5:10 ` asitshah
2020-11-13 15:19 ` Josh Boyer [this message]
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='CA+5PVA5eWkyWuG6ehcfsO=h_LSOzyOpdB_d3=y0O6m+jeeobEg@mail.gmail.com' \
    --to=jwboyer@gmail.com \
    --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=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).