From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Rework of request firmware
Date: Sun, 20 Mar 2005 17:39:46 +0000 [thread overview]
Message-ID: <1111340386.21516.74.camel@localhost.localdomain> (raw)
In-Reply-To: <9e473391050319200625032789@mail.gmail.com>
On Sun, 2005-03-20 at 12:19 -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.
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.
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_id\x14396&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
next prev parent reply other threads:[~2005-03-20 17:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-20 4:06 Rework of request firmware Jon Smirl
2005-03-20 13:37 ` Kay Sievers
2005-03-20 15:35 ` Jon Smirl
2005-03-20 16:47 ` Jon Smirl
2005-03-20 17:16 ` Kay Sievers
2005-03-20 17:19 ` David Zeuthen
2005-03-20 17:39 ` Kay Sievers [this message]
2005-03-20 17:52 ` Kay Sievers
2005-03-20 17:52 ` Darren Salt
2005-03-20 18:00 ` Kay Sievers
2005-03-20 18:24 ` Jon Smirl
2005-03-20 19:02 ` Jon Smirl
2005-03-20 19:17 ` Kay Sievers
2005-03-20 19:27 ` Kay Sievers
2005-03-20 19:50 ` Jon Smirl
2005-03-20 20:25 ` Kay Sievers
2005-03-20 20:39 ` Jon Smirl
2005-03-21 2:37 ` Kay Sievers
2005-03-22 0:29 ` Linas Vepstas
2005-03-22 2:25 ` Kay Sievers
2005-03-22 3:06 ` Jon Smirl
2005-03-22 8:27 ` Roman Kagan
2005-03-22 10:45 ` Kay Sievers
2005-03-22 10:55 ` Kay Sievers
2005-03-22 14:37 ` Jon Smirl
2005-03-22 17:53 ` Linas Vepstas
2005-03-22 18:09 ` Linas Vepstas
2005-03-22 18:43 ` Jon Smirl
2005-03-23 1:08 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1111340386.21516.74.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).