lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55D64D94.70408@broadcom.com>
Date:	Thu, 20 Aug 2015 23:58:44 +0200
From:	Arend van Spriel <arend@...adcom.com>
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 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@...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? 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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ