From: David Woodhouse <dwmw2@infradead.org>
To: Tadeusz Struk <tadeusz.struk@intel.com>
Cc: linux-firmware@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware: Automatically pull missing FW files
Date: Wed, 20 Aug 2014 15:39:00 -0500 [thread overview]
Message-ID: <1408567140.9484.0.camel@infradead.org> (raw)
In-Reply-To: <53F4F533.5010308@intel.com>
[-- Attachment #1: Type: text/plain, Size: 847 bytes --]
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
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5745 bytes --]
next prev parent reply other threads:[~2014-08-20 20:39 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
2014-08-20 20:39 ` David Woodhouse [this message]
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=1408567140.9484.0.camel@infradead.org \
--to=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
Powered by JetHome