Re: [PATCH] add TIMEOUT to firmware_class hotplug event

[Greg KH <greg@kroah.com>]

On Thu, Mar 17, 2005 at 12:07:55PM +0100, Kay Sievers wrote:
> On Wed, 2005-03-16 at 21:46 -0800, Greg KH wrote:
> > On Thu, Mar 17, 2005 at 03:34:31AM +0100, Kay Sievers wrote:
> > > On Tue, 2005-03-15 at 09:25 +0100, Hannes Reinecke wrote:
> > > > The current implementation of the firmware class breaks a fundamental
> > > > assumption in udevd: that the physical device can be initialised fully
> > > > prior to executing the next event for that device.
> > > 
> > > Here we add a TIMEOUT value to the hotplug environment of the firmware
> > > requesting event. I will adapt udevd not to wait for anything else, if
> > > it finds a TIMEOUT key.
> > 
> > Can't you just trigger off of the FIRMWARE variable instead?
> 
> Sure, that will work too. I just thought it would be nice to give
> userspace a hint about the event behavior the kernel expects, instead of
> adding an exception to the udevd event management?

Hm, so by adding the TIMEOUT value, we are telling userspace that we
better act on this operation soon, right?  That's a special case too :)

Anyway, sure, this is fine, I'll go add this to the driver-bk tree.

thanks,

greg k-h