On Wed, Apr 20, 2016 at 10:59:46AM -0400, [email protected] wrote: > From: Robert Foss <[email protected]> > > Avoid moving the cursor plane when on non-intel hardware. > Running the move block on hardware with more than IGT_PLANE_CURSOR > number of planes causes planes do be zeroed out. > > Signed-off-by: Robert Foss <[email protected]> > --- > lib/igt_kms.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/lib/igt_kms.c b/lib/igt_kms.c > index 3f953ec..522ede5 100644 > --- a/lib/igt_kms.c > +++ b/lib/igt_kms.c > @@ -1363,7 +1363,7 @@ void igt_display_init(igt_display_t *display, int > drm_fd) > * only 1 sprite, that's the wrong slot and we need to > * move it down. > */ > - if (p != IGT_PLANE_CURSOR) { > + if (IS_INTEL(drm_fd) && p != IGT_PLANE_CURSOR) {
Reading this again, isn't the problem that on some hw there's simply no cursor plane? With universal planes the cursor plane should alias with some of the real planes, and we simply need to make sure that we get that aliasing right. But if there's no cursor registered, well there's no cursor ... -Daniel > pipe->planes[p] = > pipe->planes[IGT_PLANE_CURSOR]; > pipe->planes[p].index = p; > memset(&pipe->planes[IGT_PLANE_CURSOR], 0, > -- > 2.5.0 > -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
