[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130114175533.4f184cd3@mj>
Date: Mon, 14 Jan 2013 17:55:33 -0500
From: Pavel Roskin <proski@....org>
To: richard -rw- weinberger <richard.weinberger@...il.com>
Cc: Xose Vazquez Perez <xose.vazquez@...il.com>,
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 Sun, 13 Jan 2013 00:09:46 +0100
richard -rw- weinberger <richard.weinberger@...il.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
--
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