From: Pavel Roskin <proski@gnu.org>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: Xose Vazquez Perez <xose.vazquez@gmail.com>,
Daniel Drake <dsd@laptop.org>,
Ulrich Kunitz <kune@deine-taler.de>,
David Woodhouse <dwmw2@infradead.org>,
Ben Hutchings <ben@decadent.org.uk>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] linux-firmware: add MISSING file
Date: Mon, 14 Jan 2013 17:55:33 -0500 [thread overview]
Message-ID: <20130114175533.4f184cd3@mj> (raw)
In-Reply-To: <CAFLxGvxTenzaaypsUz6pYmjiyEeUtkNGDKwBNeAVFUb5ZZgonQ@mail.gmail.com>
On Sun, 13 Jan 2013 00:09:46 +0100
richard -rw- weinberger <richard.weinberger@gmail.com> wrote:
> > +This file attempts to document the reason why a firmware is not
> > present +in this bundle.
>
> From the user's point of view this not really helpful.
> Wouldn't a in-kernel table of known but missing firmware files make
> more sense? The kernel could write a log like "Yeah, I know this
> firmware but sadly I don't have it because of ..."
The firmware file may be absent on the system even if it's in the
linux-firmware tree. Conversely, the firmware may be present on the
system but not in the linux-firmware tree.
The kernel doesn't know whether the firmware is missing due to
licensing issues or due to misconfiguration. The kernel cannot know
that. And I don't think the kernel should include as much information
as the MISSING file would include.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2013-01-14 22:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 22:39 [PATCH] linux-firmware: add MISSING file Xose Vazquez Perez
2013-01-12 23:09 ` richard -rw- weinberger
2013-01-14 22:55 ` Pavel Roskin [this message]
2013-01-21 1:31 ` Ben Hutchings
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=20130114175533.4f184cd3@mj \
--to=proski@gnu.org \
--cc=ben@decadent.org.uk \
--cc=dsd@laptop.org \
--cc=dwmw2@infradead.org \
--cc=kune@deine-taler.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
--cc=xose.vazquez@gmail.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;
as well as URLs for NNTP newsgroup(s).