Re: [Dri-devel] Hello

[Daryll S. <da...@va...>]

On Mon, Jul 10, 2000 at 01:08:58PM -0400, Hetz Ben Hamo wrote:
> My job here is to support Graphics hardware on Linux - which means any
> hardware that Linux can be used with. The info I will get from my
> experience will be included on our upcoming product which, I cannot talk
> about it yet.
> 
> One of the benefits I have here is that I can get my hands on almost any
> graphics card imaginable. Starting from 16 Bit Trident cards, all the
> way to the latest and greatest graphics cards.
> 
> So, I would like to contribute by testing any hardware needed (if I
> don't have it here - I'll buy 2 copies of it - trust me on that one)
> with any processor combination (Intel/AMD) with any version of DRI -
> public or private.
> 
> So, any hardware testing needed with DRI? I'm ready :)

Hello and Welcome!

To answer the first part of the question there are currently several
boards that run under the DRI:
       The Matrox G200 and G400
       The Intel i810
       The ATI Rage128
       The 3dfx Voodoo Banshee, Voodoo3, and Voodoo5

Many of these boards have multiple configurations, which may increase
the number of boards if you want a full set. We've also been talking to
SiS and Intense3D so boards from those companies may be coming into the
tree in the near future.

The first question that comes to mind is what should you test? We use
what tools we have to do testing before we make releases. xtest is a
suite that tests correctness of 2D operations in the X server. Xmark
measures performance of the 2D X server. Viewperf is a standard 3D
performance measurement. For OpenGL correctness we've been using Glean.
Finally, we do some application testing, by running those applications
we know people are using and making sure they seem to work.

Glean needs more tests. We're looking for contributions there. Writing
good tests is hard, you have to be very careful that you are testing
what you think you are. Take a look at the glean project
http://glean.sourceforge.net if you're interested. 

If you do start testing boards, then I'd like to see two things come out
of this. The obvious first piece is bug reports. We need those fed back
into the bug tracking system so they can be squashed. The second, is
that it would be great if you could produce some web page with results
(performance and correctness) of your testing. This would be something
we could host on SourceForge if you want. It would be very useful if
people could look at single location and get some feel for how well the
various boards are being supported.

						- |Daryll