On Mon, 2002-01-28 at 10:00, Vladimir Dergachev wrote: > > > On 28 Jan 2002, Michel [ISO-8859-1] Dänzer wrote: > > > On Mon, 2002-01-28 at 04:54, Davor Buvinic wrote: > > > > > > Yes, running glxgears cause the movie player to crawl and if I start to move > > > or resize their windows X crashes. > > > > > > The movie player is MPlayer, today cvs. > > > > > > Here is my log file from X. As you can see, at the end of the file the > > > following messages appears: > > > > > > [...] > > > (II) R128(0): StopVideo > > > (EE) R128(0): Idle timed out, resetting engine... > > > [...] > > > > I have an idea what the problem could be. The Xv code still uses direct > > register access, even when the CCE is running. That's exactly what we > > want to avoid, because it can crash the chip. :) > > > > I probably won't have time this week to work on a solution but I suggest > > you try either shutting down the CCE before accessing registers or > > adding new Xv functions which use the CCE for register access (à la the > > CCE accel functions). I'd prefer not shutting down the CCE at any rate. > > > > Yes, that's what happens. I do think we need to shutdown CCE because in > some case we want to read registers - and not only write. The short term > solution would be to use XAA->Sync() instead of WaitForEngineIdle because > WaitForEngineIdle does not guarantee the card is quiscent in CCE mode.
Sounds like the correct fix, except I don't even see 'WaitForEngineIdle' in my trees - is that a GATOS novelty? :) -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
