Tim Smith wrote: > I have a nice, 100% reliable way to lock up my Radeon 7500 using the most > recent CVS. I can do this with Tux Racer, if I play for a couple of > courses, but it's much easier to do using the Neverwinter Nights Toolset > beta running under WINE, because that's really quite intensive and produces > the lockup in about 5 seconds (much longer if debugging is enabled, which > seems interesting). This was stable with the drivers in XFree 4.2, except > that they would fail to texture things (e.g. the penguin in Tux Racer was a > white blob). > > I've played around with *all* the radeon driver options in XF86Config, to no > significant effect (well I managed to lock X on startup with a too-high > CPusecTimeout :-). It won't let me assign more than 2MB to BufferSize and I > presume there's a good reason for that, so 32 buffers seems the maximum > unless the size of each buffer can be reduced. How much of that 64K gets > used? Is it worth trying that?
It depends a little on which driver you're using. The two in CVS make full use of each buffer & only release it when it's full. XFree 4.2 driver is pretty primitive in some repects & fires after each (run of similar) primitive so can be quite wasteful. How does the CVS code hold up? You can download binaries from the sourceforge download page... URL? Keith _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
