From: Valdis.Kletnieks@vt.edu
To: Mike Waychison <mikew@google.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-firmware tree
Date: Mon, 02 May 2011 18:22:05 -0400 [thread overview]
Message-ID: <33956.1304374925@localhost> (raw)
In-Reply-To: Your message of "Mon, 02 May 2011 14:40:33 PDT." <BANLkTinTUdAgF4eQ8_JtWgT_jJB5f7nT-A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 495 bytes --]
On Mon, 02 May 2011 14:40:33 PDT, Mike Waychison said:
> I don't see anything in the build (looking at scripts/Makefile.fwinst
> in particular) that allows the build to enumerate out-of-tree firmware
> files required by drivers. Do you have any thoughts on how this could
> be enumerated? (if it isn't already?)
MODULE_FIRMWARE tags in the drivers, combined with (possibly)
the CONFIG_EXTRA_FIRMWARE and CONFIG_EXTRA_FIRMWARE_DIR
Kconfig variables if the needed bits aren't in /lib/firmware?
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2011-05-02 22:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 18:57 linux-firmware tree Mike Waychison
2011-05-02 19:38 ` David Woodhouse
2011-05-02 21:40 ` Mike Waychison
2011-05-02 21:56 ` David Woodhouse
2011-05-02 22:22 ` Valdis.Kletnieks [this message]
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=33956.1304374925@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikew@google.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