I was feeling a bit frisky yesterday and built new DRI packages for
Debian Unstable using the Xorg xc tree. Any feedback would be greatly
appreciated.
http://www.nixnuts.net/files/experimental/
I'm still wondering where /usr/X11R6/lib/modules/codeconv/ went though.
Is there a define to build
First let me say that if anyone would like to take over updating the
dri-trunk-sid packages on a semi-regular basis, I'd really appreciate
it. I don't track the Debian X or DRI mailing lists closely enough to
keep up with changes.
On Tue, 2004-12-28 at 15:00 -0800, Mike Mestnik wrote:
The
On Wednesday 06 October 2004 06:54, Felix Kühling wrote:
On Mon, 04 Oct 2004 12:09:09 +0100
Keith Whitwell [EMAIL PROTECTED] wrote:
John,
I'd say the problem is with these lines in savagetris.c:
if (index (_TNL_BIT_COLOR1|_TNL_BIT_FOG)) {
EMIT_ATTR( _TNL_ATTRIB_COLOR1,
On Friday 01 October 2004 04:03, Keith Whitwell wrote:
John Lightsey wrote:
A while back I mentioned on dri-devel that Savage cards will segfault
RTCW while loading the Checkpoint demo.
( http://www.nixnuts.net/benchmarks/current/ ) The problem is in
Mesa/src/mesa/tnl/t_tertex.c around
-AttribPtr[a[j].attrib];
a[j].inputstride = vptr-stride;
...
}
vptr is null in the middle of the for loop ( j=2 is null j=0, 1, and 3 is
valid.) I have no idea why this is the case, but I've attached a simple fix
which eliminates the problem.
John Lightsey
--- xc/../Mesa/src/mesa
On Monday 23 August 2004 12:36, Ian Romanick wrote:
John Lightsey wrote:
Once I have all the benchmarks together I'll make some pretty little
graphs.
Soany suggestions, comments, feedback?
First off, great work! Hopefully you'll be willing to re-run those
tests to look
This is my third attempt sending this email. If sourceforge decides to let
all three copies through at once, you'll have to forgive me.
A while back it was suggested that benchmarking all of the various
DRI-compatible video cards might provide some interesting information. I
just finished my
On Sunday 22 August 2004 04:57, Simon 'corecode' Schubert wrote:
On 22.08.2004, at 08:16, John Lightsey wrote:
glxgears - let it run for 1 minute then marked down the highest score
how reproducable and meaningful is a highest score? I don't know, but I
got a feeling that using a mean
On Sunday 22 August 2004 04:59, Felix Kühling wrote:
On Sun, 22 Aug 2004 01:16:18 -0500
John Lightsey [EMAIL PROTECTED] wrote:
Diamond Speedstar a90 16MB (savage 4 pro+) Lots of lockups. glxgears
gave this a disappointing 229 fps.
There are rumors about some Savage4's that lock up when
A while back it was suggested that benchmarking all of the various
DRI-compatible video cards might provide some interesting information. I
just finished my first attempt at performing a slew of benchmarks with this
goal, and the results haven't been great. It's certainly possible that (a)
On Sunday 22 August 2004 01:52, Adam Jackson wrote:
On Sunday 22 August 2004 02:16, John Lightsey wrote:
At any rate, here are the results of the first run. If anyone has
suggestions for fixing any of the cards which failed in one way or
another, I would really appreciate the feedback
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I sent this message earlier, but it doesn't seem to have made it through.
Subject: First DRI uber-benchmark
Date: Saturday 21 August 2004 13:17
From: John Lightsey [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
A while back it was suggested
On Sunday 22 August 2004 05:39, Alan Cox wrote:
On Sul, 2004-08-22 at 07:16, John Lightsey wrote:
I shut off most of the services on the machine. rcconf shows klogd,
makedev, and sysklogd as the only services active at boot. The kernel
used was 2.6.7-1-k7 from Debian.
Which DRI kernel
Here are the FGLRX and Nvidia scores for comparison...
The Nvidia drivers were built from the packages in Debian non-free (1.0.6111)
and the FGLRX drivers were built from Flavio Stanchina's packages (3.11.1).
BFG FX5200 Ultra 128MB
glxgears - 3934.8
q2 640x480 - 337.1
q2 800x600 - 312.3
q2
On Sunday 22 August 2004 18:37, Ville Syrjälä wrote:
On Sun, Aug 22, 2004 at 01:16:18AM -0500, John Lightsey wrote:
Matrox G400 32MB (mga)
...
I'm aware of two perfomance bottlenecks in the driver.
Number one is that it always uses synchronous DMA. I have asynchronous
DMA working just fine
On Thursday 22 July 2004 17:23, Philipp Klaus Krause wrote:
Since the packages from Micahel Dänzer are outdated and don't
contain the S3TC patch we now have the strange situation that the
lates non-free ATI drivers are easier to use on Debian GNU/Linux
than the lates DRI drivers.
Would it be
16 matches
Mail list logo
