On Thu, Jan 20, 2000 at 02:51:47PM +0000, Neal Tringham wrote:
> Is there anything that me or Eero could do to help people track down
> this problem more precisely?
If this happens at random times, then I'd be more suspicious of hardware
failures than anything else. Either the board overheating or just dieing.
If it is reproducable, then you can help track it down. Get the Glide
sources from http://linux.3dfx.com. You should be able to get them to
build under Windows, hopefully without too much trouble. If you look in
swlibs/include/<whichever make product you use>/3dfx.mak for the line
that says # DEBUG = xx. Remove the comment and turn on deubgging.
Glide with debugging on will report a number of bad types of data being
sent to the board. See where it hangs. It will most likely be hung
waiting for the FIFO. That means the board itself has hung. The
instruction that caused the hang will have happened earlier.
The easiest way to hang the fifo is to send a triangle with bad
values. That means values > 2048 or < -2048. For the V1 and Rush it also
means triangles that aren't snapped to floating point values of 1/16.
That should be enough instructions to get you started debugging the
Voodoo boards. If you run into questions, let me know.
- |Daryll
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
