From: Josh Boyer <jwboyer@kernel.org> To: smagar@codeaurora.org Cc: 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>, Stanimir Varbanov <stanimir.varbanov@linaro.org>, linux-media-owner@vger.kernel.org, vgarodia@codeaurora.org, dikshita@codeaurora.org, adhudase@codeaurora.org, sampnimm@codeaurora.org, mansur@codeaurora.org Subject: Re: Request to update venus-5.10 FW files Date: Wed, 21 Apr 2021 07:18:46 -0400 [thread overview] Message-ID: <CA+5PVA7pbgVRpwkM71ToxRwBKfH=j51GrZcz+8Q5H2MpmmL-_w@mail.gmail.com> (raw) In-Reply-To: <8885c6fbfcc91043a5406cf6e528e0b9@codeaurora.org> On Wed, Apr 21, 2021 at 2:59 AM <smagar@codeaurora.org> wrote: > > Hello Team, > > Please include updated firmware bins for venus-5.10. > > Snapshot of pull request is as below, let me know if anything is > missing. > > > > The following changes since commit > 5c893c65b862906a627cea238ae8c2d099027dee: > > Updated Venus firmware files for v5.10 (2021-04-20 11:48:28 +0530) > > are available in the git repository at: > > https://github.com/suraj714/linux-firmware-venus.git master > > for you to fetch changes up to 2565c9d2576ce1275206483e106d6fb627ace042: > > qcom :venus_v5.10: updated venus firmware files for v5.10 (2021-04-21 > 12:04:59 +0530) > > ---------------------------------------------------------------- > smagar (1): > qcom :venus_v5.10: updated venus firmware files for v5.10 > > qcom/sc7280/vpu20_1v.b00 | Bin 0 -> 692 bytes > qcom/sc7280/vpu20_1v.b01 | Bin 0 -> 7376 bytes > qcom/sc7280/vpu20_1v.b02 | Bin 0 -> 300 bytes > qcom/sc7280/vpu20_1v.b03 | Bin 0 -> 20 bytes > qcom/sc7280/vpu20_1v.b04 | Bin 0 -> 20 bytes > qcom/sc7280/vpu20_1v.b05 | Bin 0 -> 20 bytes > qcom/sc7280/vpu20_1v.b06 | Bin 0 -> 20 bytes > qcom/sc7280/vpu20_1v.b07 | Bin 0 -> 24 bytes > qcom/sc7280/vpu20_1v.b08 | Bin 0 -> 16 bytes > qcom/sc7280/vpu20_1v.b09 | Bin 0 -> 939184 bytes > qcom/sc7280/vpu20_1v.b10 | Bin 0 -> 42976 bytes > qcom/sc7280/vpu20_1v.b11 | 0 > qcom/sc7280/vpu20_1v.b12 | 0 > qcom/sc7280/vpu20_1v.b13 | 0 > qcom/sc7280/vpu20_1v.b14 | 0 > qcom/sc7280/vpu20_1v.b15 | 0 > qcom/sc7280/vpu20_1v.b16 | 0 > qcom/sc7280/vpu20_1v.b17 | 0 > qcom/sc7280/vpu20_1v.b18 | 0 > qcom/sc7280/vpu20_1v.b19 | 1 + > qcom/sc7280/vpu20_1v.mbn | Bin 0 -> 2031188 bytes > qcom/sc7280/vpu20_1v.mdt | Bin 0 -> 8068 bytes > qcom/sc7280/vpu20_1v_unsigned.mbn | Bin 0 -> 2031188 bytes This looks weird. You're adding 23 new files, none of which are mentioned in WHENCE. Also, why do you have a bunch of 0 byte files? Is this correct? josh > 23 files changed, 1 insertion(+) > create mode 100644 qcom/sc7280/vpu20_1v.b00 > create mode 100644 qcom/sc7280/vpu20_1v.b01 > create mode 100644 qcom/sc7280/vpu20_1v.b02 > create mode 100644 qcom/sc7280/vpu20_1v.b03 > create mode 100644 qcom/sc7280/vpu20_1v.b04 > create mode 100644 qcom/sc7280/vpu20_1v.b05 > create mode 100644 qcom/sc7280/vpu20_1v.b06 > create mode 100644 qcom/sc7280/vpu20_1v.b07 > create mode 100644 qcom/sc7280/vpu20_1v.b08 > create mode 100644 qcom/sc7280/vpu20_1v.b09 > create mode 100644 qcom/sc7280/vpu20_1v.b10 > create mode 100644 qcom/sc7280/vpu20_1v.b11 > create mode 100644 qcom/sc7280/vpu20_1v.b12 > create mode 100644 qcom/sc7280/vpu20_1v.b13 > create mode 100644 qcom/sc7280/vpu20_1v.b14 > create mode 100644 qcom/sc7280/vpu20_1v.b15 > create mode 100644 qcom/sc7280/vpu20_1v.b16 > create mode 100644 qcom/sc7280/vpu20_1v.b17 > create mode 100644 qcom/sc7280/vpu20_1v.b18 > create mode 100644 qcom/sc7280/vpu20_1v.b19 > create mode 100644 qcom/sc7280/vpu20_1v.mbn > create mode 100644 qcom/sc7280/vpu20_1v.mdt > create mode 100644 qcom/sc7280/vpu20_1v_unsigned.mbn > > Regards, > Suraj Magar
WARNING: multiple messages have this Message-ID (diff)
From: Josh Boyer <jwboyer@kernel.org> To: smagar@codeaurora.org Cc: 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>, Stanimir Varbanov <stanimir.varbanov@linaro.org>, linux-media-owner@vger.kernel.org, vgarodia@codeaurora.org, dikshita@codeaurora.org, adhudase@codeaurora.org, sampnimm@codeaurora.org, mansur@codeaurora.org Subject: Re: Request to update venus-5.10 FW files Date: Wed, 21 Apr 2021 07:18:46 -0400 [thread overview] Message-ID: <CA+5PVA7pbgVRpwkM71ToxRwBKfH=j51GrZcz+8Q5H2MpmmL-_w@mail.gmail.com> (raw) Message-ID: <20210421111846.G_mtcitrxVqRuFm-pZM3kKELTPOIO7VEMGEpWofj5og@z> (raw) In-Reply-To: <8885c6fbfcc91043a5406cf6e528e0b9@codeaurora.org> On Wed, Apr 21, 2021 at 2:59 AM <smagar@codeaurora.org> wrote: > > Hello Team, > > Please include updated firmware bins for venus-5.10. > > Snapshot of pull request is as below, let me know if anything is > missing. > > > > The following changes since commit > 5c893c65b862906a627cea238ae8c2d099027dee: > > Updated Venus firmware files for v5.10 (2021-04-20 11:48:28 +0530) > > are available in the git repository at: > > https://github.com/suraj714/linux-firmware-venus.git master > > for you to fetch changes up to 2565c9d2576ce1275206483e106d6fb627ace042: > > qcom :venus_v5.10: updated venus firmware files for v5.10 (2021-04-21 > 12:04:59 +0530) > > ---------------------------------------------------------------- > smagar (1): > qcom :venus_v5.10: updated venus firmware files for v5.10 > > qcom/sc7280/vpu20_1v.b00 | Bin 0 -> 692 bytes > qcom/sc7280/vpu20_1v.b01 | Bin 0 -> 7376 bytes > qcom/sc7280/vpu20_1v.b02 | Bin 0 -> 300 bytes > qcom/sc7280/vpu20_1v.b03 | Bin 0 -> 20 bytes > qcom/sc7280/vpu20_1v.b04 | Bin 0 -> 20 bytes > qcom/sc7280/vpu20_1v.b05 | Bin 0 -> 20 bytes > qcom/sc7280/vpu20_1v.b06 | Bin 0 -> 20 bytes > qcom/sc7280/vpu20_1v.b07 | Bin 0 -> 24 bytes > qcom/sc7280/vpu20_1v.b08 | Bin 0 -> 16 bytes > qcom/sc7280/vpu20_1v.b09 | Bin 0 -> 939184 bytes > qcom/sc7280/vpu20_1v.b10 | Bin 0 -> 42976 bytes > qcom/sc7280/vpu20_1v.b11 | 0 > qcom/sc7280/vpu20_1v.b12 | 0 > qcom/sc7280/vpu20_1v.b13 | 0 > qcom/sc7280/vpu20_1v.b14 | 0 > qcom/sc7280/vpu20_1v.b15 | 0 > qcom/sc7280/vpu20_1v.b16 | 0 > qcom/sc7280/vpu20_1v.b17 | 0 > qcom/sc7280/vpu20_1v.b18 | 0 > qcom/sc7280/vpu20_1v.b19 | 1 + > qcom/sc7280/vpu20_1v.mbn | Bin 0 -> 2031188 bytes > qcom/sc7280/vpu20_1v.mdt | Bin 0 -> 8068 bytes > qcom/sc7280/vpu20_1v_unsigned.mbn | Bin 0 -> 2031188 bytes This looks weird. You're adding 23 new files, none of which are mentioned in WHENCE. Also, why do you have a bunch of 0 byte files? Is this correct? josh > 23 files changed, 1 insertion(+) > create mode 100644 qcom/sc7280/vpu20_1v.b00 > create mode 100644 qcom/sc7280/vpu20_1v.b01 > create mode 100644 qcom/sc7280/vpu20_1v.b02 > create mode 100644 qcom/sc7280/vpu20_1v.b03 > create mode 100644 qcom/sc7280/vpu20_1v.b04 > create mode 100644 qcom/sc7280/vpu20_1v.b05 > create mode 100644 qcom/sc7280/vpu20_1v.b06 > create mode 100644 qcom/sc7280/vpu20_1v.b07 > create mode 100644 qcom/sc7280/vpu20_1v.b08 > create mode 100644 qcom/sc7280/vpu20_1v.b09 > create mode 100644 qcom/sc7280/vpu20_1v.b10 > create mode 100644 qcom/sc7280/vpu20_1v.b11 > create mode 100644 qcom/sc7280/vpu20_1v.b12 > create mode 100644 qcom/sc7280/vpu20_1v.b13 > create mode 100644 qcom/sc7280/vpu20_1v.b14 > create mode 100644 qcom/sc7280/vpu20_1v.b15 > create mode 100644 qcom/sc7280/vpu20_1v.b16 > create mode 100644 qcom/sc7280/vpu20_1v.b17 > create mode 100644 qcom/sc7280/vpu20_1v.b18 > create mode 100644 qcom/sc7280/vpu20_1v.b19 > create mode 100644 qcom/sc7280/vpu20_1v.mbn > create mode 100644 qcom/sc7280/vpu20_1v.mdt > create mode 100644 qcom/sc7280/vpu20_1v_unsigned.mbn > > Regards, > Suraj Magar _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-04-21 11:18 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-21 6:59 Request to update venus-5.10 FW files smagar 2021-04-21 11:18 ` Josh Boyer [this message] 2021-04-21 11:18 ` Josh Boyer 2021-04-23 13:27 ` vgarodia 2021-04-28 12:33 ` smagar
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+5PVA7pbgVRpwkM71ToxRwBKfH=j51GrZcz+8Q5H2MpmmL-_w@mail.gmail.com' \ --to=jwboyer@kernel.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 \ --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: linkBe 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.