On Sat, 2001-12-01 at 02:55, Yom, Francis wrote:
> I tried the patch. It wouldn't patch properly with 'patch' but I
> understood what you were trying to do, and so I simply hand cut and
> pasted the section of code over just like your patch indicates.
>
> It didn't work :-(
:(
> > Does this patch help? If not, can you try moving the
> > RADEONEngineRestore() call after the DRI specific code again?
> >
>
> Can you elaborate? I don't know what you'd like me to do. Did you mean
> return to the unpatched state and then what?
No, this:
Index: radeon_driver.c
===================================================================
RCS file:
/cvs/xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c,v
retrieving revision 1.44
diff -u -r1.44 radeon_driver.c
--- radeon_driver.c 2001/11/24 14:38:19 1.44
+++ radeon_driver.c 2001/12/01 13:48:23
@@ -4383,13 +4383,15 @@
RADEONInfoPtr info = RADEONPTR(pScrn);
RADEONTRACE(("RADEONEnterVT\n"));
+
+ if (!RADEONModeInit(pScrn, pScrn->currentMode)) return FALSE;
+
#ifdef XF86DRI
if (RADEONPTR(pScrn)->directRenderingEnabled) {
RADEONCP_START(pScrn, info);
DRIUnlock(pScrn->pScreen);
}
#endif
- if (!RADEONModeInit(pScrn, pScrn->currentMode)) return FALSE;
if (info->accelOn)
RADEONEngineRestore(pScrn);
But I'm afraid this won't help either, it may be an entirely different
issue than I thought it was.
BTW you aren't using Option "UseFBDev", are you? The radeon driver is
broken with that and DRI at least for VT switching, guess I'll have to
fix that. I'll post to dri-devel about it soon.
--
Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
