linux-kernel - Re: [PATCH] firmware: Automatically pull missing FW files

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: <1408567140.9484.0.camel@infradead.org>
Date:	Wed, 20 Aug 2014 15:39:00 -0500
From:	David Woodhouse <dwmw2@...radead.org>
To:	Tadeusz Struk <tadeusz.struk@...el.com>
Cc:	linux-firmware@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] firmware: Automatically pull missing FW files

On Wed, 2014-08-20 at 12:21 -0700, Tadeusz Struk wrote:
> Hi David,
> On 08/20/2014 11:34 AM, David Woodhouse wrote:
> > I'm not sure I understand. Precisely what fails?
> 
> I clone a subsystem, configure it to use
> CONFIG_EXTRA_FIRMWARE="qat_895xcc.bin", type make && make install and get:
> 
> MK_FW   firmware/qat_895xxc.bin.gen.S
> make[1]: *** No rule to make target `firmware/qat_895xxc.bin', needed by
> `firmware/qat_895xxc.bin.gen.o'.  Stop.

Can't you already just use CONFIG_EXTRA_FIRMWARE_DIR ? 

> Yes, if you use udev helper. When you want to compile in the blobs to
> your kernel it is needed in build time, right?

Yes. But seriously: don't do that. Let firmware get loaded from
userspace the normal way. Don't build kernel images that you can't distribute
because they include non-GPL parts.

-- 
dwmw2


Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (5745 bytes)