From: Mike Waychison <mikew@google.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-firmware tree
Date: Mon, 2 May 2011 14:40:33 -0700 [thread overview]
Message-ID: <BANLkTinTUdAgF4eQ8_JtWgT_jJB5f7nT-A@mail.gmail.com> (raw)
In-Reply-To: <1304365095.6400.20.camel@macbook.infradead.org>
On Mon, May 2, 2011 at 12:38 PM, David Woodhouse <dwmw2@infradead.org> wrote:
> On Mon, 2011-05-02 at 19:57 +0100, Mike Waychison wrote:
>> Hi David,
>>
>> I'm trying to understand the purpose of the linux-firmware tree.
>> Forgive me if this is a stupid question, but the only information
>> about it I could find was your original post back in 2008:
>> https://lwn.net/Articles/294308/
>>
>> Will the Linux kernel sources always continue to have the firmware
>> blobs and the linux-firmware tree is only for those users of distros
>> that strip the firmware out?
>
> No, the legacy firmware images from the kernel tree are going to be
> removed. They were only kept for backward compatibility.
>
> The linux-firmware tree has a lot of things that were never included in
> the kernel source; no *new* firmware images are being (or at least
> should be) added to the kernel source itself.
>
> Everyone should be using the linux-firmware tree by now.
Fair enough. We haven't actually hit a case where the firmware
required by any of the drivers we use isn't already present in the
tree.
I'm trying to figure out how we could ship firmware blobs on our
systems going forward. Currently, we let firmware get installed to
our install root via the modules_install target, and then package up
the install root. If drivers are going to request firmware blobs from
userland without them being picked up in-tree by
fw-shipped-$(CONFIG_FOO), we'll need to know at build time which
firmware blobs to package up.
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?)
The alternative would be to ship the whole of the linux-firmware tree
on every machine we have, but that seems like a bad idea as it is only
going to grow with time and we don't have the MiB budget for such a
thing.
next prev parent reply other threads:[~2011-05-02 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 18:57 Mike Waychison
2011-05-02 19:38 ` David Woodhouse
2011-05-02 21:40 ` Mike Waychison [this message]
2011-05-02 21:56 ` David Woodhouse
2011-05-02 22:22 ` Valdis.Kletnieks
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=BANLkTinTUdAgF4eQ8_JtWgT_jJB5f7nT-A@mail.gmail.com \
--to=mikew@google.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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®