From: David Woodhouse <dwmw2@infradead.org>
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 16:15:32 -0700 [thread overview]
Message-ID: <1440112532.3303.100.camel@infradead.org> (raw)
In-Reply-To: <55D64AD2.9060900@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
On Thu, 2015-08-20 at 17:46 -0400, 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?
You cannot do that. The old firmware/ directory in the source tree is
incomplete, out of date and scheduled for deletion.
Firmware should *only* go into the separate linux-firmware.git
repository.
> 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).
Do not do that. It is believed by many to be a violation of the GPL.
If the firmware is needed to mount the root file system, then you can
put it into an initramfs and load it that way, rather than building it
into the GPL'd kernel image.
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5691 bytes --]
next prev parent reply other threads:[~2015-08-20 23:15 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
2015-08-20 23:15 ` David Woodhouse [this message]
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=1440112532.3303.100.camel@infradead.org \
--to=dwmw2@infradead.org \
--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