xf86-video-vmware: Changes to 'vmwgfx_branch'

[Thomas Hellstrom]

 vmwgfx/vmwgfx_driver.c |   48 ++++++++++++++++---
 vmwgfx/vmwgfx_driver.h |    5 ++
 vmwgfx/vmwgfx_saa.c    |  119 +++++++++++++++++++++++++++++++++++--------------
 vmwgfx/vmwgfx_saa.h    |    4 +
 4 files changed, 134 insertions(+), 42 deletions(-)

New commits:
commit aff799d007c8383321213ad177e5a9deec2b3978
Author: Thomas Hellstrom <thellstrom at vmware.com>
Date:   Tue Nov 1 15:39:07 2011 +0100

    vmwgfx: Add an option to use a scanout surface
    
    With this option enabled, we compose all contents (both sw and hw) in
    the guest before presenting it. Just like the old xorg state tracker did
    when 3D was enabled. It's not as bad as the old xorg state tracker was for
    interactivity, but there's a small but noticeable lag when moving windows.
    
    It's mainly intended for testing purposes, like testing the surface
    dirty paths in the kernel module.
    
    Signed-off-by: Thomas Hellstrom <thellstrom at vmware.com>
    Reviewed-by: Jakob Bornecrantz <jakob at vmware.com>

commit 5137e8736edfab1aaebef4046baab37361584b2e
Author: Thomas Hellstrom <thellstrom at vmware.com>
Date:   Tue Nov 1 09:59:18 2011 +0100

    vmwgfx: Be correct when setting up damage tracking
    
    When setting up damage tracking, previously the code would guess wether
    sw or hw was currently dirty. The caller always have that information,
    so pass it to the damage tracking setup function.
    
    Signed-off-by: Thomas Hellstrom <thellstrom at vmware.com>
    Reviewed-by: Jakob Bornecrantz <jakob at vmware.com>

commit ed7bba3cda4b454eec771d3bf0ebed4fd998a82a
Author: Thomas Hellstrom <thellstrom at vmware.com>
Date:   Tue Nov 1 08:38:52 2011 +0100

    vmwgfx: Add an option for direct presents
    
    With this option set to true, accelerated copies to a scanout pixmap will
    be performed as hardware presents instead of copies to an intermediate
    3D surface backing the scanout pixmap, followed by a present.
    
    Depending on the application this might be a performance boost, but since
    it might trigger device software readbacks in other situations, for example
    dri2 copy front->fake_front, it might be a performance hog in other situations,
    so disable it by default. (Before this commit it was enabled by default).
    
    Signed-off-by: Thomas Hellstrom <thellstrom at vmware.com>
    Reviewed-by: Jakob Bornecrantz <jakob at vmware.com>