Article View: comp.sys.sun.hardware
Article #2595Re: SS20 too slow for 2D or hw malfunction?
From: ultrasparc3
Date: Fri, 20 Jun 2003 07:34
Date: Fri, 20 Jun 2003 07:34
23 lines
2743 bytes
2743 bytes
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. >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.
Technical Details
Message-ID:
<2003520.02731.14904@cable.prodigy.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!feed2.news.rcn.net!rcn!elnk-nf1-atl!newsfeed.earthlink.net!prodigy.com!newsmst01.news.prodigy.com!prodigy.com!postmaster.news.prodigy.com!newssvr21.news.prodigy.com.POSTED!8c99c469!not-for-mailReferences:
<3EEFB4DA.53AF5BAC@neoholistic.org> <bctcuf$fj2$1@jedi.apana.org.au>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f4671,8b1b6e084b2535a8 X-Google-Attributes: gidf4671,public X-Google-Thread: 113606,8e82577aad67e10b X-Google-Attributes: gid113606,public X-Google-Thread: 10d053,8e82577aad67e10b X-Google-Attributes: gid10d053,public X-Google-ArrivalTime: 2003-06-20 00:35:07 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!feed2.news.rcn.net!rcn!elnk-nf1-atl!newsfeed.earthlink.net!prodigy.com!newsmst01.news.prodigy.com!prodigy.com!postmaster.news.prodigy.com!newssvr21.news.prodigy.com.POSTED!8c99c469!not-for-mail Newsgroups: comp.sys.sun.hardware,aus.computers.sun,uk.comp.sys.sun Subject: Re: SS20 too slow for 2D or hw malfunction? References: <3EEFB4DA.53AF5BAC@neoholistic.org> <bctcuf$fj2$1@jedi.apana.org.au> Message-ID: <2003520.02731.14904@cable.prodigy.com> From: ultrasparc3@hotmail.com Organization: SPARCs'R'Us User-Agent: nn/6.6.5 Lines: 23 NNTP-Posting-Host: 66.125.228.119 X-Complaints-To: abuse@prodigy.net X-Trace: newssvr21.news.prodigy.com 1056094470 ST000 66.125.228.119 (Fri, 20 Jun 2003 03:34:30 EDT) NNTP-Posting-Date: Fri, 20 Jun 2003 03:34:30 EDT X-UserInfo1: FKPO@MONZRUYCU\Y\BCD^VX@WB]^PCPDLXUNNH\KMAVNDQUBLNTC@AWZWDXZXQ[K\FFSKCVM@F_N_DOBWVWG__LG@VVOIPLIGX\\BU_B@\P\PFX\B[APHTWAHDCKJF^NHD[YJAZMCY_CWG[SX\Y]^KC\HSZRWSWKGAY_PC[BQ[BXAS\F\\@DMTLFZFUE@\VL Date: Fri, 20 Jun 2003 07:34:30 GMT