From: Gerd Hoffmann <kraxel@redhat.com>
To: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [RESEND PATCH 00/14] QXL atomic modesetting
Date: Tue, 28 Feb 2017 10:50:02 +0100 [thread overview]
Message-ID: <1488275402.26614.2.camel@redhat.com> (raw)
In-Reply-To: <20170227204328.18761-1-krisman@collabora.co.uk>
On Mo, 2017-02-27 at 17:43 -0300, Gabriel Krisman Bertazi wrote:
> Hi,
>
> This is a resend of the qxl atomic modesetting patchset to include the reviewed-by tags from Gustavo and rebase on top of the tip of drm-misc-next.
>
> This series implements support for Atomic Modesetting in the QXL driver.
> The first 4 patches in the series are some cleanups to prepare the
> ground, while the rest implement Atomic in 3 phases, as suggested by
> Daniel's blog post[1].
>
> Testing was done with the X server, igt, libdrm testsuit and some custom
> code that I can share if requested. I hope this covers the main use
> cases.
Patches look good, great job. I'll go run some more tests and if all
goes fine I'll push to drm-misc-next.
thanks,
Gerd
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-02-28 9:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 20:43 [RESEND PATCH 00/14] QXL atomic modesetting Gabriel Krisman Bertazi
2017-02-27 20:43 ` [RESEND PATCH 01/14] drm: qxl: Drop device flags attribute Gabriel Krisman Bertazi
2017-02-27 20:43 ` [RESEND PATCH 02/14] drm: qxl: Consolidate bo reservation when pinning Gabriel Krisman Bertazi
2017-02-27 20:43 ` [RESEND PATCH 03/14] drm: qxl: Don't initialize vblank support Gabriel Krisman Bertazi
2017-02-27 20:43 ` [RESEND PATCH 04/14] drm: qxl: Expose creation of universal primary plane Gabriel Krisman Bertazi
2017-02-27 20:43 ` [RESEND PATCH 05/14] drm: qxl: Atomic phase 1: convert cursor to universal plane Gabriel Krisman Bertazi
2017-02-27 20:43 ` [RESEND PATCH 06/14] drm: qxl: Atomic phase 1: Use drm_plane_helpers for primary plane Gabriel Krisman Bertazi
2017-02-27 20:43 ` [RESEND PATCH 07/14] drm: qxl: Atomic phase 1: Implement mode_set_nofb Gabriel Krisman Bertazi
2017-02-27 20:43 ` [RESEND PATCH 08/14] drm: qxl: Atomic phase 1: Don't unpin primary when disabling crtc Gabriel Krisman Bertazi
2017-02-27 20:43 ` [RESEND PATCH 09/14] drm: qxl: Atomic phase 2: Wire up state object handlers Gabriel Krisman Bertazi
2017-02-27 20:43 ` [RESEND PATCH 10/14] drm: qxl: Atomic phase 2: Use drm_atomic_set_fb_for_plane helper Gabriel Krisman Bertazi
2017-02-27 20:43 ` [RESEND PATCH 11/14] drm: qxl: Atomic phase 3: Use atomic handlers for planes Gabriel Krisman Bertazi
2017-02-27 20:43 ` [RESEND PATCH 12/14] drm: qxl: Atomic phase 3: Wire up atomic set_config helper Gabriel Krisman Bertazi
2017-02-27 20:43 ` [RESEND PATCH 13/14] drm: qxl: Atomic phase 3: Wire up atomic page_flip helper Gabriel Krisman Bertazi
2017-02-27 20:43 ` [RESEND PATCH 14/14] drm: qxl: Enable atomic modesetting ioctl Gabriel Krisman Bertazi
2017-02-28 9:50 ` Gerd Hoffmann [this message]
2017-02-28 16:27 ` [RESEND PATCH 00/14] QXL atomic modesetting Gerd Hoffmann
2017-02-28 13:29 ` Gerd Hoffmann
2017-02-28 15:02 ` Gerd Hoffmann
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=1488275402.26614.2.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=krisman@collabora.co.uk \
/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).