https://bugs.freedesktop.org/show_bug.cgi?id=38030
--- Comment #26 from Alex Deucher <[email protected]> 2011-07-12 08:19:41 PDT --- I think what's happening is that when the monitor scans inputs, it generates connect/disconnect signals on the hotplug pin when it switches to/from the input in use. This generates an interrupt which in turn sends a hotplug event to userspace. The X driver then gets the event and assumes the monitor is plugged/unplugged and attempts to turn the output on/off. I'm not entirely sure how the windows driver handles it. I suspect what we want to do is look at the rate at which plug/unplug interrupts are generated and wait to see how much time has elapsed since the previous event before actually generating an event for userspace. If you are interested, the evergreen irq handler is evergreen_irq_process() in evergreen.c and the hotplug work handler is radeon_hotplug_work_func() in radeon_irq_kms.c in the kernel. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ xorg-driver-ati mailing list [email protected] http://lists.x.org/mailman/listinfo/xorg-driver-ati
