xf86-video-vmware: Changes to 'vmwgfx_branch'

[Thomas Hellstrom]

 vmwgfx/vmwgfx_driver.c |    1 
 vmwgfx/vmwgfx_saa.c    |   94 ++++++++++++++++++++++++++++++++-----------------
 2 files changed, 64 insertions(+), 31 deletions(-)

New commits:
commit 70487eee975c63b5ed1492927bbc661425278276
Author: Thomas Hellstrom <thellstrom at vmware.com>
Date:   Wed Nov 9 11:34:16 2011 +0100

    vmwgfx: Make sure we don't render when VT switched
    
    When compiz is enabled, we may try to DMA sw rendered contents of dri2
    drawables to surfaces while VT switched. I'm not sure how this could be
    happening, but queue the DMA until the next block handler.
    
    Signed-off-by: Thomas Hellstrom <thellstrom at vmware.com>
    Reviewed-by: Alan Hourihane <alanh at vmware.com>

commit e1810e0b09e07bdab05a57fdef74450a507e9dfa
Author: Thomas Hellstrom <thellstrom at vmware.com>
Date:   Tue Nov 8 15:28:40 2011 +0100

    vmwgfx: Fix rendering errors when rotating / unrotating a screen.
    
    The dirty trackers weren't correctly translated to
    pending presents / updates when a pixmap was bound as a scanout.
    
    Signed-off-by: Thomas Hellstrom <thellstrom at vmware.com>
    Reviewed-by: Jakob Bornecrants <jakob at vmware.com>

commit d0b493d67afd1b5e8c8397c7938752ecd56c91ba
Author: Thomas Hellstrom <thellstrom at vmware.com>
Date:   Tue Nov 8 14:49:36 2011 +0100

    vmwgfx: A number of damage fixes
    
    A damage tracker was sometimes attached to a pixmap in the middle of an
    operation. That meant that damage was never registered for that operation
    which caused dirty-tracking to fail. Instead, add a damage tracker as
    soon as we have storage attached to the pixmap.
    
    Also, when a pixmap was resized, the dirty region trackers could become
    stale, and cause DMA operation extending outside of the pixmap with
    server crashes as a result. This commit fixes that.
    
    Signed-off-by: Thomas Hellstrom <thellstrom at vmware.com>
    Reviewed-by: Jakob Bornecrantz <jakob at vmware.com>