From: Jon Smirl <jonsmirl@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Rework of request firmware
Date: Tue, 22 Mar 2005 03:06:30 +0000 [thread overview]
Message-ID: <9e4733910503211906211b7778@mail.gmail.com> (raw)
In-Reply-To: <9e473391050319200625032789@mail.gmail.com>
On Tue, 22 Mar 2005 03:25:05 +0100, Kay Sievers <kay.sievers@vrfy.org> wrote:
> This way we can replay or cancel events at any time if something goes
> wrong. We would get a generic transaction model for the kernel to
> request a configuration action from userspace like copying a firmware
> image, setup a device or run any other userspace helper.
>
> How does that sound? Can this work?
That's what I was trying to get at. It's the abort of the event that
causes problems. The better model is that the event stays active until
it is satisfied -- there is no way to automatically abort it. If the
event has not been satisfied by module exit time it just gets cleaned
up.
It would be convenient to have a sysfs variable on an event like
'replay'. If I set 'replay' to 1 the event will get regenerated to
/sbin/hotplug. After I fix things I could manually retrigger the
event and it would run in the hotplug execution environment. You might
not even need to be root to trigger a replay.
Timeout is still useful. Timeout tells the system to generate a user
message saying that the device is stuck. But timeout should not abort
the event.
What about a universal driver model for this? Right now we have
probe(). Should we add post()? If post() is null just call probe(). If
the driver has a post() function call it instead. The completion event
would then call probe(). probe() could still fail and the driver would
not be activated.
Doing it in the driver layer makes this process standard. Now we can
add a uniform device attribute like status. status=offline,
status=posting, status=online.
You could probably cancel an event. Canceling an event would remove it
from sysfs and make sure probe() never gets called. Status would stay
at offline. The only way to reactivate the device would be to remove
the driver. I don't think we need cancel but if it is there it would
be a user controlled action.
--
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_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-22 3:06 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
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 [this message]
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=9e4733910503211906211b7778@mail.gmail.com \
--to=jonsmirl@gmail.com \
--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).