From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Sun, 20 Mar 2005 19:27:24 +0000 Subject: Re: Rework of request firmware Message-Id: <1111346844.23995.50.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 14:02 -0500, Jon Smirl wrote: > On Sun, 20 Mar 2005 12:19:38 -0500, David Zeuthen wrote: > > > > Hey Kay, > > > > On Sun, 2005-03-20 at 14:37 +0100, Kay Sievers wrote: > > > before we start hacking on it. The current request_firmware() is a > > > not-so-nice example for doing it that way. All that stuff needs to play > > > with hotplug, initramfs/bootup, suspend/resume. And we should come up > > > with something that fits _all_ the needs and move the current > > > request_firmware-users over to it. > > > > On that topic, one of the things I'd like a future scheme to do is not > > only emitting the request_firmware() event, but also emitting events > > like someone_uploaded_firmware() and timeout_waiting_for_firmware(). > > Plus some state in sysfs to keep track of the state. All but > > request_firmware() probably don't need hotplug events; kobject_uevents > > would be fine for me, since I'd want some daemon to listen to it anyway. > > > > All that probably needs to be changed to fit in with what Jon is doing; > > the idea here is that we want to notify the user, in the desktop > > session, that the firmware/initialization needed is not available. Then > > the user can take appropriate action. > > Instead of deleting the attributes and returning to the user at > timeout expiration, maybe we should leave the attributes in place and > generate an event that the use can see. But if the config event does not know how to fulfill the request, it may cancel the operation by triggering the sysfs attribute. And that will lead to a failing device initialization which is an event that userspace is interested in. Again, the way such errors are send to userspace in a sane way, needs to be solved for this to happen ... 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