summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2023-10-07gitlab CI: ensure libtool is installed in build containerHEADmasterAlan Coopersmith1-3/+3
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
2023-02-09gitlab CI: stop requiring Signed-off-by in commitsAlan Coopersmith1-2/+2
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
2023-01-24Bump the version number to 13.4.0xf86-video-vmware-13.4.0Peter Hutterer1-1/+1
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2022-09-29Man page syntax fix.Ville Skyttä1-1/+1
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
2022-09-29Spelling fixes.Ville Skyttä5-5/+5
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
2022-08-23Build xz tarballs instead of bzip2Alan Coopersmith1-1/+1
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
2022-07-18gitlab CI: add a basic build testAlan Coopersmith1-0/+98
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
2022-06-21Garbled XvPutImage output for FOURCC_YV12 when using 3D-accel-texture adaptorMartin Krastev1-3/+10
A helper for the PutImage callback in adaptor 'XA G3D Textured Video' was not taking into account the source data pitches for YV12 format, resulting in garbled frames for misaligned frame widths. Issue reported by Doug Brown. This patch is based off the patch proposed by Doug. Repro of the original issue: gst-launch-1.0 videotestsrc ! video/x-raw,format=YV12,width=449,height=240 ! xvimagesink Reported-by: Doug Brown <doug@schmorgal.com> Signed-off-by: Martin Krastev <krastevm@vmware.com> Reviewed-by: Zack Rusin <zackr@vmware.com>
2022-05-08vmwgfx: fix missing array notation Rudi Heitbaum1-1/+1
Fixes error identified by gcc-12.1.0 compiler make CC libvmwgfx_la-vmwgfx_tex_video.lo vmwgfx_tex_video.c: In function 'stop_video': vmwgfx_tex_video.c:240:20: error: the comparison will always evaluate as 'true' for the address of 'yuv' will never be NULL [-Werror=address] 240 | if (priv->yuv[i]) { | ^~~~
2021-11-30vmwgfx: Change header inclusion order to avoid xorg headers catching stdbool.hMartin Krastev2-4/+4
libdrm commit e641e2a632d779f638ac2ba983b9fceb20b3fac4 added stdbool.h to the library headers which conflicts with xorg headers. Signed-off-by: Martin Krastev <krastevm@vmware.com> Reviewed-by: Zack Rusin <zackr@vmware.com> Signed-off-by: Zack Rusin <zackr@vmware.com>
2019-01-28vmwgfx: Unify style in scanout_update and present functionsThomas Hellstrom1-16/+25
Since the functions are pretty similar, Make them look more similar in terms of memory allocation methods and variable names Reported-by: Brian Paul <brianp@vmware.com> Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Brian Paul <brianp@vmware.com>
2019-01-28vmwgfx: Limit the number of cliprects in a drm present_readback command v3Thomas Hellstrom1-29/+42
The drm present readback command number of cliprects should not exceed DRM_MODE_FB_DIRTY_MAX_CLIPS. If that number is exceeded, split the command up. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Brian Paul <brianp@vmware.com> Reviewed-by: Deepak Rawat <drawat@vmware.com> #v1
2019-01-28vmwgfx: Limit the number of cliprects in a drm present command v3Thomas Hellstrom1-18/+27
The drm present command number of cliprects should not exceed DRM_MODE_FB_DIRTY_MAX_CLIPS. If that number is exceeded, split the command up. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Brian Paul <brianp@vmware.com> #v2 Reviewed-by: Deepak Rawat < drawat@vmware.com> #v1
2019-01-28vmwgfx: Limit the number of cliprects in a drm dirtyfb command v3Thomas Hellstrom2-14/+29
The drm dirtyfb command would error if the number of cliprects were larger than DRM_MODE_FB_DIRTY_MAX_CLIPS. If that number is exceeded, split the command up. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Brian Paul <brianp@vmware.com> #v2 Reviewed-by: Deepak Rawat <drawat@vmware.com> #v1
2019-01-28vmwgfx: Don't exceed the device command size limit v3Thomas Hellstrom2-69/+79
With a huge number of DMA clip rects we could exceed the device command buffer command size limit. Fix this by sending multiple DMA commands when we exceed the limit. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Brian Paul <brianp@vmware.com> Reviewed-by: Deepak Rawat <drawat@vmware.com> #v1
2018-11-29vmwgfx: Fix invalid memory accesses in CloseScreenThomas Hellstrom1-1/+4
Some of the CloseScreen callbacks were referencing XA objects so move the destruction of the XA state tracker to the end of drv_close_screen to avoid referencing freed resources. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Deepak Rawat <drawat@vmware.com>
2018-11-29saa: Make sure damage destruction happens at the correct locationThomas Hellstrom3-10/+75
Incorrect DestroyPixmap wrapping previously made the destruction of damage objects typically happen in damageDestroyPixmap(), leaving a dangling damage pointer in saa_destroy_pixmap() which was only cleared. However in some cases that caused us to leak damage objects. Rework saa initialization somewhat to make sure saa_destroy_pixmap happens before damageDestroyPixmap and destroy the damage object in saa_destroy_pixmap. Also add a damage object destruction notifier callback that clears the saa pixmap damage pointer should the damage object destruction accidentally happen elsewhere. This makes sure we don't leak damage objects. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Deepak Rawat <drawat@vmware.com>
2018-11-29vmwgfx: Use libdrm to obtain the drm device node name v2Thomas Hellstrom3-12/+51
We were relying on a linux-specific way to do this. Now that the code is used also on FreeBSD and there is functionality in libdrm to do this, Use that functionality. v2: Remove unused variable warning in the !VMWGFX_LIBDRM_DEVICENAME case. Co-authored-by: Johannes Lundberg <johalun0@gmail.com> Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Deepak Rawat <drawat@vmware.com> #v1
2018-11-28vmwgfx: Fix a memory leakThomas Hellstrom1-0/+1
We were leaking a pointer to a drm encoder. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Brian Paul <brianp@vmware.com>
2018-11-28vmwgfx: Fix XVideo memory leaksThomas Hellstrom4-22/+44
We were not properly freeing the port privates. In order to access those at CloseScreen time, don't free the adaptor pointers at XV screen init, but hold on to them until CloseScreen. Also properly free the new_adaptors pointer. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Brian Paul <brianp@vmware.com>
2018-11-12Remove obsolete B16 & B32 tags in struct definitionsAlan Coopersmith1-35/+35
They were defined as empty strings on all platforms except for the long unsupported Cray systems which needed to use bitfields to define any type smaller than 64-bits. Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com> Reviewed-by: Thomas Hellstrom <thellstrom@vmware.com>
2018-05-17Bump version number for releasexf86-video-vmware-13.3.0Thomas Hellstrom1-1/+1
Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Sinclair Yeh <syeh@vmware.com> Reviewed-by: Deepak Rawat <drawat@vmware.com>
2018-05-17Require at least XA version 2.4 to enable dri3Thomas Hellstrom1-1/+1
The XA version was bumped from 2.3 to 2.4 to signal that there were no significant correctness or performance regressions when running dri3 compared to dri2 on the vmware driver stack. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Brian Paul <brianp@vmware.com> Reviewed-by: Sinclair Yeh <syeh@vmware.com> Reviewed-by: Deepak Rawat <drawat@vmware.com>
2018-04-26vmwgfx: Clear the DRM mode before useThomas Hellstrom1-0/+1
Avoid sending partially uninitialized data to the kernel. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Brian Paul <brianp@vmware.com> Reviewed-by: Sinclair Yeh <syeh@vmware.com>
2018-03-14saa: Build compatibility with xserver 1.20Adam Jackson1-0/+4
fbGetRotatedPixmap went away with 24bpp support, just treat it as NULL and we'll do the right thing. Signed-off-by: Adam Jackson <ajax@redhat.com> Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
2018-02-20Fix a couple of shadowed declaration warningsThomas Hellstrom3-32/+32
In some enviroments, "index", "y1" and "y2" are defined globally causing warnings about shadowed declarations. Fix this. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Brian Paul <brianp@vmware.com>
2018-02-20Build fixesThomas Hellstrom4-3/+21
A couple of more build fixes for older X servers. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Sinclair Yeh <syeh@vmware.com>
2018-02-15vmwgfx: Fix server termination due to a mesa loader bugThomas Hellstrom1-0/+23
Some versions of the Gallium loader close our drm file descriptor if xa_tracker_create() fails (typically 2D VMs.) While this is mostly fixed everywhere, we implement a workaround to avoid tracking down the same bug again and again on those setups where this is not fixed in mesa. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Brian Paul <brianp@vmware.com> Reviewed-by: Sinclair Yeh <syeh@vmware.com> Reviewed-by: Deepak Rawat <drawat@vmware.com>
2018-02-15legacy: Silence a warning about an unused constantThomas Hellstrom1-0/+2
VMWAREBuildStr was only used in the !LIBPCIACCESS path. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Brian Paul <brianp@vmware.com> Reviewed-by: Sinclair Yeh <syeh@vmware.com> Reviewed-by: Deepak Rawat <drawat@vmware.com>
2018-02-15legacy: Avoid using the xf86[Un]blockSigio functionsThomas Hellstrom1-1/+19
They have been deprecated since mouse doesn't use SIGIO anymore. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Brian Paul <brianp@vmware.com> Reviewed-by: Sinclair Yeh <syeh@vmware.com> Reviewed-by: Deepak Rawat <drawat@vmware.com>
2018-02-15vmwgfx: Fix potential libudev include and link failuresThomas Hellstrom1-2/+2
We were not including the proper include- and link flags for libudev. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Brian Paul <brianp@vmware.com> Reviewed-by: Sinclair Yeh <syeh@vmware.com> Reviewed-by: Deepak Rawat <drawat@vmware.com>
2018-02-15Fix a number of compilation warningsThomas Hellstrom5-18/+55
There are a number of compilation warnings caused by const char pointers being either explicitly or implicitly cast to char pointers. There are a number of ABI differences that have hindered this so far, but make a new attempt using the common_compat.h defines. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Brian Paul <brianp@vmware.com> Reviewed-by: Sinclair Yeh <syeh@vmware.com> Reviewed-by: Deepak Rawat <drawat@vmware.com>
2018-02-15vmwgfx: Remove old XWayland and XMir driversThomas Hellstrom5-422/+1
Old-style XWayland and XMir aren't available anymore. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Brian Paul <brianp@vmware.com> Reviewed-by: Sinclair Yeh <syeh@vmware.com> Reviewed-by: Deepak Rawat <drawat@vmware.com>
2018-02-15vmwgfx: Fix compilation failure if dri3 is not availableThomas Hellstrom1-0/+4
Compilation on CentOS failed due to some code not being conditioned on DRI3 headers being present. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Brian Paul <brianp@vmware.com> Reviewed-by: Sinclair Yeh <syeh@vmware.com> Reviewed-by: Deepak Rawat <drawat@vmware.com>
2018-02-15saa: Fix an include pathThomas Hellstrom1-1/+1
Fix compilation failure on CentOS 6.5 due to an incorrect include path. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Brian Paul <brianp@vmware.com> Reviewed-by: Sinclair Yeh <syeh@vmware.com> Reviewed-by: Deepak Rawat <drawat@vmware.com>
2018-01-03Bump version number for release candidateThomas Hellstrom1-1/+1
Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
2018-01-03Add the common_compat.h source file for distributionThomas Hellstrom1-1/+2
The common_compat.h source file was missing from Makefile.am causing "make distcheck" to fail. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
2017-08-21vmwgfx: Support DRI3 v2Thomas Hellstrom7-21/+382
Add server-side DRI3 support Currently DRI3 introduces extra latency with gnome-shell for the following reasons: 1) We enable GLX_EXT_buffer_age. Causes gnome-shell to post fullscreen damage. 2) We enable GLX_OML_sync_control. Cases additional slowdown. Not exactly sure why. Probably we want to implement workarounds in mesa so that we don't enable these extensions for gnome-shell. That can be done with driconf, using some trickery. v2: Verify that sharing an ARGB surface as XRGB works before enabling DRI3. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Sinclair Yeh <syeh@vmware.com>
2017-08-21Revert "vmware/vmwgfx: Support multiple dri driver names"Thomas Hellstrom1-7/+2
This reverts commit d5550b7f8375c3d9003731578c1570e014577348. The commit was intended to support video drivers, but has the side effect that GLX thinks our driver supports more than it does. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Sinclair Yeh <syeh@vmware.com>
2017-08-07vmware/vmwgfx: Wrap deprecatedDeepak Singh Rawat1-0/+2
Deprecated with 43dbc556f3a4d743b9121d6cfc21961be4a9da56 Signed-off-by: Deepak Rawat <drawat@vmware.com> Reviewed-by: Thomas Hellstrom <thellstrom@vmware.com>
2017-08-07vmware: Fix build warningsDeepak Singh Rawat6-15/+32
Due to following commit in xserver there were build warnings, as variables now declared const. d89b42bda46d36fc0879611cc3b3566957ce36d0 e1e01d2e33c632e395d7e396f73fba8ae606b15a Added a compat header file. Signed-off-by: Deepak Rawat <drawat@vmware.com> Reviewed-by: Brian Paul <brianp@vmware.com> Reviewed-by: Thomas Hellstrom <thellstrom@vmware.com>:q
2017-07-13Revert "Revert "vmware/vmwgfx: Support multiple dri driver names""Sinclair Yeh1-2/+7
This reverts commit ea94dc570846655bbb8a7c75bf465907e454bef9. Temporarily revert this for internal testing.
2017-07-13Revert "vmwgfx: Support DRI3 v2"Sinclair Yeh7-382/+21
This reverts commit d0d5cf3e35fd47b44f32065c5cb64ba62661f03a. Temporarily revert this for internal testing.
2017-05-11vmwgfx: Support DRI3 v2Thomas Hellstrom7-21/+382
Add server-side DRI3 support Currently DRI3 introduces extra latency with gnome-shell for the following reasons: 1) We enable GLX_EXT_buffer_age. Causes gnome-shell to post fullscreen damage. 2) We enable GLX_OML_sync_control. Cases additional slowdown. Not exactly sure why. Probably we want to implement workarounds in mesa so that we don't enable these extensions for gnome-shell. That can be done with driconf, using some trickery. v2: Verify that sharing an ARGB surface as XRGB works before enabling DRI3. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Sinclair Yeh <syeh@vmware.com>
2017-05-11Revert "vmware/vmwgfx: Support multiple dri driver names"Thomas Hellstrom1-7/+2
This reverts commit d5550b7f8375c3d9003731578c1570e014577348. The commit was intended to support video drivers, but has the side effect that GLX thinks our driver supports more than it does. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Sinclair Yeh <syeh@vmware.com>
2017-01-26autogen: add default patch prefixMihail Konev1-0/+3
Signed-off-by: Mihail Konev <k.mvc@ya.ru>
2017-01-26autogen.sh: use quoted string variablesEmil Velikov1-4/+4
Place quotes around the $srcdir, $ORIGDIR and $0 variables to prevent fall-outs, when they contain space. Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2017-01-26autogen.sh: use exec instead of waiting for configure to finishPeter Hutterer1-1/+1
Syncs the invocation of configure with the one from the server. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Emil Velikov <emil.velikov@collabora.com>
2017-01-26autogen.sh: Honor NOCONFIGURE=1Alan Coopersmith1-2/+3
See http://people.gnome.org/~walters/docs/build-api.txt Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
2017-01-26configure: Drop AM_MAINTAINER_MODEAlan Coopersmith2-2/+2
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>