On Tue, 17 Feb 2004 08:59:20 -0300 Rafael Maximo <[EMAIL PROTECTED]> wrote:
> At 07:45 PM 14/2/2004, Felix Kühling wrote: > > >I'm downloading the game just now. :) I get another reproducable hard > >lockup when the glblur xscreensaver hack exits. I havn't had time to > >look into it yet. Can you try if setting SAVAGE_CMD_DMA to 0 in > >savagedma.h helps. Just a guess. > > > >Note that multiple contexts are almost certain to lock up the chip if > >SAVAGE_CMD_DMA is set to 1. > > > > I got the latest driver on CVS yesterday and i noticed that now DMA is > disabled by default and i used to get about 500FPS on glxgears with DMA > enabled and now i get only 300FPS (DMA disabled) and as you said with DMA > disabled the driver is more stable and i didn't get any lockup. Does that > indicate it is a problem with DMA? That's what I hoped. But unfortunately that's not the case. Now the driver locks up in other situations that were fine before. Disabling DMA apparently just masked the problem in some cases. I discussed this with Alex on IRC yesterday. I'm going to try to use a feature called shadow status which may prevent lockups. When the lockups are sorted out and when I manage to get DMA working on SavageIX I might enable it by default again. Anyway, the DMA stuff will change a lot in the future. Using mixed command and vertex DMA buffers like the driver does now is a security nightmare (mach64 has this problem). Unlike Mach64, Savage chips also have the capability to use pure vertex DMA buffers. Then simple indexed drawing commands can be submitted via the BCI. I think this would be the way to go. Regards, Felix ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56&alloc_id438&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel