From: Arend van Spriel <arend@broadcom.com>
To: Murali Karicheri <m-karicheri2@ti.com>,
<linux-kernel@vger.kernel.org>, <linux-firmware@kernel.org>
Subject: Re: Question on adding a firmware ihex file in the kernel source
Date: Thu, 20 Aug 2015 23:58:44 +0200 [thread overview]
Message-ID: <55D64D94.70408@broadcom.com> (raw)
In-Reply-To: <55D64AD2.9060900@ti.com>
On 08/20/2015 11:46 PM, Murali Karicheri wrote:
> All,
>
> Please help me understand the procedure to add a firmware ihex file to
> kernel source tree under firmware/ folder. The README.AddingFirmware
> file explains that file should be added to
> git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git and
> the patch for the same to be send to linux-firmware@kernel.org. And this
> requires it to be in binary form. How does then that end up in the
> firmware/ folder of the Linux source tree as an ihex file? I would like
> to have one of the firmware statically built into the kernel as it is
> needed to be loaded even before file system is initialized in kernel
> (network driver firmware). Some other firmwares are to be used from the
> filesystem. Both would make use of the request_firmare() interface.
> Please help me understand the procedure.
Your firmware does not need to end up in the firmware/ folder of the
Linux source tree. That folder is more or less obsolete. If you want
firmware to be built into the kernel, you have to specify it in Kconfig.
Look for EXTRA_FIRMWARE. The help text is a good read.
Regards,
Arend
next prev parent reply other threads:[~2015-08-20 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 21:46 Question on adding a firmware ihex file in the kernel source Murali Karicheri
2015-08-20 21:58 ` Arend van Spriel [this message]
2015-08-20 23:15 ` David Woodhouse
2015-09-02 16:54 ` Murali Karicheri
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=55D64D94.70408@broadcom.com \
--to=arend@broadcom.com \
--cc=linux-firmware@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-karicheri2@ti.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