linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Clark <robdclark@gmail.com>
To: Nathan Hebert <nhebert@chromium.org>
Cc: linux-firmware@kernel.org, linux-arm-msm@vger.kernel.org,
	quic_vgarodia@quicinc.com, Fritz Koenig <frkoenig@chromium.org>,
	Bjorn Andersson <andersson@kernel.org>
Subject: Re: [PULL]: qcom: SC7180 and SC7280 venus firmware updates
Date: Wed, 19 Oct 2022 09:02:10 -0700	[thread overview]
Message-ID: <CAF6AEGtsw5GTB+MzvA7mE8y=m6qDFtQNFnnAVtuFSxnDAT0YuA@mail.gmail.com> (raw)
In-Reply-To: <CAF6AEGvvsx+6OSxOaqjoUO=J4tO_J5ZSidenx9EXdz34_myBqQ@mail.gmail.com>

Actually, isn't the .mbn the joined fw?  If so all you need to do is
remove the other files?

On Wed, Oct 19, 2022 at 8:52 AM Rob Clark <robdclark@gmail.com> wrote:
>
> Hmm, does venus not support the combined firmware yet?  Elsewhere
> we've moved away from split fw to using a single ELF file..
>
> BR,
> -R
>
> On Tue, Oct 18, 2022 at 2:18 PM Nathan Hebert <nhebert@chromium.org> wrote:
> >
> > The following changes since commit 48407ffd7adb9511701547068b1e6f0956bd1c94:
> >
> >   cnm: update chips&media wave521c firmware. (2022-10-17 10:20:43 -0400)
> >
> > are available in the Git repository at:
> >
> >   https://github.com/nathan-google/linux-firmware.git
> > update_sc7180_and_sc7280_firmwares
> >
> > for you to fetch changes up to 76e160366a28010fa06ddc965659c38a44d159d9:
> >
> >   qcom: update venus firmware files for VPU-2.0 (2022-10-18 13:42:58 -0700)
> >
> > ----------------------------------------------------------------
> > Nathan Hebert (2):
> >       qcom: update venus firmware files for v5.4
> >       qcom: update venus firmware files for VPU-2.0
> >
> >  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 873596 -> 875020 bytes
> >  qcom/venus-5.4/venus.b03 | Bin 33792 -> 33896 bytes
> >  qcom/venus-5.4/venus.mbn | Bin 919708 -> 921236 bytes
> >  qcom/venus-5.4/venus.mdt | Bin 7020 -> 7020 bytes
> >  qcom/vpu-2.0/venus.b00   | Bin 692 -> 692 bytes
> >  qcom/vpu-2.0/venus.b01   | Bin 7376 -> 7376 bytes
> >  qcom/vpu-2.0/venus.b02   | Bin 300 -> 300 bytes
> >  qcom/vpu-2.0/venus.b04   | Bin 20 -> 20 bytes
> >  qcom/vpu-2.0/venus.b09   | Bin 939184 -> 939472 bytes
> >  qcom/vpu-2.0/venus.b10   | Bin 42976 -> 43120 bytes
> >  qcom/vpu-2.0/venus.mbn   | Bin 2031188 -> 2031620 bytes
> >  qcom/vpu-2.0/venus.mdt   | Bin 8068 -> 8068 bytes
> >  14 files changed, 0 insertions(+), 0 deletions(-)

  reply	other threads:[~2022-10-19 16:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 21:12 [PULL]: qcom: SC7180 and SC7280 venus firmware updates Nathan Hebert
2022-10-19 15:52 ` Rob Clark
2022-10-19 16:02   ` Rob Clark [this message]
2022-10-19 17:09     ` Vikash Garodia
2022-10-20 16:52       ` Nathan Hebert
2022-10-20 18:00         ` Dmitry Baryshkov
2022-10-25  6:20           ` Vikash Garodia
2022-10-25 15:13             ` Nathan Hebert

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='CAF6AEGtsw5GTB+MzvA7mE8y=m6qDFtQNFnnAVtuFSxnDAT0YuA@mail.gmail.com' \
    --to=robdclark@gmail.com \
    --cc=andersson@kernel.org \
    --cc=frkoenig@chromium.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-firmware@kernel.org \
    --cc=nhebert@chromium.org \
    --cc=quic_vgarodia@quicinc.com \
    /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).