From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: event sequencing
Date: Sat, 26 Feb 2005 18:28:10 +0000 [thread overview]
Message-ID: <1109442490.7400.91.camel@localhost.localdomain> (raw)
In-Reply-To: <9e473391050225081838f673c7@mail.gmail.com>
On Sat, 2005-02-26 at 12:34 -0500, Jon Smirl wrote:
>On Sat, 26 Feb 2005 14:11:08 +0100, Kay Sievers <kay.sievers@vrfy.org> wrote:
>> Stuff like HAL heavily depends on that as it needs to get the initial
>> state of all devices at startup to present this to applications. But if
>> there is any other way to get that without sysfs, it would work too,
>> sure.
>
>I do have somewhat of a race issue.
>
>1) receive hardware interrupt of monitor change
>2) empty the list of valid modes in sysfs
>3) generate hotplug event to run userspace helper
>4) userspace helper sets in new mode list
>5) driver generates HAL event
>
>X could have picked a mode from the modelist before #1
>Then tried to set it between #1 and #4
>In this case X will get an error about invalid mode
>That should cause a popup that tells the user to try again
>while that popup is up the HAL event occurs indicating a new mode list
>is available
>This needs to be sorted out so that the contents of the mode selection
>dialog update
Yeah, this happens with other devices too and I don't see it as a big
problem as long as is fails and the caller get an error back.
>There need to be two events:
>MODELIST_CHANGE
>MODE_CHANGE
>
>MODE_CHANGE occurs if you are in an xterm and set a new mode via the
>command line. X needs to know in order to fix the display.
Are the list and the current state available as device attributes in
sysfs? So you may just send a KOBJ_CHANGE event for that specific
attributes with the kobject_uevent() which can have an attribute passed
down which is appended to the devpath of the device.
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-02-26 18:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-25 16:18 event sequencing Jon Smirl
2005-02-25 16:53 ` Kay Sievers
2005-02-25 21:56 ` Jon Smirl
2005-02-26 0:16 ` Jon Smirl
2005-02-26 0:46 ` Kay Sievers
2005-02-26 1:18 ` Jon Smirl
2005-02-26 3:27 ` Greg KH
2005-02-26 3:29 ` Greg KH
2005-02-26 3:43 ` Kay Sievers
2005-02-26 3:58 ` Greg KH
2005-02-26 5:08 ` Kay Sievers
2005-02-26 5:35 ` Greg KH
2005-02-26 6:25 ` Jon Smirl
2005-02-26 13:11 ` Kay Sievers
2005-02-26 14:00 ` Kay Sievers
2005-02-26 17:34 ` Jon Smirl
2005-02-26 17:37 ` Jon Smirl
2005-02-26 18:28 ` Kay Sievers [this message]
2005-02-26 19:17 ` Jon Smirl
2005-02-26 19:41 ` Kay Sievers
2005-02-27 0:27 ` Jon Smirl
2005-02-28 4:53 ` Jon Smirl
2005-02-28 11:25 ` Kay Sievers
2005-02-28 19:07 ` Jon Smirl
2005-02-28 19:51 ` Greg KH
2005-02-28 19:52 ` Greg KH
2005-02-28 19:56 ` Greg KH
2005-02-28 21:13 ` Jon Smirl
2005-03-01 8:01 ` Greg KH
2005-03-01 8:30 ` Jon Smirl
2005-03-01 8:41 ` 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=1109442490.7400.91.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).