[git pull] vmwgfx-next-5.9

Dave, Daniel, vmwgfx fixes pull for 5.9. The drm_mode_config_reset patches are very important fixing a recently introduced kernel crash, the others fix various older issues which are a bit less serious in practice. (Although still pending a solution for the other crash introduced by

[git-pull] vmwgfx-next

Dave, Daniel, The first vmwgfx-next pull for 5.7. Roland Scheidegger will follow up with a larger pull request for functionality needed for GL4 support. - Disable DMA when using SEV encryption - An -RT fix - Code cleanups Thanks, Thomas The following changes since commit

Re: [git pull] vmwgfx-next

On 1/20/20 10:09 PM, Dave Airlie wrote: On Thu, 16 Jan 2020 at 19:30, Thomas Hellström (VMware) wrote: Dave, Daniel The main 5.6 -next pull from vmwgfx. Minor things here and there, as well as an added ioctl for host messaging and a corresponding api version bump. Is there userspace for this

Re: [git pull] vmwgfx-next

On 1/20/20 10:09 PM, Dave Airlie wrote: On Thu, 16 Jan 2020 at 19:30, Thomas Hellström (VMware) wrote: Dave, Daniel The main 5.6 -next pull from vmwgfx. Minor things here and there, as well as an added ioctl for host messaging and a corresponding api version bump. Is there userspace for this

Re: [git pull] vmwgfx-next

On Thu, 16 Jan 2020 at 19:30, Thomas Hellström (VMware) wrote: > > Dave, Daniel > > The main 5.6 -next pull from vmwgfx. Minor things here and there, as well > as an added ioctl for host messaging and a corresponding api version bump. Is there userspace for this ioctl somewhere? I need a pointer

[git pull] vmwgfx-next

Dave, Daniel The main 5.6 -next pull from vmwgfx. Minor things here and there, as well as an added ioctl for host messaging and a corresponding api version bump. Thanks, Thomas The following changes since commit 71e7274066c646bb3d9da39d2f4db0a6404c0a2d: Merge tag 'drm-intel-next-2020-01-14'

[git pull] vmwgfx-next

Dave, Daniel Two minor cleanups / fixes for -next. The following changes since commit 3ca3a9eab7085b3c938b5d088c3020269cfecdc8: Merge tag 'drm-misc-next-fixes-2019-11-06' of git://anongit.freedesktop.org/drm/drm-misc into drm-next (2019-11-08 16:48:22 +1000) are available in the Git

[git pull] vmwgfx-next

From: Thomas Hellstrom (VMware) Dave, Daniel A couple of independent patches extracted from the 5.3 pull request, fixed for merge conflicts and a single unused variable warning. And the drmP.h removal from Sam. /Thomas The following changes since commit

Re: [git pull] vmwgfx-next

On 8/14/19 9:31 AM, Thomas Hellström (VMware) wrote: From: Thomas Hellstrom (VMware) Dave, Daniel A couple of independent patches extracted from the 5.3 pull request, fixed for merge conflicts. Hmm. Just noted an unused variable resulting from one of the commits. Please ignore this for now,

[git pull] vmwgfx-next

From: Thomas Hellstrom (VMware) Dave, Daniel A couple of independent patches extracted from the 5.3 pull request, fixed for merge conflicts. And the drmP.h removal from Sam. /Thomas The following changes since commit e7f7287bf5f746d29f3607178851246a005dd398: Merge tag

[git pull] vmwgfx-next

Dave, Daniel - The coherent memory changes including mm changes. - Some vmwgfx debug fixes. - Removal of vmwgfx legacy security checks. The following changes since commit 561564bea3248293398dc32ec36da40fb71faed0: Merge tag 'omapdrm-5.3' of

Re: [git pull] vmwgfx-next-2018-12-13

Old pull message. Please ignore. The correct one coming up. /Thomas On Wed, 2019-02-06 at 20:42 +0100, Thomas Hellstrom wrote: > Hi, Dave > > Two minor fixes for the previous vmwgfx-next pull: > > The following changes since commit > 9a01135b98b9d5a7033c544245da7aad0d886758: > >

[git pull] vmwgfx-next-2018-12-13

Hi, Dave Two minor fixes for the previous vmwgfx-next pull: The following changes since commit 9a01135b98b9d5a7033c544245da7aad0d886758: drm/vmwgfx: Use the standard atomic helpers for page-flip (2018-12-05 10:09:55 +0100) are available in the Git repository at:

[git pull] vmwgfx-next-2018-12-13

Hi, Dave Two minor fixes for the previous vmwgfx-next pull: The following changes since commit 9a01135b98b9d5a7033c544245da7aad0d886758: drm/vmwgfx: Use the standard atomic helpers for page-flip (2018-12-05 10:09:55 +0100) are available in the Git repository at:

[git pull] vmwgfx-next

Hi Dave, The vmwgfx -next changes for 4.21: Page flip with damage by Deepak and others, Various vmwgfx minor fixes anc cleanups. The following changes since commit 818182dd1097fdc492aaef9b08755ea13274352d: Merge tag 'imx-drm-next-2018-12-03' of git://git.pengutronix.de/git/pza/linux into

[git pull] vmwgfx-next

Hi, Dave I realize this is probably too late for the next merge window. If that's the case, then we can just postpone it for 4.21. Mostly code reorganizations and optimizations for vmwgfx. - Move TTM code that's only used by vmwgfx to vmwgfx - Break out the vmwgfx buffer- and resource

[git pull] vmwgfx-next-4.19-3

Dave, This introduces a header update and support for multisample surfaces. The following changes since commit 812a954b787ab5a91d62e597a36351628b08d079: drm/vmwgfx: Remove an obsolete __le32 conversion (2018-07-03 20:41:23 +0200) are available in the Git repository at:

[git pull] vmwgfx-next-4.19-2

Dave, A series of cleanups / reorganizations and modesetting changes that mostly target atomic state validation. The following changes since commit 07c13bb78c8b8a9cb6ee169659528945038d5e85: drm: Change deadlock-avoidance algorithm for the modeset locks. (2018-07-03 09:46:05 +0200) are

[git pull] vmwgfx-next WW mutex update

Hi, Dave. A patchset worked out together with Peter Zijlstra. Ingo is OK with taking it through the DRM tree: This is a small fallout from a work to allow batching WW mutex locks and unlocks. Our Wound-Wait mutexes actually don't use the Wound-Wait algorithm but the Wait-Die algorithm. One

[GIT PULL] vmwgfx-next for 4.17

Hi, Dave. A relative large set of various improvements for vmwgfx. Some of them have been around for a while, some are relatively new, but functionality should have been tested in our standalone repo. There was a kbuild test robot compilation failure on Debian for "drm/vmwgfx: Add a cpu blit

[Git PULL] vmwgfx-next

Hi Dave, The following changes since commit 7c0059dd832cc686bf0febefdcf8295cdd93007f: Merge branch 'linux-4.14' of git://github.com/skeggsb/linux into drm-next (2017-08-23 05:32:26 +1000) are available in the git repository at: git://people.freedesktop.org/~syeh/repos_linux

Re: [Git PULL] vmwgfx-next

On Tue, Aug 29, 2017 at 06:35:38AM +1000, Dave Airlie wrote: > On 29 August 2017 at 06:22, Sinclair Yeh wrote: > > Hi Dave, > > > > The following changes since commit 7c0059dd832cc686bf0febefdcf8295cdd93007f: > > Just a reminder, -next branches need to be sent before rc6 if you

Re: [Git PULL] vmwgfx-next

On 29 August 2017 at 06:22, Sinclair Yeh wrote: > Hi Dave, > > The following changes since commit 7c0059dd832cc686bf0febefdcf8295cdd93007f: Just a reminder, -next branches need to be sent before rc6 if you want them in the next kernel. I'll take a look at this branch later

[git pull] vmwgfx-next

Hi Dave, The following changes since commit 6b1462700b4a6a1244c018cdd2fa97ded43090a0: Merge tag 'drm-misc-next-fixes-2017-04-20' of git://anongit.freedesktop.org/git/drm-misc into drm-next (2017-04-21 13:51:59 +1000) are available in the git repository at:

Re: [git pull] vmwgfx-next

On Sun, Apr 02, 2017 at 08:11:12PM +0200, Daniel Vetter wrote: > On Fri, Mar 31, 2017 at 04:32:55PM -0700, Sinclair Yeh wrote: > > Hi Dave, > > > > This series enables atomic mode set for vmwgfx. A number of features and > > larger fixes are also included. > > > > The following changes since

Re: [git pull] vmwgfx-next

On Fri, Mar 31, 2017 at 04:32:55PM -0700, Sinclair Yeh wrote: > Hi Dave, > > This series enables atomic mode set for vmwgfx. A number of features and > larger fixes are also included. > > The following changes since commit 8cd3ac52963f2e99f4c21d1c9ce89531ce66c2d6: > > Merge branch

[git pull] vmwgfx-next

Hi Dave, This series enables atomic mode set for vmwgfx. A number of features and larger fixes are also included. The following changes since commit 8cd3ac52963f2e99f4c21d1c9ce89531ce66c2d6: Merge branch 'drm-next-4.12' of git://people.freedesktop.org/~agd5f/linux into drm-next (2017-03-31

[git pull] vmwgfx-next

Hi Dave, This is to address what we've discussed, moving some of the minor changes into a drm-next request. - The following changes since commit f0493e653f9679114d1dfd54ab88b54ce95576e1: drm/mgag200: Added support for the new device G200eH3 (2017-01-23 11:57:08 +1000) are available in

[git pull] vmwgfx-next

Dave, One is fix for a regression in 4.3, One irq locking rework. The following changes since commit b76ff5ea1cf6fe648e7ce2b84e636f8a95849a0b: drm/vmwgfx: Replace iowrite/ioread with volatile memory accesses (2015-11-02 00:16:05 -0800) are available in the git repository at:

[git pull] vmwgfx-next

Dave, Changes for vmwgfx for 4.4. If there is time, I'll follow up with a series to move to threaded irqs. The following changes since commit a76edb8cec0cc864c8b72fa7e84a72336e033e23: Merge tag 'topic/drm-misc-2015-10-22' of git://anongit.freedesktop.org/drm-intel into drm-next (2015-10-30

[git pull] vmwgfx-next-15-09-01

Dave, A single commit. Workaround for https://bugzilla.redhat.com/show_bug.cgi?id=1227193 The following changes since commit 36d4e87b497d9cb3bf8e1bb2f803c7aa41dfb463: drm/vmwgfx: Remove duplicate ttm_bo_device_release (2015-08-21 00:38:23 -0700) are available in the git repository at:

[git pull] vmwgfx-next-15-08-21

Dave, The third pull request for 4.3. Contains two fixes for regressions introduced with previous pull requests. The following changes since commit 294947a5c7f6d228b70fcc51a89527e74a38a2c5: Merge branch 'vmwgfx-next' of git://people.freedesktop.org/~thomash/linux into drm-next (2015-08-17

[git pull] vmwgfx-next gl3 support

Hi, Dave. This pull request is on top of the earlier vmwgfx pull request (sent out 15-08-06) A couple of fixes from the previous pull request as well as gl3 support. There is one drm core change, an export of a previously private function. The following changes since commit

[git pull] vmwgfx-next

Dave, Take 2 implementing screen targets, this time with the fbdev code adjusted accordingly. Also there is an implementation of register-driven command buffers, that overrides the FIFO ring for command processing. It's needed for our upcoming hardware revision. The following changes since