From: Valdis.Kletnieks@vt.edu
To: Tadeusz Struk <tadeusz.struk@intel.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-firmware@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware: Automatically pull missing FW files
Date: Wed, 20 Aug 2014 16:17:13 -0400 [thread overview]
Message-ID: <22524.1408565833@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 20 Aug 2014 12:21:23 -0700." <53F4F533.5010308@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
On Wed, 20 Aug 2014 12:21:23 -0700, Tadeusz Struk said:
> 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.
Is this what you were looking for?
config EXTRA_FIRMWARE_DIR
string "Firmware blobs root directory"
depends on EXTRA_FIRMWARE != ""
default "firmware"
help
This option controls the directory in which the kernel build system
looks for the firmware files listed in the EXTRA_FIRMWARE option.
The default is firmware/ in the kernel source tree, but by changing
this option you can point it elsewhere, such as /lib/firmware/ or
some other directory containing the firmware files.
[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]
next prev parent reply other threads:[~2014-08-20 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 18:21 Tadeusz Struk
2014-08-20 18:34 ` David Woodhouse
2014-08-20 19:21 ` Tadeusz Struk
2014-08-20 20:17 ` Valdis.Kletnieks [this message]
2014-08-20 20:39 ` David Woodhouse
2014-08-20 20:48 ` Tadeusz Struk
2014-08-21 12:31 ` Henrique de Moraes Holschuh
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=22524.1408565833@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=dwmw2@infradead.org \
--cc=linux-firmware@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tadeusz.struk@intel.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
all inboxes | Powered by JetHome®