[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1440112532.3303.100.camel@infradead.org>
Date: Thu, 20 Aug 2015 16:15:32 -0700
From: David Woodhouse <dwmw2@...radead.org>
To: Murali Karicheri <m-karicheri2@...com>,
linux-kernel@...r.kernel.org, linux-firmware@...nel.org
Subject: Re: Question on adding a firmware ihex file in the kernel source
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@...nel.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
Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (5691 bytes)
Powered by blists - more mailing lists