linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: vgarodia@codeaurora.org (Vikash Garodia)
To: linux-arm-kernel@lists.infradead.org
Subject: qcom: add firmware file for Venus on SDM845
Date: Sat, 26 May 2018 13:48:35 +0530	[thread overview]
Message-ID: <bcb4ba3ccd3b139ce03b6736d8d07cbe@codeaurora.org> (raw)
In-Reply-To: <CA+5PVA67tow+prVC55XF4=CbRGXJvPi2SuCMyhRyuw5qt8T6_Q@mail.gmail.com>

Hi Josh,

On 2018-05-25 17:34, Josh Boyer wrote:
> On Fri, May 25, 2018 at 7:03 AM Vikash Garodia 
> <vgarodia@codeaurora.org>
> wrote:
> 
>> This pull request adds firmware files for Venus h/w codec found on the
> Qualcomm SDM845 chipset.
> 
>> The following changes since commit
> 2a9b2cf50fb32e36e4fc1586c2f6f1421913b553:
> 
>>    Merge branch 'for-upstreaming-v1.7.2' of
> https://github.com/felix-cavium/linux-firmware (2018-05-18 08:35:22 
> -0400)
> 
>> are available in the git repository at:
> 
> 
>>    https://github.com/vgarodia/linux-firmware master
> 
>> for you to fetch changes up to 
>> d6088b9c9d7f49d3c6c43681190889eca0abdcce:
> 
>>    qcom: add venus firmware files for v5.2 (2018-05-25 15:16:43 +0530)
> 
>> ----------------------------------------------------------------
>> Vikash Garodia (1):
>>        qcom: add venus firmware files for v5.2
> 
>>   WHENCE                   |   9 +++++++++
>>   qcom/venus-5.2/venus.b00 | Bin 0 -> 212 bytes
>>   qcom/venus-5.2/venus.b01 | Bin 0 -> 6600 bytes
>>   qcom/venus-5.2/venus.b02 | Bin 0 -> 819552 bytes
>>   qcom/venus-5.2/venus.b03 | Bin 0 -> 33536 bytes
>>   qcom/venus-5.2/venus.b04 |   1 +
>>   qcom/venus-5.2/venus.mbn | Bin 0 -> 865408 bytes
>>   qcom/venus-5.2/venus.mdt | Bin 0 -> 6812 bytes
>>   8 files changed, 10 insertions(+)
>>   create mode 100644 qcom/venus-5.2/venus.b00
>>   create mode 100644 qcom/venus-5.2/venus.b01
>>   create mode 100644 qcom/venus-5.2/venus.b02
>>   create mode 100644 qcom/venus-5.2/venus.b03
>>   create mode 100644 qcom/venus-5.2/venus.b04
>>   create mode 100644 qcom/venus-5.2/venus.mbn
>>   create mode 100644 qcom/venus-5.2/venus.mdt
> 
> The venus.mbn file isn't mentioned in WHENCE:
> 
> [jwboyer at vader linux-firmware]$ ./check_whence.py
> E: qcom/venus-5.2/venus.mbn not listed in WHENCE
> [jwboyer at vader linux-firmware]$
> 
> Can you fix that up and let me know when to re-pull?
I have fixed the error and is ready to be re-pulled from the same git 
repository.
I have noted the process to run check_whence.py before uploading the 
firmwares.

Do i need to resend the pull request as the end commit is now changed to
7602644358157e4b89960472b6d59ffcc040ca52 ?

-Vikash

  reply	other threads:[~2018-05-26  8:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25 11:03 qcom: add firmware file for Venus on SDM845 Vikash Garodia
2018-05-25 11:03 ` Vikash Garodia
2018-05-25 12:04   ` Josh Boyer
2018-05-26  8:18     ` Vikash Garodia [this message]
2018-06-04 12:52       ` Josh Boyer
  -- strict thread matches above, loose matches on Subject: below --
2018-04-23  6:11 Vikash Garodia

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=bcb4ba3ccd3b139ce03b6736d8d07cbe@codeaurora.org \
    --to=vgarodia@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.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).