vmwgfx-xorg: Avoid enabling unwanted outputs in initial configuration
authorThomas Hellstrom <thellstrom@vmware.com>
Tue, 30 Aug 2011 10:22:53 +0000 (12:22 +0200)
committerThomas Hellstrom <thellstrom@vmware.com>
Wed, 31 Aug 2011 12:39:21 +0000 (14:39 +0200)
commit3c2f9cc43f7d36952e78d10d224da0ba68ecefea
treec4b31562faf98ca2b2408c7a4d086983b0af3020
parentf17abaa926fdbedab1e6236e109fa746fcc2320b
vmwgfx-xorg: Avoid enabling unwanted outputs in initial configuration

Add a hack so that we avoid enabling all connected outputs during the
initial configuration. On older X servers they would be enabled as cloned,
which didn't really cause any problem, but on later X servers they would
initially be enabled next to eachother which looks odd.

A RandR call will still show the disabled outputs as connected, and if there
is a monitor section in the config file for the output in question,
it will also have a connected status, so that it may be explicitly enabled
or disabled from a config file.

Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
Reviewed-by: Jakob Bornecrantz <jakob@vmware.com>
vmwgfx/vmwgfx_driver.c
vmwgfx/vmwgfx_driver.h
vmwgfx/vmwgfx_output.c