[PATCH] add TIMEOUT to firmware_class hotplug event

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.

Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

diff --git a/drivers/base/firmware_class.c b/drivers/base/firmware_class.c
index 26c9464af80af79583b42c37925194098e4e9dc3..97fe13f7f07c85d6fa2d07efd3f04afab932ec46 100644 (file)
--- a/drivers/base/firmware_class.c
+++ b/drivers/base/firmware_class.c
@@ -102,6 +102,9 @@ firmware_class_hotplug(struct class_device *class_dev, char **envp,
        if (add_hotplug_env_var(envp, num_envp, &i, buffer, buffer_size, &len,
                        "FIRMWARE=%s", fw_priv->fw_id))
                return -ENOMEM;
+       if (add_hotplug_env_var(envp, num_envp, &i, buffer, buffer_size, &len,
+                       "TIMEOUT=%i", loading_timeout))
+               return -ENOMEM;
 
        envp[i] = NULL;