linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: event sequencing
Date: Fri, 25 Feb 2005 16:18:33 +0000	[thread overview]
Message-ID: <9e473391050225081838f673c7@mail.gmail.com> (raw)

I working on adding hotplug monitor change detection code to some
framebuffer drivers. I having trouble with event sequencing.

In my probe function I do a class_simple_device_add() to create the
class entry. Later in the probe function I do
kobject_hotplug(&info->class_device->kobj, KOBJ_MOUNT); to indicate a
monitor change.

I'm receiving the MOUNT event before the ADD one. How can I control the order?

Even in cases where MOUNT comes after ADD udev has not built my device
nodes yet. My MOUNT app needs to use the device node. This is my
bigger problem.

I'm using RH FC3 but this needs to work on all distributions when finished.

-- 
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

             reply	other threads:[~2005-02-25 16:18 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-25 16:18 Jon Smirl [this message]
2005-02-25 16:53 ` event sequencing 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
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=9e473391050225081838f673c7@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).