Re: event sequencing

[Kay Sievers <kay.sievers@vrfy.org>]

[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]

On Fri, 2005-02-25 at 11:18 -0500, Jon Smirl wrote:
>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.

Don't use that function. It is only for the driver core. It will execute
a usermode_helper which is not the way to do new stuff. Use the netlink
events for that: If your application is some low-level stuff, listen
directly to uevents:
  http://www.kernel.org/pub/linux/utils/kernel/hotplug/uevent_listen.c

or if it's desktop stuff, add support to HAL for it.

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

Record the events with something like the attached script placed as:
  /etc/hotplug.d/default/00-log.hotplug

and post the result here, if you don't see what's going wrong.

Good luck,
Kay

[-- Attachment #2: 00-log.hotplug --]
[-- Type: application/x-shellscript, Size: 140 bytes --]