<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - [regression] recent ABI changes in xorg-video-intel (intel_drv.so) breaks dual-head XBMC" href="https://bugs.freedesktop.org/show_bug.cgi?id=82619#c59">Comment # 59</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - [regression] recent ABI changes in xorg-video-intel (intel_drv.so) breaks dual-head XBMC" href="https://bugs.freedesktop.org/show_bug.cgi?id=82619">bug 82619</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>XRandR has two calls: XRRGetScreenResources() and XRRGetScreenResourcesCurrent(). The first forces the Xserver and kernel do a laborious and expensive hardware probe to see exactly what is attached. The second, added later when it was realised just how stupid that was given hardware and kernels that do autodetection of new hardware, just queries the kernel for the current set of outputs and their configuration. xrandr --current uses XRRGetScreenResourcesCurrent(), and does not imply only querying the current output. It is the right call to use after receiving a hotplug notification after a XRRNotifyEvent (which is X telling you that the current configuration has indeed changed). Without --current, the call can take up to a few seconds to complete and cause the displays to flash (though typically with good hardware only 0.2-0.5s). Do not use this unless you know exactly what you are doing at the hardware level.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>