Re: Rework of request firmware

[Jon Smirl <jonsmirl@gmail.com>]

On Sun, 20 Mar 2005 18:52:12 +0100, Kay Sievers <kay.sievers@vrfy.org> wrote:
> o Emit events for devices to request a userspace-action on that
>   device like copying data into a sysfs file or run a userspace
>   program to setup this device.
>   -Is this limited to physical devices?

Do virtual devices have a 'struct device' too? It could be generalized
even more to work off from a kobject instead of device.

> o Events can happen anytime, not only on device creation time.

true, I also have a problem with monitor hotplug needing to run a user
space helper.

> o We need an efficient way for the dumb hotplug-multiplexer to recognize
>   that kind of events to prevent the execution of just another script
>   for every hotplug event.
> 
> o The events should act asynchronously and the kernel should detect or is
>   to be notified that the request has finished.
>   -Do we need any timeout here?

Timeout may the source of a problem. If user space is messed up and
the event doesn't get run correctly the timeout happens. Timeout
removes the attributes and reports an error. Now the user fixes
whatever was wrong in user space. How do they restart the event?

It might be better to get rid of the timeouts and just leave
everything in place. Then you could just rerun the user space app that
failed.

> o For data-loading-requests like the firmware case we need to be able to
>   request more than one file for one single device.

I would just do these sequentially. If everything is working the loads
happen quickly.

> o The DEVPATH of the request should be the device itself, that asks for data
>   or setup.
>   -Should the requests create a own child at the device directory or just
>    attributes there?

Doesn't creating a directory cause a hotplug add event? There are only
two attributes: status and data. We could just pick standard names for
them. Alternatively those two attributes could always be present in
the device directory reporting a status of inactive.

>   -How should attributes be named if we have multiple request for the
>    same device?

I would not allow this

-- 
Jon Smirl
jonsmirl@gmail.com


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel