[xrandr] Only use the current information when setting modes

Before we change the state (e.g. adding a mode or applying one to an output), we query the screen resources for the right identifiers. This should only use the current information rather than force a reprobe on all hardware - not only can that reprobe be very slow (e.g. EDID timeouts on the order

Re: [xrandr] Only use the current information when setting modes

On Sun, Sep 13, 2015 at 12:14:57PM +0100, Chris Wilson wrote: > On Sun, Sep 13, 2015 at 01:08:11PM +0200, Mark Kettenis wrote: > > Seems you already can get the behaviour you want by specifying > > --current. Whereas there is no convenient way to force a probe, other > > than an explicit query? >

Re: [xrandr] Only use the current information when setting modes

> From: Chris Wilson > Date: Sun, 13 Sep 2015 11:40:37 +0100 > > Before we change the state (e.g. adding a mode or applying one to an > output), we query the screen resources for the right identifiers. This > should only use the current information rather than force a

Re: [xrandr] Only use the current information when setting modes

On Sun, Sep 13, 2015 at 01:08:11PM +0200, Mark Kettenis wrote: > > From: Chris Wilson > > Date: Sun, 13 Sep 2015 11:40:37 +0100 > > > > Before we change the state (e.g. adding a mode or applying one to an > > output), we query the screen resources for the right

Re: [xrandr] Only use the current information when setting modes

On Sun, Sep 13, 2015 at 08:01:46PM +0200, Mark Kettenis wrote: > > Date: Sun, 13 Sep 2015 12:14:57 +0100 > > From: Chris Wilson > > > > On Sun, Sep 13, 2015 at 01:08:11PM +0200, Mark Kettenis wrote: > > > > From: Chris Wilson > > > > Date:

Re: [xrandr] Only use the current information when setting modes

> Date: Sun, 13 Sep 2015 12:14:57 +0100 > From: Chris Wilson > > On Sun, Sep 13, 2015 at 01:08:11PM +0200, Mark Kettenis wrote: > > > From: Chris Wilson > > > Date: Sun, 13 Sep 2015 11:40:37 +0100 > > > > > > Before we change the state (e.g.