From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Sun, 20 Mar 2005 17:52:12 +0000 Subject: Re: Rework of request firmware Message-Id: <1111341133.21516.88.camel@localhost.localdomain> 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, 2005-03-20 at 11:47 -0500, Jon Smirl wrote: > 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. Ok, let's collect what's need to get that: 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? o Events can happen anytime, no only on device creation time. 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? o For data-loading-requests like the firmware case we need to be able to request more than one file for one single device. 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? -How should attributes be named if we have multiple request for the same device? Thanks, Kay ------------------------------------------------------- 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