Attachment 141138 Details for Bug 107519 – Use correct FB handle in radeon_do_pageflip

[patch] Use correct FB handle in radeon_do_pageflip

0001-Use-correct-FB-handle-in-amdgpu_do_pageflip.patch (text/plain), 1.43 KB, created by Michel Dänzer on 2018-08-16 14:43:41 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Michel Dänzer

Created: 2018-08-16 14:43:41 UTC

Size: 1.43 KB

patch

obsolete

>From 373e26f73a5a75d7eaa3dba4da5b9650d6e2e820 Mon Sep 17 00:00:00 2001
>From: =?UTF-8?q?Michel=20D=C3=A4nzer?= <michel.daenzer@amd.com>
>Date: Thu, 16 Aug 2018 16:39:27 +0200
>Subject: [PATCH xf86-video-ati] Use correct FB handle in radeon_do_pageflip
>MIME-Version: 1.0
>Content-Type: text/plain; charset=UTF-8
>Content-Transfer-Encoding: 8bit
>
>We were always using the handle of the client provided FB, which
>prevented RandR transforms from working, and could result in a black
>screen.
>
>Fixes: 740f0850f1e4 "Store FB for each CRTC in drmmode_flipdata_rec"
>---
> src/drmmode_display.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/src/drmmode_display.c b/src/drmmode_display.c
>index 0b92b70c6..68d6254d7 100644
>--- a/src/drmmode_display.c
>+++ b/src/drmmode_display.c
>@@ -3386,7 +3386,7 @@ Bool radeon_do_pageflip(ScrnInfoPtr scrn, ClientPtr client,
> 		if (crtc == ref_crtc) {
> 			if (drmmode_page_flip_target_absolute(pRADEONEnt,
> 							      drmmode_crtc,
>-							      fb->handle,
>+							      flipdata->fb[i]->handle,
> 							      flip_flags,
> 							      drm_queue_seq,
> 							      target_msc) != 0)
>@@ -3394,7 +3394,7 @@ Bool radeon_do_pageflip(ScrnInfoPtr scrn, ClientPtr client,
> 		} else {
> 			if (drmmode_page_flip_target_relative(pRADEONEnt,
> 							      drmmode_crtc,
>-							      fb->handle,
>+							      flipdata->fb[i]->handle,
> 							      flip_flags,
> 							      drm_queue_seq, 0) != 0)
> 				goto flip_error;
>-- 
>2.18.0
>

Actions: View | Splinter Review

Attachments on bug 107519: 141138

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.