[rescue] octane question

[Big Endian]

>Err, you have an octane don't you?  What is it's graphical setup?

No I don't but I've dealt with IMPACT indigo2s and I've done a LOT of 
research on the octane (read mental masturbation over the octane). 
The *I cards on the octane are repackages of the IMPACT cards for 
indigo2s and use XIO instead of GI)64.  Octanes w/ MXI graphics 
report "4 TRAMS" to /usr/gfx/gfxinfo and hinv.  If anybody has seen 
differently I would *LOVE* to be proven wrong (and then grab an MXI 
octane).  The nice thing about XIO is the raw throughput 
(800mb/sec/direction burst)  so you can *STREAM* textures in and out 
of ram.  This is hard to do w/ a lesser machine or even a greater 
machine (EBUS is 1.2GB/sec but its a shared bus and I'm not sure if 
thats a full duplex figure).

>I'll have to write up a sample program to test what the capabilities 
>of octanes
>with low/no TRAM are one of these days.

You can still get CPU based texturing on the SI and SSI cards.  I'm 
sure that it sucks... but you can do it.  The O2, even with all the 
stuff they do on the CPU *HAS* hardware texture because CPU texture 
sucks.  I wouldn't bother testing w/ no TRAMS.

daniel
-- 
-----------------------------------------------------------------
"Fragile. Do not drop." -- Posted on a Boeing 757.