From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Sun, 20 Mar 2005 18:00:01 +0000 Subject: Re: Rework of request firmware Message-Id: <1111341601.21516.96.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 18:39 +0100, Kay Sievers wrote: > On Sun, 2005-03-20 at 12:19 -0500, David Zeuthen wrote: > > 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. > > We need to cover the early boot and initramfs anyway and therefore need > to fork something here. But that will be tunneled > through /proc/sys/kernel/hotplug, so if userspace has taken over the > hotplug events, it can switch that off and get everything from the > netlink events. > > > 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. > > Hmm, we will need a sane way to propagate errors form the kernel to > userspace anyway. Currently there is nothing like that available and I > really see the need for a more generic solution then reading dmesg. :) > > Remember the block I/O errors we wanted to send over netlink. We need > something more generic here, that is able to relay classes of errors and > error-data to userspace. That errors would be nice to catch with HAL and > give them a sane context to be handled in userspace. > > Everything else will just be another dirty hack, I think. Last year Dan Stekloff started: "A list of actionable error events that includes the current message string, possible causes, and possible actions..." http://linux-diag.sourceforge.net/first_failure/FirstFailure.html We may work on something like this and add support for it to HAL. Any ideas to let that happen or just start with something "small", but in that direction? 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