Nvidia QUADRO G-SYNC II, Руководство пользователя

Страница: 56 / 73

During operation, you can also query any of these on each X screen:

NV _ CTRL _ FRAMELOCK _ PORT0 _ STATUS

NV _ CTRL _ FRAMELOCK _ PORT1 _ STATUS

NV _ CTRL _ FRAMELOCK _ HOUSE _ STATUS

NV _ CTRL _ FRAMELOCK _ SYNC _ READY

NV _ CTRL _ FRAMELOCK _ STEREO _ SYNC

NV _ CTRL _ FRAMELOCK _ ETHERNET _ DETECTED

NV _ CTRL _ FRAMELOCK _ SYNC _ RATE

NV _ CTRL _ FRAMELOCK _ TIMING
nvidia-settings registers a
gtk+
timeout function and queries
the state of these on each X screen every few seconds.
Writing a Frame Lock Client for NV-
CONTROL 1.9 (and later)
These are the two major changes to frame lock
con
fi guration in NV-CONTROL 1.9:

Display devices (instead of X Screens) are now selected
as the clients and slaves of a frame lock group.

Frame lock attributes should now be set/queried on Quadros
(
NV _ CTRL _ TARGET _ TYPE _ GPU
) and Quadro G-Sync
II (frame lock) devices (
NV _ CTRL _ TARGET _ TYPE _
FRAMELOCK
) using the new NV-CONTROL targeting API.
See the sample NV-CONTROL clients in the samples directory for basic
examples of how to use the new targeting API (
nv-control-targets.
c
) and a basic frame lock client (
nv-control-framelock.c
). See the fi le
ctkframelock.c
for a much more involved example of how the nvidia-
settings utility programs the frame lock attributes.
The constants referenced below are de fi ned in
NVCtrl.h.
. See the
comments in that fi le for an explanation of each attribute. It may also be
useful to search the
ctkframelock.c
fi le using a grep utility to see how
each attribute is used.
NVIDIA Frame Synchronization Under Linux
52