Linux-Firmware Archive on lore.kernel.org
 help / color / Atom feed
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,
	sampnimm@codeaurora.org
Subject: Update venus firmware files for v5.4 and v5.2
Date: Wed, 25 Nov 2020 14:11:35 +0530
Message-ID: <78c092f9b8d8b3833d7ac4f36253f7d3@codeaurora.org> (raw)
Message-ID: <20201125084135.jgNcP-2B-eUFEg8jrXB9YUTTJyhCGVcAlr5617PuxU8@z> (raw)

Hi Team,

Please include updated Venus Firmware bins for v5.4 and v5.2 .

Snapshot of pull request is as below, let me know if anything is 
missing.

>>>>>> 

The following changes since commit 
b362fd4cb8963ad75517dbcf424974f65a29a60e:

   Mellanox: Add new mlxsw_spectrum firmware xx.2008.2018 (2020-11-24 
09:55:03 -0500)

are available in the git repository at:

   https://github.com/shahasit/linux-firmware-video/tree/master

for you to fetch changes up to e6459dce893a5b8dbf684762d5396acc11149186:

   qcom : updated venus firmware files for v5.2 (2020-11-25 14:02:10 
+0530)

----------------------------------------------------------------
Asit Shah (2):
       qcom : updated venus firmware files for v5.4
       qcom : updated venus firmware files for v5.2

  qcom/venus-5.2/venus.b00 | Bin 212 -> 212 bytes
  qcom/venus-5.2/venus.b01 | Bin 6600 -> 6808 bytes
  qcom/venus-5.2/venus.b02 | Bin 837304 -> 856432 bytes
  qcom/venus-5.2/venus.b03 | Bin 33640 -> 33648 bytes
  qcom/venus-5.2/venus.mbn | Bin 883264 -> 902400 bytes
  qcom/venus-5.2/venus.mdt | Bin 6812 -> 7020 bytes
  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 -> 873704 bytes
  qcom/venus-5.4/venus.b03 | Bin 33792 -> 33792 bytes
  qcom/venus-5.4/venus.mbn | Bin 919792 -> 919816 bytes
  qcom/venus-5.4/venus.mdt | Bin 7020 -> 7020 bytes
  12 files changed, 0 insertions(+), 0 deletions(-)

<<<<<<

Regards,
Asit

             reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25  8:41 asitshah [this message]
2020-11-25  8:41 ` asitshah
2020-11-25 16:02 ` Stanimir Varbanov
2020-11-25 16:02   ` Stanimir Varbanov

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=78c092f9b8d8b3833d7ac4f36253f7d3@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=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

Linux-Firmware Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-firmware/0 linux-firmware/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-firmware linux-firmware/ https://lore.kernel.org/linux-firmware \
		linux-firmware@kernel.org
	public-inbox-index linux-firmware

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.lore.linux-firmware


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git