Re: event sequencing

[Jon Smirl <jonsmirl@gmail.com>]

On Tue, 1 Mar 2005 00:01:43 -0800, Greg KH <greg@kroah.com> wrote:
> Anyway, let's do this properly, it's on the todo list, and will get done
> in a few weeks.

I'll add notes in my fbdev patches that the class_device child code is
temporary and waiting on a real fix.

I'm changing the driver design to assume that I can do this. This
eliminates the need for a MODE_CHANGE event type. It makes more sense
looking at the sysfs entries too.

sys
  class
    graphics
      fb0(mode_list, mode)
        monitor(edid)
      fb1(mode_list, mode)
        monitor(edid)

If you unplug the monitor the monitor directory disappears and the
mode_list goes empty. The framebuffer is still there. Plug is back in
and the monitor directory is created and we get the hotplug event.
Hotplug event rebuilds the valid mode_list.

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