From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Smirl Date: Sun, 20 Mar 2005 16:47:36 +0000 Subject: Re: Rework of request firmware Message-Id: <9e47339105032008473fcc362b@mail.gmail.com> List-Id: References: <9e473391050319200625032789@mail.gmail.com> In-Reply-To: <9e473391050319200625032789@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Sun, 20 Mar 2005 14:37:16 +0100, Kay Sievers wrote: > I still would like to see clearly defined list of requirements for: > o async userspace data-requests into the kernel > o async userspace configuration-requests from the kernel Here's another model that might be more general... accept_user_data() -- adds the data/status attributes to the device sysfs entry request_helper(completion, environment string) -- causes ACTION=helper, the environment string is added onto the normal environment for an event from this device class. Only async version. In the completion routine... release_user_data() -- deletes the attributes, frees the data This model addresses both the need to receive data and run helpers that don't need data. -- 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_id396&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