🚀 go-pugleaf

ultrasparc3@hotmail.com wrote:
> In <bctcuf$fj2$1@jedi.apana.org.au> cd@lios.apana.org.au (Kralizec Craig) writes:
> 
>>Make absolutely sure you configure the Xservers file correctly too - to get
>>the best performance you *must* run Xsun in Truecolor mode. This means you
>>need to specify:
> 
> 
> and if you have SX-optimized software (XIL pipelines, etc) you should
> reserve some of your memory for the SX to use.  it requires a chunk
> of physically-contiguous memory for best operation since it operates
> on physical, not virtual, addresses.  the sx_cmem kernel module did
> that and you really only got excellent performance using the graphics
> plug-ins (XIL pipelines, etc.) that made use of sx_cmem.  there was a
> sxconfig program that would set it up for you.  refer to the man page
> for details.
> 

Oh, I reserved 32MB of contiguous memory, but both imagetool & showmetv 
(which are linked against the xil libraries) run really slow. In 
particular, window scrolling in imagetool is a joke. And image 
operations using the pallete (rotations in particular) often lead to 
image corruption in my system.

> 
>>Using a single SM71 CPU doesn't help either. You *need* as much CPU
>>brute-force as possible when using any 24-bit video platform, and since the
>>SX/cg14 is tied directly into the local buses on the SS20 system board,
>>better CPU performance translates directly into better video performance.
> 
> 
> SuperSPARC-only modules also did a better (at least until processors
> faster than 60MHz showed up) since having the SuperCACHE would add a
> cycle or two of latency to the MBus accesses which is how you talk
> to the cg14.

Interesting. So you traded cpu performance for gfx performance. Great 
design.