I tried the patch with a G400 16MB and a VIA KX133 chipset. Hard locked every time I tried to run Q3a or UT. Now I see why you don't have it enabled :) -- John Tobin [EMAIL PROTECTED] http://ogre.rocky-road.net http://ogre.rocky-road.net/cdr.shtml > > Message: 6 > From: Steven Newbury <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: [Dri-devel] mga.o still doesn't use AGP memory for g200 ? > Date: Thu, 24 May 2001 04:59:19 +0100 > Cc: [EMAIL PROTECTED] > > >>Aaron Holtzman wrote: >> >>>It would seem that Gareth Hughes ([EMAIL PROTECTED]) said: >>> >>>>At no time has the Matrox DRI driver used AGP memory for textures. >>>> >>>Can you give us a quick outline of the work required to make this >>>happen? >>> >>>cheers, >>>aaron >>> >>> >>well.. i tried but couldnt make it stable. >>one client works from for some time but two wont. >>i guess its because i still couldnt figure out how to sync >>texture uploads between contexts. >>agptexture support was pretty complete anyway :) >>when someone else wants to take a look.... >> > [patch snipped] > > I have been trying your patch against the current XFree86-CVS and it seems to > work quite well with my G400MAX. running quake2,Q3A and xscreensaver hacks. > Running at 1600x1200x32 with 32Mb allocated to agpsize I did not encounter > any instability. I have been playing Q3 with no crashes at all - even > running lament from XScreenSaver 3.32 at the same time doesn't seem to cause > any problems. > > There are a couple of quirks though, The option AGPSize seems to have no > effect, I haven't looked into this but I suppose it should be quite an easy > fix. For my tests I just hardcoded the agpsize in mga_dri.c. > > There does seem to be a strange problem with Q3 when running in vertex mode. > The frame rate drops down to 5-7 FPS for short periods in certain places. It > seems like is doing a texture upload but it keeps doing it.. Running in > lightmap mode seems okay. It doesn't seem to matter what detail textures > are used either, it runs fine at maximum with lightmap turned on. > > I did encounter problems when I tried settimg the onboard texture memory to > zero though. Normally at 1600x1200x32 I have about 2.5Mb left for textures > on my G400, wIth it set to zero, Q3 seemed okay when first run but suffered > texture upload errors of some kind and died when the video was restarted. > Also the Q3 cinematics ran in Mach64/Voodoo compatibility mode?!? > > My system is: G400MAX, AMD K6-2@550, Microstar ALI chipset motherboard,128Mb > 100Mhz SDRAM AGP2x linux-2.4.4-ac9+tux+imon RedHat-7.1 (gcc-2.96) > > Now all I need to do is to upgrade my K6-2 to an Athlon and run at AGP4x > with 266Mhz ram :) > > > --__--__-- > > Message: 7 > From: Steven Newbury <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: [Dri-devel] mga.o still doesn't use AGP memory for g200 ? > Date: Thu, 24 May 2001 10:24:06 +0100 > Cc: [EMAIL PROTECTED] > > On Thursday 24 May 2001 04:59, Steven Newbury wrote: > >>>Aaron Holtzman wrote: >>> >>>>It would seem that Gareth Hughes ([EMAIL PROTECTED]) said: >>>> >>>>>At no time has the Matrox DRI driver used AGP memory for textures. >>>>> >>>>Can you give us a quick outline of the work required to make this >>>>happen? >>>> >>>>cheers, >>>>aaron >>>> >>>well.. i tried but couldnt make it stable. >>>one client works from for some time but two wont. >>>i guess its because i still couldnt figure out how to sync >>>texture uploads between contexts. >>>agptexture support was pretty complete anyway :) >>>when someone else wants to take a look.... _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
