Attachment 8023 Details for Bug 2859 – may not fix everyone's problems but works for me

[patch] may not fix everyone's problems but works for me

radeon_modeinit.diff (text/plain), 1.37 KB, created by Roland Scheidegger on 2006-12-08 16:06:52 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Roland Scheidegger

Created: 2006-12-08 16:06:52 UTC

Size: 1.37 KB

patch

obsolete

>@@ -123,6 +123,7 @@ static void RADEONGetMergedFBOptions(Scr
> static void RADEONSetDynamicClock(ScrnInfoPtr pScrn, int mode);
> static void RADEONForceSomeClocks(ScrnInfoPtr pScrn);
> static void RADEONSaveMemMapRegisters(ScrnInfoPtr pScrn, RADEONSavePtr save);
>+static void RADEONSaveMode(ScrnInfoPtr pScrn, RADEONSavePtr save);
> 
> #ifdef XF86DRI
> static void RADEONAdjustMemMapRegisters(ScrnInfoPtr pScrn, RADEONSavePtr save);
>@@ -6450,6 +6453,9 @@ static Bool RADEONModeInit(ScrnInfoPtr p
> 
>     RADEONTRACE(("RADEONModeInit()\n"));
> 
>+/* some of the functions called in RADEONInit rely on some state already
>+   set e.g. the TMDS_TRANSMITTER_CNTL must not be overwritten with 0 */
>+    RADEONSaveMode(pScrn, &info->ModeReg);
>     if (!RADEONInit(pScrn, mode, &info->ModeReg)) return FALSE;
> 
>     pScrn->vtSema = TRUE;
>diff --git a/src/radeon_exa.c b/src/radeon_exa.c
>diff --git a/src/radeon_exa_funcs.c b/src/radeon_exa_funcs.c
>diff --git a/src/radeon_exa_render.c b/src/radeon_exa_render.c
>diff --git a/src/radeon_macros.h b/src/radeon_macros.h
>diff --git a/src/radeon_mergedfb.c b/src/radeon_mergedfb.c
>diff --git a/src/radeon_mergedfb.h b/src/radeon_mergedfb.h
>diff --git a/src/radeon_misc.c b/src/radeon_misc.c
>diff --git a/src/radeon_mm_i2c.c b/src/radeon_mm_i2c.c
>diff --git a/src/radeon_modes.c b/src/radeon_modes.c
>index 70bf184..531247e 100644
>--- a/src/radeon_modes.c
>+++ b/src/radeon_modes.c

Actions: View | Splinter Review

Attachments on bug 2859: 2256 | 2257 | 2258 | 2306 | 2307 | 2308 | 2591 | 5305 | 8023 | 8437 | 8821 | 17563 | 17616 | 17617

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.