[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFLxGvxTenzaaypsUz6pYmjiyEeUtkNGDKwBNeAVFUb5ZZgonQ@mail.gmail.com>
Date: Sun, 13 Jan 2013 00:09:46 +0100
From: richard -rw- weinberger <richard.weinberger@...il.com>
To: Xose Vazquez Perez <xose.vazquez@...il.com>
Cc: Daniel Drake <dsd@...top.org>, Ulrich Kunitz <kune@...ne-taler.de>,
David Woodhouse <dwmw2@...radead.org>,
Ben Hutchings <ben@...adent.org.uk>,
linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] linux-firmware: add MISSING file
On Sat, Jan 12, 2013 at 11:39 PM, Xose Vazquez Perez
<xose.vazquez@...il.com> wrote:
> to document the reason why a firmware is not present
>
> Cc: Daniel Drake <dsd@...top.org>
> Cc: Ulrich Kunitz <kune@...ne-taler.de>
> Cc: David Woodhouse <dwmw2@...radead.org>
> Cc: Ben Hutchings <ben@...adent.org.uk>
> Cc: <linux-wireless@...r.kernel.org>
> Cc: <linux-kernel@...r.kernel.org>
> Signed-off-by: Xose Vazquez Perez <xose.vazquez@...il.com>
> ---
> MISSING | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
> create mode 100644 MISSING
>
> diff --git a/MISSING b/MISSING
> new file mode 100644
> index 0000000..f228099
> --- /dev/null
> +++ b/MISSING
> @@ -0,0 +1,20 @@
> + ***********
> + * MISSING *
> + ***********
> +
> +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 ..."
--
Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists