From: Thomas Hellstrom <thellstrom@vmware.com>
To: dri-devel@lists.freedesktop.org
Subject: [PATCH 0/7] drm/vmwgfx: Various atomic modesetting fixes
Date: Tue, 16 Jan 2018 14:34:27 +0100 [thread overview]
Message-ID: <1516109674-10087-1-git-send-email-thellstrom@vmware.com> (raw)
Part of the pageflip functionality that was intended to be performed using
atomic commit was only present in the legacy pageflip ioctl. That problem
is fixed in this series.
We also better support nonblocking commits as some time-consuming operations
previously were performed in the calling process even if that process had
requested a non-blocking commit.
Finally we fix an issue where cursor image updates were performed on each
cursor move.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-01-16 13:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 13:34 Thomas Hellstrom [this message]
2018-01-16 13:34 ` [PATCH 1/7] drm/vmwgfx: Avoid iterating over display unit if crtc is available Thomas Hellstrom
2018-01-16 13:34 ` [PATCH 2/7] drm/vmwgfx: Move surface copy cmd to atomic function Thomas Hellstrom
2018-01-16 13:34 ` [PATCH 3/7] drm/vmwgfx: Remove drm_crtc_arm_vblank_event from atomic flush Thomas Hellstrom
2018-01-16 13:34 ` [PATCH 4/7] drm/vmwgfx: Move screen object page flip to atomic function Thomas Hellstrom
2018-01-16 13:34 ` [PATCH 5/7] drm/vmwgfx: Move the stdu vblank event " Thomas Hellstrom
2018-01-16 13:34 ` [PATCH 6/7] drm/vmwgfx: Send the correct nonblock option for atomic_commit Thomas Hellstrom
2018-01-17 8:24 ` Daniel Vetter
2018-01-16 13:34 ` [PATCH 7/7] drm/vmwgfx: Cursor update fixes Thomas Hellstrom
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=1516109674-10087-1-git-send-email-thellstrom@vmware.com \
--to=thellstrom@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
/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;
as well as URLs for NNTP newsgroup(s).