xf86-video-vmware: Changes to 'master'

[Thomas Hellstrom]

 configure.ac           |    2 +-
 vmwgfx/vmwgfx_dri2.c   |    9 +++++++--
 vmwgfx/vmwgfx_driver.c |   12 ------------
 3 files changed, 8 insertions(+), 15 deletions(-)

New commits:
commit d5550b7f8375c3d9003731578c1570e014577348
Author: Thomas Hellstrom <thellstrom at vmware.com>
Date:   Wed Apr 20 20:10:41 2016 +0200

    vmware/vmwgfx: Support multiple dri driver names
    
    Support sending multiple driver names and dri2 INFOREC v4.
    
    Signed-off-by: Thomas Hellstrom <thellstrom at vmware.com>
    Reviewed-by: Brian Paul <brianp at vmware.com>

commit 0bcd4df1843f00f8e8507750401ec2a2a29330dc
Author: Thomas Hellstrom <thellstrom at vmware.com>
Date:   Thu Feb 11 09:45:58 2016 +0100

    vmware: Bump minor to signal availability of new features
    
    While this may never be an official release, bump minor to enable the
    new resolutionKMS functionality. This signals the availability of
    autolayout and resolutionKMS support.
    
    Signed-off-by: Thomas Hellstrom <thellstrom at vmware.com>
    Reviewed-by: Brian Paul <brianp at vmware.com>

commit 5036e9d11a899d831b1471f64132eefcf459b222
Author: Thomas Hellstrom <thellstrom at vmware.com>
Date:   Thu Feb 11 09:40:55 2016 +0100

    vmware/vmwgfx: Don't require screen objects to run
    
    Using the vmwgfx ldu backend works just as fine except that we're limited
    to implicit layout placement.
    
    With this test on, we may end up in the odd situation that the vmwgfx kernel
    module and the vwmare legacy Xorg driver are enabled simultaneously, and that
    is an unsupported configuration. It will also break resolutionKMS which will
    be enabled based on vmwgfx version but should be disabled since the legacy
    Xorg driver runs...
    
    Signed-off-by: Thomas Hellstrom <thellstrom at vmware.com>
    Reviewed-by: Brian Paul <brianp at vmware.com>