From: santosh.shilimkar@oracle.com (santosh.shilimkar at oracle.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 1/2] soc: ti: display firmware file name as part of boot log
Date: Wed, 9 Sep 2015 10:12:25 -0700 [thread overview]
Message-ID: <55F06879.3060000@oracle.com> (raw)
In-Reply-To: <55F06075.6050405@ti.com>
On 9/9/15 9:38 AM, Murali Karicheri wrote:
> On 09/04/2015 11:53 PM, santosh.shilimkar at oracle.com wrote:
>> On 9/4/15 5:46 PM, Murali Karicheri wrote:
>>> To help the user, print the PDSP file name as part of
>>> knav_queue_load_pdsp(). This will be useful for users to know what
>>> version of the firmware is loaded to PDSP. Also update the
>>> document for the location of the QMSS accumulator PDSP firmware.
>>>
>>> Signed-off-by: Murali Karicheri <m-karicheri2@ti.com>
>>> ---
>>
>> Looks fine. Will pick both the patches.
>>
>
> Thanks Santhosh.
>
> Is there a requirement to add the firmware to linux-firmware.git. Right
> now I have provided link to ti git repo that has the firmware. I have
> the patch ready in case this is required. Do you know?
>
Standard distro's will look for linux-firmware.git as a source to get
the firmware files used by kernel so yes, you should add these firmware
files to that repo.
Regards,
Santosh
next prev parent reply other threads:[~2015-09-09 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 21:46 [PATCH v1 1/2] soc: ti: display firmware file name as part of boot log Murali Karicheri
2015-09-04 21:46 ` [PATCH v1 2/2] ARM: dts: keystone: enable accumulator channels Murali Karicheri
2015-09-05 3:53 ` [PATCH v1 1/2] soc: ti: display firmware file name as part of boot log santosh.shilimkar at oracle.com
2015-09-09 16:38 ` Murali Karicheri
2015-09-09 17:12 ` santosh.shilimkar at oracle.com [this message]
2015-09-09 17:23 ` Murali Karicheri
2015-09-15 18:14 ` Murali Karicheri
2015-09-15 21:20 ` santosh shilimkar
2015-09-16 17:01 ` Murali Karicheri
2015-09-16 19:13 ` santosh shilimkar
2015-09-17 16:18 ` santosh.shilimkar at oracle.com
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=55F06879.3060000@oracle.com \
--to=santosh.shilimkar@oracle.com \
--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).