C H A P T E R 1 |
TurboGXplus Frame Buffer |
This chapter describes how you can configure your system using a TurboGXplus card to suit your specific video and graphics requirements. The information describes how to set up your TurboGXplus to support different screen resolutions and how to set up the system to support multiple monitors.
TABLE 1-1 shows the list of monitors supported by the TurboGXplus card.
Note - The monitors listed in TABLE 1-1 are subject to change as Sun Microsystems announces new monitors. Contact your local Sun representative for a listing of supported monitors. |
1. The default resolution at power-on initialization. 2. Monitor ID sense code is user-selectable by the rear switch. |
TABLE 1-2 lists the default screen resolutions by monitor ID sense code.
Programming the screen resolution for TurboGXplus frame buffers must be done in nvramrc, a nonvolatile PROM script memory. When the PROM reaches the device probing stage, it checks the use-nvramrc? variable and if it is true, executes the Forth code that resides in nvramrc. Otherwise, it calls probe-sbus (for all pre-Ultra systems) or probe-all (for all Ultra systems), install-console, and banner.
The following example places resolution initialization between the probe-sbus (or probe-all) stage and the install-console stage.
First probe-sbus or probe-all is called to probe all devices, so that the device tree is created, and the devices are initialized.
The next line defines a Forth word called vsetup which contains the monitor video setup values.
The following string of values (defined in TABLE 1-3) are the specifications for a video setup:
" 117000000,71691,67,16,112,224,1280,2,8,33,1024,COLOR,0OFFSET" |
The line, vsetup 4, pushes the video string on the stack, the number 4 defines the sense code of the monitor to change the resolution on. See TABLE 1-4 for supported monitor codes. The number used should match the monitor attached to the TurboGXplus frame buffer.
The next line pushes the string /sbus/cgsix@1 onto the Forth stack, the path for the device where the resolution is to be changed. The "1" in cgsix@1 identifies the SBus slot number.
The following example changes the cgsix frame buffer on SBus slot 1.
The "override" string is the actual entry point in the cgsix fcode PROM that reconfigures the resolution from the data on the forth stack. execute-device-method actually calls override and returns a pass or fail flag, which is ignored by the drop command that follows.
The remaining two lines install-console and banner, installs a terminal driver on the display device, then prints the banner at reset time or reboot time.
The following is a UNIX script used to configure the TurboGXplus for a resolution of 1280 x 1024 at 67 Hz.
The following example uses the PROM method to configure the TurboGXplus for a resolution of 1280 x 1024 at 67 Hz.
TABLE 1-1 contains codes for TurboGXplus-supported resolutions:
The following is an example of how to set up a TurboGXplus card in slot 2 to 1024 x 768 at 60 Hz using a 16-inch monitor.
The following is a UNIX script that sets a 1024 x 768 at 60 Hz for the TurboGXplus card in slot 2.
The following example shows a UNIX script that sets up the TurboGXplus card in slot 1 to 1152 x 900 at 76 Hz, and another TurboGXplus card in slot 3 to 1280 x 1024 at 67 Hz using two 19-inch monitors.
For more information on running multiple monitors, see Chapter 12.
Copyright © 2002, Sun Microsystems, Inc. All rights reserved.