Re: event sequencing

[Jon Smirl <jonsmirl@gmail.com>]

On Sat, 26 Feb 2005 20:41:16 +0100, Kay Sievers <kay.sievers@vrfy.org> wrote:
> >That leaves my private monitor change interrupt event in
> >kobject_hotplug(&info->class_device->kobj, KOBJ_MOUNT); It doesn't
> >make sense to remove/add the framebuffer device just because the
> >monitor attached changed. Remove/add would force X to close the
> >framebuffer device and lose all of the state loaded inside of it (font
> >cache, textures if DRM is running) .
> 
> For exactly that reason I was asking if it wouldn't be better to create
> a child for the monitor, which can appear and disappear and can hold the
> DDC data you get from the physical monitor.

I just spent half a day trying to get this to work. class_device can
not make child nodes (class/graphics/fb0/monitor) in it's current
form. It forces the node to appear in class/graphics/monitor.

I tried building the monitor entry directly off from kobjects but I
need all of the hotplug support from class_device and most of the
functions are declared static.

I also tried this:
	class_device = kmalloc(sizeof(*class_device), GFP_KERNEL);
	memset(class_device, 0, sizeof(*class_device));
	class_device->kobj.parent = &info->class_device->kobj;
	strncpy(class_device->class_id, "monitor", sizeof(class_device->class_id));
	ret = class_device_register(class_device);

But class_device_register will trap in class_device_add_attrs because
'class' is null. If I set class the node will appear in
class/graphics/monitor

I can try and fix up class_device but for this to work Greg is going
to need to change class_device to officially support child nodes.

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