--- Felix Kühling <[EMAIL PROTECTED]> wrote: > Hi, > > I just took a brief look at the savage 2D driver. It looks like the > COB > is never enabled. On Savage4 and ProSavages it explicitly left > disabled > in SavageInitialize2DEngine. On the Savage3D/MX/IX that function is > never even called. Yet I'm surprised that the 3D driver doesn't crash > and burn all the time, since it assumes quite a large COB. Am I > missing > something?
According to Tim (savage_driver.c): /* * The Savage4 and ProSavage have COB coherency bugs which render * the buffer useless. COB seems to make the SuperSavage slower. * We disable it. */ Hence, I left it disabled. SavageInitialize2DEngine() gets called for all chips in SavageWriteMode() when using the bios. It looks like SavageInitialize2DEngine() should be called in the non-bios case as well... I'm not sure why it is commented out. I'll check into it. Alex > > I thought this may be responsible for occasional lockups. But it's > not. > A reproducible lockup with flightgear doesn't go away if I limit the > used FIFO size to 32 entries. > > Regards, > Felix __________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html ------------------------------------------------------- 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_id=1356&alloc_id=3438&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
