On Thu, 2003-10-02 at 22:30, Keith Whitwell wrote: > Keith Whitwell wrote: > > > > The problem seems to be that RADEONAdjustFrame() is designed to be > > called from cursor handling routines that are executed outside the > > Wakeup/Block handlers (perhaps this came in with SilkenMouse?) but is > > being called during initialization after the point the lock is grabbed. > > Actually, looking more closely at RADEONAdjustFrame(), I would guess that the > test of (info->CPStarted) is designed to avoid precisely this problem, right? > So I wonder why that's not working for you...
Me too, considering that it seems to be working for the vast majority of people. Also, DRI{Lock,Unlock}() are designed to handle nested calls. It seems the problem must be somewhere else, maybe it is a subtle architecture difference after all? -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel