Re: [Dri-devel] Slow MGA G400 and Return to castle Wolfenstein (and others)

2001-10-24 Thread ralf willenbacher
B. van den Heuvel wrote: But will it help if I lower my resolution ? yep, and to reduce the color depth. its printed in the X log: (II) MGA(0): Reserved 12288 kb for textures at offset 0x140 but i just realized that my g400 box still runs with some patch i made. (no, i wont pollute the

Re: [Dri-devel] Slow MGA G400 and Return to castle Wolfenstein (and others)

2001-10-24 Thread Keith Whitwell
ralf willenbacher wrote: B. van den Heuvel wrote: But will it help if I lower my resolution ? yep, and to reduce the color depth. its printed in the X log: (II) MGA(0): Reserved 12288 kb for textures at offset 0x140 but i just realized that my g400 box still runs with some

Re: [Dri-devel] Mach64: cannot map registers

2001-10-24 Thread Carl Busjahn
Your depth is 24. 3D depths are only 16bit and 32bit. The Mach64 is really not powerful enough to handle 32bit (which is what 24 yeilds in XFree86 4.1). I'm not even sure if the driver supports 32bit depth, but it's not a good idea anyway. Plus you're going to get better overall quality

[Dri-devel] Need assistance compiling mesa-4-0-branch

2001-10-24 Thread Daniel T. Chen
Hi folks, I'm attempting to incorporate DRI's mesa-4-0-branch into my current X 4.1.0.1 (Debian sid from X 4_1 branch) setup but am running into difficulties. I checked out the mesa-4-0-branch and created the build tree as the DRI compilation guide instructed (which btw is rather

Re: [Dri-devel] Mach64: cannot map registers

2001-10-24 Thread Gareth Hughes
Frank C. Earl wrote: On Wednesday 24 October 2001 07:17 pm, Carl Busjahn wrote: Your depth is 24. 3D depths are only 16bit and 32bit. The Mach64 is really not powerful enough to handle 32bit (which is what 24 yeilds in XFree86 4.1). I'm not even sure if the driver supports 32bit depth, but

Re: [Dri-devel] mach64 dma question

2001-10-24 Thread Frank C . Earl
On Wednesday 24 October 2001 01:54 am, [EMAIL PROTECTED] wrote: a=readl(kms-reg_aperture+MACH64_BUS_CNTL); writel((a | (31) )(~(16)), kms-reg_aperture+MACH64_BUS_CNTL); same other code works fine. Now why would this be ? This could be caused by the same thing

Re: [Dri-devel] Mach64: cannot map registers

2001-10-24 Thread Frank C . Earl
On Wednesday 24 October 2001 11:30 pm, Gareth Hughes wrote: Hmm, in a day where you can get PC graphics hardware that can run Quake3 at 1600x1200@32 with maximum quality settings at around 100 fps, perhaps you should reevaluate your idea of powerful enough... Now, now, not everybody can use

Re: [Dri-devel] Mach64: cannot map registers

2001-10-24 Thread Gareth Hughes
Frank C. Earl wrote: Now, now, not everybody can use your employer's gear, Gareth... :- It's not hard to get something rather more powerful than a Rage Pro -- anandtech.com lists current-generation hardware for under $120. One would guess going back a generation or two would bring the