Attachment 38519 Details for Bug 30049 – fix

[patch] fix

0001-drm-radeon-kms-fix-regression-in-RMX-code.patch (text/plain), 1.47 KB, created by Alex Deucher on 2010-09-07 10:21:18 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Alex Deucher

Created: 2010-09-07 10:21:18 UTC

Size: 1.47 KB

patch

obsolete

>From 7ef7778e1944b9aaa01a1973643e99325dade9de Mon Sep 17 00:00:00 2001
>From: Alex Deucher <alexdeucher@gmail.com>
>Date: Tue, 7 Sep 2010 13:17:29 -0400
>Subject: [PATCH] drm/radeon/kms: fix regression in RMX code
>
>caused by d65d65b175a29bd7ea2bb69c046419329c4a5db7
>
>need to update the radeon crtc priv native mode before using it.
>
>Fixes:
>https://bugs.freedesktop.org/show_bug.cgi?id=30049
>
>Signed-off-by: Alex Deucher <alexdeucher@gmail.com>
>---
> drivers/gpu/drm/radeon/radeon_display.c |    8 ++++----
> 1 files changed, 4 insertions(+), 4 deletions(-)
>
>diff --git a/drivers/gpu/drm/radeon/radeon_display.c b/drivers/gpu/drm/radeon/radeon_display.c
>index c7f5017..8c987c9 100644
>--- a/drivers/gpu/drm/radeon/radeon_display.c
>+++ b/drivers/gpu/drm/radeon/radeon_display.c
>@@ -1140,14 +1140,14 @@ bool radeon_crtc_scaling_mode_fixup(struct drm_crtc *crtc,
> 				radeon_crtc->rmx_type = radeon_encoder->rmx_type;
> 			else
> 				radeon_crtc->rmx_type = RMX_OFF;
>-			src_v = crtc->mode.vdisplay;
>-			dst_v = radeon_crtc->native_mode.vdisplay;
>-			src_h = crtc->mode.hdisplay;
>-			dst_h = radeon_crtc->native_mode.hdisplay;
> 			/* copy native mode */
> 			memcpy(&radeon_crtc->native_mode,
> 			       &radeon_encoder->native_mode,
> 				sizeof(struct drm_display_mode));
>+			src_v = crtc->mode.vdisplay;
>+			dst_v = radeon_crtc->native_mode.vdisplay;
>+			src_h = crtc->mode.hdisplay;
>+			dst_h = radeon_crtc->native_mode.hdisplay;
> 
> 			/* fix up for overscan on hdmi */
> 			if (ASIC_IS_AVIVO(rdev) &&
>-- 
>1.7.1.1
>

Actions: View | Splinter Review

Attachments on bug 30049: 38483 | 38519 | 38520 | 38521

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.