summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichel Dänzer <michel.daenzer@amd.com>2016-03-24 18:08:22 +0900
committerMichel Dänzer <michel.daenzer@amd.com>2016-03-24 18:08:22 +0900
commited31cffba0d1bd4b14e5348a1456e4377277059c (patch)
treee12650f1dab20cd8fde683226e500fd6ac6abc09
parente592f32f8b5f5873fcc18b10a69dd5e4ccf11073 (diff)
Call RADEONBlockHandler_KMS before setting initial modes
Doing it the other way around meant that there was still a possibility for the front buffer contents to be uninitialized when they start being scanned out. (Ported from amdgpu commit 4a60b4b1851a3cbc2d8ad9048d68eeb6947cf132) Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
-rw-r--r--src/radeon_kms.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/radeon_kms.c b/src/radeon_kms.c
index 38642819..555d7367 100644
--- a/src/radeon_kms.c
+++ b/src/radeon_kms.c
@@ -633,9 +633,9 @@ static void RADEONBlockHandler_oneshot(BLOCKHANDLER_ARGS_DECL)
ScrnInfoPtr pScrn = xf86ScreenToScrn(pScreen);
RADEONInfoPtr info = RADEONPTR(pScrn);
- drmmode_set_desired_modes(pScrn, &info->drmmode, TRUE);
-
RADEONBlockHandler_KMS(BLOCKHANDLER_ARGS);
+
+ drmmode_set_desired_modes(pScrn, &info->drmmode, TRUE);
}
static void