<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta name="generator" content=
"HTML Tidy for Linux (vers 1 September 2005), see www.w3.org">
<meta http-equiv="Content-Type" content=
"text/html; charset=us-ascii">
<title>Chapter 26. Configuring Frame Lock and
Genlock</title>
<meta name="generator" content="DocBook XSL Stylesheets V1.68.1">
<link rel="start" href="index.html" title=
"NVIDIA Accelerated Linux Graphics Driver README and Installation Guide">
<link rel="up" href="part-01.html" title=
"Part I. Installation and Configuration Instructions">
<link rel="prev" href="chapter-25.html" title=
"Chapter 25. Configuring SLI and Multi-GPU FrameRendering">
<link rel="next" href="chapter-27.html" title=
"Chapter 27. Configuring SDI Video Output">
</head>
<body>
<div class="navheader">
<table width="100%" summary="Navigation header">
<tr>
<th colspan="3" align="center">Chapter 26. Configuring
Frame Lock and Genlock</th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href=
"chapter-25.html">Prev</a> </td>
<th width="60%" align="center">Part I. Installation and
Configuration Instructions</th>
<td width="20%" align="right"> <a accesskey="n" href=
"chapter-27.html">Next</a></td>
</tr>
</table>
<hr></div>
<div class="chapter" lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a name="framelock" id=
"framelock"></a>Chapter 26. Configuring Frame Lock and
Genlock</h2>
</div>
</div>
</div>
<p>NOTE: Frame Lock and Genlock features are supported only on
specific hardware, as noted below.</p>
<p>Visual computing applications that involve multiple displays, or
even multiple windows within a display, can require special signal
processing and application controls in order to function properly.
For example, in order to produce quality video recording of
animated graphics, the graphics display must be synchronized with
the video camera. As another example, applications presented on
multiple displays must be synchronized in order to complete the
illusion of a larger, virtual canvas.</p>
<p>This synchronization is enabled through the frame lock and
genlock capabilities of the NVIDIA driver. This section describes
the setup and use of frame lock and genlock.</p>
<h3>Definition of Terms</h3>
<p>GENLOCK: Genlock refers to the process of synchronizing the
pixel scanning of one or more displays to an external
synchronization source. NVIDIA Genlock requires the external signal
to be either TTL or composite, such as used for NTSC, PAL, or HDTV.
It should be noted that the NVIDIA Genlock implementation is
guaranteed only to be frame-synchronized, and not necessarily
pixel-synchronized.</p>
<p>FRAME LOCK: Frame Lock involves the use of hardware to
synchronize the frames on each display in a connected system. When
graphics and video are displayed across multiple monitors, frame
locked systems help maintain image continuity to create a virtual
canvas. Frame lock is especially critical for stereo viewing, where
the left and right fields must be in sync across all displays.</p>
<p>In short, to enable genlock means to sync to an external signal.
To enable frame lock means to sync 2 or more display devices to a
signal generated internally by the hardware, and to use both means
to sync 2 or more display devices to an external signal.</p>
<p>SWAP SYNC: Swap sync refers to the synchronization of buffer
swaps of multiple application windows. By means of swap sync,
applications running on multiple systems can synchronize the
application buffer swaps between all the systems. In order to work
across multiple systems, swap sync requires that the systems are
frame locked.</p>
<p>G-SYNC DEVICE: A G-Sync Device refers to devices capable of
Frame lock/Genlock. This can be a graphics card (Quadro FX 3000G)
or a stand alone device (Quadro FX G-Sync). See "Supported
Hardware" below.</p>
<h3>Supported Hardware</h3>
<p>Frame lock and genlock are supported for the following
hardware:</p>
<div class="informaltable">
<table summary="(no summary available)" border="0">
<colgroup>
<col>
<col></colgroup>
<thead>
<tr>
<th>Card</th>
<td class="auto-generated"> </td>
</tr>
</thead>
<tbody>
<tr>
<td>Quadro FX 3000G</td>
<td class="auto-generated"> </td>
</tr>
<tr>
<td>Quadro FX G-Sync, used in conjunction with a Quadro FX 4400,
Quadro FX 4500, or Quadro FX 5500</td>
<td class="auto-generated"> </td>
</tr>
<tr>
<td>Quadro FX G-Sync II, used in conjunction with a Quadro FX 4600,
or Quadro FX 5600</td>
<td class="auto-generated"> </td>
</tr>
</tbody>
</table>
</div>
<p></p>
<h3>Hardware Setup</h3>
<p>Before you begin, you should check that your hardware has been
properly installed. If you are using the Quadro FX 3000G, the
genlock/frame lock signal processing hardware is located on the
dual-slot card itself, and after installing the card, no additional
setup is necessary.</p>
<p>If you are using the Quadro FX G-Sync card in conjunction with a
graphics card, the following additional setup steps are required.
These steps must be performed when the system is off.</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>On the Quadro FX G-Sync card, locate the fourteen-pin connector
labeled "primary". If the associated ribbon cable is not already
joined to this connector, do so now. If you plan to use frame lock
or genlock in conjunction with SLI FrameRendering or Multi-GPU
FrameRendering (see <a href="chapter-25.html" title=
"Chapter 25. Configuring SLI and Multi-GPU FrameRendering">
Chapter 25, <i>Configuring SLI and Multi-GPU
FrameRendering</i></a>) or other multi-GPU configurations, you
should connect the fourteen-pin connector labeled "secondary" to
the second GPU. A section at the end of this appendix describes
restrictions on such setups.</p>
</li>
<li>
<p>Install the Quadro FX G-Sync card in any available slot. Note
that the slot itself is only used for support, so even a known
"bad" slot is acceptable. The slot must be close enough to the
graphics card that the ribbon cable can reach.</p>
</li>
<li>
<p>Connect the other end of the ribbon cable to the fourteen-pin
connector on the graphics card.</p>
</li>
</ol>
</div>
<p>You may now boot the system and begin the software setup of
genlock and/or frame lock. These instructions assume that you have
already successfully installed the NVIDIA Accelerated Linux Driver
Set. If you have not done so, see <a href="chapter-04.html" title=
"Chapter 4. Installing the NVIDIA Driver">Chapter 4,
<i>Installing the NVIDIA Driver</i></a>.</p>
<h3>Configuration with nvidia-settings GUI</h3>
<p>Frame lock and genlock are configured through the
nvidia-settings utility. See the <code class=
"filename">nvidia-settings(1)</code> man page, and the
nvidia-settings online help (click the "Help" button in the lower
right corner of the interface for per-page help information).</p>
<p>From the nvidia-settings frame lock panel, you may control the
addition of G-Sync (and display) devices to the frame lock/genlock
group, monitor the status of that group, and enable/disable frame
lock and genlock.</p>
<p>After the system has booted and X Windows has been started, run
nvidia-settings as</p>
<pre class="screen">
% nvidia-settings
</pre>
<p>You may wish to start this utility before continuing, as we
refer to it frequently in the subsequent discussion.</p>
<p>The setup of genlock and frame lock are described separately. We
then describe the use of genlock and frame lock together.</p>
<h3>Genlock Setup</h3>
<p>After the system has been booted, connect the external signal to
the house sync connector (the BNC connector) on either the graphics
card or the G-Sync card. There is a status LED next to the
connector. A solid red LED indicates that the hardware cannot
detect the timing signal. A green LED indicates that the hardware
is detecting a timing signal. An occasional red flash is okay. The
G-Sync device (graphics card or G-Sync card) will need to be
configured correctly for the signal to be detected.</p>
<p>In the frame lock panel of the nvidia-settings interface, add
the X Server that contains the display and G-Sync devices that you
would like to sync to this external source by clicking the "Add
Devices..." button. An X Server is typically specified in the
format <code class="computeroutput">system:m</code>, e.g.:</p>
<pre class="screen">
mycomputer.domain.com:0
</pre>
<p>or</p>
<pre class="screen">
localhost:0
</pre>
<p>After adding an X Server, rows will appear in the "G-Sync
Devices" section on the frame lock panel that displays relevant
status information about the G-Sync devices, GPUs attached to those
G-Sync devices and the display devices driven by those GPUs. In
particular, the G-Sync rows will display the server name and G-Sync
device number along with "Receiving" LED, "Rate", "House" LED,
"Port0"/"Port1" Images, and "Delay" information. The GPU rows will
display the GPU product name information along with the GPU ID for
the server. The Display Device rows will show the display device
name and device type along with server/client checkboxes, refresh
rate, "Timing" LED and "Stereo" LED.</p>
<p>Once the G-Sync and display devices have been added to the frame
lock/genlock group, a Server display device will need to be
selected. This is done by selecting the "Server" checkbox of the
desired display device.</p>
<p>If you are using a G-Sync card, you must also click the "Use
House Sync if Present" checkbox. To enable synchronization of this
G-Sync device to the external source, click the "Enable Frame Lock"
button. The display device(s) may take a moment to stabilize. If it
does not stabilize, you may have selected a synchronization signal
that the system cannot support. You should disable synchronization
by clicking the "Disable Frame Lock" button and check the external
sync signal.</p>
<p>Modifications to genlock settings (e.g., "Use House Sync if
Present", "Add Devices...") must be done while synchronization is
disabled.</p>
<p><a name="framelocksetup" id="framelocksetup"></a></p>
<h3>Frame Lock Setup</h3>
<p>Frame Lock is supported across an arbitrary number of Quadro FX
3000 or Quadro FX G-Sync systems, although mixing the two in the
same frame lock group is not supported. Additionally, each system
to be included in the frame lock group must be configured with
identical mode timings. See <a href="chapter-19.html" title=
"Chapter 19. Programming Modes">Chapter 19,
<i>Programming Modes</i></a> for information on mode timings.</p>
<p>Connect the systems through their RJ45 ports using standard CAT5
patch cables. These ports are located on the frame lock card itself
(either the Quadro FX 3000 or the Quadro FX G-Sync card).
<span class="emphasis"><em>Do not connect a frame lock port to an
ethernet card or hub. Doing so may permanently damage the
hardware</em></span>. The connections should be made in a
daisy-chain fashion: each card has two RJ45 ports, call them 1 and
2. Connect port 1 of system A to port 2 of system B, connect port 1
of system B to port 2 of system C, etc. Note that you will always
have two empty ports in your frame lock group.</p>
<p>The ports self-configure as inputs or outputs once frame lock is
enabled. Each port has a yellow and a green LED that reflect this
state. A flashing yellow LED indicates an output and a flashing
green LED indicates an input. A solid green LED indicates that the
port has not yet configured.</p>
<p>In the frame lock panel of the nvidia-settings interface, add
the X server that contains the display devices that you would like
to include in the frame lock group by clicking the "Add Devices..."
button (see the description for adding display devices in the
previous section on GENLOCK SETUP. Like the genlock status
indicators, the "Port0" and "Port1" columns in the table on the
frame lock panel contain indicators whose states mirror the states
of the physical LEDs on the RJ45 ports. Thus, you may monitor the
status of these ports from the software interface.</p>
<p>Any X Server can be added to the frame lock group, provided
that</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>The system supporting the X Server is configured to support
frame lock and is connected via RJ45 cable to the other systems in
the frame lock group.</p>
</li>
<li>
<p>The system driving nvidia-settings can locate and has display
privileges on the X server that is to be included for frame
lock.</p>
</li>
</ol>
</div>
<p>A system can gain display privileges on a remote system by
executing</p>
<pre class="screen">
% xhost +
</pre>
<p>on the remote system. See the xhost(1) man page for details.
Typically, frame lock is controlled through one of the systems that
will be included in the frame lock group. While this is not a
requirement, note that nvidia-settings will only display the frame
lock panel when running on an X server that supports frame
lock.</p>
<p>To enable synchronization on these display devices, click the
"Enable Frame Lock" button. The screens may take a moment to
stabilize. If they do not stabilize, you may have selected mode
timings that one or more of the systems cannot support. In this
case you should disable synchronization by clicking the "Disable
Frame Lock" button and refer to <a href="chapter-19.html" title=
"Chapter 19. Programming Modes">Chapter 19,
<i>Programming Modes</i></a> for information on mode timings.</p>
<p>Modifications to frame lock settings (e.g. "Add/Remove
Devices...") must be done while synchronization is disabled.</p>
<h3>Frame Lock + Genlock</h3>
<p>The use of frame lock and genlock together is a simple extension
of the above instructions for using them separately. You should
first follow the instructions for <a href=
"chapter-26.html#framelocksetup" title="Frame Lock Setup">Frame
Lock Setup</a>, and then to one of the systems that will be
included in the frame lock group, attach an external sync source.
In order to sync the frame lock group to this single external
source, you must select a display device driven by the GPU
connected to the G-Sync card (through the primary connector) that
is connected to the external source to be the signal server for the
group. This is done by selecting the checkbox labeled "Server" of
the tree on the frame lock panel in nvidia-settings. If you are
using a G-Sync based frame lock group, you must also select the
"Use House Sync if Present" checkbox. Enable synchronization by
clicking the "Enable Frame Lock" button. As with other frame
lock/genlock controls, you must select the signal server while
synchronization is disabled.</p>
<h3>Configuration with nvidia-settings command line</h3>
<p>Frame Lock may also be configured through the nvidia-settings
command line. This method of configuring Frame Lock may be useful
in a scripted environment to automate the setup process. (Note that
the examples listed below depend on the actual hardware
configuration and as such may not work as-is.)</p>
<p>To properly configure Frame Lock, the following steps should be
completed:</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>Make sure Frame Lock Sync is disabled on all GPUs.</p>
</li>
<li>
<p>Make sure all display devices that are to be frame locked have
the same refresh rate.</p>
</li>
<li>
<p>Configure which (display/GPU) device should be the master.</p>
</li>
<li>
<p>Configure house sync (if applicable).</p>
</li>
<li>
<p>Configure the slave display devices.</p>
</li>
<li>
<p>Enable frame lock sync on the master GPU.</p>
</li>
<li>
<p>Enable frame lock sync on the slave GPUs.</p>
</li>
<li>
<p>Toggle the test signal on the master GPU (for testing the
hardware connectivity.)</p>
</li>
</ol>
</div>
<p></p>
<p>For a full list of the nvidia-settings Frame Lock attributes,
please see the <code class="filename">nvidia-settings(1)</code> man
page. Examples:</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>1 System, 1 Frame Lock board, 1 GPU, and 1 display device
syncing to the house signal:</p>
<pre class="screen">
# - Make sure frame lock sync is disabled
nvidia-settings -a [gpu:0]/FrameLockEnable=0
nvidia-settings -q [gpu:0]/FrameLockEnable
# - Query the enabled displays on the gpu
nvidia-settings -q [gpu:0]/EnabledDisplays
# - Check that the refresh rate is the one we want
nvidia-settings -q [gpu:0]/RefreshRate
# - Set the master display device to CRT-0. The desired display
# device(s) to be set are passed in as a hexadecimal number
# in which specific bits denote which display devices to set.
# examples:
#
# 0x00000001 - CRT-0
# 0x00000002 - CRT-1
# 0x00000003 - CRT-0 and CRT-1
#
# 0x00000100 - TV-0
# 0x00000200 - TV-1
#
# 0x00020000 - DFP-1
#
# 0x00010101 - CRT-0, TV-0 and DFP-0
#
# 0x000000FF - All CRTs
# 0x0000FF00 - All TVs
# 0x00FF0000 - All DFPs
#
# Note that the following command:
#
# nvidia-settings -q [gpu:0]/EnabledDisplays
#
# will list the available displays on the given GPU.
nvidia-settings -a [gpu:0]/FrameLockMaster=0x00000001
nvidia-settings -q [gpu:0]/FrameLockMaster
# - Enable use of house sync signal
nvidia-settings -a [framelock:0]/FrameLockUseHouseSync=1
# - Configure the house sync signal video mode
nvidia-settings -a [framelock:0]/FrameLockVideoMode=0
# - Set the slave display device to none (to avoid
# having unwanted display devices locked to the
# sync signal.)
nvidia-settings -a [gpu:0]/FrameLockSlaves=0x00000000
nvidia-settings -q [gpu:0]/FrameLockSlaves
# - Enable framelocking
nvidia-settings -a [gpu:0]/FrameLockEnable=1
# - Toggle the test signal
nvidia-settings -a [gpu:0]/FrameLockTestSignal=1
nvidia-settings -a [gpu:0]/FrameLockTestSignal=0
</pre>
<p></p>
</li>
<li>
<p>2 Systems, each with 2 GPUs, 1 Frame Lock board and 1 display
device per GPU syncing from the first system's first display
device:</p>
<pre class="screen">
# - Make sure frame lock sync is disabled
nvidia-settings -a myserver:0[gpu:0]/FrameLockEnable=0
nvidia-settings -a myserver:0[gpu:1]/FrameLockEnable=0
nvidia-settings -a myslave1:0[gpu:0]/FrameLockEnable=0
nvidia-settings -a myslave1:0[gpu:1]/FrameLockEnable=0
# - Query the enabled displays on the GPUs
nvidia-settings -q myserver:0[gpu:0]/EnabledDisplays
nvidia-settings -q myserver:0[gpu:1]/EnabledDisplays
nvidia-settings -q myslave1:0[gpu:0]/EnabledDisplays
nvidia-settings -q myslave1:0[gpu:1]/EnabledDisplays
# - Check the refresh rate is the same for all displays
nvidia-settings -q myserver:0[gpu:0]/RefreshRate
nvidia-settings -q myserver:0[gpu:1]/RefreshRate
nvidia-settings -q myslave1:0[gpu:0]/RefreshRate
nvidia-settings -q myslave1:0[gpu:1]/RefreshRate
# - Make sure the display device we want as master is masterable
nvidia-settings -q myserver:0[gpu:0]/FrameLockMasterable
# - Set the master display device (CRT-0)
nvidia-settings -a myserver:0[gpu:0]/FrameLockMaster=0x00000001
# - Disable the house sync signal on the master device
nvidia-settings -a myserver:0[framelock:0]/FrameLockUseHouseSync=0
# - Set the slave display devices
nvidia-settings -a myserver:0[gpu:1]/FrameLockSlaves=0x00000001
nvidia-settings -a myslave1:0[gpu:0]/FrameLockSlaves=0x00000001
nvidia-settings -a myslave1:0[gpu:1]/FrameLockSlaves=0x00000001
# - Enable framelocking on server
nvidia-settings -a myserver:0[gpu:0]/FrameLockEnable=1
# - Enable framelocking on slave devices
nvidia-settings -a myserver:0[gpu:1]/FrameLockEnable=1
nvidia-settings -a myslave1:0[gpu:0]/FrameLockEnable=1
nvidia-settings -a myslave1:0[gpu:1]/FrameLockEnable=1
# - Toggle the test signal
nvidia-settings -a myserver:0[gpu:0]/FrameLockTestSignal=1
nvidia-settings -a myserver:0[gpu:0]/FrameLockTestSignal=0
</pre>
<p></p>
</li>
<li>
<p>1 System, 4 GPUs, 2 Frame Lock boards and 2 display devices per
GPU syncing from the first GPU's display device:</p>
<pre class="screen">
# - Make sure frame lock sync is disabled
nvidia-settings -a [gpu:0]/FrameLockEnable=0
nvidia-settings -a [gpu:1]/FrameLockEnable=0
nvidia-settings -a [gpu:2]/FrameLockEnable=0
nvidia-settings -a [gpu:3]/FrameLockEnable=0
# - Query the enabled displays on the GPUs
nvidia-settings -q [gpu:0]/EnabledDisplays
nvidia-settings -q [gpu:1]/EnabledDisplays
nvidia-settings -q [gpu:2]/EnabledDisplays
nvidia-settings -q [gpu:3]/EnabledDisplays
# - Check the refresh rate is the same for all displays
nvidia-settings -q [gpu:0]/RefreshRate
nvidia-settings -q [gpu:1]/RefreshRate
nvidia-settings -q [gpu:2]/RefreshRate
nvidia-settings -q [gpu:3]/RefreshRate
# - Make sure the display device we want as master is masterable
nvidia-settings -q myserver:0[gpu:0]/FrameLockMasterable
# - Set the master display device (CRT-0)
nvidia-settings -a [gpu:0]/FrameLockMaster=0x00000001
# - Disable the house sync signal on the master device
nvidia-settings -a [framelock:0]/FrameLockUseHouseSync=1
# - Set the slave display devices
nvidia-settings -a [gpu:0]/FrameLockSlaves=0x00000002 # CRT-1
nvidia-settings -a [gpu:1]/FrameLockSlaves=0x00000003 # CRT-0 and CRT-1
nvidia-settings -a [gpu:2]/FrameLockSlaves=0x00000003 # CRT-0 and CRT-1
nvidia-settings -a [gpu:3]/FrameLockSlaves=0x00000003 # CRT-0 and CRT-1
# - Enable framelocking on master GPU
nvidia-settings -a [gpu:0]/FrameLockEnable=1
# - Enable framelocking on slave devices
nvidia-settings -a [gpu:1]/FrameLockEnable=1
nvidia-settings -a [gpu:2]/FrameLockEnable=1
nvidia-settings -a [gpu:3]/FrameLockEnable=1
# - Toggle the test signal
nvidia-settings -a [gpu:0]/FrameLockTestSignal=1
nvidia-settings -a [gpu:0]/FrameLockTestSignal=0
</pre>
<p></p>
</li>
</ol>
</div>
<p></p>
<h3>Leveraging Frame Lock/Genlock in OpenGL</h3>
<p>With the GLX_NV_swap_group extension, OpenGL applications can be
implemented to join a group of applications within a system for
local swap sync, and bind the group to a barrier for swap sync
across a frame lock group. A universal frame counter is also
provided to promote synchronization across applications.</p>
<h3>Frame Lock Restrictions:</h3>
<p>The following restrictions must be met for enabling frame
lock:</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>All display devices set as client in a frame lock group must
have the same mode timings as the server (master) display device.
If a House Sync signal is used (instead of internal timings), all
client display devices must be set to have the same refresh rate as
the incoming house sync signal.</p>
</li>
<li>
<p>All X Screens (driving the selected client/server display
devices) must have the same stereo setting. See <a href=
"appendix-b.html" title=
"Appendix B. X Config Options">Appendix B, <i>X
Config Options</i></a> for instructions on how to set the stereo X
option.</p>
</li>
<li>
<p>The frame lock server (master) display device must be on a GPU
on the primary connector to a G-Sync device.</p>
</li>
<li>
<p>If connecting a single GPU to a G-Sync device, the primary
connector must be used.</p>
</li>
<li>
<p>In configurations with more than one display device per GPU, we
recommend enabling frame lock on all display devices on those
GPUs.</p>
</li>
<li>
<p>VT-switching or mdoe-switching will disable frame lock on the
display device. Note that the glXQueryFrameCountNV entry point
(provided by the GLX_NV_swap_group extension) will only provide
incrementing numbers while frame lock is enabled. Therefore,
applications that use glXQueryFrameCountNV to control animation
will appear to stop animating while frame lock is disabled.</p>
</li>
</ol>
</div>
<p></p>
<h3>Supported Frame Lock Configurations:</h3>
<p>The following configurations are currently supported:</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>Basic Frame Lock: Single GPU, Single X Screen, Single Display
Device with or without OpenGL applications that make use of
Quad-Buffered Stereo and/or the GLX_NV_swap_group extension.</p>
</li>
<li>
<p>Frame Lock + TwinView: Single GPU, Single X Screen, Multiple
Display Devices with or without OpenGL applications that make use
of Quad-Buffered Stereo and/or the GLX_NV_swap_group extension.</p>
</li>
<li>
<p>Frame Lock + Xinerama: 1 or more GPU(s), Multiple X Screens,
Multiple Display Devices with or without OpenGL applications that
make use of Quad-Buffered Stereo and/or the GLX_NV_swap_group
extension.</p>
</li>
<li>
<p>Frame Lock + TwinView + Xinerama: 1 or more GPU(s), Multiple X
Screens, Multiple Display Devices with or without OpenGL
applications that make use of Quad-Buffered Stereo and/or the
GLX_NV_swap_group extension.</p>
</li>
<li>
<p>Frame Lock + SLI SFR, AFR, or AA: 2 GPUs, Single X Screen,
Single Display Device with either OpenGL applications that make use
of Quad-Buffered Stereo or the GLX_NV_swap_group extension. Note
that for Frame Lock + SLI Frame Rendering applications that make
use of both Quad-Buffered Stereo and the GLX_NV_swap_group
extension are not supported. Note that only 2-GPU SLI
configurations are currently supported.</p>
</li>
<li>
<p>Frame Lock + Multi-GPU SFR, AFR, or AA: 2 GPUs, Single X Screen,
Single Display Device with either OpenGL applications that make use
of Quad-Buffered Stereo or the GLX_NV_swap_group extension. Note
that for Frame Lock + Multi-GPU Frame Rendering applications that
make use of both Quad-Buffered Stereo and the GLX_NV_swap_group
extension are not supported.</p>
</li>
</ol>
</div>
<p></p>
</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left"><a accesskey="p" href=
"chapter-25.html">Prev</a> </td>
<td width="20%" align="center"><a accesskey="u" href=
"part-01.html">Up</a></td>
<td width="40%" align="right"> <a accesskey="n" href=
"chapter-27.html">Next</a></td>
</tr>
<tr>
<td width="40%" align="left" valign="top">
Chapter 25. Configuring SLI and Multi-GPU
FrameRendering </td>
<td width="20%" align="center"><a accesskey="h" href=
"index.html">Home</a></td>
<td width="40%" align="right" valign="top">
Chapter 27. Configuring SDI Video Output</td>
</tr>
</table>
</div>
</body>
</html>
distrib
>
Mandriva
>
2010.1
>
x86_64
>
media
>
non-free-release
>
by-pkgid
>
2bc856bd2f534db528cd46d1d32cafd0
>
files
>
39
