Platform Notes: SPARCstation 10SX and SPARCstation 20 System Configuration Guide
Cover

Platform Notes: SPARCstation

(TM)

10SX

and SPARCstation 20 System

Configuration Guide


Sun Microsystems Computer Company
2550 Garcia Avenue
Mountain View, CA 94043 USA
415 960-1300
fax 415 969-9131
Part No: 802-3726-10
Revision A, November 1995
Credits
(C) 1995 Sun Microsystems, Inc. 2550 Garcia Avenue, Mountain View, California 94043-1100 U.S.A.
All rights reserved. This product and related documentation are protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or related documentation may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any.
Portions of this product may be derived from the UNIX(R) and Berkeley 4.3 BSD systems, licensed from UNIX System Laboratories, Inc. and the University of California, respectively. Third-party font software in this product is protected by copyright and licensed from Sun's Font Suppliers.
RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the United States Government is subject to the restrictions set forth in DFARS 252.227-7013 (c)(1)(ii) and FAR 52.227-19.
The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications.
TRADEMARKS Sun, Sun Microsystems, the Sun logo, Sun Microsystems Computer Corporation, the SMCC logo, SunSoft, the SunSoft logo, Solaris, SunOS, OpenWindows,XGL,XIL, DeskSet, ONC, and NFS are trademarks or registered trademarks of Sun Microsystems, Inc. UNIX and OPEN LOOK are registered trademarks of UNIX System Laboratories, Inc. All other product names mentioned herein are the trademarks of their respective owners.
All SPARC trademarks, including the SCD Compliant Logo, are trademarks or registered trademarks of SPARC International, Inc. SPARCstation, SPARCserver, SPARCengine, SPARCworks, and SPARCompiler are licensed exclusively to Sun Microsystems, Inc. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.
The OPEN LOOK(R) and Sun(TM) Graphical User Interfaces were developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun's licensees who implement OPEN LOOK GUIs and otherwise comply with Sun's written license agreements.
X Window System is a trademark and product of the Massachusetts Institute of Technology.
THIS PUBLICATION IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS PUBLICATION COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THE PUBLICATION. SUN MICROSYSTEMS, INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS PUBLICATION AT ANY TIME.
FrenchCopyright
Copyright 1995 Sun Microsystems, Inc., 2550 Garcia Avenue, Mountain View, Californie 94043-1100 U.S.A.
Tous droits réservés. Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignent l'utilisation, la copie et la décompilation. Aucune partie de ce produit ou de sa documentation associée ne peut être reproduits sous aucune forme, par quelque moyen que ce soit sans l'autorisation préalable et écrite de Sun et de ses bailleurs de licence, s'il y en a.
Des parties de ce produit pourront être derivées du système UNIX(R) et du système Berkeley 4.3 BSD licencié par l'Université de Californie. UNIX est une marque enregistrée aux Etats-Unis et dans d'autres pays, et licenciée exclusivement par X/Open Company Ltd. Le logiciel détenu par des tiers, et qui comprend la technologie relative aux polices de caractères, est protégé par un copyright et licencié par des fournisseurs de Sun.
Sun, Sun Microsystems, le logo Sun, et Solaris sont des marques déposées ou enregistrées par Sun Microsystems, Inc. aux Etats-Unis et dans certains d'autres pays. Toutes les marques SPARC, utilisées sous license, sont des marques déposées ou enregistrées de SPARC International, Inc. aux Etats-Unis et dans d'autres pays. Les produits portant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc.
Les utilisateurs d'interfaces graphiques OPEN LOOK(R) et Sun(TM) ont été développés par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sun reconnaît les efforts de pionniers de Xerox pour la recherche et le développement du concept des interfaces d'utilisation visuelle ou graphique pour l'industrie de l'informatique. Sun détient une licence non exclusive de Xerox sur l'interface d'utilisation graphique, cette licence couvrant aussi les licenciés de Sun qui mettent en place OPEN LOOK GUIs et qui en outre se conforment aux licences écrites de Sun.
Le système X Window est un produit du X Consortium, Inc.
CETTE PUBLICATION EST FOURNIE "EN L'ETAT" SANS GARANTIE D'AUCUNE SORTE, NI EXPRESSE NI IMPLICITE, Y COMPRIS, ET SANS QUE CETTE LISTE NE SOIT LIMITATIVE, DES GARANTIES CONCERNANT LA VALEUR MARCHANDE, L'APTITUDE DES PRODUITS A REPONDRE A UNE UTILISATION PARTICULIERE OU LE FAIT QU'ILS NE SOIENT PAS CONTREFAISANTS DE PRODUITS DE TIERS.
Contents

............................Contents

..Preface xi

1. Introduction to Graphics on the SPARCstation 10SX and
..SPARCstation 20 1-1

2. Reserving DRAM for SX Accelerated Applications 		2-1
..2.1 Introduction 2-1
..2.2 Advantages of Using SXDRAM 2-2
..2.3 When to Reserve SXDRAM 2-2
..2.4 Calculating SXDRAM to Reserve 2-2
..2.5 Configuring SXDRAM 2-3
.....2.5.1 Memory Bank Layout on the SPARCstation 10SX . 2-3
.....2.5.2 Memory Bank Layout on the SPARCstation 20 2-7
.....2.5.3 System Software Constraints for SXDRAM
..........Configuration 2-7
.....2.5.4 Recommended DSIMM/VSIMM Configuration for the
..........SPARCstation 10SX 2-8
.....2.5.5 SXDRAM Configuration 2-9

3. Running OpenWindows on the SPARCstation 10SX and
..SPARCstation 20 3-1
...3.1 CG14 Pixel Modes for Running the Window System 3-1
...3.2 Visuals Supported By Openwindows 3.3 3-2
...3.3 False Color Effects 3-3

4. XIL Acceleration on SX 		4-1
...4.1 SX XIL Features 4-1
.....4.1.1 Imaging Molecules 4-5

5. XGL Accelerator Guide for SX 		5-1
...5.1 Overview 5-1
...5.2 Texture Mapping 5-3
...5.3 X Visuals 5-3
.....5.3.1 XGL_3D_CTX_JITTER_OFFSET 5-4
.....5.3.2 SIGFPE 5-4
.....5.3.3 XGL_CTX_PICK_APERTURE 5-4
.....5.3.4 XGL_DEV_COLOR_TYPE and
..........XGL_DEV_REAL_COLOR_TYPE 5-4
...5.4 Antialiasing 5-4
...5.5 Performance Considerations 5-5

A. Boot Messages 		A-1
Tables

............................Tables

Table 2-1 SPARCstation 10SX System Memory Layout 16 MByte DSIMMs only2-5
Table 2-2 SPARCstation 10SX System Memory Layout 1 4 MByte VSIMM, 7 16 MByte DSIMMs2-5
Table 2-3 SPARCstation 10SX System Memory Layout 1 4 MByte VSIMM, 7 64 MByte DSIMMs2-6
Table 2-4 Comparing Slot Locations on the SPARCstation 10SX and SPARCstation 202-7
Table 4-1 Dyadic Functions4-2
Table 4-2 Other Imaging Functions4-3
Table 4-3 Convolution Kernel Sizes Supported on SPARCstation 10SX and SPARCstation 204-4
Table 4-4 Variations of xil_lookup Supported on SPARCstation 10SX and SPARCstation 204-5
Table 4-5 Variations of xil_color_convert Supported on SPARCstation 10SX and SPARCstation 204-5
Table 4-6 Imaging Molecules4-6
Figures

............................Figures

Figure 2-1 Memory Layout on Mother Board of SPARCstation 10SX2-4
Preface

Preface

This manual, Platform Notes: SPARCstation 10SX and SPARCstation 20, describes the machine-dependent functionalities of the Solaris(R) 2.x graphics and window system APIs (Application Program Interfaces) such as XGL(TM)(2-D and 3-D Graphics Library), XIL(TM) (X Imaging Library), and Xlib, as related to the SX video subsystem. In addition, this document describes configuring and tuning the SX video subsystem to enhance the performance of the applications using the XGL and XIL APIs.
This document should be used as an addendum to the Solaris 2.x document set and the SPARCstation 10SX Hardware Owner's Guide or SPARCstation 20 Hardware Owner's Guide.

Who Should Use This Book

This book is intended for developers who want to tune the SPARCstation(TM) 10SX or SPARCstation 20 video subsystem for using OpenWindows(TM), XGL, or XIL applications.

How This Book Is Organized

Chapter 1, "Introduction to Graphics on the SPARCstation 10SX and SPARCstation 20", gives a brief description of the SPARCstation 10SX and 20SX.
Chapter 2, "Reserving DRAM for SX Accelerated Applications", discusses issues pertinent to configuring the SPARCstation 10SX to enhance Sun Pixel Arithmetic Memory processor (SX) accelerator performance.
Chapter 3, "Running OpenWindows on the SPARCstation 10SX and SPARCstation 20", discusses the visuals that are present when running OpenWindows on the SPARCstation 10SX.
Chapter 4, "XIL Acceleration on SX", covers commonly-used XIL functions which have been accelerated on the SX.
Chapter 5, "XGL Accelerator Guide for SX", discusses the operation of XGL 3.0.2 on the SX.
Appendix A, "Boot Messages", shows messages displayed on the SPARCstation 10SX or 20SX during the boot process following SXDRAM configuration.

What Typographic Changes Mean

The following table describes the typographic changes used in this book.
Table P-1 Typographic Conventions
Typeface or SymbolMeaningExample
AaBbCc123The names of commands, files, and directories; on-screen computer outputEdit your .login file. Use ls -a to list all files. machine_name% You have mail.
AaBbCc123What you type, contrasted with on-screen computer output

 machine_name%su  
 Password:
AaBbCc123Command-line placeholder: replace with a real name or valueTo delete a file, type rm filename.
AaBbCc123Book titles, new words or terms, or words to be emphasizedRead Chapter 6 in User's Guide. These are called class options. You must be root to do this.

Shell Prompts in Command Examples

The following table shows the default system prompt and superuser prompt for the C shell, Bourne shell, and Korn shell.
Table P-2 Shell Prompts
ShellPrompt
C shell promptmachine_name%
C shell superuser promptmachine_name#
Bourne shell and Korn shell prompt$
Bourne shell and Korn shell superuser prompt#

Ordering Sun Documents

The SunDocs(TM) Order Desk is a distribution center for Sun Microsystems technical documentation. You can use major credit cards and company purchase orders. You can order documentation in the following ways:
In the U.S.A.Outside the U.S.A.
Call 1-800-247-0250Call 1-801-342-3450
Fax 1-801-373-6798Fax 1-801-373-6798
World Wide Web: http://www.sun.com/sundocs/catalog.html

Sun Welcomes Your Comments

Please use the Reader Comment Card that accompanies this document. We are interested in improving our documentation and welcome your comments and suggestions.
If a card is not attached, you can also email or fax your comments to us. Please include the part number of your document in the subject line of your email or fax message.
  • Email: smcc-docs@sun.com
Fax: SMCC Document Feedback
1-415-786-6443
1 Introduction to Graphics on the SPARCstation 10SX and SPARCstation 20

Introduction to Graphics on the SPARCstation 10SX and SPARCstation 20

1

The SPARCstation 10SX is a variant of the SPARCstation 10. The critical architectural difference between the SPARCstation 10 and the SPARCstation 10SX is the video subsystem. The SPARCstation 10SX integrates the graphics/imaging accelerator into the system memory controller. This assembly is referred to as the Scalable Memory Controller (SMC). SMC is an integer vector processor which is used for graphics and imaging acceleration. The accelerator renders directly into DRAM or video RAM. The SMCC official product name for the graphics/imaging accelerator is SX.
All SPARCstation 20 machines have the SX graphics/imaging accelerator.
The video RAM (here referred to as the frame buffer) for the SPARCstation 10SX is integrated into the system main memory address space. It is available on a video SIMM card (VSIMM) in two configurations:
  • With 4 MBytes of video RAM
  • With 8 MBytes of video RAM.
This frame buffer offers true color functionality.
The video SIMM by itself functions as a dumb frame buffer. The acceleration when rendering to the video memory is provided by the SX imaging and graphics accelerator. The SMCC official product name for the frame buffer in SPARCstation 10SX and SPARCstation 20 workstations is cgfourteen.
2 Reserving DRAM for SX Accelerated Applications

Reserving DRAM for SX Accelerated Applications

2

2.1 Introduction

2.1 Introduction

One of the performance enhancements for SX applications is the availability of physically contiguous DRAM. Physically contiguous DRAM for SX will be referred to in this document as SXDRAM. This document describes:
  • The process of configuring SXDRAM for exclusive use by the SX accelerated applications.
  • The application context in which SXDRAM is used
  • The advantages of using SXDRAM
SX provides acceleration of the graphics and imaging segments of applications that run on a SPARCstation 10SX or SPARCstation 20 workstation. Acceleration can be used for a wide range of pixel operations, including 2D and 3D graphics rendering, multimedia, and image processing.
The SX accelerator, built into the SMC, can directly accelerate operations on both the system main memory (DRAM) and the video memory (VRAM). The SMC is comprised of:
  1. An error-correcting code memory controller which interfaces with both the system main memory (DRAM) and the video memory (VRAM; the frame buffer) to the system memory bus.

  2. The SX imaging and graphics accelerator.

2.2 Advantages of Using SXDRAM

2.2 Advantages of Using SXDRAM

As a configuration option, you can reserve SXDRAM. When SXDRAM is reserved, the SX has additional optimizations available to it when accessing SXDRAM, and operations on SXDRAM execute more quickly. The reserved memory, however, is then not available for use by other applications. For example, on a 48-megabyte system, allocating 16 megabytes of SXDRAM means that the system will in effect run as a 32-megabyte system.
2.3 When to Reserve SXDRAM

2.3 When to Reserve SXDRAM

CAUTION Caution - The memory reserved for SXDRAM will not be available for system use. When reserving SXDRAM, consider the amount of memory left for system use. Ensure that there is sufficient memory left for system use that system performance is not adversely affected.
Reserving SXDRAM can improve the performance of an application that uses the foundation libraries XIL or XGL.
The default configuration is to use no SXDRAM. XGL uses SXDRAM for Z buffers and double-buffering. Typically, 8 MBytes of SXDRAM must be reserved if both Z-buffering and double-buffering are used. 4 MBytes must be reserved when Z-buffering is used or when double-buffering is used alone.
XIL uses SXDRAM for table lookup operations and for image rotation operations. For table lookup operations, the SXDRAM size varies between 256 bytes and 128K bytes. However, the minimum SXDRAM that can be configured is 1 MByte.
For image rotation operations, the amount of SXDRAM that must be reserved should be the same as the size of the image, rounded up to the nearest integer multiple of 1 MByte. For example, a 1200 x 1200 image with four 8-bit channels per pixel will fit in 5.493 MBytes, requiring 6 MBytes of SXDRAM.
2.4 Calculating SXDRAM to Reserve

2.4 Calculating SXDRAM to Reserve

To calculate the amount of SXDRAM to reserve, add up the individual requirements and round up to the next multiple of 1 MByte. The individual requirements are:
  1. The XGL Z buffer requires 4 bytes per pixel. The XGL back buffer is required only for RGB double buffering, and is also 4 bytes per pixel. For example, if the application uses an animated 24-bit Z-buffered raster that is limited to 900 x 900 pixels, then the SXDRAM requirement is 900 x 900 x 8 = 6480000 . 7 MBytes (1048576 x 7 bytes).

  2. The XIL lookup tables require 128K bytes of SXDRAM per table used. For operations such as image rotation, enough SXDRAM to store the entire source image should be reserved.

2.5 Configuring SXDRAM

2.5 Configuring SXDRAM

This section lists the steps to follow in order to configure SXDRAM. It also discusses the constraints imposed by the system software and hardware. It is essential that you understand the system memory map before you configure SXDRAM.
Note that there are some key differences in the way memory is arranged on the SPARCstation 10SX and the SPARCstation 20:
  • The physical sequence of slots is different
  • The slots that can use VSIMMs are different
Information specific to the SPARCstation 20 is provided in Section 2.5.2, "Memory Bank Layout on the SPARCstation 20," on page 2-7. To plan SXDRAM configurations for those systems, take this information into account when applying the principles explained in the material covering the SPARCstation 10SX.

2.5.1 Memory Bank Layout on the SPARCstation 10SX

There are two memory banks on a SPARCstation 10SX. Bank 0 is comprised of slots 0, 1, 2, and 3. Bank 1 is comprised of slots 4, 5, 6, and 7. These 8 slots are available for configuring memory on the SPARCstation 10SX. Each bank of memory can map 256 MByte of physical address space. Each slot in each memory bank maps 64 MByte of physical address space.
The beginning physical address for bank 0 is 0. For bank 1, it is 0x10000000.
Slots 4 must be configured with a VSIMM; slot 5 may be configured with either a DSIMM or a VSIMM (CG14). The SPARCstation 10SX supports 16 MByte and 64 MByte DSIMMs, and 4 MByte and 8 MByte VSIMMs. Each slot maps 64 MByte of physical address space regardless of the size and type of SIMM that is configured in the slot.
Figure 2-1 Memory Layout on Mother Board of SPARCstation 10SX

View Image

Table 2-1 below illustrates the physical address map of a system configured with 16 MByte DSIMMS in all the slots
Table 2-1 SPARCstation 10SX System Memory Layout 16 MByte DSIMMs only
SIMM SlotsDSIMM SizePhysical Address
Slot 716 MByte DSIMM0x1c000000
Slot 316 MByte DSIMM0xc000000
Slot 616 MByte DSIMM0x18000000
Slot 216 MByte DSIMM0x8000000
Slot 516 MByte DSIMM0x14000000
Slot 116 MByte DSIMM0x4000000
Slot 416 MByte DSIMM0x10000000
Slot 016 MByte DSIMM0x0
Table 2-2 below illustrates the physical address map of a system configured with one 4 MByte VSIMM installed in slot 4 and 16 MByte DSIMMs in the remaining slots.
Table 2-2 SPARCstation 10SX System Memory Layout 1 4 MByte VSIMM, 7 16 MByte DSIMMs
SIMM SlotsDSIMM/VSIMM SizePhysical Address
Slot 716 MByte DSIMM0x1c000000
Slot 316 MByte DSIMM0xc000000
Slot 616 MByte DSIMM0x18000000
Slot 216 MByte DSIMM0x8000000
Slot 516 MByte DSIMM0x14000000
Slot 116 MByte DSIMM0x4000000
Slot 44 MByte VSIMM0xf0000000
Slot 016 MByte DSIMM0x0
Thus, on systems configured with 16 MByte DSIMMS, the maximum size of a physically contiguous block of DRAM is 16 MByte. However, you can reserve multiple blocks of SXDRAM on such systems. In order to be able to configure a single block of SXDRAM greater than 16 MByte, the system must be configured with 64 MByte DSIMMs.
Table 2-3 illustrates a system configured with one 4 MByte VSIMM and seven 64 MByte DSIMMs.
Table 2-3 SPARCstation 10SX System Memory Layout 1 4 MByte VSIMM, 7 64 MByte DSIMMs
SIMM SlotsDSIMM/VSIMM SizePhysical Address
Slot 764 MByte DSIMM0x1c000000
Slot 364 MByte DSIMM0xc000000
Slot 664 MByte DSIMM0x18000000
Slot 264 MByte DSIMM0x8000000
Slot 564 MByte DSIMM0x14000000
Slot 164 MByte DSIMM0x4000000
Slot 44 MByte VSIMM0xf0000000
Slot 064 MByte DSIMM0x0
This layout results in one contiguous block of 256 MBytes (slots 0, 1, 2, and 3) beginning at physical address 0, and another block of 192 MBytes (slots 4, 5, 6, and 7) beginning at physical address 0x14000000. Therefore, the maximum amount of DRAM that can be installed in this configuration is 448 MBytes.
A typical system will most likely have 16 MByte and 64 MByte DSIMMs, and VSIMMs. There are a large number of possible permutations of the system configuration which, due to space limitations, will not be discussed here.
To be able to allocate the largest possible block of SXDRAM with a given set of VSIMMs and DSIMMs, use the illustrations in this section as a guide.
The next section provides some information unique to the SPARCstation 20. The two sections following that discuss system software constraints and configuration recommendations that involve both systems.

2.5.2 Memory Bank Layout on the SPARCstation 20

On the SPARCstation 20, the physical sequence of slots is different from that slots on the SPARCstation 10SX. The slots that can be used for VSIMMs differ as well. The different layouts are compared in Table 2-4.
Table 2-4 Comparing Slot Locations on the SPARCstation 10SX and SPARCstation 20
Slot Names on
SPARCstation 10SX		Slot Names on
SPARCstation 20
Slot 7Slot 0
Slot 3Slot 2
Slot 6Slot 5
Slot 2Slot 3
Slot 5 (can be VSIMM 1)Slot 6
Slot 1Slot 1
Slot 4 (can be VSIMM 0)Slot 7 (can be VSIMM 0)
Slot 0Slot 4 (can be VSIMM 1)

2.5.3 System Software Constraints for SXDRAM Configuration

The following constraints are described in terms of the SPARCstation 10SX, but the same concerns apply to the SPARCstation 20.
  1. The first slot (slot 0) must always be configured with a DSIMM.

  2. The minimum recommended amount of memory required for reasonable SPARCstation 10SX performance is 32 MByte. Thus, to be able to reserve SXDRAM, a system should be configured with more than 32 MBytes of DRAM. However, users can configure the minimum amount of memory that must be reserved for system use by using the -l option of the sxconfig (1M) command. The difference between the amount of DRAM installed on the system and the configured minimum limit (32 MBytes by default) is the maximum amount of memory that can be reserved for SXDRAM.

  3. The amount of physically contiguous memory that should be reserved must be specified as an integer multiple of 1 MByte. Thus, the minimum amount that can be reserved is 1 MByte.

2.5.4 Recommended DSIMM/VSIMM Configuration for the SPARCstation 10SX

  1. The VSIMM can only be installed in slots 4 or 5 on the SPARCstation 10SX. If there is only one VSIMM, it can be installed in either slot 4 or 5. To install the VSIMM in slot 5, an AVB (Auxiliary Video Board) card is required. This card is not bundled with the SPARCstation 10SX.

  2. Always install a 16 MByte DSIMM in slot 0 when you have a combination of 16 MByte and 64 MByte DSIMMs.

  3. If the memory system consists only of 16 MByte DSIMMs. They can be configured in any slots, provided that the first 16 MByte DSIMM is installed in slot 0.

  4. Within a memory bank, always install the DSIMMs in the order of decreasing DSIMM sizes (the ordering does not matter if all the DSIMMs are of the same size). In other words, if there is a combination of 64 MByte DSIMMs and 16 MByte DSIMMs, install the 64 MByte DSIMM in the lowest-number slot, followed by the 16 MByte in the immediate next slot.

    When configuring the memory subsystem with 64 MByte DSIMMs and 16 MByte DSIMMs, the following examples can be used as a guide:

    System configuration: 1 VSIMM, 2 16 MByte DSIMMs, 2 64 MByte DSIMMs

    Can be configured as:

    1 16 MByte DSIMM in slot 0 1 16 MByte DSIMM in slot 7 1 64 MByte DSIMM in slot 6 1 64 MByte DSIMM in slot 5 1 VSIMM in slot 4

    or

    1 16 MByte DSIMM in slot 0 1 16 MByte DSIMM in slot 3 1 64 MByte DSIMM in slot 2 1 64 MByte DSIMM in slot 1 1 VSIMM in slot 4 or 5

2.5.5 SXDRAM Configuration

The operating system includes a driver for reserving and managing physically contiguous memory. The memory should be reserved as part of the boot process, because it is likely to be the least fragmented at this time, and chances of finding large blocks of physically contiguous memory are higher during boot time.
The amount of SXDRAM to reserve can be specified by using the sxconfig(1M) command. sxconfig can be executed only by a process with superuser privileges. Here are some examples of sxconfig command use.
To disable fragmentation, enter:

  # sxconfig -n
To restore all configuration parameters to the default values, enter:

  # sxconfig -d
By default, 0 MBytes of physically contiguous memory is reserved, fragmentation is not allowed, and 32 MBytes of memory is reserved for system use.
To display the current configuration parameters in the driver configuration file, enter:

  # sxconfig -c
If the system was not booted after the last time the configuration parameters were changed, then the displayed values will not reflect the actual system set-up. For more information about using sxconfig, refer to the on-line man page.
The sxconfig command resides in the directory /platform/SUNW,SPARCstation-10,SX/sbin; the shell environment variable PATH must include this directory. To find out whether the PATH environment variable includes the /platform/SUNW,SPARCstation- 10,SX/sbin directory, type:

  # echo $PATH
Your search path will be displayed. An example:

  /bin:/etc/:/usr/bin:
If the line displayed does not include /platform/SUNW,SPARCstation- 10,SX/sbin, enter the following if you are in either the Bourne shell or the Korn shell:

  # PATH=$PATH:/platform/SUNW,SPARCstation-10,SX/sbin export PATH
followed by:

  # export PATH
if you are in the Bourne shell.
If you are in the C shell, enter:

  # setenv PATH "$PATH /platform/SUNW,SPARCstation-10,SX/sbin"
If 16 MBytes of memory must be reserved, enter:

  # sxconfig -s 16
On a system configured with 16 MByte DSIMMs, the maximum amount of SXDRAM that can be reserved in a single block is 16 MBytes. On such systems, when more than 16 MBytes of memory must be reserved for
SXDRAM, the sxconfig command can be used to specify that fragmented reservation of the requested amount of SXDRAM is allowed. For example, to reserve 32 MBytes of memory on a system configured with 16 MBytes, enter:

  # sxconfig -s 32 -f
sxconfig and reboot causes a search of the system page pool for a contiguous block of memory of the specified size. If the block of memory is found, it is reserved. If fragmentation is specified (as shown above), more than 16 MBytes is specified, and the search fails, the operating system searches for contiguous blocks of 16 MBytes. If no blocks of this size are found, the operating system searches for contiguous blocks of 256 KBytes.
When the SXDRAM configuration is finished, halt the system:

  # halt
The Open Boot PROM prompt is displayed on the console:

  ok
Boot the system by entering:

  ok  boot disk -rv
The -r option specifies a reconfiguration boot. The -v option specifies verbose mode. As part of the boot process, the requested amount of SXDRAM will be reserved. Refer to Appendix A, "Boot Messages" for a listing of the messages that will be displayed.
After the system is rebooted, log in, start OpenWindows, and start the XGL or XIL application of your choice.
3 Running Open Windows on the SPARCstation 10SX and SPARCstation 20

Running OpenWindows on the SPARCstation 10SX and SPARCstation 20

3

This chapter discusses the visuals that are present when running OpenWindows on the SPARCstation 10SX and SPARCstation 20.
3.1 CG14 Pixel Modes for Running the Window System

3.1 CG14 Pixel Modes for Running the Window System

The cgfourteen frame buffer is configurable to scan out either 8-bit pixels or 32-bit pixels. This allows the cgfourteen to be used in high resolution modes. For example, you can configure a 4MByte cgfourteen connected to a multi-sync monitor to display 8-bit pixels at 1280x1024 resolution with the command:

  /platform/SUNW,SPARCstation-10,SX/sbin/cg14config -r  
  1280x1024@66
When the system is rebooted the monitor displays at the new resolution. Since 4MBytes is insufficient memory to have 32 bits per pixel, invoking OpenWindows will automatically select 8-bit pixels only.
The same hardware, when configured to display at 1152x900 resolution with the command:

  /platform/SUNW,SPARCstation-10,SX/sbin/cg14config -r 1152x900@76
will allow OpenWindows to use 32 bits per pixel, after rebooting.
In both modes, the left-over VRAM not displayed on the screen is utilized by the window system for pixmap allocation.
It is possible to use the frame buffer in 8-bit pixel mode even when there is sufficient VRAM for 32-bit pixels. There is a significant performance improvement when the frame buffer is in 8-bit pixel mode. To force the pixel mode, put the verb pixelmode="8" in the OWconfig file used by the server. The OWconfig file is typically in /usr/openwin/server/etc.
A complete entry with this in the file would look like:

  # CG14 display adapter  
  class="XSCREEN" name="SUNWcg14"  
          ddxHandler="ddxSUNWcg14.so.1" ddxInitFunc="sunCG14Init" pixelmode= "8";
3.2 Visuals Supported By Openwindows 3.3

3.2 Visuals Supported By Openwindows 3.3

When the window system runs in 8-bit mode, it exports the same visuals that are exported by Openwindows 3.3 on other 8-bit frame buffers:
  • 8-bit StaticGray
  • 8-bit GrayScale
  • 8-bit StaticColor
  • 8-bit PseudoColor
  • 8-bit TrueColor and
  • 8-bit DirectColor.
Only one hardware color lookup table is available to be shared by all X11 colormaps.
In 32-bit mode, the server supports a 24-bit TrueColor visual, in addition to all of the visuals present in 8-bit mode.
When the server is started with the following option:

  /usr/openwin/bin/openwin -dev /dev/fbs/cgfourteen0 defdepth 8
the default visual, in which the root window is created, is an 8-bit PseudoColor visual.
When the following option is used:

  /usr/openwin/bin/openwin -dev /dev/fbs/cgfourteen0 defdepth 24
the default visual is a 24-bit TrueColor visual.
3.3 False Color Effects

3.3 False Color Effects

The phenomenon of seeing the wrong colors in a window because another X11 colormap is installed in the hardware is called false color.
The best way to avoid false color is to use a TrueColor visual. Since all 32 bits are available for TrueColor visuals, the colors always show up correctly. The SX hardware renders 24-bit visuals with the same speed as it renders 8-bit visuals, so there is no performance penalty when using 24-bit visuals.
In 32-bit mode the StaticGray visual has its own dedicated hardware color lookup table (actually a linear ramp). Hence StaticGray windows in 32-bit mode will never cause other 8-bit windows to appear incorrectly.
4 XIL Acceleration on SX

XIL Acceleration on SX

4

This section covers commonly used XIL functions which have been accelerated on the SPARCstation 10SX system and SPARCstation 20 system for XIL_BYTE and XIL_SHORT images. There are certain restrictions which have been placed on the functions in order for acceleration to occur. If the function is not accelerated on a SPARCstation 10SX system and SPARCstation 20 system, it is performed using the memory driver of XIL.
Two functions, xil_rotate()and xil_affine() require SXDRAM in the amount of the memory required for the source image. In addition, xil_lookup() also requires tables larger than 4096 bytes be stored in SXDRAM. Refer to Chapter 2, "Reserving DRAM for SX Accelerated Applications" for further details on how to allocate SXDRAM.
To obtain optimum performance from the SPARCstation 10SX system, two conditions must be satisfied.
  1. The image must have been touched by the system already. That is, there is a performance penalty the first time the SPARCstation 10SX system and SPARCstation 20 system touches a particular image).

  2. Mixing of the SPARCstation 10SX system and SPARCstation 20 system accelerated and unaccelerated functions must be kept to a minimum.

4.1 SX XIL Features

4.1 SX XIL Features

For dyadic functions, the following restrictions apply:
  • 1, 3, 4 banded XIL_BYTE images.
  • 3 banded child of 4 banded XIL_BYTE image
  • Child images with x,y offsets ok, no band offsets
  • Full support for ROIs
Table 4-1 describes dyadic functions.
Table 4-1 Dyadic Functions
XIL Function1 bandXIL_BYTE 3 bands4 bandsXIL_SHORT n bandsXIL_BYTE Child 3/4
xil_addxxxxx
xil_andxxxxx
xil_multiplyxxxxx
xil_orxxxxx
xil_subtractxxxxx
xil_xorxxxxx
For other imaging functions (see Table 4-2), the following restrictions apply:
  • 1 band XIL_SHORT images
  • 1, 3, 4 band XIL_BYTE images
  • 3-banded child of a 4-banded image
  • Child images w/ x, y offsets, no band offsets
  • Full support for ROIs
Table 4-2 Other Imaging Functions
XIL Function1 bandXIL_BYTE 3 bands4 bandsXIL_SHORT 1 bandXIL_BYTE Child3/4
xil_add_constxxxxx
xil_and_constxxxxx
xil_divide_constxxxxx
xil_multiply_constxxxxx
xil_notxxxxx
xil_or_constxxxxx
xil_subtract_constxxxxx
xil_subtract_from_constxxxxx
xil_xor_constxxxxx
xil_minxxxxx
xil_maxxxxxx
xil_absolute


x
xil_blendxxxxx
xil_paintxxxxx
xil_scalexxxxx
xil_rescalexxxxx
xil_set_valuexxxxx
xil_extremaxxxxx
1 xil_convolvexxxxx
xil_rotate (Nearest Neighbor only, no ROI)xxxxx
xil_affine (Nearest Neighbor only, no ROI) xil_lookup2 xil_color_convert3xxx
x
4 xil_copyxxxxx
Table 4-2 Other Imaging Functions (Continued)
XIL Function1 bandXIL_BYTE 3 bands4 bandsXIL_SHORT 1 bandXIL_BYTE Child3/4
xil_thresholdx

x
xil_transposexxxxx
xil_translatexxxxx
xil_get_pixelxxxxx
xil_put_pixelxxxxx
5 xil_band_combine
6 xil_decompress
7 xil_cast
x
x (3-band)
1. Convolve is implemented for the a limited number of kernels with central key pixels, as shown in Table 4-3.
2. The variations of xil_lookup are implemented, as shown in Table 4-4.
3. The variations of xil_color_convert are implemented, as shown in Table 4-5.
4. Copy function also allows the insertion and extraction of one band from 3/4 banded XIL_BYTE and 3-banded XIL_SHORT images.
5. xil_band_combine has been implemented for 3-banded XIL_SHORT and XIL_BYTE images.
6. For JPEG, the molecules decompress->color_convert->display and decompress->color_convert->scale(2X)->display have been implemented.
7. xil_cast has been implemented for conversion between 3-banded XIL_BYTE and 3-banded XIL_SHORT images, and between 1-banded XIL_BYTE and 1-banded XIL_SHORT images.

Table 4-3 Convolution Kernel Sizes Supported on SPARCstation 10SX and SPARCstation 20
XIL FunctionKernel
xil_convolve3x3
xil_convolve5x5
xil_convolve7x7
xil_convolve3x1/1x3 (molecule)
xil_convolve5x1/1x5 (molecule)
xil_convolve7x1/1x7 (molecule)
Table 4-4 Variations of xil_lookup Supported on SPARCstation 10SX and SPARCstation 20
XIL FunctionFrom-ToBands
xil_lookup8-81 band XIL_BYTE
xil_lookup16_161 band XIL_SHORT
xil_lookup8_161 band XIL_BYTE to XIL_SHORT
xil_lookup16_81 band XIL_SHORT to XIL_BYTE
xil_lookup8_241 band to 3 bands XIL_BYTE
xil_lookup24_243 bands to 3 band XIL_BYTEs
xil_lookup8_321 band to 4 bands XIL_BYTE
xil_lookup32_324 bands to 4 band XIL_BYTE
Table 4-5 Variations of xil_color_convert SPARCstation 20 Supported on SPARCstation 10SX and
Source Colorspace
Destination Colorspace
rgblinear
rgb709
rgblinear
ycc709
rgblinear
ycc601
rgblinear
ylinear
rgblinear
cmyk
ycc601
rgb709
rgb709
rgblinear
rgb709
ycc601
rgb709
photoycc
photoycc
rgb709
cmyk
rgblinear

4.1.1 Imaging Molecules

In addition to decompression molecules, imaging molecules, as described in
Table 4-6, are implemented.
Table 4-6 Imaging Molecules

Function		Bands (XIL_BYTE only)
1 3 4
xil_copy+displayx x x
xil_rotate+displayx x x
xil_scale+displayx x x
xil_set_value+displayx x x
xil_translate+displayx x x
xil_transpose+displayx x x
xil_convolve+xil_convolvex x x (for separable convolution)
5 XGL Accelerator Guide for SX

XGL Accelerator Guide for SX

5

This chapter discusses the operation of XGL 3.1 on SX. It describes the SX and the implementation of the XGL/SX driver so that you can understand how to use their features most effectively.
5.1 Overview

5.1 Overview

The SX is a programmable device that accelerates operations on pixels; for XGL, this includes:
  • Drawing

    · Dots

    · Antialiased dots

    · Lines

    · Antialiased lines

    · Spans

    · Triangles

  • Operations on areas such as:

    · Filling

    · Copying

    · Accumulation buffering

and anything else that involves reading and writing pixel data (color and Z buffer included.) The pixel data can reside either in video ram (the cg14 frame buffer, VRAM), or in main memory (DRAM.)
The SPARCstation 10SX system and SPARCstation 20 system are now used to accelerate all XGL pixel operations except accessing a textured pixel from a texture MipMap when certain attributes are not set
The SX does not support floating point operations. Thus, the transformation, clip checking, clipping, and optionally lighting steps that comprise the 2D and 3D graphics pipeline are done on the CPU. Since the SX runs in parallel with the CPU, typically the CPU will be transforming an object while the SX is rendering the previous object.
The SX has a single hardware context. This context is switched among all processes using SX. For example, using Xlib to render pixels via the server's SX driver, then XGL to render pixels via the XGL/SX driver, will cause a delay as the hardware context is switched between the two processes. Running a performance meter, for example, can cause a noticeable glitch in application animation when the SX context is switched between the meter process and the application. Use of Direct X when mixing Xlib and XGL rendering is highly recommended as, typically, no context switch will occur. The same SX context will be shared between the Xlib rendering calls and the XGL/SX driver. Similarly, mixing XIL, XGL and Direct X in the same process will cause no context switches.
The frame buffer, cg14, supports both 8 and 24 bit drawables, and can have both visible simultaneously. If window identifiers have not all been used up by other 8 bit double-buffered drawables, then the cg14 will use buffer switching for double buffering. Otherwise, the XGL/SX driver uses copy double buffering, using the SX to accelerate the copy. The driver always uses copy double buffering for 24 bit drawables.
The Z buffer is stored in DRAM, with one allocated for each XGL raster that has Z buffering turned on. The SX accelerates Z buffer clearing and comparison.
If SXDRAM is available, the XGL/SX driver will use it for Z buffers, and back buffers as well (if double buffering is enabled, and copy double buffering is being used.) SXDRAM significantly improves line-drawing and context-switching performance. Other pixel operations run about 10%-20% faster.
5.2 Texture Mapping

5.2 Texture Mapping

The 3.1 release of the XGL/SX driver has limited support for accelerated texture mapping of 3d triangle_strips and multi_simple_polygons. All texture mapping functionality is fully supported. If the following XGL attributes are set to the indicated values, then the SPARCstation 10SX system and SPARCstation 20 system hardware is used to render the following textured surfaces:

  XGL_3D_CTX_SURF_FACE_DISTINGUISH       FALSE  
  XGL_3D_CTX_SURF_FRONT_ILLUMINATION     XGL_ILLUM_NONE  
  XGL_3D_CTX_SURF_TMAP_PERSP_CORRECTION  XGL_TEXTURE_PERSP_NONE  
  Xgl_texture_interp_method              XGL_TEXTURE_INTERP_POINT  
   (desc.interp_info.filter1/filter2)  
  Xgl_texture_op                         XGL_TEXTURE_OP_REPLACE  
   (desc.comp_info.render_component_desc[0].texture_op)
You also need sufficient SXDRAM available to hold the texture. Refer to Chapter 2, "Reserving DRAM for SX Accelerated Applications" for further details, such as the size of the texture that should be included when calculating the size of SXDRAM that needs to be reserved.
5.3 X Visuals

5.3 X Visuals

The XGL/SX driver supports the following subset of the available cg14 visuals:
  • 8-bit PseudoColor
  • 8-bit StaticColor
  • 8-bit StaticGray
  • 8-bit GrayScale
  • 24-bit TrueColor
Note that the application must recognize that 8-bit DirectColor and 8-bit TrueColor visuals exist, and be programmed to not use them with XGL (XGL will reject any attempt to make such a visual an XGL raster.) Also, since the window system can come up in defdepth 24 (see the openwin(1) man page), the application should not assume that the root window is of depth 8 with a default colormap available.

5.3.1 XGL_3D_CTX_JITTER_OFFSET

If accumulation buffering (global antialiasing) is intended, a non-zero jitter value must be used. The XGL/SX driver draws Bresenham-style lines in 3D when the X and Y jitter values are exactly zero, and true sampled lines (suitable for accumulation) otherwise.

5.3.2 SIGFPE

To maximize performance, zero divides and floating point overflows are allowed to occur in normal operation of the XGL/SX driver. The default is to ignore these exceptions. If the application enables these exceptions, they should be set up to be ignored before calling XGL.

5.3.3 XGL_CTX_PICK_APERTURE

The SX uses the rasterization semantic for picking. See the Solaris XGL 3.0.2 Reference Manual for a complete description of this semantic.

5.3.4 XGL_DEV_COLOR_TYPE and XGL_DEV_REAL_COLOR_TYPE

The XGL/SX driver supports only matching XGL_DEV_COLOR_TYPE and XGL_DEV_REAL_COLOR_TYPE; they must both be either XGL_COLOR_INDEX or XGL_COLOR_RGB. Otherwise, the slower XGL/Xlib driver will be used to render into the window raster.
5.4 Antialiasing

5.4 Antialiasing

cg14config(1M) should be used to set the gamma value to a reasonable value for your monitor before viewing antialiased lines and dots. A good invocation to start with is

  /platform/SUNW,SPARCstation-10,SX/sbin/cg14config -g 2.2 -u 2.2
Otherwise, the antialiased objects will not look right.
5.5 Performance Considerations

5.5 Performance Considerations

The gcache should be used where possible to draw polygons other than triangles.
Not all rendering functions are equally accelerated by the XGL/SX driver. The greatest effort was focused on maximizing the performance of the most useful ones. The following is a necessarily-incomplete list of these. Please note that functions not on this list are not slow; they are just not as fast as they could be in the next release of the XGL/SX driver. If operations that are critical to your application are not in this list, please make a request for their speed to be increased.
xgl_context_copy_raster()From window raster to window raster.
xgl_multi_marker()2D circles of radii 1 to 32 pixels.
xgl_multi_polyline()In 2D, thin lines, solid or patterned, containing no color or homogeneous values, and with XGL_CTX_ROP equal to XGL_ROP_COPY.

In 3D, thin lines, solid or patterned, containing no color, flag, homogeneous or data values, not model clipped, clipped to +w only, and with XGL_CTX_ROP equal to XGL_ROP_COPY.

xgl_multi_simple_polygon()In 3D, triangles. The hint flags must be set to XGL_FACET_FLAG_SIDES_ARE_3.
xgl_triangle_strip()Triangles that have no homogeneous or data values, are not model clipped, are clipped to +w only, are 24-bit, have edges turned off, are solid and opaque, and have XGL_3D_CTX_Z_BUFFER_COMP_METHOD equal to

XGL_Z_COMP_LESS_THAN_OR_EQUAL.

xgl_context_accumulate()All operations.
A Boot Messages

Boot Messages

A

This Appendix lists messages such as are displayed on the SPARCstation 10SX or SPARCstation 20 during the boot process following SXDRAM configuration. These messages provide information regarding the amount of contiguous memory that has been reserved.

  SunOS Release 5.3 Version alpha2.3 [UNIX(R) System V Release 4.0]  
  Copyright (c) 1983-1993, Sun Microsystems, Inc.  
  pac: enabled - SuperSPARC/SuperCache  
  cpu 0: TI,TMS390Z55 (mid 8 impl 0x0 ver 0x0 clock 40 MHz)  
  mem = 49152K (0x3000000)  
  avail mem = 41820160  
  Ethernet address = 8:0:20:13:0:37  
  root nexus = SUNW,Premier-24  
  iommu0 at root: obio 0xe0000000  
  sbus0 at iommu0: obio 0xe0001000  
  espdma0 at sbus0: SBus slot f 0x400000  
  esp0 at espdma0: SBus slot f 0x800000 sparc ipl 4  
  sd0 at esp0: target 0 lun 0  
  sd0 is /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,  
  800000/sd@0,0  
  <SUN0669 cyl 1614 alt 2 hd 15 sec 54>  
  sd2 at esp0: target 2 lun 0  
  sd2 is /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,  
  800000/sd@2,0  
  <SUN0424 cyl 1151 alt 2 hd 9 sec 80>  
  sd3 at esp0: target 3 lun 0  
  sd3 is /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,  
  800000/sd@3,0  


  <SUN0424 cyl 1151 alt 2 hd 9 sec 80>  
  sd6 at esp0: target 6 lun 0  
  sd6 is /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,  
  800000/sd@6,0  
  <>  
  Unable to install/attach driver 'isp'  
  root on /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,  
  800000/sd@3,0:a fstype ufs  
  obio0 at root  
  zs0 at obio0: obio 0x100000 sparc ipl 12  
  zs0 is /obio/zs@0,100000  
  zs1 at obio0: obio 0x0 sparc ipl 12  
  zs1 is /obio/zs@0,0  
  configuring network interfaces:ledma0 at sbus0: SBus slot f  
  0x400010  
  le0 at ledma0: SBus slot f 0xc00000 sparc ipl 6  
  le0 is /iommu@f,e0000000/sbus@f,e0001000/ledma@f,400010/le@f,  
  c00000  
   le0.  
  Hostname: example  
  dump on /dev/dsk/c0t3d0s1 size 65860K  
  Configuring the /devices directory  
  Unable to install/attach driver 'bwtwo'  
  Unable to install/attach driver 'audio'  
  Unable to install/attach driver 'cgthree'  
  st4:    <Archive QIC-150>  
  st4 at esp0: target 4 lun 0  
  st4 is /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,  
  800000/st@4,0  
  Unable to install/attach driver 'isp'  
  SUNW,fdtwo0 at obio0: obio 0x700000 sparc ipl 11  
  SUNW,fdtwo0 is /obio/SUNW,fdtwo@0,700000  
  Unable to install/attach driver 'cgsix'  
  Unable to install/attach driver 'vme'  
  Unable to install/attach driver 'ipi3sc'  
  Unable to install/attach driver 'id'  
  Unable to install/attach driver 'vme'  
  Unable to install/attach driver 'vmemem'  
  sbusmem0 at sbus0: SBus slot 0 0x0  
  sbusmem0 is /iommu@f,e0000000/sbus@f,e0001000/sbusmem@0,0  
  sbusmem1 at sbus0: SBus slot 1 0x0  
  sbusmem1 is /iommu@f,e0000000/sbus@f,e0001000/sbusmem@1,0  
  sbusmem2 at sbus0: SBus slot 2 0x0  
  sbusmem2 is /iommu@f,e0000000/sbus@f,e0001000/sbusmem@2,0  
  sbusmem3 at sbus0: SBus slot 3 0x0  


  sbusmem3 is /iommu@f,e0000000/sbus@f,e0001000/sbusmem@3,0  
  sbusmem14 at sbus0: SBus slot e 0x0  
  sbusmem14 is /iommu@f,e0000000/sbus@f,e0001000/sbusmem@e,0  
  sbusmem15 at sbus0: SBus slot f 0x0  
  sbusmem15 is /iommu@f,e0000000/sbus@f,e0001000/sbusmem@f,0  
  Unable to install/attach driver 'xbox'  
  SUNW,bpp0 at sbus0: SBus slot f 0x4800000 SBus level 2 sparc ipl 3  
  SUNW,bpp0 is /iommu@f,e0000000/sbus@f,e0001000/SUNW,bpp@f,  
  4800000  
  Unable to install/attach driver 'pn'  
  Unable to install/attach driver 'lebuffer'  
  Unable to install/attach driver 'cgeight'  
  Unable to install/attach driver 'ipi3sc'  
  SUNW,DBRIe0 at sbus0: SBus slot e 0x10000 SBus level 5 sparc ipl 9  
  SUNW,DBRIe0 is /iommu@f,e0000000/sbus@f,e0001000/SUNW,DBRIe@e,  
  10000  
  MMCODEC: Manufacturer id 1, Revision 1  
  pseudo-device: vol0  
  vol0 is /pseudo/vol@0  
  Unable to install/attach driver 'xbox'  
  Unable to install/attach driver 'vme'  
  Unable to install/attach driver 'mcp'  
  Unable to install/attach driver 'vme'  
  Unable to install/attach driver 'mcp'  
  Unable to install/attach driver 'mcpzsa'  
  Unable to install/attach driver 'vme'  
  Unable to install/attach driver 'mcp'  
  Unable to install/attach driver 'mcpp'  
  SUNW,sx0 at root: obio 0x80000000 and obio 0x80001000  
  SUNW,sx0 is /SUNW,sx@f,80000000  
  cgfourteen0 at obio0: obio 0x0 and obio 0x0 sparc ipl 8  
  cgfourteen0 is /obio/cgfourteen@1,0  
  sx_cmem: Installed 112MB  
           Reserved 8MB  
           Fragment 0  
           Avail For System Use 104MB  
  pseudo-device: sx_cmem0  
  sx_cmem0 is /pseudo/sx_cmem@0  
  Unable to install/attach driver 'stc'  
  Unable to install/attach driver 'isp'  
  Unable to install/attach driver 'cgtwelve'  
  Unable to install/attach driver 'gt'  
  Unable to install/attach driver 'leo'  
  Unable to install/attach driver 'rtvc'  
  Unable to install/attach driver 'tcx'  


  Configuring the /dev directory  
  Configuring the /dev directory (compatibility devices)  
  The system is coming up.  Please wait.  
  ...
Index

Index

A

antialiasing5-4

C

cg14frame buffer5-2
cg14 visuals5-3
cgfourteen device driver1-1
configuring SXDRAM2-3 to 2-11

D

double-buffering2-2

F

false color effects3-3

O

OpenWindows on SPARCstation 10SX3-1

S

Scalable Memory Controller (SMC)1-1
SIGFPE5-4
SMC (Scalable Memory Controller)1-1, 2-1
SPARCstation 101-1
SPARCstation 10SX1-1
.....XIL accelerator guide4-1
SPARCstation 201-1
.....XIL accelerator guide4-1
SX hardware context5-2
SX imaging and graphics accelerator1-1, 2-1
SXDRAM2-1 to 2-11
.....calculating amount to reserve2-2
.....configuring2-3 to 2-11
system memory controller1-1

V

video RAM1-1
video subsystem1-1
visuals, supported by OpenWindows3-2
VSIMM1-1

X

XGL 3.0.2 accelerator guide for SX5-1 to 5-5
XGL, use of SXDRAM by2-2 to 2-3
XGL/SX driver5-2, 5-5
XGL_3D_CTX_JITTER_OFFSET5-4
XGL_CTX_PICK_APERTURE5-4
XGL_DEV_COLOR_TYPE5-4
XGL_DEV_REAL_COLOR_TYPE5-4
XIL acceleration on SX4-1 to ??
XIL accelerator guide
.....SPARCstation 10SX and 204-1
XIL, use of SXDRAM by2-2 to 2-3

Z

Z buffer5-2
Z-buffering2-2