xf86-video-vmware: Changes to 'master'

[Thomas Hellstrom]

 vmwgfx/vmwgfx_crtc.c     |   23 ++++++++++++++++++++++-
 vmwgfx/vmwgfx_driver.c   |   26 ++++++++++++++++++++------
 vmwgfx/vmwgfx_driver.h   |    1 +
 vmwgfx/vmwgfx_drm.h      |    1 +
 vmwgfx/vmwgfx_saa.c      |   15 +++++++++++----
 vmwgfx/vmwgfx_saa.h      |    7 +++++--
 vmwgfx/vmwgfx_saa_priv.h |    1 +
 7 files changed, 61 insertions(+), 13 deletions(-)

New commits:
commit 1e443c4717a8b107c0c9283e222482703ac0f358
Author: Thomas Hellstrom <thellstrom at vmware.com>
Date:   Wed Feb 25 01:51:11 2015 -0800

    vmware/vmwgfx: Try to use only_hw_present semantics if screen targets are enabled
    
    If screen targets are enabled and there is a reasonable chance that the vmwgfx
    drm driver can use the surface backing a pixmap as a screen target surface,
    then make that surface a modesetting framebuffer rather than the corresponding
    DMA buffer. In practice this applies when we start scanning out from the
    origin (0,0) of the pixmap. However, we would also like to apply the constraint
    that the scanout area is the entire pixmap, since that is the constraint used
    by the drm driver, but that would currently require drm framebuffer
    reallocations and possible flicker, so disable that for now. The drm driver
    will correctly handle the possibly oversized surface handed to it anyway, and
    the cost we pay for this is an extra hardware copy of the dirtied area when
    doing a software update of the scanout.
    
    Signed-off-by: Thomas Hellstrom <thellstrom at vmware.com>
    Reviewed-by: Sinclair Yeh <syeh at vmware.com>