From: Thomas Hellstrom <thellstrom@vmware.com>
To: airlied@gmail.com, airlied@redhat.com
Cc: pv-drivers@vmware.com, Thomas Hellstrom <thellstrom@vmware.com>,
linux-graphics-maintainer@vmware.com,
dri-devel@lists.freedesktop.org
Subject: [git pull] vmwgfx-fixes-4.19
Date: Thu, 20 Sep 2018 08:39:35 +0200 [thread overview]
Message-ID: <20180920063935.35492-1-thellstrom@vmware.com> (raw)
Hi Dave,
A couple of modesetting fixes and a fix for a long-standing buffer-eviction
problem cc'd stable.
The following changes since commit 8ca4fff974ad5288d38298f15bf218f2eac2d5e7:
Merge tag 'drm-intel-fixes-2018-09-19' of git://anongit.freedesktop.org/drm/drm-intel into drm-fixes (2018-09-20 10:01:53 +1000)
are available in the Git repository at:
git://people.freedesktop.org/~thomash/linux vmwgfx-fixes-4.19
for you to fetch changes up to e71cf591876536f7dd5a54ef68d631278ca6faa1:
drm/vmwgfx: Fix buffer object eviction (2018-09-20 08:05:14 +0200)
----------------------------------------------------------------
Deepak Rawat (4):
drm/vmwgfx: don't check for old_crtc_state enable status
drm/vmwgfx: limit screen size to stdu_max during check_modeset
drm/vmwgfx: limit mode size for all display unit to texture_max
drm/vmwgfx: Don't impose STDU limits on framebuffer size
Thomas Hellstrom (1):
drm/vmwgfx: Fix buffer object eviction
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 2 +-
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 42 +++++++++++++++++++++++----------
drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c | 25 --------------------
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c | 24 +++++++++++--------
4 files changed, 45 insertions(+), 48 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2018-09-20 6:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180920063935.35492-1-thellstrom@vmware.com \
--to=thellstrom@vmware.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=pv-drivers@vmware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox