From: Daniel Vetter <daniel@ffwll.ch>
To: Rob Clark <robdclark@gmail.com>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: [RFCv1 11/12] drm: Atomic modeset ioctl
Date: Mon, 7 Oct 2013 19:56:02 +0200 [thread overview]
Message-ID: <20131007175602.GB2676@phenom.ffwll.local> (raw)
In-Reply-To: <CAF6AEGvyy16dnauY4ArWp+OP5aQ1dkoYeoiAqceOQom1QMdqNA@mail.gmail.com>
On Mon, Oct 07, 2013 at 11:20:54AM -0400, Rob Clark wrote:
> yeah, current atomic patch is almost an afterthought in this series.
> I still need to get planes working on msm and find some test code (I
> guess you have some somewhere?).. so other than just rebasing it
> enough to compile, I didn't really spend any time on it yet. Right
> now I was more interested in getting folks to have a look at the
> atomic funcs and helpers.
One in-kernel test user we have is the fbdev restore code - it needs to
get rid of all planes, cursors and set up its new config on all crtcs. I
think this would be a fairly nice (albeit really basic testcase): You can
set up a bunch of planes/cursors, then vt-switch to the fbcon - this way
we can exercise the atomic stuff in drivers a bit better even without
needing to add any ioctl.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-10-07 17:55 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 0:45 [RFCv1 00/12] Atomic/nuclear modeset/pageflip Rob Clark
2013-10-06 0:45 ` [RFCv1 01/12] drm: add atomic fxns Rob Clark
2013-10-06 0:45 ` [RFCv1 02/12] drm: add object property type Rob Clark
2013-10-07 13:43 ` Ville Syrjälä
2013-10-07 14:44 ` Rob Clark
2013-10-06 0:45 ` [RFCv1 03/12] drm: add DRM_MODE_PROP_DYNAMIC property flag Rob Clark
2013-10-07 13:46 ` Ville Syrjälä
2013-10-07 14:46 ` Rob Clark
2013-10-06 0:45 ` [RFCv1 04/12] drm: add DRM_MODE_PROP_SIGNED " Rob Clark
2013-10-07 14:46 ` Matt Plumtree
2013-10-06 0:45 ` [RFCv1 05/12] drm: helpers to find mode objects (BEFORE drm: split property values out) Rob Clark
2013-10-06 0:48 ` Rob Clark
2013-10-06 0:45 ` [RFCv1 06/12] drm: split propvals out and blob property support Rob Clark
2013-10-06 0:45 ` [RFCv1 07/12] drm: Allow drm_mode_object_find() to look up an object of any type Rob Clark
2013-10-06 0:45 ` [RFCv1 08/12] drm: Refactor object property check code Rob Clark
2013-10-07 13:47 ` Ville Syrjälä
2013-10-06 0:45 ` [RFCv1 09/12] drm: convert plane to properties/state Rob Clark
2013-10-06 0:45 ` [RFCv1 10/12] drm: convert crtc " Rob Clark
2013-10-07 13:39 ` Ville Syrjälä
2013-10-07 14:03 ` Rob Clark
2013-10-07 14:19 ` Ville Syrjälä
2013-10-07 14:29 ` Rob Clark
2013-10-07 17:51 ` Daniel Vetter
2013-10-06 0:45 ` [RFCv1 11/12] drm: Atomic modeset ioctl Rob Clark
2013-10-07 13:28 ` Ville Syrjälä
2013-10-07 13:55 ` Rob Clark
2013-10-07 14:18 ` Ville Syrjälä
2013-10-07 14:39 ` Rob Clark
2013-10-07 15:05 ` Ville Syrjälä
2013-10-07 15:20 ` Rob Clark
2013-10-07 17:56 ` Daniel Vetter [this message]
2013-10-07 18:49 ` Rob Clark
2013-10-08 18:35 ` Matt Roper
2013-10-08 18:46 ` Rob Clark
2013-10-06 0:45 ` [RFCv1 12/12] ARM: add get_user() support for 8 byte types Rob Clark
2013-10-06 8:53 ` Russell King - ARM Linux
2013-10-06 14:09 ` Rob Clark
2013-10-06 15:56 ` Russell King - ARM Linux
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=20131007175602.GB2676@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=robdclark@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.