[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121003224554.23fca4af@pyramind.ukuu.org.uk>
Date: Wed, 3 Oct 2012 22:45:54 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Kay Sievers <kay@...y.org>
Cc: Greg KH <gregkh@...uxfoundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Al Viro <viro@...iv.linux.org.uk>,
Mauro Carvalho Chehab <mchehab@...hat.com>,
Ming Lei <ming.lei@...onical.com>,
Lennart Poettering <lennart@...ttering.net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kay Sievers <kay@...hat.com>,
Linux Media Mailing List <linux-media@...r.kernel.org>,
Michael Krufky <mkrufky@...uxtv.org>,
Ivan Kalvachev <ikalvachev@...il.com>
Subject: Re: udev breakages - was: Re: Need of an ".async_probe()" type of
callback at driver's core - Was: Re: [PATCH] [media] drxk: change it to use
request_firmware_nowait()
On Wed, 3 Oct 2012 23:18:06 +0200
Kay Sievers <kay@...y.org> wrote:
> On Wed, Oct 3, 2012 at 11:05 PM, Greg KH <gregkh@...uxfoundation.org> wrote:
>
> > As for the firmware path, maybe we should
> > change that to be modified by userspace (much like /sbin/hotplug was) in
> > a proc file so that distros can override the location if they need to.
>
> If that's needed, a CONFIG_FIRMWARE_PATH= with the array of locations
> would probably be sufficient.
The current system permits firmware to be served by a daemon, or even
assembled on the fly from parts. You break that for one.
Just fix udev, and if you can't fix it someone please just fork the last
working one.
Alan
--
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