Attachment 139016 Details for Bug 105736 – Simplify drmmode_handle_transform

[patch] Simplify drmmode_handle_transform

0002-Simplify-drmmode_handle_transform.patch (text/plain), 1.38 KB, created by Michel Dänzer on 2018-04-23 17:07:31 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Michel Dänzer

Created: 2018-04-23 17:07:31 UTC

Size: 1.38 KB

patch

obsolete

>From 6a6436274f1b13fc5815bf0807628d204d2720fb Mon Sep 17 00:00:00 2001
>From: =?UTF-8?q?Michel=20D=C3=A4nzer?= <michel.daenzer@amd.com>
>Date: Mon, 23 Apr 2018 18:52:02 +0200
>Subject: [PATCH xf86-video-amdgpu] Simplify drmmode_handle_transform
>MIME-Version: 1.0
>Content-Type: text/plain; charset=UTF-8
>Content-Transfer-Encoding: 8bit
>
>Set crtc->driverIsPerformingTransform for any case we can handle before
>calling xf86CrtcRotate. We already clear it afterwards when the latter
>clears crtc->transform_in_use.
>
>This should allow our separate scanout buffer mechanism to be used in
>more cases.
>---
> src/drmmode_display.c | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
>diff --git a/src/drmmode_display.c b/src/drmmode_display.c
>index 240e88b90..536890d18 100644
>--- a/src/drmmode_display.c
>+++ b/src/drmmode_display.c
>@@ -631,13 +631,9 @@ drmmode_handle_transform(xf86CrtcPtr crtc)
> 	Bool ret;
> 
> #if XORG_VERSION_CURRENT >= XORG_VERSION_NUMERIC(1,15,99,903,0)
>-	if (crtc->transformPresent || crtc->rotation != RR_Rotate_0)
>-	    crtc->driverIsPerformingTransform = XF86DriverTransformOutput;
>-	else
>-	    crtc->driverIsPerformingTransform = XF86DriverTransformNone;
>+	crtc->driverIsPerformingTransform = XF86DriverTransformOutput;
> #else
> 	crtc->driverIsPerformingTransform = !crtc->transformPresent &&
>-		crtc->rotation != RR_Rotate_0 &&
> 		(crtc->rotation & 0xf) == RR_Rotate_0;
> #endif
> 
>-- 
>2.17.0
>

Actions: View | Splinter Review

Attachments on bug 105736: 138347 | 138348 | 138644 | 138672 | 138960 | 139015 | 139016

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.