On Sat, Jan 12, 2013 at 11:39 PM, Xose Vazquez Perez <[email protected]> wrote: > to document the reason why a firmware is not present > > Cc: Daniel Drake <[email protected]> > Cc: Ulrich Kunitz <[email protected]> > Cc: David Woodhouse <[email protected]> > Cc: Ben Hutchings <[email protected]> > Cc: <[email protected]> > Cc: <[email protected]> > Signed-off-by: Xose Vazquez Perez <[email protected]> > --- > 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 [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
