From: Simon Schubert Date: Wed, 9 Sep 2009 15:33:44 +0000 (+0200) Subject: import NVIDIA-FreeBSD-x86-185.18.36 X-Git-Url: https://gitweb.dragonflybsd.org/~corecode/nvidia.git/commitdiff_plain/5b34fd865b9624a0ff7d34a2b51ec0e74323019a import NVIDIA-FreeBSD-x86-185.18.36 --- diff --git a/Makefile b/Makefile index 45feb17..6838606 100644 --- a/Makefile +++ b/Makefile @@ -8,7 +8,7 @@ afterinstall: @${.CURDIR}/scripts/linux.sh @echo @echo "Installation of the NVIDIA Accelerated Graphics Driver" - @echo "180.29 for FreeBSD is now complete. You can now" + @echo "185.18.36 for FreeBSD is now complete. You can now" @echo "run the nvidia-xconfig utility to automatically update" @echo "your X server configuration file. Please see the README" @echo "for details if you wish to update your X configuration" diff --git a/doc/README b/doc/README index 16669cd..ab49613 100644 --- a/doc/README +++ b/doc/README @@ -1,8 +1,8 @@ NVIDIA Accelerated FreeBSD Graphics Driver README and Installation Guide NVIDIA Corporation - Last Updated: Tue Feb 3 09:57:25 PST 2009 - Most Recent Driver Version: 180.29 + Last Updated: Fri Aug 14 16:24:14 PDT 2009 + Most Recent Driver Version: 185.18.36 Published by NVIDIA Corporation @@ -44,7 +44,7 @@ countries. Other company and product names may be trademarks or registered trademarks of the respective owners with which they are associated. -Copyright 2006 - 2008 NVIDIA Corporation. All rights reserved. +Copyright 2006 - 2009 NVIDIA Corporation. All rights reserved. ______________________________________________________________________________ @@ -52,36 +52,36 @@ TABLE OF CONTENTS ______________________________________________________________________________ Chapter 1. Introduction -Chapter 2. Installing the NVIDIA Driver -Chapter 3. Using Linux Compatibility Support -Chapter 4. Configuring X for the NVIDIA Driver -Chapter 5. Frequently Asked Questions -Chapter 6. Common Problems -Chapter 7. Known Issues -Chapter 8. Specifying OpenGL Environment Variable Settings -Chapter 9. Configuring AGP -Chapter 10. Configuring TwinView -Chapter 11. Configuring GLX in Xinerama -Chapter 12. Configuring Multiple X Screens on One Card -Chapter 13. Configuring TV-Out -Chapter 14. Using the XRandR Extension -Chapter 15. Configuring a Notebook -Chapter 16. Programming Modes -Chapter 17. Configuring Flipping and UBB -Chapter 18. Using the X Composite Extension -Chapter 19. Using the nvidia-settings Utility -Chapter 20. Configuring SLI and Multi-GPU FrameRendering -Chapter 21. Configuring Frame Lock and Genlock -Chapter 22. Configuring SDI Video Output -Chapter 23. Configuring Depth 30 Displays -Chapter 24. NVIDIA Contact Info and Additional Resources -Chapter 25. Credits -Chapter 26. Acknowledgements - -Appendix A. Minimum Software Requirements -Appendix B. Installed Components -Appendix C. The Sysctl Interface -Appendix D. Configuring Low-level Parameters +Chapter 2. Minimum Software Requirements +Chapter 3. Installing the NVIDIA Driver +Chapter 4. Installed Components +Chapter 5. Using Linux Compatibility Support +Chapter 6. Configuring X for the NVIDIA Driver +Chapter 7. Frequently Asked Questions +Chapter 8. Common Problems +Chapter 9. Known Issues +Chapter 10. Specifying OpenGL Environment Variable Settings +Chapter 11. Configuring AGP +Chapter 12. Configuring TwinView +Chapter 13. Configuring GLX in Xinerama +Chapter 14. Configuring Multiple X Screens on One Card +Chapter 15. Configuring TV-Out +Chapter 16. Using the XRandR Extension +Chapter 17. Configuring a Notebook +Chapter 18. Programming Modes +Chapter 19. Configuring Flipping and UBB +Chapter 20. The Sysctl Interface +Chapter 21. Configuring Low-level Parameters +Chapter 22. Using the X Composite Extension +Chapter 23. Using the nvidia-settings Utility +Chapter 24. Configuring SLI and Multi-GPU FrameRendering +Chapter 25. Configuring Frame Lock and Genlock +Chapter 26. Configuring SDI Video Output +Chapter 27. Configuring Depth 30 Displays +Chapter 28. NVIDIA Contact Info and Additional Resources +Chapter 29. Credits +Chapter 30. Acknowledgements + Appendix A. Supported NVIDIA GPU Products Appendix B. X Config Options Appendix C. Display Device Names @@ -104,7 +104,7 @@ functionality and high-performance OpenGL support to FreeBSD x86 with the use of NVIDIA graphics processing units (GPUs). These drivers provide optimized hardware acceleration for OpenGL and X -applications and support nearly all recent NVIDIA GPU products (see Appendix E +applications and support nearly all recent NVIDIA GPU products (see Appendix A for a complete list of supported GPUs). TwinView, TV-Out and flat panel displays are also supported. @@ -112,10 +112,10 @@ displays are also supported. 1B. ABOUT THIS DOCUMENT This document provides instructions for the installation and use of the NVIDIA -Accelerated FreeBSD Graphics Driver. Chapter 2, Chapter 3 and Chapter 4 walk +Accelerated FreeBSD Graphics Driver. Chapter 3, Chapter 5 and Chapter 6 walk the user through the process of downloading, installing and configuring the -driver. Chapter 5 addresses frequently asked questions about the installation -process, and Chapter 6 provides solutions to common problems. The remaining +driver. Chapter 7 addresses frequently asked questions about the installation +process, and Chapter 8 provides solutions to common problems. The remaining chapters include details on different features of the NVIDIA FreeBSD Driver. Frequently asked questions about specific tasks are included in the relevant chapters. @@ -125,19 +125,19 @@ chapters. It is assumed that the user and reader of this document has at least a basic understanding of FreeBSD techniques and terminology. However, new FreeBSD -users can refer to Appendix L for details on parts of the installation +users can refer to Appendix H for details on parts of the installation process. 1D. ADDITIONAL INFORMATION -In case additional information is required, Chapter 24 provides contact +In case additional information is required, Chapter 28 provides contact information for NVIDIA FreeBSD driver resources, as well as a brief listing of external resources. ______________________________________________________________________________ -Appendix A. Minimum Software Requirements +Chapter 2. Minimum Software Requirements ______________________________________________________________________________ The official minimum software requirements for the NVIDIA FreeBSD Graphics @@ -156,7 +156,7 @@ Note that FreeBSD -STABLE versions older than FreeBSD 5.3 and FreeBSD 6.x/7.x ______________________________________________________________________________ -Chapter 2. Installing the NVIDIA Driver +Chapter 3. Installing the NVIDIA Driver ______________________________________________________________________________ This installation procedure will likely be simplified further in the future, @@ -177,7 +177,7 @@ kernel. ______________________________________________________________________________ -Appendix B. Installed Components +Chapter 4. Installed Components ______________________________________________________________________________ The NVIDIA Accelerated FreeBSD Graphics Driver consists of the following @@ -214,17 +214,17 @@ components. nvidia2 /dev nvidia3 /dev nvidiactl /dev - libGL.so.180.29 /compat/linux/usr/lib - libnvidia-tls.so.180.29 /compat/linux/usr/lib - libGLcore.so.180.29 /compat/linux/usr/lib - libvdpau.so.180.29 /compat/linux/usr/lib - libvdpau_trace.so.180.29 /compat/linux/usr/lib - libvdpau_nvidia.so.180.29 /compat/linux/usr/lib + libGL.so.185.18.36 /compat/linux/usr/lib + libnvidia-tls.so.185.18.36 /compat/linux/usr/lib + libGLcore.so.185.18.36 /compat/linux/usr/lib + libvdpau.so.185.18.36 /compat/linux/usr/lib + libvdpau_trace.so.185.18.36 /compat/linux/usr/lib + libvdpau_nvidia.so.185.18.36 /compat/linux/usr/lib ______________________________________________________________________________ -Chapter 3. Using Linux Compatibility Support +Chapter 5. Using Linux Compatibility Support ______________________________________________________________________________ If you wish to run Linux OpenGL applications on your FreeBSD computer, you @@ -248,18 +248,18 @@ the Linux ABI compatibility layer (see 'nv-freebsd.h' for details). ______________________________________________________________________________ -Chapter 4. Configuring X for the NVIDIA Driver +Chapter 6. Configuring X for the NVIDIA Driver ______________________________________________________________________________ The X configuration file provides a means to configure the X server. This section describes the settings necessary to enable the NVIDIA driver. A -comprehensive list of parameters is provided in Appendix F. +comprehensive list of parameters is provided in Appendix B. The NVIDIA Driver includes a utility called nvidia-xconfig, which is designed to make editing the X configuration file easy. You can also edit it by hand. -4A. USING NVIDIA-XCONFIG TO CONFIGURE THE X SERVER +6A. USING NVIDIA-XCONFIG TO CONFIGURE THE X SERVER nvidia-xconfig will find the X configuration file and modify it to use the NVIDIA X driver. In most cases, you can simply answer "Yes" when the installer @@ -278,7 +278,7 @@ manual page by running. -4B. MANUALLY EDITING THE CONFIGURATION FILE +6B. MANUALLY EDITING THE CONFIGURATION FILE In April 2004 the X.Org Foundation released an X server based on the XFree86 server. While your release may use the X.Org X server, rather than XFree86, @@ -347,21 +347,21 @@ Section "Module" EndSection There are numerous options that may be added to the X config file to tune the -NVIDIA X driver. See Appendix F for a complete list of these options. +NVIDIA X driver. See Appendix B for a complete list of these options. Once you have completed these edits to the X config file, you may restart X and begin using the accelerated OpenGL libraries. After restarting X, any OpenGL application should automatically use the new NVIDIA libraries. (NOTE: -If you encounter any problems, see Chapter 6 for common problem diagnoses.) +If you encounter any problems, see Chapter 8 for common problem diagnoses.) ______________________________________________________________________________ -Chapter 5. Frequently Asked Questions +Chapter 7. Frequently Asked Questions ______________________________________________________________________________ This section provides answers to frequently asked questions associated with the NVIDIA FreeBSD x86 Driver and its installation. Common problem diagnoses -can be found in Chapter 6 and tips for new users can be found in Appendix L. +can be found in Chapter 8 and tips for new users can be found in Appendix H. Also, detailed information for specific setups is provided in the Appendices. @@ -504,7 +504,7 @@ A. The XRandR X extension is not presently aware of multiple display devices This behavior can be disabled by setting the X configuration option "DynamicTwinView" to FALSE. - For details, see Chapter 10. + For details, see Chapter 12. Q. Why does starting certain applications result in Xlib error messages @@ -528,7 +528,7 @@ A. If your X config file has a "Module" section that does not list the ______________________________________________________________________________ -Chapter 6. Common Problems +Chapter 8. Common Problems ______________________________________________________________________________ This section provides solutions to common problems associated with the NVIDIA @@ -577,7 +577,7 @@ Q. X starts for me, but OpenGL applications terminate immediately. A. If X starts but you have trouble with OpenGL, you most likely have a problem with other libraries in the way, or there are stale symlinks. See - Appendix B for details. + Chapter 4 for details. You should also check that the correct extensions are present; @@ -586,10 +586,10 @@ A. If X starts but you have trouble with OpenGL, you most likely have a should show the "GLX" and "NV-GLX" extensions present. If these two extensions are not present, then there is most likely a problem loading the glx module, or it is unable to implicitly load GLcore. Check your X config - file and make sure that you are loading glx (see Chapter 4). If your X + file and make sure that you are loading glx (see Chapter 6). If your X config file is correct, then check the X log file for warnings/errors pertaining to GLX. Also check that all of the necessary symlinks are in - place (refer to Appendix B). + place (refer to Chapter 4). Q. When Xinerama is enabled, my stereo glasses are shuttering only when the @@ -613,11 +613,11 @@ Q. Stereo is not in sync across multiple displays. A. There are two cases where this may occur. If the displays are attached to the same GPU, and one of them is out of sync with the stereo glasses, you will need to reconfigure your monitors to drive identical mode timings; see - Chapter 16 for details. + Chapter 18 for details. If the displays are attached to different GPUs, the only way to synchronize stereo across the displays is with a G-Sync device, which is only supported - by certain Quadro cards. See Chapter 21 for details. This applies to + by certain Quadro cards. See Chapter 25 for details. This applies to seperate GPUs on seperate cards as well as seperate GPUs on the same card, such as Quadro FX 4500 X2. Note that the Quadro FX 4500 X2 only provides a single DIN connector for stereo, tied to the bottommost GPU. In order to @@ -751,13 +751,13 @@ A. When initialized by an application executed with 'root' privileges, the Q. My system runs, but seems unstable. -A. Your stability problems may be AGP-related. See Chapter 9 for details. +A. Your stability problems may be AGP-related. See Chapter 11 for details. Q. OpenGL applications are running slowly A. The application is probably using a different library that still remains on - your system, rather than the NVIDIA supplied OpenGL library. See Appendix B + your system, rather than the NVIDIA supplied OpenGL library. See Chapter 4 for details. @@ -795,7 +795,7 @@ A. Most of the X startup delay problems we have found are caused by incorrect data in video BIOSes about what display devices are possibly connected or what i2c port should be used for detection. You can work around these problems with the X config option IgnoreDisplayDevices (see the description - in Appendix F). + in Appendix B). Q. Fonts are incorrectly sized after installing the NVIDIA driver. @@ -809,7 +809,7 @@ A. Incorrectly sized fonts are generally caused by incorrect DPI (Dots Per This will report the size in pixels, and in millimeters. If these numbers are wrong, you can correct them by modifying the X - server's DPI setting. See Appendix I for details. + server's DPI setting. See Appendix E for details. Q. General problems with ALi chipsets @@ -889,7 +889,7 @@ A. The NVIDIA OpenGL driver must be able to map the '/dev/zero' device node ______________________________________________________________________________ -Chapter 7. Known Issues +Chapter 9. Known Issues ______________________________________________________________________________ The following problems still exist in this release and are in the process of @@ -899,7 +899,7 @@ Known Issues Notebooks - If you are using a notebook see the "Known Notebook Issues" in Chapter 15. + If you are using a notebook see the "Known Notebook Issues" in Chapter 17. FSAA @@ -926,7 +926,7 @@ libGL DSO finalizer and pthreads XVideo and the Composite X extension XVideo will not work correctly when Composite is enabled unless using - X.Org 7.1 or later. See Chapter 18. + X.Org 7.1 or later. See Chapter 22. GLX visuals in Xinerama @@ -940,6 +940,30 @@ GLX visuals in Xinerama X server with the -logverbose 6 option and then check the X server log file. +Some X servers have trouble with multiple GPUs + + Some versions of the X.Org server version 1.5.0 and higher have a bug that + causes X to fail with an error similar to the following when there is more + than one GPU in the computer: + + (!!) More than one possible primary device found + (II) Primary Device is: + (EE) No devices detected. + + Fatal server error: + no screens found + + You can work around this problem by specifying the bus ID of the device + you wish to use. For more details, please search the xorg.conf manual page + for "BusID". You can configure the X server with an X screen on each + NVIDIA GPU by running: + + nvidia-xconfig --enable-all-gpus + + + Please see http://bugs.freedesktop.org/show_bug.cgi?id=18321 for more + details on this X server problem. + This section describes problems that will not be fixed. Usually, the source of the problem is beyond the control of NVIDIA. Following is the list of problems: @@ -972,7 +996,7 @@ Irongate Chip sets with AGP 1x ALi chipsets, ALi1541 and ALi1647 On ALi1541 and ALi1647 chipsets, NVIDIA drivers disable AGP to work around - timing issues and signal integrity issues. See Chapter 6 for more + timing issues and signal integrity issues. See Chapter 8 for more information on ALi chipsets. NV-CONTROL versions 1.8 and 1.9 @@ -1004,14 +1028,42 @@ NV-CONTROL versions 1.8 and 1.9 problem (i.e., the only driver to use either version 1.8 or 1.9 of the NV-CONTROL X extension) is 1.0-8756. +CPU throttling reducing memory bandwidth on IGP systems + + For some models of CPU, the CPU throttling technology may affect not only + CPU core frequency, but also memory frequency/bandwidth. On systems using + integrated graphics, any reduction in memory bandwidth will affect the GPU + as well as the CPU. This can negatively affect applications that use + significant memory bandwidth, such as video decoding using VDPAU, or + certain OpenGL operations. This may cause such applications to run with + lower performance than desired. + + To work around this problem, NVIDIA recommends configuring your CPU + throttling implementation to avoid reducing memory bandwidth. This may be + as simple as setting a certain minimum frequency for the CPU. + + Depending on your operating system and/or distribution, this may be as + simple as writing to a configuration file in the /sys or /proc + filesystems, or other system configuration file. Please read, or search + the Internet for, documentation regarding CPU throttling on your operating + system. + +VDPAU initialization failures on supported GPUs + + If VDPAU gives the VDP_STATUS_NO_IMPLEMENTATION error message on a GPU + which was labeled or specified as supporting PureVideo or PureVideo HD, + one possible reason is a hardware defect. After ruling out any other + software problems, NVIDIA recommends returning the GPU to the manufacturer + for a replacement. + ______________________________________________________________________________ -Chapter 8. Specifying OpenGL Environment Variable Settings +Chapter 10. Specifying OpenGL Environment Variable Settings ______________________________________________________________________________ -8A. FULL SCENE ANTIALIASING +10A. FULL SCENE ANTIALIASING Antialiasing is a technique used to smooth the edges of objects in a scene to reduce the jagged "stairstep" effect that sometimes appears. By setting the @@ -1026,13 +1078,33 @@ performance. To see the available values for __GL_FSAA_MODE along with their descriptions, run: -nvidia-settings --query=fsaa --verbose + nvidia-settings --query=fsaa --verbose The __GL_FSAA_MODE environment variable uses the same integer values that are used to configure FSAA through nvidia-settings and the NV-CONTROL X extension. +In other words, these two commands are equivalent: + + export __GL_FSAA_MODE=5 + + nvidia-settings --assign FSAA=5 + +Note that there are three FSAA related configuration attributes (FSAA, +FSAAAppControlled and FSAAAppEnhanced) which together determine how a GL +application will behave. If FSAAAppControlled is 1, the FSAA specified through +nvidia-settings will be ignored, in favor of what the application requests +through FBConfig selection. If FSAAAppControlled is 0 but FSAAAppEnhanced is +1, then the FSAA value specified through nvidia-settings will only be applied +if the application selected a multisample FBConfig. + +Therefore, to be completely correct, the nvidia-settings command line to +unconditionally assign FSAA should be: + + nvidia-settings --assign FSAA=5 --assign FSAAAppControlled=0 --assign +FSAAAppEnhanced=0 + -8B. ANISOTROPIC TEXTURE FILTERING +10B. ANISOTROPIC TEXTURE FILTERING Automatic anisotropic texture filtering can be enabled by setting the environment variable __GL_LOG_MAX_ANISO. The possible values are: @@ -1049,7 +1121,7 @@ environment variable __GL_LOG_MAX_ANISO. The possible values are: available on GeForce 6800 or newer GPUs. -8C. VBLANK SYNCING +10C. VBLANK SYNCING Setting the environment variable __GL_SYNC_TO_VBLANK to a non-zero value will force glXSwapBuffers to sync to your monitor's vertical refresh (perform a @@ -1062,11 +1134,11 @@ __GL_SYNC_DISPLAY_DEVICE to specify to which display device OpenGL should sync. You should set this environment variable to the name of a display device; for example "CRT-1". Look for the line "Connected display device(s):" in your X log file for a list of the display devices present and their names. -You may also find it useful to review Chapter 10 "Configuring Twinview" and -the section on Ensuring Identical Mode Timings in Chapter 16. +You may also find it useful to review Chapter 12 "Configuring Twinview" and +the section on Ensuring Identical Mode Timings in Chapter 18. -8D. CONTROLLING THE SORTING OF OPENGL FBCONFIGS +10D. CONTROLLING THE SORTING OF OPENGL FBCONFIGS The NVIDIA GLX implementation sorts FBConfigs returned by glXChooseFBConfig() as described in the GLX specification. To disable this behavior set @@ -1080,7 +1152,7 @@ This option may be be useful to work around problems in which applications pick an unexpected FBConfig. -8E. OPENGL YIELD BEHAVIOR +10E. OPENGL YIELD BEHAVIOR There are several cases where the NVIDIA OpenGL driver needs to wait for external state to change before continuing. To avoid consuming too much CPU @@ -1109,7 +1181,7 @@ should do when it wants to yield. The possible values are: -8F. CONTROLLING WHICH OPENGL FBCONFIGS ARE AVAILABLE +10F. CONTROLLING WHICH OPENGL FBCONFIGS ARE AVAILABLE The NVIDIA GLX implementation will hide FBConfigs that are associated with a 32-bit ARGB visual when the XLIB_SKIP_ARGB_VISUALS environment variable is @@ -1117,9 +1189,24 @@ defined. This matches the behavior of libX11, which will hide those visuals from XGetVisualInfo and XMatchVisualInfo. This environment variable is useful when applications are confused by the presence of these FBConfigs. + +10G. USING UNOFFICIAL GLX PROTOCOL + +By default, the NVIDIA GLX implementation will not expose GLX protocol for GL +commands if the protocol is not considered complete. Protocol could be +considered incomplete for a number of reasons. The implementation could still +be under development and contain known bugs, or the protocol specification +itself could be under development or going through review. If users would like +to test the client-side portion of such protocol when using indirect +rendering, they can set the __GL_ALLOW_UNOFFICIAL_PROTOCOL environment +variable to a non-zero value before starting their GLX application. When an +NVIDIA GLX server is used, the related X Config option +"AllowUnofficialGLXProtocol" will need to be set as well to enable support in +the server. + ______________________________________________________________________________ -Chapter 9. Configuring AGP +Chapter 11. Configuring AGP ______________________________________________________________________________ There are several choices for configuring the NVIDIA kernel module's use of @@ -1269,7 +1356,7 @@ System BIOS version ______________________________________________________________________________ -Chapter 10. Configuring TwinView +Chapter 12. Configuring TwinView ______________________________________________________________________________ TwinView is a mode of operation where two display devices (digital flat @@ -1290,10 +1377,10 @@ distinct advantages over other techniques (such as Xinerama): If you are interested in using each display device as a separate X screen, see -Chapter 12. +Chapter 14. -10A. X CONFIG TWINVIEW OPTIONS +12A. X CONFIG TWINVIEW OPTIONS To enable TwinView, you must specify the following option in the Device section of your X Config file: @@ -1323,7 +1410,7 @@ and restarting your X server. Or, you can configure TwinView dynamically in the "Display Configuration" page in nvidia-settings. -10B. DETAILED DESCRIPTION OF OPTIONS +12B. DETAILED DESCRIPTION OF OPTIONS TwinView @@ -1344,7 +1431,7 @@ SecondMonitorVertRefresh These options are normally not needed: by default, the NVIDIA X driver retrieves the valid frequency ranges from the display device's EDID (see - Appendix F for a description of the "UseEdidFreqs" option). The + Appendix B for a description of the "UseEdidFreqs" option). The SecondMonitor options will override any frequency ranges retrieved from the EDID. @@ -1360,11 +1447,11 @@ VertRefresh Option "HorizSync" "CRT-0: 50-110; DFP-0: 40-70" Option "VertRefresh" "CRT-0: 60-120; DFP-0: 60" - See Appendix G on Display Device Names for more information. + See Appendix C on Display Device Names for more information. These options are normally not needed: by default, the NVIDIA X driver retrieves the valid frequency ranges from the display device's EDID (see - Appendix F for a description of the "UseEdidFreqs" option). The + Appendix B for a description of the "UseEdidFreqs" option). The "HorizSync" and "VertRefresh" options override any frequency ranges retrieved from the EDID or any frequency ranges specified with the "SecondMonitorHorizSync" and "SecondMonitorVertRefresh" options. @@ -1435,7 +1522,8 @@ MetaModes within its panning domain, as long as the viewport is contained by the bounding box of the MetaMode. Once the mouse leaves the bounding box of the MetaMode, the entire MetaMode (i.e., all display devices) will be - panned to follow the mouse within the virtual screen. Note that individual + panned to follow the mouse within the virtual screen, unless the + "PanAllDisplays" X configuration option is disabled. Note that individual display devices' panning domains default to being clamped to the position of the display devices' viewports, thus the default behavior is just that viewports remain "locked" together and only perform the second type of @@ -1522,7 +1610,7 @@ Just as in all X config entries, spaces are ignored and all entries are case insensitive. -10C. DYNAMIC TWINVIEW +12C. DYNAMIC TWINVIEW Using the NV-CONTROL X extension, the display devices in use by an X screen, the mode pool for each display device, and the MetaModes for each X screen can @@ -1590,7 +1678,7 @@ A. Yes. The NVIDIA X driver provides a Xinerama extension that X clients (such Unfortunately, the data provided by XineramaQueryScreens() appears to confuse some window managers; to work around such broken window mangers, you can disable communication of the TwinView screen layout with the - "NoTwinViewXineramaInfo" X config Option (see Appendix F for details). + "NoTwinViewXineramaInfo" X config Option (see Appendix B for details). The order that display devices are reported in via the TwinView Xinerama information can be configured with the TwinViewXineramaInfoOrder X @@ -1611,7 +1699,7 @@ A. Yes. The NVIDIA X driver provides a Xinerama extension that X clients (such regions of the virtual screen (see the MetaMode description above). A third solution is to use two separate X screens, rather than use - TwinView. See Chapter 12. + TwinView. See Chapter 14. Q. Why can I not get a resolution of 1600x1200 on the second display device @@ -1686,7 +1774,7 @@ A. Yes. While the details of configuration will vary from game to game, the ______________________________________________________________________________ -Chapter 11. Configuring GLX in Xinerama +Chapter 13. Configuring GLX in Xinerama ______________________________________________________________________________ The NVIDIA FreeBSD Driver supports GLX when Xinerama is enabled on similar @@ -1758,10 +1846,10 @@ Known Issues: ______________________________________________________________________________ -Chapter 12. Configuring Multiple X Screens on One Card +Chapter 14. Configuring Multiple X Screens on One Card ______________________________________________________________________________ -GPUs that support TwinView (Chapter 10) can also be configured to treat each +GPUs that support TwinView (Chapter 12) can also be configured to treat each connected display device as a separate X screen. While there are several disadvantages to this approach as compared to TwinView @@ -1843,7 +1931,7 @@ For further details, refer to the XF86Config(5x) or xorg.conf(5x) man pages. ______________________________________________________________________________ -Chapter 13. Configuring TV-Out +Chapter 15. Configuring TV-Out ______________________________________________________________________________ NVIDIA GPU-based graphics cards with a TV-Out connector can use a television @@ -1964,7 +2052,7 @@ console it is recommended that you upgrade to XFree86 4.3 or later. ______________________________________________________________________________ -Chapter 14. Using the XRandR Extension +Chapter 16. Using the XRandR Extension ______________________________________________________________________________ X.Org version X11R6.8.1 contains support for the rotation component of the @@ -2003,18 +2091,18 @@ to "Above" or "Below". ______________________________________________________________________________ -Chapter 15. Configuring a Notebook +Chapter 17. Configuring a Notebook ______________________________________________________________________________ -15A. INSTALLATION AND CONFIGURATION +17A. INSTALLATION AND CONFIGURATION Installation and configuration of the NVIDIA FreeBSD Driver Set on a notebook is the same as for any desktop environment, with a few additions, as described below. -15B. POWER MANAGEMENT +17B. POWER MANAGEMENT All notebook NVIDIA GPUs support power management, both S3 (also known as "Standby" or "Suspend to RAM") and S4 (also known as "Hibernate", "Suspend to @@ -2029,7 +2117,7 @@ by default on some notebooks. Please see the known issues below for more details. -15C. HOTKEY SWITCHING OF DISPLAY DEVICES +17C. HOTKEY SWITCHING OF DISPLAY DEVICES Mobile NVIDIA GPUs also have the capacity to react to a display change hotkey event, toggling between each of the connected display devices and each @@ -2072,7 +2160,7 @@ will be used as when you switched away, regardless of what display change hotkey activity occurred while the virtual terminal was active. -15D. DOCKING EVENTS +17D. DOCKING EVENTS All notebook NVIDIA GPUs support docking, however support may be limited by the OS or system. There are three types of notebook docking (hot, warm, and @@ -2083,10 +2171,10 @@ system that has been powered off. Only warm and cold docking are supported by the NVIDIA driver. -15E. TWINVIEW +17E. TWINVIEW All notebook NVIDIA GPUs support TwinView. TwinView on a notebook can be -configured in the same way as on a desktop computer (refer to Chapter 10 ); +configured in the same way as on a desktop computer (refer to Chapter 12 ); note that in a TwinView configuration using the notebook's internal flat panel and an external CRT, the CRT is the primary display device (specify its HorizSync and VertRefresh in the Monitor section of your X config file) and @@ -2097,10 +2185,10 @@ options). The "UseEdidFreqs" X config option is enabled by default, so normally you should not need to specify the "SecondMonitorHorizSync" and "SecondMonitorVertRefresh" options. See the description of the UseEdidFreqs -option in Appendix F for details). +option in Appendix B for details). -15F. KNOWN NOTEBOOK ISSUES +17F. KNOWN NOTEBOOK ISSUES There are a few known issues associated with notebooks: @@ -2111,7 +2199,7 @@ There are a few known issues associated with notebooks: problematic. o ACPI Display change hotkey switching is not supported by X.Org X servers - earlier than 1.2.0; see EnableACPIHotkeys in Appendix F for details. + earlier than 1.2.0; see EnableACPIHotkeys in Appendix B for details. o In many cases, suspending and/or resuming will fail. As mentioned above, this functionality is very system-specific. There are still many cases @@ -2143,7 +2231,7 @@ There are a few known issues associated with notebooks: ______________________________________________________________________________ -Chapter 16. Programming Modes +Chapter 18. Programming Modes ______________________________________________________________________________ The NVIDIA Accelerated FreeBSD Graphics Driver supports all standard VGA and @@ -2168,7 +2256,7 @@ example: See the nvidia-xconfig(1) man page for details. -16A. DEPTH, BITS PER PIXEL, AND PITCH +18A. DEPTH, BITS PER PIXEL, AND PITCH While not directly a concern when programming modes, the bits used per pixel is an issue when considering the maximum programmable resolution; for this @@ -2194,7 +2282,7 @@ think of this as the horizontal resolution multiplied by the bytes per pixel product due to alignment constraints. -16B. MAXIMUM RESOLUTIONS +18B. MAXIMUM RESOLUTIONS The NVIDIA Accelerated FreeBSD Graphics Driver and NVIDIA GPU-based graphics cards support resolutions up to 8192x8192 pixels for the GeForce 8 series and @@ -2207,7 +2295,7 @@ refresh rate, video memory bandwidth used by a programmed mode does affect the overlay quality. -16C. USEFUL FORMULAS +18C. USEFUL FORMULAS The maximum resolution is a function both of the amount of video memory and the bits per pixel you elect to use: @@ -2246,7 +2334,7 @@ the log file. Your X log should contain a line like this: which indicates the maximum pixel clock for that display device. -16D. HOW MODES ARE VALIDATED +18D. HOW MODES ARE VALIDATED In traditional XFree86/X.Org mode validation, the X server takes as a starting point the X server's internal list of VESA standard modes, plus any modes @@ -2339,11 +2427,11 @@ extensions. If only one display device is in use by the X screen when the X server starts, all modes in the mode pool are implicitly made available to the X server. See -the "IncludeImplicitMetaModes" X configuration option in Appendix F for +the "IncludeImplicitMetaModes" X configuration option in Appendix B for details. -16E. THE NVIDIA-AUTO-SELECT MODE +18E. THE NVIDIA-AUTO-SELECT MODE You can request a special mode by name in the X config file, named "nvidia-auto-select". When the X driver builds the mode pool for a display @@ -2403,15 +2491,14 @@ and restarting your X server. The X driver can generally do a much better job of selecting the "nvidia-auto-select" mode if the display device's EDID is available. This is -one reason why the "IgnoreEDID" X configuration option has been deprecated, -and that it is recommended to only use the "UseEDID" X configuration option -sparingly. Note that, rather than globally disable all uses of the EDID with -the "UseEDID" option, you can individually disable each particular use of the -EDID using the "UseEDIDFreqs", "UseEDIDDpi", and/or the "NoEDIDModes" argument -in the "ModeValidation" X configuration option. +one reason why it is recommended to only use the "UseEDID" X configuration +option sparingly. Note that, rather than globally disable all uses of the EDID +with the "UseEDID" option, you can individually disable each particular use of +the EDID using the "UseEDIDFreqs", "UseEDIDDpi", and/or the "NoEDIDModes" +argument in the "ModeValidation" X configuration option. -16F. MODE VALIDATION REPORTING +18F. MODE VALIDATION REPORTING When log verbosity is set to 6 or higher (see FAQ section on increasing the amount of data printed in the X log file), the X log @@ -2420,7 +2507,7 @@ and report whether the mode passed or failed. For modes that were considered invalid, the log will report why the mode was considered invalid. -16G. ENSURING IDENTICAL MODE TIMINGS +18G. ENSURING IDENTICAL MODE TIMINGS Some functionality, such as Active Stereo with TwinView, requires control over exactly which mode timings are used. For explicit control over which mode @@ -2441,7 +2528,7 @@ this: -16H. ADDITIONAL INFORMATION +18H. ADDITIONAL INFORMATION An XFree86 ModeLine generator, conforming to the GTF Standard is available at http://gtf.sourceforge.net/. Additional generators can be found by searching @@ -2449,7 +2536,7 @@ for "modeline" on freshmeat.net. ______________________________________________________________________________ -Chapter 17. Configuring Flipping and UBB +Chapter 19. Configuring Flipping and UBB ______________________________________________________________________________ The NVIDIA Accelerated FreeBSD Graphics Driver supports Unified Back Buffer @@ -2459,7 +2546,7 @@ certain situations. o Unified Back Buffer (UBB): UBB is available only on the Quadro family of GPUs (Quadro4 NVS excluded) and is enabled by default when there is sufficient video memory available. This can be disabled with the UBB X - config option described in Appendix F. When UBB is enabled, all windows + config option described in Appendix B. When UBB is enabled, all windows share the same back, stencil and depth buffers. When there are many windows, the back, stencil and depth usage will never exceed the size of that used by a full screen window. However, even for a single small @@ -2482,7 +2569,7 @@ certain situations. ______________________________________________________________________________ -Appendix C. The Sysctl Interface +Chapter 20. The Sysctl Interface ______________________________________________________________________________ The sysctl interface allows you to obtain run-time information about the @@ -2558,7 +2645,7 @@ hw.nvidia.registry.* ______________________________________________________________________________ -Appendix D. Configuring Low-level Parameters +Chapter 21. Configuring Low-level Parameters ______________________________________________________________________________ The NVIDIA resource manager recognizes several low-level configuration @@ -2700,7 +2787,7 @@ EnableAGPFW ______________________________________________________________________________ -Chapter 18. Using the X Composite Extension +Chapter 22. Using the X Composite Extension ______________________________________________________________________________ X.Org X servers, beginning with X11R6.8.0, contain experimental support for a @@ -2710,7 +2797,7 @@ the Damage and Render extensions, this allows a program called a composite manager to blend windows together to draw the screen. Performance will be degraded significantly if the "RenderAccel" option is -disabled in xorg.conf. See Appendix F for more details. +disabled in xorg.conf. See Appendix B for more details. When the NVIDIA X driver is used with an X.Org X server X11R6.9.0 or newer and the Composite extension is enabled, NVIDIA's OpenGL implementation interacts @@ -2751,6 +2838,10 @@ The Composite extension also causes problems with other driver components: are incompatible with Composite. These features will be automatically disabled when Composite is detected. + o The Composite extension is currently incompatible with Xinerama, due to + limitations in the X.Org X server. Composite will be automatically + disabled when Xinerama is enabled. + This NVIDIA FreeBSD supports OpenGL rendering to 32-bit ARGB windows on X.Org 7.2 and higher or when the "AddARGBGLXVisuals" X config file option is @@ -2823,7 +2914,7 @@ http://freedesktop.org/Software/CompositeExt ______________________________________________________________________________ -Chapter 19. Using the nvidia-settings Utility +Chapter 23. Using the nvidia-settings Utility ______________________________________________________________________________ A graphical configuration utility, 'nvidia-settings', is included with the @@ -2837,19 +2928,17 @@ in a terminal window. Detailed information about the configuration options available are documented in the help window in the utility. -For more information, see the nvidia-settings man page or the user guide -available here: -ftp://download.nvidia.com/XFree86/Linux-x86/nvidia-settings-user-guide.txt +For more information, see the nvidia-settings man page. The source code to nvidia-settings is released as GPL and is available here: ftp://download.nvidia.com/XFree86/nvidia-settings/ If you have trouble running the nvidia-settings binary shipped with the NVIDIA -FreeBSD Graphics Driver, refer to the nvidia-settings entry in Chapter 6. +FreeBSD Graphics Driver, refer to the nvidia-settings entry in Chapter 8. ______________________________________________________________________________ -Chapter 20. Configuring SLI and Multi-GPU FrameRendering +Chapter 24. Configuring SLI and Multi-GPU FrameRendering ______________________________________________________________________________ The NVIDIA FreeBSD driver contains support for NVIDIA SLI FrameRendering and @@ -2865,6 +2954,9 @@ together GPUs on the same graphics card, you should use the "MultiGPU" X config option. If you have two cards, each with two GPUs, and you wish to link them all together, you should use the "SLI" option. + +24A. RENDERING MODES + In FreeBSD, with two GPUs SLI and Multi-GPU can both operate in one of three modes: Alternate Frame Rendering (AFR), Split Frame Rendering (SFR), and Antialiasing (AA). When AFR mode is active, one GPU draws the next frame while @@ -2885,8 +2977,16 @@ AFR of AA, pairs of GPUs render alternate frames, each GPU in a pair doing half of the antialiasing work. Note that these scenarios apply whether you have four separate cards or you have two cards, each with two GPUs. +With a Quadro Plex Visual Computing System (VCS), the same options as above +are available, if your Quadro Plex VCS has two or four GPUs. In addition, +there is a special SLI Mosaic Mode to extend a single X screen transparently +across all of the available display outputs on the Quadro Plex VCS. + + +24B. ENABLING MULTI-GPU + Multi-GPU is enabled by setting the "MultiGPU" option in the X configuration -file; see Appendix F for details about the "MultiGPU" option. +file; see Appendix B for details about the "MultiGPU" option. The nvidia-xconfig utility can be used to set the "MultiGPU" option, rather than modifying the X configuration file by hand. For example: @@ -2894,8 +2994,11 @@ than modifying the X configuration file by hand. For example: % nvidia-xconfig --multigpu=on + +24C. ENABLING SLI + SLI is enabled by setting the "SLI" option in the X configuration file; see -Appendix F for details about the SLI option. +Appendix B for details about the SLI option. The nvidia-xconfig utility can be used to set the SLI option, rather than modifying the X configuration file by hand. For example: @@ -2904,7 +3007,54 @@ modifying the X configuration file by hand. For example: -20A. HARDWARE REQUIREMENTS +24D. ENABLING SLI MOSAIC MODE + +The simplest way to configure Mosaic Mode using a grid of monitors is to use +'nvidia-settings' (see Chapter 23). The steps to perform this configuration +are as follows: + + + + 1. Install your Quadro Plex VCS into the system, following the steps + provided in the Quadro Plex Installation Guide. + + 2. Connect all of the monitors you would like to use to the Quadro Plex VCS. + If you are going to use fewer monitors than there are connectors, connect + one monitor to each GPU before adding a second monitor to any GPUs. + + 3. Install the NVIDIA display driver set. + + 4. Configure an X screen to use the "nvidia" driver on at least one of the + GPUs in your Quadro Plex VCS (see Chapter 6 for more information). + + 5. Start X. + + 6. Run 'nvidia-settings'. You should see a tab in the left pane of + nvidia-settings labeled "SLI Mosaic Mode Settings". Note that you may + need to expand the entry for the X screen you configured earlier. + + 7. Check the "Use SLI Mosaic Mode" check box. + + 8. Select the monitor grid configuration you'd like to use from the "display + configuration" dropdown. + + 9. Choose the resolution and refresh rate at which you would like to drive + each individual monitor. + + 10. Set any overlap you would like between the displays. + + 11. Click the "Save to X Configuration File" button. NOTE: If you don't have + permissions to write to your system's X configuration file, you will be + prompted to choose a location to save the file. After doing so, you MUST + copy the X configuration file into a location the X server will consider + upon startup (usually '/etc/X11/xorg.conf' for X.Org servers or + '/etc/X11/XF86Config' for XFree86 servers). + + 12. Exit nvidia-settings and restart your X server. + + + +24E. HARDWARE REQUIREMENTS SLI functionality requires: @@ -2914,12 +3064,14 @@ SLI functionality requires: o In most cases, a video bridge connecting the two graphics cards + o A Quadro Plex VCS to use Mosaic Mode + For the latest in supported SLI and Multi-GPU configurations, including SLI- and Multi-GPU capable GPUs and SLI-capable motherboards, see http://www.slizone.com. -20B. OTHER NOTES AND REQUIREMENTS +24F. OTHER NOTES AND REQUIREMENTS The following other requirements apply to SLI and Multi-GPU: @@ -2928,12 +3080,13 @@ The following other requirements apply to SLI and Multi-GPU: o SLI on Quadro-based graphics cards always requires a video bridge o TwinView is also not supported with SLI or Multi-GPU. Only one display - can be used when SLI or Multi-GPU is enabled. + can be used when SLI or Multi-GPU is enabled, with the exception of + Mosaic. o If X is configured to use multiple screens and screen 0 has SLI or - Multi-GPU enabled, the other screens will be disabled. Note that if SLI - or Multi-GPU is enabled, the GPUs used by that configuration will be - unavailable for single GPU rendering. + Multi-GPU enabled, the other screens configured to use the nvidia driver + will be disabled. Note that if SLI or Multi-GPU is enabled, the GPUs used + by that configuration will be unavailable for single GPU rendering. @@ -2977,7 +3130,7 @@ A. The NVIDIA Accelerated FreeBSD Graphics Driver does not automatically ______________________________________________________________________________ -Chapter 21. Configuring Frame Lock and Genlock +Chapter 25. Configuring Frame Lock and Genlock ______________________________________________________________________________ NOTE: Frame Lock and Genlock features are supported only on specific hardware, @@ -2996,7 +3149,7 @@ capabilities of the NVIDIA driver. This section describes the setup and use of frame lock and genlock. -21A. DEFINITION OF TERMS +25A. DEFINITION OF TERMS GENLOCK: Genlock refers to the process of synchronizing the pixel scanning of one or more displays to an external synchronization source. NVIDIA Genlock @@ -3027,7 +3180,7 @@ lock/Genlock. This can be a graphics card (Quadro FX 3000G) or a stand alone device (Quadro FX G-Sync). See "Supported Hardware" below. -21B. SUPPORTED HARDWARE +25B. SUPPORTED HARDWARE Frame lock and genlock are supported for the following hardware: @@ -3041,7 +3194,7 @@ Frame lock and genlock are supported for the following hardware: -21C. HARDWARE SETUP +25C. HARDWARE SETUP 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 @@ -3056,7 +3209,7 @@ performed when the system is off. "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 - Chapter 20) or other multi-GPU configurations, you should connect the + Chapter 24) 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. @@ -3071,10 +3224,10 @@ performed when the system is off. 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 FreeBSD Driver Set. If you have not done so, -see Chapter 2. +see Chapter 3. -21D. CONFIGURATION WITH NVIDIA-SETTINGS GUI +25D. CONFIGURATION WITH NVIDIA-SETTINGS GUI Frame lock and genlock are configured through the nvidia-settings utility. See the 'nvidia-settings(1)' man page, and the nvidia-settings online help (click @@ -3097,7 +3250,7 @@ The setup of genlock and frame lock are described separately. We then describe the use of genlock and frame lock together. -21E. GENLOCK SETUP +25E. GENLOCK SETUP 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 @@ -3144,12 +3297,12 @@ Modifications to genlock settings (e.g., "Use House Sync if Present", "Add Devices...") must be done while synchronization is disabled. -21F. FRAME LOCK SETUP +25F. FRAME LOCK SETUP 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 Chapter 16 for information +must be configured with identical mode timings. See Chapter 18 for information on mode timings. Connect the systems through their RJ45 ports using standard CAT5 patch cables. @@ -3198,7 +3351,7 @@ 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 Chapter 16 for information on +the "Disable Frame Lock" button and refer to Chapter 18 for information on mode timings. Modifications to frame lock settings (e.g. "Add/Remove Devices...") must be @@ -3212,7 +3365,7 @@ line such as the following can be added to the '~/.xinitrc' file: -21G. FRAME LOCK + GENLOCK +25G. FRAME LOCK + GENLOCK 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 @@ -3229,7 +3382,7 @@ button. As with other frame lock/genlock controls, you must select the signal server while synchronization is disabled. -21H. CONFIGURATION WITH NVIDIA-SETTINGS COMMAND LINE +25H. CONFIGURATION WITH NVIDIA-SETTINGS COMMAND LINE 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 @@ -3421,7 +3574,7 @@ For a full list of the nvidia-settings Frame Lock attributes, please see the -21I. LEVERAGING FRAME LOCK/GENLOCK IN OPENGL +25I. LEVERAGING FRAME LOCK/GENLOCK IN OPENGL 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 @@ -3429,7 +3582,7 @@ 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. -21J. FRAME LOCK RESTRICTIONS: +25J. FRAME LOCK RESTRICTIONS: The following restrictions must be met for enabling frame lock: @@ -3440,7 +3593,7 @@ The following restrictions must be met for enabling frame lock: signal. 2. All X Screens (driving the selected client/server display devices) must - have the same stereo setting. See Appendix F for instructions on how to + have the same stereo setting. See Appendix B for instructions on how to set the stereo X option. 3. The frame lock server (master) display device must be on a GPU on the @@ -3461,7 +3614,7 @@ The following restrictions must be met for enabling frame lock: -21K. SUPPORTED FRAME LOCK CONFIGURATIONS: +25K. SUPPORTED FRAME LOCK CONFIGURATIONS: The following configurations are currently supported: @@ -3498,7 +3651,7 @@ The following configurations are currently supported: ______________________________________________________________________________ -Chapter 22. Configuring SDI Video Output +Chapter 26. Configuring SDI Video Output ______________________________________________________________________________ Broadcast, film, and video post production and digital cinema applications can @@ -3514,11 +3667,11 @@ SDI and HD-SDI video output is provided through the use of the NVIDIA driver along with an NVIDIA SDI output daughter board. In addition to single- and dual-link SDI/HD-SDI digital video output, frame lock and genlock synchronization are provided in order to synchronize the outgoing video with -an external source signal (see Chapter 21 for details on these technologies). +an external source signal (see Chapter 25 for details on these technologies). This section describes the setup and use of the SDI video output. -22A. HARDWARE SETUP +26A. HARDWARE SETUP Before you begin, you should check that your hardware has been properly installed. If you are using the Quadro FX 4000 SDI, the SDI/HD-SDI hardware is @@ -3553,10 +3706,10 @@ must be performed when the system is off. Once the above installation is complete, you may boot the system and configure the SDI video output using nvidia-settings. These instructions assume that you have already successfully installed the NVIDIA FreeBSD Accelerated Graphics -Driver. If you have not done so, see Chapter 2 for details. +Driver. If you have not done so, see Chapter 3 for details. -22B. CLONE MODE CONFIGURATION WITH 'nvidia-settings' +26B. CLONE MODE CONFIGURATION WITH 'nvidia-settings' SDI video output is configured through the nvidia-settings utility. See the 'nvidia-settings(1)' man page, and the nvidia-settings online help (click the @@ -3624,7 +3777,7 @@ configure the SDI video output. -22C. CONFIGURATION FOR TWINVIEW OR AS A SEPARATE X SCREEN +26C. CONFIGURATION FOR TWINVIEW OR AS A SEPARATE X SCREEN SDI video output can be configured through the nvidia-settings X Server Display Configuration page, for use in TwinView or as a separate X screen. The @@ -3650,7 +3803,7 @@ in TwinView or as a separate X screen. ______________________________________________________________________________ -Chapter 23. Configuring Depth 30 Displays +Chapter 27. Configuring Depth 30 Displays ______________________________________________________________________________ This driver release supports X screens with screen depths of 30 bits per pixel @@ -3658,9 +3811,12 @@ This driver release supports X screens with screen depths of 30 bits per pixel chip architectures. This provides about 1 billion possible colors, allowing for higher color precision and smoother gradients. -When displaying a depth 30 image on a digital flat panel, the color data will -be dithered to 8 or 6 bits per pixel, depending on the capabilities of the -flat panel. VGA outputs can display the full 10 bit range of colors. +When displaying a depth 30 image, the color data may be dithered to lower bit +depths, depending on the capabilities of the display device and how it is +connected to the GPU. Some devices connected via analog VGA, DisplayPort, and +HDMI can display the full 10 bit range of colors. Devices connected via DVI, +as well as laptop internal panels connected via LVDS, will be dithered to 8 or +6 bits per pixel. To work reliably, depth 30 requires X.Org 7.3 or higher and pixman 0.11.6 or higher. @@ -3675,7 +3831,7 @@ start. ______________________________________________________________________________ -Chapter 24. NVIDIA Contact Info and Additional Resources +Chapter 28. NVIDIA Contact Info and Additional Resources ______________________________________________________________________________ If you believe that you have found a bug or have a problem that you need @@ -3701,7 +3857,7 @@ OpenGL ______________________________________________________________________________ -Chapter 25. Credits +Chapter 29. Credits ______________________________________________________________________________ The port of the NVIDIA driver to FreeBSD is due in no small part to the many @@ -3710,7 +3866,7 @@ Dodd . ______________________________________________________________________________ -Chapter 26. Acknowledgements +Chapter 30. Acknowledgements ______________________________________________________________________________ The driver splash screen is decoded using 'libpng': @@ -3725,264 +3881,282 @@ __cmpdi2, __fixunssfdi, __fixunsdfdi, __ashldi3 and __lshrdi3. ______________________________________________________________________________ -Appendix E. Supported NVIDIA GPU Products +Appendix A. Supported NVIDIA GPU Products ______________________________________________________________________________ For the most complete and accurate listing of supported GPUs, please see the Supported Products List, available from the NVIDIA FreeBSD x86 Graphics Driver download page. Please go to http://www.nvidia.com/object/unix.html, follow the -Archive link under the FreeBSD x86 heading, follow the link for the 180.29 +Archive link under the FreeBSD x86 heading, follow the link for the 185.18.36 driver, and then go to the Supported Products List. -E1. NVIDIA GEFORCE GPUS - - - NVIDIA GPU product Device PCI ID - ------------------------------------------------------ --------------- - GeForce 6800 Ultra 0x0040 - GeForce 6800 0x0041 - GeForce 6800 LE 0x0042 - GeForce 6800 XE 0x0043 - GeForce 6800 XT 0x0044 - GeForce 6800 GT 0x0045 - GeForce 6800 GT 0x0046 - GeForce 6800 GS 0x0047 - GeForce 6800 XT 0x0048 - GeForce 7800 GTX 0x0090 - GeForce 7800 GTX 0x0091 - GeForce 7800 GT 0x0092 - GeForce 7800 GS 0x0093 - GeForce 7800 SLI 0x0095 - GeForce Go 7800 0x0098 - GeForce Go 7800 GTX 0x0099 - GeForce 6800 GS 0x00C0 - GeForce 6800 0x00C1 - GeForce 6800 LE 0x00C2 - GeForce 6800 XT 0x00C3 - GeForce Go 6800 0x00C8 - GeForce Go 6800 Ultra 0x00C9 - Unknown GPU 0x00F0 - GeForce 6600 GT 0x00F1 - GeForce 6600 0x00F2 - GeForce 6200 0x00F3 - GeForce 6600 LE 0x00F4 - GeForce 7800 GS 0x00F5 - GeForce 6800 GS 0x00F6 - GeForce 6800 Ultra 0x00F9 - GeForce 6600 GT 0x0140 - GeForce 6600 0x0141 - GeForce 6600 LE 0x0142 - GeForce 6600 VE 0x0143 - GeForce Go 6600 0x0144 - GeForce 6610 XL 0x0145 - GeForce Go 6600 TE/6200 TE 0x0146 - GeForce 6700 XL 0x0147 - GeForce Go 6600 0x0148 - GeForce Go 6600 GT 0x0149 - GeForce 6200 0x014F - GeForce 6500 0x0160 - GeForce 6200 TurboCache(TM) 0x0161 - GeForce 6200SE TurboCache(TM) 0x0162 - GeForce 6200 LE 0x0163 - GeForce Go 6200 0x0164 - GeForce Go 6400 0x0166 - GeForce Go 6200 0x0167 - GeForce Go 6400 0x0168 - GeForce 6250 0x0169 - GeForce 7100 GS 0x016A - GeForce 8800 GTX 0x0191 - GeForce 8800 GTS 0x0193 - GeForce 8800 Ultra 0x0194 - Tesla C870 0x0197 - GeForce 7350 LE 0x01D0 - GeForce 7300 LE 0x01D1 - GeForce 7300 SE/7200 GS 0x01D3 - GeForce Go 7200 0x01D6 - GeForce Go 7300 0x01D7 - GeForce Go 7400 0x01D8 - GeForce 7500 LE 0x01DD - GeForce 7300 GS 0x01DF - GeForce 6800 0x0211 - GeForce 6800 LE 0x0212 - GeForce 6800 GT 0x0215 - GeForce 6800 XT 0x0218 - GeForce 6200 0x0221 - GeForce 6200 A-LE 0x0222 - GeForce 6150 0x0240 - GeForce 6150 LE 0x0241 - GeForce 6100 0x0242 - GeForce Go 6150 0x0244 - GeForce Go 6100 0x0247 - GeForce 7900 GTX 0x0290 - GeForce 7900 GT/GTO 0x0291 - GeForce 7900 GS 0x0292 - GeForce 7950 GX2 0x0293 - GeForce 7950 GX2 0x0294 - GeForce 7950 GT 0x0295 - GeForce Go 7950 GTX 0x0297 - GeForce Go 7900 GS 0x0298 - GeForce Go 7900 GTX 0x0299 - GeForce 7600 GT 0x02E0 - GeForce 7600 GS 0x02E1 - GeForce 7300 GT 0x02E2 - GeForce 7900 GS 0x02E3 - GeForce 7950 GT 0x02E4 - GeForce 7650 GS 0x0390 - GeForce 7600 GT 0x0391 - GeForce 7600 GS 0x0392 - GeForce 7300 GT 0x0393 - GeForce 7600 LE 0x0394 - GeForce 7300 GT 0x0395 - GeForce Go 7700 0x0397 - GeForce Go 7600 0x0398 - GeForce Go 7600 GT 0x0399 - GeForce 6150SE nForce 430 0x03D0 - GeForce 6100 nForce 405 0x03D1 - GeForce 6100 nForce 400 0x03D2 - GeForce 6100 nForce 420 0x03D5 - GeForce 8600 GTS 0x0400 - GeForce 8600 GT 0x0401 - GeForce 8600 GT 0x0402 - GeForce 8600GS 0x0403 - GeForce 8400 GS 0x0404 - GeForce 9500M GS 0x0405 - GeForce 8600M GT 0x0407 - GeForce 9650M GS 0x0408 - GeForce 8700M GT 0x0409 - GeForce 8400 SE 0x0420 - GeForce 8500 GT 0x0421 - GeForce 8400 GS 0x0422 - GeForce 8300 GS 0x0423 - GeForce 8400 GS 0x0424 - GeForce 8600M GS 0x0425 - GeForce 8400M GT 0x0426 - GeForce 8400M GS 0x0427 - GeForce 8400M G 0x0428 - GeForce 9400 GT 0x042C - GeForce 9300M G 0x042E - GeForce 7150M / nForce 630M 0x0531 - GeForce 7000M / nForce 610M 0x0533 - GeForce 7050 PV / NVIDIA nForce 630a 0x053A - GeForce 7050 PV / NVIDIA nForce 630a 0x053B - GeForce 7025 / NVIDIA nForce 630a 0x053E - GeForce GTX 295 0x05E0 - GeForce GTX 280 0x05E1 - GeForce GTX 260 0x05E2 - GeForce GTX 285 0x05E3 - GeForce 8800 GTS 512 0x0600 - GeForce 9800 GT 0x0601 - GeForce 8800 GT 0x0602 - GeForce 9800 GX2 0x0604 - GeForce 9800 GT 0x0605 - GeForce 8800 GS 0x0606 - GeForce 9800M GTX 0x0608 - GeForce 8800M GTS 0x0609 - GeForce 9800M GT 0x060B - GeForce 8800M GTX 0x060C - GeForce 8800 GS 0x060D - GeForce 9600 GSO 0x0610 - GeForce 8800 GT 0x0611 - GeForce 9800 GTX/9800 GTX+ 0x0612 - GeForce 9800 GTX+ 0x0613 - GeForce 9800 GT 0x0614 - GeForce 9800M GTX 0x0617 - GeForce 9600 GT 0x0622 - GeForce 9600 GS 0x0623 - GeForce 9800M GTS 0x0628 - GeForce 9700M GTS 0x062A - GeForce 9800M GS 0x062B - GeForce 9800M GTS 0x062C - GeForce 9500 GT 0x0640 - GeForce 9500 GT 0x0643 - GeForce 9600M GT 0x0647 - GeForce 9600M GS 0x0648 - GeForce 9600M GT 0x0649 - GeForce 9700M GT 0x064A - GeForce 9500M G 0x064B - GeForce 9650M GT 0x064C - GeForce 9650 S 0x0656 - GeForce 9300 GE 0x06E0 - GeForce 9300 GS 0x06E1 - GeForce 8400 GS 0x06E4 - GeForce 9300M GS 0x06E5 - GeForce 9200M GS 0x06E8 - GeForce 9300M GS 0x06E9 - GeForce 7150 / NVIDIA nForce 630i 0x07E0 - GeForce 7100 / NVIDIA nForce 630i 0x07E1 - GeForce 7050 / NVIDIA nForce 610i 0x07E3 - GeForce 9100M G 0x0844 - GeForce 8200M G 0x0845 - GeForce 9100 0x0847 - GeForce 8300 0x0848 - GeForce 8200 0x0849 - nForce 730a 0x084A - GeForce 8200 0x084B - nForce 780a SLI 0x084C - nForce 750a SLI 0x084D - GeForce 8100 / nForce 720a 0x084F - GeForce 9400M G 0x0862 - GeForce 9400M 0x0863 - - - -E2. NVIDIA QUADRO GPUS - - - NVIDIA GPU product Device PCI ID - ------------------------------------------------------ --------------- - Quadro FX 4000 0x004E - Quadro FX 4500 0x009D - Quadro FX Go1400 0x00CC - Quadro FX 3450/4000 SDI 0x00CD - Quadro FX 1400 0x00CE - Quadro FX 4400/Quadro FX 3400 0x00F8 - Quadro NVS 440 0x014A - Quadro FX 540M 0x014C - Quadro FX 550 0x014D - Quadro FX 540 0x014E - Quadro NVS 285 0x0165 - Quadro FX 5600 0x019D - Quadro FX 4600 0x019E - Quadro NVS 110M 0x01D7 - Quadro NVS 110M 0x01DA - Quadro NVS 120M 0x01DB - Quadro FX 350M 0x01DC - Quadro FX 350 0x01DE - Quadro NVS 210S / NVIDIA GeForce 6150LE 0x0245 - Quadro FX 2500M 0x029A - Quadro FX 1500M 0x029B - Quadro FX 5500 0x029C - Quadro FX 3500 0x029D - Quadro FX 1500 0x029E - Quadro FX 4500 X2 0x029F - Quadro FX 560 0x039E - Quadro FX 370 0x040A - Quadro NVS 320M 0x040B - Quadro FX 570M 0x040C - Quadro FX 1600M 0x040D - Quadro FX 570 0x040E - Quadro FX 1700 0x040F - Quadro NVS 140M 0x0429 - Quadro NVS 130M 0x042A - Quadro NVS 135M 0x042B - Quadro FX 360M 0x042D - Quadro NVS 290 0x042F - Quadro CX 0x05F9 - Quadro FX 5800 0x05FD - Quadro FX 4800 0x05FE - Quadro FX 3700 0x061A - Quadro FX 3600M 0x061C - Quadro FX 2700M 0x063A - Quadro FX 770M 0x065C - Quadro NVS 150M 0x06EA - Quadro NVS 160M 0x06EB - Quadro NVS 420 0x06F8 - Quadro FX 370 LP 0x06F9 - Quadro NVS 450 0x06FA - Quadro NVS 295 0x06FD - Quadro FX 470 0x087A - Quadro FX 470M 0x087F +A1. NVIDIA GEFORCE GPUS + + + NVIDIA GPU product Device PCI ID + ---------------------------------- ---------------------------------- + GeForce 6800 Ultra 0x0040 + GeForce 6800 0x0041 + GeForce 6800 LE 0x0042 + GeForce 6800 XE 0x0043 + GeForce 6800 XT 0x0044 + GeForce 6800 GT 0x0045 + GeForce 6800 GT 0x0046 + GeForce 6800 GS 0x0047 + GeForce 6800 XT 0x0048 + GeForce 7800 GTX 0x0090 + GeForce 7800 GTX 0x0091 + GeForce 7800 GT 0x0092 + GeForce 7800 GS 0x0093 + GeForce 7800 SLI 0x0095 + GeForce Go 7800 0x0098 + GeForce Go 7800 GTX 0x0099 + GeForce 6800 GS 0x00C0 + GeForce 6800 0x00C1 + GeForce 6800 LE 0x00C2 + GeForce 6800 XT 0x00C3 + GeForce Go 6800 0x00C8 + GeForce Go 6800 Ultra 0x00C9 + GeForce 6600 GT 0x00F1 + GeForce 6600 0x00F2 + GeForce 6200 0x00F3 + GeForce 6600 LE 0x00F4 + GeForce 7800 GS 0x00F5 + GeForce 6800 GS 0x00F6 + GeForce 6800 Ultra 0x00F9 + GeForce 6600 GT 0x0140 + GeForce 6600 0x0141 + GeForce 6600 LE 0x0142 + GeForce 6600 VE 0x0143 + GeForce Go 6600 0x0144 + GeForce 6610 XL 0x0145 + GeForce Go 6600 TE/6200 TE 0x0146 + GeForce 6700 XL 0x0147 + GeForce Go 6600 0x0148 + GeForce Go 6600 GT 0x0149 + GeForce 6200 0x014F + GeForce 6500 0x0160 + GeForce 6200 TurboCache(TM) 0x0161 + GeForce 6200SE TurboCache(TM) 0x0162 + GeForce 6200 LE 0x0163 + GeForce Go 6200 0x0164 + GeForce Go 6400 0x0166 + GeForce Go 6200 0x0167 + GeForce Go 6400 0x0168 + GeForce 6250 0x0169 + GeForce 7100 GS 0x016A + GeForce 8800 GTX 0x0191 + GeForce 8800 GTS 0x0193 + GeForce 8800 Ultra 0x0194 + Tesla C870 0x0197 + GeForce 7350 LE 0x01D0 + GeForce 7300 LE 0x01D1 + GeForce 7300 SE/7200 GS 0x01D3 + GeForce Go 7200 0x01D6 + GeForce Go 7300 0x01D7 + GeForce Go 7400 0x01D8 + GeForce 7500 LE 0x01DD + GeForce 7300 GS 0x01DF + GeForce 6200 0x0221 + GeForce 6200 A-LE 0x0222 + GeForce 6150 0x0240 + GeForce 6150 LE 0x0241 + GeForce 6100 0x0242 + GeForce Go 6150 0x0244 + GeForce Go 6100 0x0247 + GeForce 7900 GTX 0x0290 + GeForce 7900 GT/GTO 0x0291 + GeForce 7900 GS 0x0292 + GeForce 7950 GX2 0x0293 + GeForce 7950 GX2 0x0294 + GeForce 7950 GT 0x0295 + GeForce Go 7950 GTX 0x0297 + GeForce Go 7900 GS 0x0298 + GeForce 7600 GT 0x02E0 + GeForce 7600 GS 0x02E1 + GeForce 7300 GT 0x02E2 + GeForce 7900 GS 0x02E3 + GeForce 7950 GT 0x02E4 + GeForce 7650 GS 0x0390 + GeForce 7600 GT 0x0391 + GeForce 7600 GS 0x0392 + GeForce 7300 GT 0x0393 + GeForce 7600 LE 0x0394 + GeForce 7300 GT 0x0395 + GeForce Go 7700 0x0397 + GeForce Go 7600 0x0398 + GeForce Go 7600 GT 0x0399 + GeForce 6150SE nForce 430 0x03D0 + GeForce 6100 nForce 405 0x03D1 + GeForce 6100 nForce 400 0x03D2 + GeForce 6100 nForce 420 0x03D5 + GeForce 8600 GTS 0x0400 + GeForce 8600 GT 0x0401 + GeForce 8600 GT 0x0402 + GeForce 8600 GS 0x0403 + GeForce 8400 GS 0x0404 + GeForce 9500M GS 0x0405 + GeForce 8600M GT 0x0407 + GeForce 9650M GS 0x0408 + GeForce 8700M GT 0x0409 + GeForce 8400 SE 0x0420 + GeForce 8500 GT 0x0421 + GeForce 8400 GS 0x0422 + GeForce 8300 GS 0x0423 + GeForce 8400 GS 0x0424 + GeForce 8600M GS 0x0425 + GeForce 8400M GT 0x0426 + GeForce 8400M GS 0x0427 + GeForce 8400M G 0x0428 + GeForce 9400 GT 0x042C + GeForce 9300M G 0x042E + GeForce 7150M / nForce 630M 0x0531 + GeForce 7000M / nForce 610M 0x0533 + GeForce 7050 PV / nForce 630a 0x053A + GeForce 7050 PV / nForce 630a 0x053B + GeForce 7025 / nForce 630a 0x053E + GeForce GTX 295 0x05E0 + GeForce GTX 280 0x05E1 + GeForce GTX 260 0x05E2 + GeForce GTX 285 0x05E3 + GeForce GTX 275 0x05E6 + GeForce GTX 295 0x05EB + GeForce 8800 GTS 512 0x0600 + GeForce 9800 GT 0x0601 + GeForce 8800 GT 0x0602 + GeForce 9800 GX2 0x0604 + GeForce 9800 GT 0x0605 + GeForce 8800 GS 0x0606 + GeForce 9800M GTX 0x0608 + GeForce 8800M GTS 0x0609 + GeForce GTX 280M 0x060A + GeForce 9800M GT 0x060B + GeForce 8800M GTX 0x060C + GeForce 8800 GS 0x060D + GeForce 9600 GSO 0x0610 + GeForce 8800 GT 0x0611 + GeForce 9800 GTX/9800 GTX+ 0x0612 + GeForce 9800 GTX+ 0x0613 + GeForce 9800 GT 0x0614 + GeForce GTS 250 0x0615 + GeForce 9800M GTX 0x0617 + GeForce GTX 260M 0x0618 + GeForce 9600 GT 0x0622 + GeForce 9600 GS 0x0623 + GeForce 9600 GSO 512 0x0625 + GeForce GT 130 0x0626 + GeForce GT 140 0x0627 + GeForce 9800M GTS 0x0628 + GeForce 9700M GTS 0x062A + GeForce 9800M GS 0x062B + GeForce 9800M GTS 0x062C + GeForce 9500 GT 0x0640 + GeForce 9400 GT 0x0641 + GeForce 9500 GT 0x0643 + GeForce 9500 GS 0x0644 + GeForce GT 120 0x0646 + GeForce 9600M GT 0x0647 + GeForce 9600M GS 0x0648 + GeForce 9600M GT 0x0649 + GeForce 9700M GT 0x064A + GeForce 9500M G 0x064B + GeForce 9650M GT 0x064C + GeForce GT 130M 0x0652 + GeForce 9650 S 0x0656 + GeForce 9300 GE 0x06E0 + GeForce 9300 GS 0x06E1 + GeForce 8400 GS 0x06E4 + GeForce 9300M GS 0x06E5 + GeForce G100 0x06E6 + GeForce 9200M GS 0x06E8 + GeForce 9300M GS 0x06E9 + GeForce G 103M 0x06EF + GeForce 7150 / nForce 630i 0x07E0 + GeForce 7100 / nForce 630i 0x07E1 + GeForce 7050 / nForce 610i 0x07E3 + GeForce 9100M G 0x0844 + GeForce 8200M G 0x0845 + GeForce 9100 0x0847 + GeForce 8300 0x0848 + GeForce 8200 0x0849 + nForce 730a 0x084A + GeForce 9200 0x084B + nForce 980a/780a SLI 0x084C + nForce 750a SLI 0x084D + GeForce 8100 / nForce 720a 0x084F + GeForce 9400M G 0x0862 + GeForce 9400M 0x0863 + GeForce 9300 / nForce 730i 0x086C + GeForce GT 230M 0x0A2A + GeForce GT 240M 0x0A34 + GeForce G210M 0x0A74 + GeForce GTS 260M 0x0CA8 + GeForce GTS 250M 0x0CA9 + + + +A2. NVIDIA QUADRO GPUS + + + NVIDIA GPU product Device PCI ID + ---------------------------------- ---------------------------------- + Quadro FX 4000 0x004E + Quadro FX 4500 0x009D + Quadro FX Go1400 0x00CC + Quadro FX 3450/4000 SDI 0x00CD + Quadro FX 1400 0x00CE + Quadro FX 3400/Quadro FX 4000 0x00F8 + Quadro NVS 440 0x014A + Quadro FX 540M 0x014C + Quadro FX 550 0x014D + Quadro FX 540 0x014E + Quadro NVS 285 0x0165 + Quadro FX 5600 0x019D + Quadro FX 4600 0x019E + Quadro NVS 110M 0x01DA + Quadro NVS 120M 0x01DB + Quadro FX 350M 0x01DC + Quadro FX 350 0x01DE + Quadro NVS 210S / GeForce 6150LE 0x0245 + Quadro NVS 510M 0x0299 + Quadro FX 2500M 0x029A + Quadro FX 1500M 0x029B + Quadro FX 5500 0x029C + Quadro FX 3500 0x029D + Quadro FX 1500 0x029E + Quadro FX 4500 X2 0x029F + Quadro FX 560 0x039E + Quadro FX 370 0x040A + Quadro NVS 320M 0x040B + Quadro FX 570M 0x040C + Quadro FX 1600M 0x040D + Quadro FX 570 0x040E + Quadro FX 1700 0x040F + Quadro NVS 140M 0x0429 + Quadro NVS 130M 0x042A + Quadro NVS 135M 0x042B + Quadro FX 360M 0x042D + Quadro NVS 290 0x042F + Quadro CX 0x05F9 + Quadro FX 5800 0x05FD + Quadro FX 4800 0x05FE + Quadro FX 3800 0x05FF + Quadro FX 3700 0x061A + Quadro FX 3600M 0x061C + Quadro FX 3700M 0x061E + Quadro FX 1800 0x0638 + Quadro FX 2700M 0x063A + Quadro FX 380 0x0658 + Quadro FX 580 0x0659 + Quadro FX 770M 0x065C + Quadro NVS 150M 0x06EA + Quadro NVS 160M 0x06EB + Quadro NVS 420 0x06F8 + Quadro FX 370 LP 0x06F9 + Quadro NVS 450 0x06FA + Quadro NVS 295 0x06FD + Quadro FX 470 0x087A Below are the legacy GPUs that are no longer supported in the unified driver. @@ -4112,7 +4286,7 @@ The 71.86.xx driver supports the following set of GPUs: ______________________________________________________________________________ -Appendix F. X Config Options +Appendix B. X Config Options ______________________________________________________________________________ The following driver options are supported by the NVIDIA X driver. They may be @@ -4133,7 +4307,7 @@ Option "NvAGP" "integer" Note that NVIDIA internal AGP support cannot work if AGPGART is either statically compiled into your kernel or is built as a module and loaded - into your kernel. See Chapter 9 for details. Default: 3. + into your kernel. See Chapter 11 for details. Default: 3. Option "NoLogo" "boolean" @@ -4165,12 +4339,12 @@ Option "NoRenderExtension" "boolean" Option "UBB" "boolean" Enable or disable the Unified Back Buffer on Quadro-based GPUs (Quadro4 - NVS excluded); see Chapter 17 for a description of UBB. This option has no + NVS excluded); see Chapter 19 for a description of UBB. This option has no effect on non-Quadro GPU products. Default: UBB is on for Quadro GPUs. Option "NoFlip" "boolean" - Disable OpenGL flipping; see Chapter 17 for a description. Default: OpenGL + Disable OpenGL flipping; see Chapter 19 for a description. Default: OpenGL will swap by flipping when possible. Option "Dac8Bit" "boolean" @@ -4255,7 +4429,7 @@ Option "RandRRotation" "boolean" rotation. This feature is supported using depth 24. This requires an X.Org X 6.8.1 or newer X server. This feature does not work with hardware overlays; emulated overlays will be used instead at a substantial - performance penalty. See Chapter 14 for details. Default: off. + performance penalty. See Chapter 16 for details. Default: off. Option "Rotate" "string" @@ -4415,7 +4589,7 @@ Option "UseEDID" "boolean" available, during construction of its mode pool. The EDID is used as a source for possible modes, for valid frequency ranges, and for collecting data on the physical dimensions of the display device for computing the - DPI (see Appendix I). However, if you wish to disable the driver's use of + DPI (see Appendix E). However, if you wish to disable the driver's use of the EDID, you can set this option to False: Option "UseEDID" "FALSE" @@ -4429,16 +4603,6 @@ Option "UseEDID" "boolean" Default: True (use EDID). -Option "IgnoreEDID" "boolean" - - This option is deprecated, and no longer affects behavior of the X driver. - See the "UseEDID" option for details. - -Option "NoDDC" "boolean" - - Synonym for "IgnoreEDID". This option is deprecated, and no longer affects - behavior of the X driver. See the "UseEDID" option for details. - Option "UseInt10Module" "boolean" Enable use of the X Int10 module to soft-boot all secondary cards, rather @@ -4447,31 +4611,31 @@ Option "UseInt10Module" "boolean" Option "TwinView" "boolean" - Enable or disable TwinView. See Chapter 10 for details. Default: off + Enable or disable TwinView. See Chapter 12 for details. Default: off (TwinView is disabled). Option "TwinViewOrientation" "string" Controls the relationship between the two display devices when using TwinView. Takes one of the following values: "RightOf" "LeftOf" "Above" - "Below" "Clone". See Chapter 10 for details. Default: string is NULL. + "Below" "Clone". See Chapter 12 for details. Default: string is NULL. Option "SecondMonitorHorizSync" "range(s)" This option is like the HorizSync entry in the Monitor section, but is for - the second monitor when using TwinView. See Chapter 10 for details. + the second monitor when using TwinView. See Chapter 12 for details. Default: none. Option "SecondMonitorVertRefresh" "range(s)" This option is like the VertRefresh entry in the Monitor section, but is - for the second monitor when using TwinView. See Chapter 10 for details. + for the second monitor when using TwinView. See Chapter 12 for details. Default: none. Option "MetaModes" "string" This option describes the combination of modes to use on each monitor when - using TwinView. See Chapter 10 for details. Default: string is NULL. + using TwinView. See Chapter 12 for details. Default: string is NULL. Option "NoTwinViewXineramaInfo" "boolean" @@ -4541,15 +4705,15 @@ Option "TwinViewXineramaInfoOverride" "string" Option "TVStandard" "string" - See Chapter 13 for details on configuring TV-out. + See Chapter 15 for details on configuring TV-out. Option "TVOutFormat" "string" - See Chapter 13 for details on configuring TV-out. + See Chapter 15 for details on configuring TV-out. Option "TVOverScan" "Decimal value in the range 0.0 to 1.0" - Valid values are in the range 0.0 through 1.0; See Chapter 13 for details + Valid values are in the range 0.0 through 1.0; See Chapter 15 for details on configuring TV-out. Option "Stereo" "integer" @@ -4592,29 +4756,54 @@ Option "Stereo" "integer" SeeReal Stereo Digital Flat Panels. 6 Color interleaved stereo mode, for use with Sharp3D Stereo Digital Flat Panels. + 7 Horizontal interlaced stereo mode, for use with + Arisawa, Hyundai, Zalman, Pavione, and Miracube + Digital Flat Panels. + 8 Checkerboard pattern stereo mode, for use with 3D + DLP Display Devices. + 9 Inverse checkerboard pattern stereo mode, for use + with 3D DLP Display Devices. Stereo is only available on Quadro cards. Stereo options 1, 2, and 3 (also known as "active" stereo) may be used with TwinView if all modes within - each MetaMode have identical timing values. See Chapter 16 for suggestions + each MetaMode have identical timing values. See Chapter 18 for suggestions on making sure the modes within your MetaModes are identical. The - identical ModeLine requirement is not necessary for Stereo option 4 - ("passive" stereo). Default: 0 (Stereo is not enabled). + identical ModeLine requirement is not necessary for Stereo options 4 + through 9 ("passive" stereo). Default: 0 (Stereo is not enabled). UBB must be enabled when stereo is enabled (this is the default behavior). - Stereo options 1, 2, and 3 ("active" stereo) are not supported on digital - flat panels. + Stereo options 1, 2, and 3 ("active" stereo) can be enabled on digital + display devices (connected via DVI, HDMI, or DisplayPort). However, some + digital display devices might not behave as desired with active stereo: + + o Some digital display devices may not be able to toggle pixel colors + quickly enough when flipping between eyes on every vblank. + + o Some digital display devices may have an optical polarization that + interferes with stereo goggles. + + o Active stereo requires high refresh rates, because a vertical refresh + is needed to display each eye. Some digital display devices have a + low refresh rate, which will result in flickering when used for + active stereo. + + o Some digital display devices might internally convert from other + refresh rates to their native refresh rate (e.g., 60Hz), resulting in + incompatible rates between the stereo glasses and stereo displayed on + screen. + + + Stereo applies to an entire X screen, so it will apply to all display + devices on that X screen, whether or not they all support the selected + Stereo mode. + + Stereo options 7, 8, and 9 are only supported on G8xGL and higher GPUs. Multi-GPU cards (such as the Quadro FX 4500 X2) provide a single connector for onboard stereo support (option 3), which is tied to the bottommost GPU. In order to synchronize onboard stereo with the other GPU, you must - use a G-Sync device (see Chapter 21 for details). - -Option "AllowDFPStereo" "boolean" - - By default, the NVIDIA X driver performs a check which disables active - stereo (stereo options 1, 2, and 3) if the X screen is driving a DFP. The - "AllowDFPStereo" option bypasses this check. + use a G-Sync device (see Chapter 25 for details). Option "ForceStereoFlipping" "boolean" @@ -4878,7 +5067,7 @@ Option "DPI" "string" will set the horizontal DPI to 75 and the vertical DPI to 85. By default, the X driver will compute the DPI of the X screen from the EDID of any - connected display devices. See Appendix I for details. Default: string is + connected display devices. See Appendix E for details. Default: string is NULL (disabled). Option "UseEdidDpi" "string" @@ -4898,7 +5087,7 @@ Option "UseEdidDpi" "string" Option "UseEdidDpi" "FALSE" - See Appendix I for details. Default: string is NULL (the driver computes + See Appendix E for details. Default: string is NULL (the driver computes the DPI from the EDID of a display device and selects the display device). Option "ConstantDPI" "boolean" @@ -5253,10 +5442,33 @@ Option "InitializeWindowBackingPixmaps" "boolean" Default: on (redirected windows are initialized). +Option "AllowUnofficialGLXProtocol" "boolean" + + By default, the NVIDIA GLX implementation will not expose GLX protocol for + GL commands if the protocol is not considered complete. Protocol could be + considered incomplete for a number of reasons. The implementation could + still be under development and contain known bugs, or the protocol + specification itself could be under development or going through review. + If users would like to test the server-side portion of such protocol when + using indirect rendering, they can enable this option. If any X screen + enables this option, it will enable protocol on all screens in the server. + + When an NVIDIA GLX client is used, the related environment variable + "__GL_ALLOW_UNOFFICIAL_PROTOCOL" will need to be set as well to enable + support in the client. + +Option "PanAllDisplays" "boolean" + + When this option is enabled, all displays in the current MetaMode will pan + as the pointer is moved. If disabled, only the displays whose panning + domain contains the pointer (at its new location) are panned. + + Default: enabled (all displays are panned when the pointer is moved). + ______________________________________________________________________________ -Appendix G. Display Device Names +Appendix C. Display Device Names ______________________________________________________________________________ A "display device" refers to some piece of hardware capable of displaying an @@ -5302,7 +5514,7 @@ reference them in the MetaMode string as follows: ______________________________________________________________________________ -Appendix H. GLX Support +Appendix D. GLX Support ______________________________________________________________________________ This release supports GLX 1.4. @@ -5343,7 +5555,7 @@ however, they are also exported as extensions for backwards compatibility. ______________________________________________________________________________ -Appendix I. Dots Per Inch +Appendix E. Dots Per Inch ______________________________________________________________________________ DPI (Dots Per Inch), also known as PPI (Pixels Per Inch), is a property of an @@ -5369,7 +5581,7 @@ the X screen, to maintain a constant DPI (see the "Physical Size" column of the `xrandr -q` output as an example). This is done because a changing DPI can cause interaction problems for some applications. To disable this behavior, and instead keep the same millimeter size for the X screen (and therefore have -a changing DPI), set the ConstantDPI option to FALSE (see Appendix F for +a changing DPI), set the ConstantDPI option to FALSE (see Appendix B for details). You can query the DPI of your X screen by running: @@ -5411,7 +5623,7 @@ determine the DPI of each X screen: used to set the DPI (see `X -h` for details). This will override the "UseEdidDpi" option. - o If the "DPI" X configuration option is specified (see Appendix F for + o If the "DPI" X configuration option is specified (see Appendix B for details), that will be used to set the DPI. This will override the "UseEdidDpi" option. @@ -5439,7 +5651,7 @@ server to the X application with X screen granularity. Solutions for this include: - o Use separate X screens, rather than TwinView; see Chapter 12 for details. + o Use separate X screens, rather than TwinView; see Chapter 14 for details. o Experiment with different DPI settings to find a DPI that is suitable for both display devices. @@ -5447,7 +5659,7 @@ include: ______________________________________________________________________________ -Appendix J. XvMC Support +Appendix F. XvMC Support ______________________________________________________________________________ This release includes support for the XVideo Motion Compensation (XvMC) @@ -5465,7 +5677,7 @@ higher enables output of warning messages. ______________________________________________________________________________ -Appendix K. VDPAU Support +Appendix G. VDPAU Support ______________________________________________________________________________ This release includes support for the Video Decode and Presentation API for @@ -5474,7 +5686,7 @@ well as motherboard chipsets with integrated graphics that have PureVideo support based on these GPUs. -K1. IMPLEMENTATION LIMITS +G1. IMPLEMENTATION LIMITS VDPAU is specified as a generic API - the choice of which features to support, and performance levels of those features, is left up to individual @@ -5557,7 +5769,12 @@ In all cases, VdpDecoder objects solely support 8-bit 4:2:0 streams, and only support writing to VDP_CHROMA_TYPE_420 surfaces. The exact set of supported VdpDecoderProfile values depends on the hardware -model in use. +model in use. Hardware-specific support is listed below. When reading these +lists, please note that VC1_SIMPLE and VC1_MAIN may be referred to as WMV, +WMV3, or WMV9 in other contexts. Partial acceleration means that VLD +(bitstream) decoding is performed on the CPU, with the GPU performing IDCT and +motion compensation. Complete acceleration means that the GPU performs all of +VLD, IDCT, and motion compensation. G84, G86, G92, G94, G96, GT200 @@ -5587,6 +5804,18 @@ These chips support the following VdpDecoderProfile values: o Maximum macroblocks: 8192 + o VDP_DECODER_PROFILE_VC1_SIMPLE, VDP_DECODER_PROFILE_VC1_MAIN, + VDP_DECODER_PROFILE_VC1_ADVANCED: + + o Partial acceleration. + + o Minimum width or height: 3 macroblocks (48 pixels). + + o Maximum width or height: 128 macroblocks (2048 pixels). + + o Maximum macroblocks: 8190 + + G98, MCP77, MCP78, MCP79, MCP7A @@ -5663,22 +5892,32 @@ In order for either VDP_VIDEO_MIXER_FEATURE_DEINTERLACE_TEMPORAL or VDP_VIDEO_MIXER_FEATURE_DEINTERLACE_TEMPORAL_SPATIAL to operate correctly, the application must supply at least 2 past and 1 future fields to each VdpMixerRender call. If those fields are not provided, the VdpMixer will fall -back to bob deinterlacing. +back to bob de-interlacing. + +Both regular de-interlacing and half-rate de-interlacing are supported. Both +have the same requirements in terms of the number of past/future fields +required. Both modes should produce equivalent results. In order for VDP_VIDEO_MIXER_FEATURE_INVERSE_TELECINE to have any effect, one of VDP_VIDEO_MIXER_FEATURE_DEINTERLACE_TEMPORAL or VDP_VIDEO_MIXER_FEATURE_DEINTERLACE_TEMPORAL_SPATIAL must be requested and enabled. Inverse telecine has the same requirement on the minimum number of -past/future fields that must be provided. +past/future fields that must be provided. Inverse telecine will not operate +when "half-rate" de-interlacing is used. + +Whilst is is possible to apply de-interlacing algorithms to progressive +streams using the techniques outlined in the VDPAU documentation, NVIDIA does +not recommend doing so. One is likely to introduce more artifacts due to the +inverse telecine process than are removed by detection of bad edits etc. VDPPRESENTATIONQUEUE -The resolution of VdpTime is approximately 10ns. At some arbitrary point -during system startup, the initial value of this clock is synchronized to the -system's real-time clock, as represented by ns since since Jan 1, 1970. -However, no attempt is made to keep the two time-bases synchronized after this -point. Divergence can and will occur. +The resolution of VdpTime is approximately 10 nanoseconds. At some arbitrary +point during system startup, the initial value of this clock is synchronized +to the system's real-time clock, as represented by nanoseconds since since Jan +1, 1970. However, no attempt is made to keep the two time-bases synchronized +after this point. Divergence can and will occur. NVIDIA's VdpPresentationQueue supports two mechanisms for displaying surfaces; overlay and blit-based. The overlay path will be used wherever possible, with @@ -5702,14 +5941,26 @@ overlay path: o The environment variable VDPAU_NVIDIA_NO_OVERLAY is set to a string representation of a non-zero integer. + o The driver determines that the performance requirements of overlay usage + cannot be met by the current hardware configuration. -At present, the overlay path always syncs to vblank, whereas the blit path -never syncs to vblank. +Both the overlay and blit path sync to VBLANK. + +When TwinView is enabled, the blit path can only sync to one of the display +devices; this may cause tearing corruption on the display device to which +VDPAU is not syncing. You can use the environment variable +VDPAU_NVIDIA_SYNC_DISPLAY_DEVICE to specify the display device to which VDPAU +should sync. You should set this environment variable to the name of a display +device; for example "CRT-1". Look for the line "Connected display device(s):" +in your X log file for a list of the display devices present and their names. +You may also find it useful to review Chapter 12 "Configuring Twinview" and +the section on Ensuring Identical Mode Timings in Chapter 18. -K2. PERFORMANCE LEVELS -This documentation describes the capabilities of the NVIDA VDPAU +G2. PERFORMANCE LEVELS + +This documentation describes the capabilities of the NVIDIA VDPAU implementation. Hardware performance may vary significantly between cards. No guarantees are made, nor implied, that any particular combination of system configuration, GPU configuration, VDPAU feature set, VDPAU API usage, @@ -5717,7 +5968,7 @@ application, video stream, etc., will be able to decode streams at any particular frame rate. -K3. GETTING THE BEST PERFORMANCE FROM THE API +G3. GETTING THE BEST PERFORMANCE FROM THE API System performance (raw throughput, latency, and jitter tolerance) can be affected by a variety of factors. One of these factors is how the client @@ -5743,32 +5994,36 @@ Further, if the video surfaces are being read by the video mixer for post-processing, and eventual display, this will "lock" the surfaces for even longer, since the video mixer needs to read the data from the surface, which prevents any subsequent decode operations from writing to the surface. Recall -that when advanced deinterlacing techniques are used, a history of video +that when advanced de-interlacing techniques are used, a history of video surfaces must be provided to the video mixer, thus necessitating that even more video surfaces be allocated. For this reason, NVIDIA recommends the following number of video surfaces be allocated: - o (num_ref + 3) for progressive content, and no deinterlacing. - - o (num_ref + 5) for interlaced content using advanced deinterlacing. + o (num_ref + 3) for progressive content, and no de-interlacing. + o (num_ref + 5) for interlaced content using advanced de-interlacing. -For applications that perform significant amounts of rendering between bitmaps -and output surfaces, a similar argument may apply to the number of output -surfaces allocated. -Finally, consider the display path via the presentation queue. This portion of +Next, consider the display path via the presentation queue. This portion of the pipeline requires at least 2 output surfaces; one that is being actively displayed by the presentation queue, and one being rendered to for subsequent display. As before, using this minimum number of surfaces may not be optimal. For some video streams, the hardware may only achieve real-time decoding on -average, not for each individual frame. Similarly, system level issues such as -scheduler algorithms and system load may prevent the CPU portion of the driver -from operating for short periods of time. Both of these potential issues may -be solved by allocating more output surfaces, and queuing more than one -outstanding output surface into the presentation queue. +average, not for each individual frame. Using compositing APIs to render OSD, +GUIs, etc., may introduce extra jitter and latency into the pipeline. +Similarly, system level issues such as scheduler algorithms and system load +may prevent the CPU portion of the driver from operating for short periods of +time. All of these potential issues may be solved by allocating more output +surfaces, and queuing more than one outstanding output surface into the +presentation queue. + +The reason for using more than the minimum number of video surfaces is to +ensure that the decoding and post-processing pipeline is not stalled, and +hence is kept busy for the maximum amount of time possible. In contrast, the +reason for using more than the minimum number of output surfaces is to hide +jitter and latency in various GPU and CPU operations. The choice of exactly how many surfaces to allocate is a resource usage v.s. performance trade-off; Allocating more than the minimum number of surfaces @@ -5793,14 +6048,14 @@ need worry about correctness (providing their API usage is legal and sensible), but simply have to worry about performance. -K4. ADDITIONAL NOTES +G4. ADDITIONAL NOTES Note that surfaces (video, output, or bitmap) are not cleared to any specific value upon allocation. It is the application's responsibility to initialize all surfaces prior to using them as input to any function. -K5. DEBUGGING AND TRACING +G5. DEBUGGING AND TRACING The VDPAU wrapper library supports tracing VDPAU function calls, and their parameters. This tracing is controlled by the following environment variables: @@ -5833,7 +6088,7 @@ information, which may be needed to diagnose some problems. ______________________________________________________________________________ -Appendix L. Tips for New FreeBSD Users +Appendix H. Tips for New FreeBSD Users ______________________________________________________________________________ This installation guide assumes that the user has at least a basic @@ -5847,7 +6102,7 @@ unfamiliar with the use of FreeBSD, we strongly recommend that you seek a tutorial through your distributor before proceeding. -L1. THE COMMAND PROMPT +H1. THE COMMAND PROMPT While newer releases of FreeBSD bring new desktop interfaces to the user, much of the work in FreeBSD takes place at the command prompt. If you are familiar @@ -5864,7 +6119,7 @@ characters '#', '$', or '%', and a cursor (possibly flashing) that indicates where the user's input will be displayed. -L2. NAVIGATING THE DIRECTORY STRUCTURE +H2. NAVIGATING THE DIRECTORY STRUCTURE FreeBSD has a hierarchical directory structure. From anywhere in the directory structure, the 'ls' command will list the contents of that directory. The @@ -5898,7 +6153,7 @@ or -L3. FILE PERMISSIONS AND OWNERSHIP +H3. FILE PERMISSIONS AND OWNERSHIP All files and directories have permissions and ownership associated with them. This is useful for preventing non-administrative users from accidentally (or @@ -5961,7 +6216,7 @@ permissions, a user would do as follows: -L4. THE SHELL +H4. THE SHELL The shell provides an interface between the user and the operating system. It is the job of the shell to interpret the input that the user gives at the @@ -5996,7 +6251,7 @@ that is encountered most frequently is the way in which environment variables are set. -L5. SETTING ENVIRONMENT VARIABLES +H5. SETTING ENVIRONMENT VARIABLES Every session has associated with it environment variables, which consist of name/value pairs and control the way in which the shell and programs run from @@ -6036,7 +6291,7 @@ in C-shell. Note the curly braces are required to protect the variable name in C-shell. -L6. EDITING TEXT FILES +H6. EDITING TEXT FILES There are several text editors available for the FreeBSD operating system. Some of these editors require the X window system, while others are designed @@ -6056,7 +6311,7 @@ each (see the section on FreeBSD Manual and Info pages). Many programs use the editing is required. -L7. ROOT USER +H7. ROOT USER Upon installation, almost all distributions set up the default administrative user with the username 'root'. There are many things on the system that only @@ -6074,7 +6329,7 @@ as long as is necessary to accomplish the task requiring 'root' privileges (another useful feature of the 'sudo' utility). -L8. FREEBSD MANUAL AND INFO PAGES +H8. FREEBSD MANUAL AND INFO PAGES System manual or info pages are usually installed during installation. These pages are typically up-to-date and generally contain a comprehensive listing diff --git a/doc/gl.h b/doc/gl.h index 6663b08..290baa2 100755 --- a/doc/gl.h +++ b/doc/gl.h @@ -1220,6 +1220,9 @@ typedef void GLvoid; #define GL_SAMPLE_COVERAGE_INVERT 0x80AB #define GL_MULTISAMPLE_BIT 0x20000000 +/* ATI_element_array */ +#define GL_ELEMENT_ARRAY_ATI 0x8768 + /* EXT_vertex_array */ #define GL_VERTEX_ARRAY_EXT 0x8074 #define GL_NORMAL_ARRAY_EXT 0x8075 @@ -1710,6 +1713,10 @@ typedef void GLvoid; #define GL_QUERY_NO_WAIT 0x8E14 #define GL_QUERY_BY_REGION_WAIT 0x8E15 #define GL_QUERY_BY_REGION_NO_WAIT 0x8E16 +#define GL_CLAMP_VERTEX_COLOR 0x891A +#define GL_CLAMP_FRAGMENT_COLOR 0x891B +#define GL_CLAMP_READ_COLOR 0x891C +#define GL_FIXED_ONLY 0x891D /*************************************************************/ @@ -2379,6 +2386,7 @@ GLAPI void GLAPIENTRY glClearBufferfi (GLenum buffer, GLint drawbuffer, GLfloat GLAPI void GLAPIENTRY glClearBufferfv (GLenum buffer, GLint drawbuffer, const GLfloat *value); GLAPI void GLAPIENTRY glClearBufferiv (GLenum buffer, GLint drawbuffer, const GLint *value); GLAPI void GLAPIENTRY glClearBufferuiv (GLenum buffer, GLint drawbuffer, const GLuint *value); +GLAPI void GLAPIENTRY glClampColor (GLenum target, GLenum clamp); #ifdef __cplusplus diff --git a/doc/glext.h b/doc/glext.h index f6735a9..58fef0b 100755 --- a/doc/glext.h +++ b/doc/glext.h @@ -593,6 +593,15 @@ typedef void (GLAPIENTRYP PFNGLPOINTPARAMETERFVEXTPROC) (GLenum pname, const GLf #endif +#ifndef GL_EXT_provoking_vertex +#define GL_EXT_provoking_vertex 1 +#ifdef GL_GLEXT_PROTOTYPES +GLAPI void GLAPIENTRY glProvokingVertexEXT (GLenum mode); +#endif /* GL_GLEXT_PROTOTYPES */ +typedef void (GLAPIENTRYP PFNGLPROVOKINGVERTEXEXTPROC) (GLenum mode); +#endif + + #ifndef GL_WIN_swap_hint #define GL_WIN_swap_hint 1 #ifdef GL_GLEXT_PROTOTYPES @@ -1217,7 +1226,9 @@ GLAPI void GLAPIENTRY glMultiTexSubImage3DEXT (GLenum texunit, GLenum target, GL GLAPI void GLAPIENTRY glCopyMultiTexSubImage3DEXT (GLenum texunit, GLenum target, GLint level, GLint xoffset, GLint yoffset, GLint zoffset, GLint x, GLint y, GLsizei width, GLsizei height); GLAPI void GLAPIENTRY glBindMultiTextureEXT (GLenum texunit, GLenum target, GLuint texture); GLAPI void GLAPIENTRY glEnableClientStateIndexedEXT (GLenum array, GLuint index); +GLAPI void GLAPIENTRY glEnableClientStateiEXT (GLenum array, GLuint index); GLAPI void GLAPIENTRY glDisableClientStateIndexedEXT (GLenum array, GLuint index); +GLAPI void GLAPIENTRY glDisableClientStateiEXT (GLenum array, GLuint index); GLAPI void GLAPIENTRY glMultiTexCoordPointerEXT (GLenum texunit, GLint size, GLenum type, GLsizei stride, const GLvoid *pointer); GLAPI void GLAPIENTRY glMultiTexEnvfEXT (GLenum texunit, GLenum target, GLenum pname, GLfloat param); GLAPI void GLAPIENTRY glMultiTexEnvfvEXT (GLenum texunit, GLenum target, GLenum pname, const GLfloat *params); @@ -1237,6 +1248,9 @@ GLAPI void GLAPIENTRY glGetMultiTexGenivEXT (GLenum texunit, GLenum coord, GLenu GLAPI void GLAPIENTRY glGetFloatIndexedvEXT (GLenum target, GLuint index, GLfloat *data); GLAPI void GLAPIENTRY glGetDoubleIndexedvEXT (GLenum target, GLuint index, GLdouble *data); GLAPI void GLAPIENTRY glGetPointerIndexedvEXT (GLenum target, GLuint index, GLvoid* *data); +GLAPI void GLAPIENTRY glGetFloati_vEXT (GLenum target, GLuint index, GLfloat *data); +GLAPI void GLAPIENTRY glGetDoublei_vEXT (GLenum target, GLuint index, GLdouble *data); +GLAPI void GLAPIENTRY glGetPointeri_vEXT (GLenum target, GLuint index, GLvoid* *data); GLAPI void GLAPIENTRY glCompressedTextureImage3DEXT (GLuint texture, GLenum target, GLint level, GLenum internalformat, GLsizei width, GLsizei height, GLsizei depth, GLint border, GLsizei imageSize, const GLvoid *bits); GLAPI void GLAPIENTRY glCompressedTextureImage2DEXT (GLuint texture, GLenum target, GLint level, GLenum internalformat, GLsizei width, GLsizei height, GLint border, GLsizei imageSize, const GLvoid *bits); GLAPI void GLAPIENTRY glCompressedTextureImage1DEXT (GLuint texture, GLenum target, GLint level, GLenum internalformat, GLsizei width, GLint border, GLsizei imageSize, const GLvoid *bits); @@ -1340,6 +1354,27 @@ GLAPI void GLAPIENTRY glNamedFramebufferTextureLayerEXT (GLuint framebuffer, GLe GLAPI void GLAPIENTRY glNamedFramebufferTextureFaceEXT (GLuint framebuffer, GLenum attachment, GLuint texture, GLint level, GLenum face); GLAPI void GLAPIENTRY glTextureRenderbufferEXT (GLuint texture, GLenum target, GLuint renderbuffer); GLAPI void GLAPIENTRY glMultiTexRenderbufferEXT (GLenum texunit, GLenum target, GLuint renderbuffer); +GLAPI void GLAPIENTRY glVertexArrayVertexOffsetEXT (GLuint vaobj, GLuint buffer, GLint size, GLenum type, GLsizei stride, GLintptr offset); +GLAPI void GLAPIENTRY glVertexArrayColorOffsetEXT (GLuint vaobj, GLuint buffer, GLint size, GLenum type, GLsizei stride, GLintptr offset); +GLAPI void GLAPIENTRY glVertexArrayEdgeFlagOffsetEXT (GLuint vaobj, GLuint buffer, GLsizei stride, GLintptr offset); +GLAPI void GLAPIENTRY glVertexArrayIndexOffsetEXT (GLuint vaobj, GLuint buffer, GLenum type, GLsizei stride, GLintptr offset); +GLAPI void GLAPIENTRY glVertexArrayNormalOffsetEXT (GLuint vaobj, GLuint buffer, GLenum type, GLsizei stride, GLintptr offset); +GLAPI void GLAPIENTRY glVertexArrayTexCoordOffsetEXT (GLuint vaobj, GLuint buffer, GLint size, GLenum type, GLsizei stride, GLintptr offset); +GLAPI void GLAPIENTRY glVertexArrayMultiTexCoordOffsetEXT (GLuint vaobj, GLuint buffer, GLenum texunit, GLint size, GLenum type, GLsizei stride, GLintptr offset); +GLAPI void GLAPIENTRY glVertexArrayFogCoordOffsetEXT (GLuint vaobj, GLuint buffer, GLenum type, GLsizei stride, GLintptr offset); +GLAPI void GLAPIENTRY glVertexArraySecondaryColorOffsetEXT (GLuint vaobj, GLuint buffer, GLint size, GLenum type, GLsizei stride, GLintptr offset); +GLAPI void GLAPIENTRY glVertexArrayVertexAttribOffsetEXT (GLuint vaobj, GLuint buffer, GLuint index, GLint size, GLenum type, GLboolean normalized, GLsizei stride, GLintptr offset); +GLAPI void GLAPIENTRY glVertexArrayVertexAttribIOffsetEXT (GLuint vaobj, GLuint buffer, GLuint index, GLint size, GLenum type, GLsizei stride, GLintptr offset); +GLAPI void GLAPIENTRY glEnableVertexArrayEXT (GLuint vaobj, GLenum array); +GLAPI void GLAPIENTRY glDisableVertexArrayEXT (GLuint vaobj, GLenum array); +GLAPI void GLAPIENTRY glEnableVertexArrayAttribEXT (GLuint vaobj, GLenum array); +GLAPI void GLAPIENTRY glDisableVertexArrayAttribEXT (GLuint vaobj, GLenum array); +GLAPI void GLAPIENTRY glGetVertexArrayIntegervEXT (GLuint vaobj, GLenum pname, GLint *param); +GLAPI void GLAPIENTRY glGetVertexArrayPointervEXT (GLuint vaobj, GLenum pname, GLvoid* *param); +GLAPI void GLAPIENTRY glGetVertexArrayIntegeri_vEXT (GLuint vaobj, GLuint index, GLenum pname, GLint *param); +GLAPI void GLAPIENTRY glGetVertexArrayPointeri_vEXT (GLuint vaobj, GLuint index, GLenum pname, GLvoid* *param); +GLAPI GLvoid* GLAPIENTRY glMapNamedBufferRangeEXT (GLuint buffer, GLintptr offset, GLsizeiptr length, GLbitfield access); +GLAPI void GLAPIENTRY glFlushMappedNamedBufferRangeEXT (GLuint buffer, GLintptr offset, GLsizeiptr length); #endif /* GL_GLEXT_PROTOTYPES */ typedef void (GLAPIENTRYP PFNGLCLIENTATTRIBDEFAULTEXTPROC) (GLbitfield mask); typedef void (GLAPIENTRYP PFNGLPUSHCLIENTATTRIBDEFAULTEXTPROC) (GLbitfield mask); @@ -1404,7 +1439,9 @@ typedef void (GLAPIENTRYP PFNGLMULTITEXSUBIMAGE3DEXTPROC) (GLenum texunit, GLenu typedef void (GLAPIENTRYP PFNGLCOPYMULTITEXSUBIMAGE3DEXTPROC) (GLenum texunit, GLenum target, GLint level, GLint xoffset, GLint yoffset, GLint zoffset, GLint x, GLint y, GLsizei width, GLsizei height); typedef void (GLAPIENTRYP PFNGLBINDMULTITEXTUREEXTPROC) (GLenum texunit, GLenum target, GLuint texture); typedef void (GLAPIENTRYP PFNGLENABLECLIENTSTATEINDEXEDEXTPROC) (GLenum array, GLuint index); +typedef void (GLAPIENTRYP PFNGLENABLECLIENTSTATEIEXTPROC) (GLenum array, GLuint index); typedef void (GLAPIENTRYP PFNGLDISABLECLIENTSTATEINDEXEDEXTPROC) (GLenum array, GLuint index); +typedef void (GLAPIENTRYP PFNGLDISABLECLIENTSTATEIEXTPROC) (GLenum array, GLuint index); typedef void (GLAPIENTRYP PFNGLMULTITEXCOORDPOINTEREXTPROC) (GLenum texunit, GLint size, GLenum type, GLsizei stride, const GLvoid *pointer); typedef void (GLAPIENTRYP PFNGLMULTITEXENVFEXTPROC) (GLenum texunit, GLenum target, GLenum pname, GLfloat param); typedef void (GLAPIENTRYP PFNGLMULTITEXENVFVEXTPROC) (GLenum texunit, GLenum target, GLenum pname, const GLfloat *params); @@ -1424,6 +1461,9 @@ typedef void (GLAPIENTRYP PFNGLGETMULTITEXGENIVEXTPROC) (GLenum texunit, GLenum typedef void (GLAPIENTRYP PFNGLGETFLOATINDEXEDVEXTPROC) (GLenum target, GLuint index, GLfloat *data); typedef void (GLAPIENTRYP PFNGLGETDOUBLEINDEXEDVEXTPROC) (GLenum target, GLuint index, GLdouble *data); typedef void (GLAPIENTRYP PFNGLGETPOINTERINDEXEDVEXTPROC) (GLenum target, GLuint index, GLvoid* *data); +typedef void (GLAPIENTRYP PFNGLGETFLOATI_VEXTPROC) (GLenum target, GLuint index, GLfloat *data); +typedef void (GLAPIENTRYP PFNGLGETDOUBLEI_VEXTPROC) (GLenum target, GLuint index, GLdouble *data); +typedef void (GLAPIENTRYP PFNGLGETPOINTERI_VEXTPROC) (GLenum target, GLuint index, GLvoid* *data); typedef void (GLAPIENTRYP PFNGLCOMPRESSEDTEXTUREIMAGE3DEXTPROC) (GLuint texture, GLenum target, GLint level, GLenum internalformat, GLsizei width, GLsizei height, GLsizei depth, GLint border, GLsizei imageSize, const GLvoid *bits); typedef void (GLAPIENTRYP PFNGLCOMPRESSEDTEXTUREIMAGE2DEXTPROC) (GLuint texture, GLenum target, GLint level, GLenum internalformat, GLsizei width, GLsizei height, GLint border, GLsizei imageSize, const GLvoid *bits); typedef void (GLAPIENTRYP PFNGLCOMPRESSEDTEXTUREIMAGE1DEXTPROC) (GLuint texture, GLenum target, GLint level, GLenum internalformat, GLsizei width, GLint border, GLsizei imageSize, const GLvoid *bits); @@ -1527,6 +1567,27 @@ typedef void (GLAPIENTRYP PFNGLNAMEDFRAMEBUFFERTEXTURELAYEREXTPROC) (GLuint fram typedef void (GLAPIENTRYP PFNGLNAMEDFRAMEBUFFERTEXTUREFACEEXTPROC) (GLuint framebuffer, GLenum attachment, GLuint texture, GLint level, GLenum face); typedef void (GLAPIENTRYP PFNGLTEXTURERENDERBUFFEREXTPROC) (GLuint texture, GLenum target, GLuint renderbuffer); typedef void (GLAPIENTRYP PFNGLMULTITEXRENDERBUFFEREXTPROC) (GLenum texunit, GLenum target, GLuint renderbuffer); +typedef void (GLAPIENTRYP PFNGLVERTEXARRAYVERTEXOFFSETEXTPROC) (GLuint vaobj, GLuint buffer, GLint size, GLenum type, GLsizei stride, GLintptr offset); +typedef void (GLAPIENTRYP PFNGLVERTEXARRAYCOLOROFFSETEXTPROC) (GLuint vaobj, GLuint buffer, GLint size, GLenum type, GLsizei stride, GLintptr offset); +typedef void (GLAPIENTRYP PFNGLVERTEXARRAYEDGEFLAGOFFSETEXTPROC) (GLuint vaobj, GLuint buffer, GLsizei stride, GLintptr offset); +typedef void (GLAPIENTRYP PFNGLVERTEXARRAYINDEXOFFSETEXTPROC) (GLuint vaobj, GLuint buffer, GLenum type, GLsizei stride, GLintptr offset); +typedef void (GLAPIENTRYP PFNGLVERTEXARRAYNORMALOFFSETEXTPROC) (GLuint vaobj, GLuint buffer, GLenum type, GLsizei stride, GLintptr offset); +typedef void (GLAPIENTRYP PFNGLVERTEXARRAYTEXCOORDOFFSETEXTPROC) (GLuint vaobj, GLuint buffer, GLint size, GLenum type, GLsizei stride, GLintptr offset); +typedef void (GLAPIENTRYP PFNGLVERTEXARRAYMULTITEXCOORDOFFSETEXTPROC) (GLuint vaobj, GLuint buffer, GLenum texunit, GLint size, GLenum type, GLsizei stride, GLintptr offset); +typedef void (GLAPIENTRYP PFNGLVERTEXARRAYFOGCOORDOFFSETEXTPROC) (GLuint vaobj, GLuint buffer, GLenum type, GLsizei stride, GLintptr offset); +typedef void (GLAPIENTRYP PFNGLVERTEXARRAYSECONDARYCOLOROFFSETEXTPROC) (GLuint vaobj, GLuint buffer, GLint size, GLenum type, GLsizei stride, GLintptr offset); +typedef void (GLAPIENTRYP PFNGLVERTEXARRAYVERTEXATTRIBOFFSETEXTPROC) (GLuint vaobj, GLuint buffer, GLuint index, GLint size, GLenum type, GLboolean normalized, GLsizei stride, GLintptr offset); +typedef void (GLAPIENTRYP PFNGLVERTEXARRAYVERTEXATTRIBIOFFSETEXTPROC) (GLuint vaobj, GLuint buffer, GLuint index, GLint size, GLenum type, GLsizei stride, GLintptr offset); +typedef void (GLAPIENTRYP PFNGLENABLEVERTEXARRAYEXTPROC) (GLuint vaobj, GLenum array); +typedef void (GLAPIENTRYP PFNGLDISABLEVERTEXARRAYEXTPROC) (GLuint vaobj, GLenum array); +typedef void (GLAPIENTRYP PFNGLENABLEVERTEXARRAYATTRIBEXTPROC) (GLuint vaobj, GLenum array); +typedef void (GLAPIENTRYP PFNGLDISABLEVERTEXARRAYATTRIBEXTPROC) (GLuint vaobj, GLenum array); +typedef void (GLAPIENTRYP PFNGLGETVERTEXARRAYINTEGERVEXTPROC) (GLuint vaobj, GLenum pname, GLint *param); +typedef void (GLAPIENTRYP PFNGLGETVERTEXARRAYPOINTERVEXTPROC) (GLuint vaobj, GLenum pname, GLvoid* *param); +typedef void (GLAPIENTRYP PFNGLGETVERTEXARRAYINTEGERI_VEXTPROC) (GLuint vaobj, GLuint index, GLenum pname, GLint *param); +typedef void (GLAPIENTRYP PFNGLGETVERTEXARRAYPOINTERI_VEXTPROC) (GLuint vaobj, GLuint index, GLenum pname, GLvoid* *param); +typedef GLvoid* (GLAPIENTRYP PFNGLMAPNAMEDBUFFERRANGEEXTPROC) (GLuint buffer, GLintptr offset, GLsizeiptr length, GLbitfield access); +typedef void (GLAPIENTRYP PFNGLFLUSHMAPPEDNAMEDBUFFERRANGEEXTPROC) (GLuint buffer, GLintptr offset, GLsizeiptr length); #endif @@ -2716,8 +2777,8 @@ GLAPI void GLAPIENTRY glGetBooleani_v (GLenum target, GLuint index, GLboolean *d GLAPI void GLAPIENTRY glGetIntegeri_v (GLenum target, GLuint index, GLint *data); GLAPI GLboolean GLAPIENTRY glIsEnabledi (GLenum target, GLuint index); GLAPI void GLAPIENTRY glColorMaski (GLuint index, GLboolean r, GLboolean g, GLboolean b, GLboolean a); -GLAPI void GLAPIENTRY glEnablei (GLenum target, GLuint index); -GLAPI void GLAPIENTRY glDisablei (GLenum target, GLuint index); +GLAPI void GLAPIENTRY glEnablei (GLenum cap, GLuint index); +GLAPI void GLAPIENTRY glDisablei (GLenum cap, GLuint index); GLAPI const GLubyte * GLAPIENTRY glGetStringi (GLenum name, GLuint index); GLAPI void GLAPIENTRY glBlitFramebuffer (GLint srcX0, GLint srcY0, GLint srcX1, GLint srcY1, GLint dstX0, GLint dstY0, GLint dstX1, GLint dstY1, GLbitfield mask, GLenum filter); GLAPI GLboolean GLAPIENTRY glIsRenderbuffer (GLuint renderbuffer); @@ -2763,6 +2824,7 @@ GLAPI void GLAPIENTRY glClearBufferfi (GLenum buffer, GLint drawbuffer, GLfloat GLAPI void GLAPIENTRY glClearBufferfv (GLenum buffer, GLint drawbuffer, const GLfloat *value); GLAPI void GLAPIENTRY glClearBufferiv (GLenum buffer, GLint drawbuffer, const GLint *value); GLAPI void GLAPIENTRY glClearBufferuiv (GLenum buffer, GLint drawbuffer, const GLuint *value); +GLAPI void GLAPIENTRY glClampColor (GLenum target, GLenum clamp); #endif /* GL_GLEXT_PROTOTYPES */ typedef void (GLAPIENTRYP PFNGLVERTEXATTRIBI1IPROC) (GLuint index, GLint x); typedef void (GLAPIENTRYP PFNGLVERTEXATTRIBI2IPROC) (GLuint index, GLint x, GLint y); @@ -2800,8 +2862,8 @@ typedef void (GLAPIENTRYP PFNGLGETBOOLEANI_VPROC) (GLenum target, GLuint index, typedef void (GLAPIENTRYP PFNGLGETINTEGERI_VPROC) (GLenum target, GLuint index, GLint *data); typedef GLboolean (GLAPIENTRYP PFNGLISENABLEDIPROC) (GLenum target, GLuint index); typedef void (GLAPIENTRYP PFNGLCOLORMASKIPROC) (GLuint index, GLboolean r, GLboolean g, GLboolean b, GLboolean a); -typedef void (GLAPIENTRYP PFNGLENABLEIPROC) (GLenum target, GLuint index); -typedef void (GLAPIENTRYP PFNGLDISABLEIPROC) (GLenum target, GLuint index); +typedef void (GLAPIENTRYP PFNGLENABLEIPROC) (GLenum cap, GLuint index); +typedef void (GLAPIENTRYP PFNGLDISABLEIPROC) (GLenum cap, GLuint index); typedef const GLubyte * (GLAPIENTRYP PFNGLGETSTRINGIPROC) (GLenum name, GLuint index); typedef void (GLAPIENTRYP PFNGLBLITFRAMEBUFFERPROC) (GLint srcX0, GLint srcY0, GLint srcX1, GLint srcY1, GLint dstX0, GLint dstY0, GLint dstX1, GLint dstY1, GLbitfield mask, GLenum filter); typedef GLboolean (GLAPIENTRYP PFNGLISRENDERBUFFERPROC) (GLuint renderbuffer); @@ -2847,6 +2909,7 @@ typedef void (GLAPIENTRYP PFNGLCLEARBUFFERFIPROC) (GLenum buffer, GLint drawbuff typedef void (GLAPIENTRYP PFNGLCLEARBUFFERFVPROC) (GLenum buffer, GLint drawbuffer, const GLfloat *value); typedef void (GLAPIENTRYP PFNGLCLEARBUFFERIVPROC) (GLenum buffer, GLint drawbuffer, const GLint *value); typedef void (GLAPIENTRYP PFNGLCLEARBUFFERUIVPROC) (GLenum buffer, GLint drawbuffer, const GLuint *value); +typedef void (GLAPIENTRYP PFNGLCLAMPCOLORPROC) (GLenum target, GLenum clamp); #endif @@ -2862,6 +2925,72 @@ typedef void (GLAPIENTRYP PFNGLCUDAMAPBUFFERNVXPROC) (void *dataPtr); typedef void (GLAPIENTRYP PFNGLCUDAUNMAPBUFFERNVXPROC) (void *dataPtr); #endif + +#ifndef GL_NV_vertex_buffer_unified_memory +#define GL_NV_vertex_buffer_unified_memory 1 +#ifdef GL_GLEXT_PROTOTYPES +GLAPI void GLAPIENTRY glBufferAddressRangeNV (GLenum pname, GLuint index, GLuint64EXT address, GLsizeiptr length); +GLAPI void GLAPIENTRY glGetBufferParameterui64vNV (GLenum target, GLenum pname, GLuint64EXT *params); +GLAPI GLboolean GLAPIENTRY glIsBufferResidentNV (GLenum target); +GLAPI void GLAPIENTRY glMakeBufferNonResidentNV (GLenum target); +GLAPI void GLAPIENTRY glMakeBufferResidentNV (GLenum target, GLenum access); +GLAPI void GLAPIENTRY glGetNamedBufferParameterui64vNV (GLuint buffer, GLenum pname, GLuint64EXT *params); +GLAPI GLboolean GLAPIENTRY glIsNamedBufferResidentNV (GLuint buffer); +GLAPI void GLAPIENTRY glMakeNamedBufferNonResidentNV (GLuint buffer); +GLAPI void GLAPIENTRY glMakeNamedBufferResidentNV (GLuint buffer, GLenum access); +GLAPI void GLAPIENTRY glVertexFormatNV (GLint size, GLenum type, GLsizei stride); +GLAPI void GLAPIENTRY glNormalFormatNV (GLenum type, GLsizei stride); +GLAPI void GLAPIENTRY glColorFormatNV (GLint size, GLenum type, GLsizei stride); +GLAPI void GLAPIENTRY glIndexFormatNV (GLenum type, GLsizei stride); +GLAPI void GLAPIENTRY glTexCoordFormatNV (GLint size, GLenum type, GLsizei stride); +GLAPI void GLAPIENTRY glEdgeFlagFormatNV (GLsizei stride); +GLAPI void GLAPIENTRY glSecondaryColorFormatNV (GLint size, GLenum type, GLsizei stride); +GLAPI void GLAPIENTRY glFogCoordFormatNV (GLenum type, GLsizei stride); +GLAPI void GLAPIENTRY glVertexAttribFormatNV (GLuint index, GLint size, GLenum type, GLboolean normalized, GLsizei stride); +GLAPI void GLAPIENTRY glVertexAttribIFormatNV (GLuint index, GLint size, GLenum type, GLsizei stride); +GLAPI void GLAPIENTRY glGetIntegerui64vNV (GLenum target, GLuint64EXT *data); +GLAPI void GLAPIENTRY glGetIntegerui64i_vNV (GLenum target, GLuint index, GLuint64EXT *data); +#endif /* GL_GLEXT_PROTOTYPES */ +typedef void (GLAPIENTRYP PFNGLBUFFERADDRESSRANGENVPROC) (GLenum pname, GLuint index, GLuint64EXT address, GLsizeiptr length); +typedef void (GLAPIENTRYP PFNGLGETBUFFERPARAMETERUI64VNVPROC) (GLenum target, GLenum pname, GLuint64EXT *params); +typedef GLboolean (GLAPIENTRYP PFNGLISBUFFERRESIDENTNVPROC) (GLenum target); +typedef void (GLAPIENTRYP PFNGLMAKEBUFFERNONRESIDENTNVPROC) (GLenum target); +typedef void (GLAPIENTRYP PFNGLMAKEBUFFERRESIDENTNVPROC) (GLenum target, GLenum access); +typedef void (GLAPIENTRYP PFNGLGETNAMEDBUFFERPARAMETERUI64VNVPROC) (GLuint buffer, GLenum pname, GLuint64EXT *params); +typedef GLboolean (GLAPIENTRYP PFNGLISNAMEDBUFFERRESIDENTNVPROC) (GLuint buffer); +typedef void (GLAPIENTRYP PFNGLMAKENAMEDBUFFERNONRESIDENTNVPROC) (GLuint buffer); +typedef void (GLAPIENTRYP PFNGLMAKENAMEDBUFFERRESIDENTNVPROC) (GLuint buffer, GLenum access); +typedef void (GLAPIENTRYP PFNGLVERTEXFORMATNVPROC) (GLint size, GLenum type, GLsizei stride); +typedef void (GLAPIENTRYP PFNGLNORMALFORMATNVPROC) (GLenum type, GLsizei stride); +typedef void (GLAPIENTRYP PFNGLCOLORFORMATNVPROC) (GLint size, GLenum type, GLsizei stride); +typedef void (GLAPIENTRYP PFNGLINDEXFORMATNVPROC) (GLenum type, GLsizei stride); +typedef void (GLAPIENTRYP PFNGLTEXCOORDFORMATNVPROC) (GLint size, GLenum type, GLsizei stride); +typedef void (GLAPIENTRYP PFNGLEDGEFLAGFORMATNVPROC) (GLsizei stride); +typedef void (GLAPIENTRYP PFNGLSECONDARYCOLORFORMATNVPROC) (GLint size, GLenum type, GLsizei stride); +typedef void (GLAPIENTRYP PFNGLFOGCOORDFORMATNVPROC) (GLenum type, GLsizei stride); +typedef void (GLAPIENTRYP PFNGLVERTEXATTRIBFORMATNVPROC) (GLuint index, GLint size, GLenum type, GLboolean normalized, GLsizei stride); +typedef void (GLAPIENTRYP PFNGLVERTEXATTRIBIFORMATNVPROC) (GLuint index, GLint size, GLenum type, GLsizei stride); +typedef void (GLAPIENTRYP PFNGLGETINTEGERUI64VNVPROC) (GLenum target, GLuint64EXT *data); +typedef void (GLAPIENTRYP PFNGLGETINTEGERUI64I_VNVPROC) (GLenum target, GLuint index, GLuint64EXT *data); +#endif + + +#ifndef GL_NV_shader_buffer_load +#define GL_NV_shader_buffer_load 1 +#ifdef GL_GLEXT_PROTOTYPES +GLAPI void GLAPIENTRY glUniformui64NV (GLint location, GLuint64EXT v0); +GLAPI void GLAPIENTRY glUniformui64vNV (GLint location, GLsizei count, const GLuint64EXT *value); +GLAPI void GLAPIENTRY glGetUniformui64vNV (GLuint program, GLint location, GLuint64EXT *params); +GLAPI void GLAPIENTRY glProgramUniformui64NV (GLuint program, GLint location, GLuint64EXT v0); +GLAPI void GLAPIENTRY glProgramUniformui64vNV (GLuint program, GLint location, GLsizei count, const GLuint64EXT *value); +#endif /* GL_GLEXT_PROTOTYPES */ +typedef void (GLAPIENTRYP PFNGLUNIFORMUI64NVPROC) (GLint location, GLuint64EXT v0); +typedef void (GLAPIENTRYP PFNGLUNIFORMUI64VNVPROC) (GLint location, GLsizei count, const GLuint64EXT *value); +typedef void (GLAPIENTRYP PFNGLGETUNIFORMUI64VNVPROC) (GLuint program, GLint location, GLuint64EXT *params); +typedef void (GLAPIENTRYP PFNGLPROGRAMUNIFORMUI64NVPROC) (GLuint program, GLint location, GLuint64EXT v0); +typedef void (GLAPIENTRYP PFNGLPROGRAMUNIFORMUI64VNVPROC) (GLuint program, GLint location, GLsizei count, const GLuint64EXT *value); +#endif + /*************************************************************/ /* Version */ @@ -2894,6 +3023,9 @@ typedef void (GLAPIENTRYP PFNGLCUDAUNMAPBUFFERNVXPROC) (void *dataPtr); #ifndef GL_ARB_color_buffer_float #define GL_ARB_color_buffer_float 1 #endif +#ifndef GL_ARB_depth_buffer_float +#define GL_ARB_depth_buffer_float 1 +#endif #ifndef GL_ARB_depth_texture #define GL_ARB_depth_texture 1 #endif @@ -3122,6 +3254,9 @@ typedef void (GLAPIENTRYP PFNGLCUDAUNMAPBUFFERNVXPROC) (void *dataPtr); #ifndef GL_EXT_point_parameters #define GL_EXT_point_parameters 1 #endif +#ifndef GL_EXT_provoking_vertex +#define GL_EXT_provoking_vertex 1 +#endif #ifndef GL_EXT_rescale_normal #define GL_EXT_rescale_normal 1 #endif @@ -3422,6 +3557,12 @@ typedef void (GLAPIENTRYP PFNGLCUDAUNMAPBUFFERNVXPROC) (void *dataPtr); #ifndef GL_NVX_gpu_sync_buffer #define GL_NVX_gpu_sync_buffer 1 #endif +#ifndef GL_NV_shader_buffer_load +#define GL_NV_shader_buffer_load 1 +#endif +#ifndef GL_NV_vertex_buffer_unified_memory +#define GL_NV_vertex_buffer_unified_memory 1 +#endif #ifndef GL_NVX_volatile_texture #define GL_NVX_volatile_texture 1 #endif @@ -3656,6 +3797,9 @@ typedef void (GLAPIENTRYP PFNGLCUDAUNMAPBUFFERNVXPROC) (void *dataPtr); #define GL_MAX_3D_TEXTURE_SIZE 0x8073 #define GL_MAX_3D_TEXTURE_SIZE_EXT 0x8073 +/* ATI_element_array */ +#define GL_ELEMENT_ARRAY_ATI 0x8768 + /* EXT_vertex_array */ #define GL_VERTEX_ARRAY_EXT 0x8074 #define GL_NORMAL_ARRAY_EXT 0x8075 @@ -5784,6 +5928,41 @@ typedef void (GLAPIENTRYP PFNGLCUDAUNMAPBUFFERNVXPROC) (void *dataPtr); #define GL_TEXTURE_SWIZZLE_A_EXT 0x8E45 #define GL_TEXTURE_SWIZZLE_RGBA_EXT 0x8E46 +/* EXT_provoking_vertex */ +#define GL_QUADS_FOLLOW_PROVOKING_VERTEX_CONVENTION_EXT 0x8E4C +#define GL_FIRST_VERTEX_CONVENTION_EXT 0x8E4D +#define GL_LAST_VERTEX_CONVENTION_EXT 0x8E4E +#define GL_PROVOKING_VERTEX_EXT 0x8E4F + +/* NV_vertex_buffer_unified_memory */ +#define GL_BUFFER_GPU_ADDRESS_NV 0x8F1D +#define GL_VERTEX_ATTRIB_ARRAY_UNIFIED_NV 0x8F1E +#define GL_ELEMENT_ARRAY_UNIFIED_NV 0x8F1F +#define GL_VERTEX_ATTRIB_ARRAY_ADDRESS_NV 0x8F20 +#define GL_VERTEX_ARRAY_ADDRESS_NV 0x8F21 +#define GL_NORMAL_ARRAY_ADDRESS_NV 0x8F22 +#define GL_COLOR_ARRAY_ADDRESS_NV 0x8F23 +#define GL_INDEX_ARRAY_ADDRESS_NV 0x8F24 +#define GL_TEXTURE_COORD_ARRAY_ADDRESS_NV 0x8F25 +#define GL_EDGE_FLAG_ARRAY_ADDRESS_NV 0x8F26 +#define GL_SECONDARY_COLOR_ARRAY_ADDRESS_NV 0x8F27 +#define GL_FOG_COORD_ARRAY_ADDRESS_NV 0x8F28 +#define GL_ELEMENT_ARRAY_ADDRESS_NV 0x8F29 +#define GL_VERTEX_ATTRIB_ARRAY_LENGTH_NV 0x8F2A +#define GL_VERTEX_ARRAY_LENGTH_NV 0x8F2B +#define GL_NORMAL_ARRAY_LENGTH_NV 0x8F2C +#define GL_COLOR_ARRAY_LENGTH_NV 0x8F2D +#define GL_INDEX_ARRAY_LENGTH_NV 0x8F2E +#define GL_TEXTURE_COORD_ARRAY_LENGTH_NV 0x8F2F +#define GL_EDGE_FLAG_ARRAY_LENGTH_NV 0x8F30 +#define GL_SECONDARY_COLOR_ARRAY_LENGTH_NV 0x8F31 +#define GL_FOG_COORD_ARRAY_LENGTH_NV 0x8F32 +#define GL_ELEMENT_ARRAY_LENGTH_NV 0x8F33 + +/* NV_shader_buffer_load */ +#define GL_GPU_ADDRESS_NV 0x8F34 +#define GL_MAX_SHADER_BUFFER_ADDRESS_NV 0x8F35 + /*************************************************************/ diff --git a/doc/html/appendix-a.html b/doc/html/appendix-a.html index c4b6403..ba64918 100644 --- a/doc/html/appendix-a.html +++ b/doc/html/appendix-a.html @@ -5,31 +5,30 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Appendix A. Minimum Software Requirements +Appendix A. Supported NVIDIA GPU Products - - - + + +
- + - +"part-02.html">Prev  + +"appendix-b.html">Next
Appendix A. Minimum -Software RequirementsAppendix A. Supported +NVIDIA GPU Products
Prev Part I. Installation and -Configuration InstructionsPart II. Appendices  Next
@@ -37,14 +36,20 @@ Configuration Instructions
-

Appendix A. Minimum Software -Requirements

+

Appendix A. Supported NVIDIA GPU +Products

-

The official minimum software requirements for the NVIDIA -FreeBSD Graphics Driver are as follows:

+

For the most complete and accurate listing of supported GPUs, +please see the Supported Products List, available from the NVIDIA +FreeBSD x86 Graphics Driver download page. Please go to http://www.nvidia.com/object/unix.html, follow the +Archive link under the FreeBSD x86 heading, follow the link for the +185.18.36 driver, and then go to the Supported Products List.

+

NVIDIA GeForce GPUs

@@ -52,46 +57,1512 @@ FreeBSD Graphics Driver are as follows:

- - + + - - + + - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Software ElementMin RequirementNVIDIA GPU productDevice PCI ID
KernelFreeBSD 5-STABLE (5.3 or later)GeForce 6800 Ultra0x0040
XFree86/X.Org4.2/6.7.0GeForce 68000x0041
GeForce 6800 LE0x0042
GeForce 6800 XE0x0043
GeForce 6800 XT0x0044
GeForce 6800 GT0x0045
GeForce 6800 GT0x0046
GeForce 6800 GS0x0047
GeForce 6800 XT0x0048
GeForce 7800 GTX0x0090
GeForce 7800 GTX0x0091
GeForce 7800 GT0x0092
GeForce 7800 GS0x0093
GeForce 7800 SLI0x0095
GeForce Go 78000x0098
GeForce Go 7800 GTX0x0099
GeForce 6800 GS0x00C0
GeForce 68000x00C1
GeForce 6800 LE0x00C2
GeForce 6800 XT0x00C3
GeForce Go 68000x00C8
GeForce Go 6800 Ultra0x00C9
GeForce 6600 GT0x00F1
GeForce 66000x00F2
GeForce 62000x00F3
GeForce 6600 LE0x00F4
GeForce 7800 GS0x00F5
GeForce 6800 GS0x00F6
GeForce 6800 Ultra0x00F9
GeForce 6600 GT0x0140
GeForce 66000x0141
GeForce 6600 LE0x0142
GeForce 6600 VE0x0143
GeForce Go 66000x0144
GeForce 6610 XL0x0145
GeForce Go 6600 TE/6200 TE0x0146
GeForce 6700 XL0x0147
GeForce Go 66000x0148
GeForce Go 6600 GT0x0149
GeForce 62000x014F
GeForce 65000x0160
GeForce 6200 TurboCache(TM)0x0161
GeForce 6200SE TurboCache(TM)0x0162
GeForce 6200 LE0x0163
GeForce Go 62000x0164
GeForce Go 64000x0166
GeForce Go 62000x0167
GeForce Go 64000x0168
GeForce 62500x0169
GeForce 7100 GS0x016A
GeForce 8800 GTX0x0191
GeForce 8800 GTS0x0193
GeForce 8800 Ultra0x0194
Tesla C8700x0197
GeForce 7350 LE0x01D0
GeForce 7300 LE0x01D1
GeForce 7300 SE/7200 GS0x01D3
GeForce Go 72000x01D6
GeForce Go 73000x01D7
GeForce Go 74000x01D8
GeForce 7500 LE0x01DD
GeForce 7300 GS0x01DF
GeForce 62000x0221
GeForce 6200 A-LE0x0222
GeForce 61500x0240
GeForce 6150 LE0x0241
GeForce 61000x0242
GeForce Go 61500x0244
GeForce Go 61000x0247
GeForce 7900 GTX0x0290
GeForce 7900 GT/GTO0x0291
GeForce 7900 GS0x0292
GeForce 7950 GX20x0293
GeForce 7950 GX20x0294
GeForce 7950 GT0x0295
GeForce Go 7950 GTX0x0297
GeForce Go 7900 GS0x0298
GeForce 7600 GT0x02E0
GeForce 7600 GS0x02E1
GeForce 7300 GT0x02E2
GeForce 7900 GS0x02E3
GeForce 7950 GT0x02E4
GeForce 7650 GS0x0390
GeForce 7600 GT0x0391
GeForce 7600 GS0x0392
GeForce 7300 GT0x0393
GeForce 7600 LE0x0394
GeForce 7300 GT0x0395
GeForce Go 77000x0397
GeForce Go 76000x0398
GeForce Go 7600 GT0x0399
GeForce 6150SE nForce 4300x03D0
GeForce 6100 nForce 4050x03D1
GeForce 6100 nForce 4000x03D2
GeForce 6100 nForce 4200x03D5
GeForce 8600 GTS0x0400
GeForce 8600 GT0x0401
GeForce 8600 GT0x0402
GeForce 8600 GS0x0403
GeForce 8400 GS0x0404
GeForce 9500M GS0x0405
GeForce 8600M GT0x0407
GeForce 9650M GS0x0408
GeForce 8700M GT0x0409
GeForce 8400 SE0x0420
GeForce 8500 GT0x0421
GeForce 8400 GS0x0422
GeForce 8300 GS0x0423
GeForce 8400 GS0x0424
GeForce 8600M GS0x0425
GeForce 8400M GT0x0426
GeForce 8400M GS0x0427
GeForce 8400M G0x0428
GeForce 9400 GT0x042C
GeForce 9300M G0x042E
GeForce 7150M / nForce 630M0x0531
GeForce 7000M / nForce 610M0x0533
GeForce 7050 PV / nForce 630a0x053A
GeForce 7050 PV / nForce 630a0x053B
GeForce 7025 / nForce 630a0x053E
GeForce GTX 2950x05E0
GeForce GTX 2800x05E1
GeForce GTX 2600x05E2
GeForce GTX 2850x05E3
GeForce GTX 2750x05E6
GeForce GTX 2950x05EB
GeForce 8800 GTS 5120x0600
GeForce 9800 GT0x0601
GeForce 8800 GT0x0602
GeForce 9800 GX20x0604
GeForce 9800 GT0x0605
GeForce 8800 GS0x0606
GeForce 9800M GTX0x0608
GeForce 8800M GTS0x0609
GeForce GTX 280M0x060A
GeForce 9800M GT0x060B
GeForce 8800M GTX0x060C
GeForce 8800 GS0x060D
GeForce 9600 GSO0x0610
GeForce 8800 GT0x0611
GeForce 9800 GTX/9800 GTX+0x0612
GeForce 9800 GTX+0x0613
GeForce 9800 GT0x0614
GeForce GTS 2500x0615
GeForce 9800M GTX0x0617
GeForce GTX 260M0x0618
GeForce 9600 GT0x0622
GeForce 9600 GS0x0623
GeForce 9600 GSO 5120x0625
GeForce GT 1300x0626
GeForce GT 1400x0627
GeForce 9800M GTS0x0628
GeForce 9700M GTS0x062A
GeForce 9800M GS0x062B
GeForce 9800M GTS0x062C
GeForce 9500 GT0x0640
GeForce 9400 GT0x0641
GeForce 9500 GT0x0643
GeForce 9500 GS0x0644
GeForce GT 1200x0646
GeForce 9600M GT0x0647
GeForce 9600M GS0x0648
GeForce 9600M GT0x0649
GeForce 9700M GT0x064A
GeForce 9500M G0x064B
GeForce 9650M GT0x064C
GeForce GT 130M0x0652
GeForce 9650 S0x0656
GeForce 9300 GE0x06E0
GeForce 9300 GS0x06E1
GeForce 8400 GS0x06E4
GeForce 9300M GS0x06E5
GeForce G1000x06E6
GeForce 9200M GS0x06E8
GeForce 9300M GS0x06E9
GeForce G 103M0x06EF
GeForce 7150 / nForce 630i0x07E0
GeForce 7100 / nForce 630i0x07E1
GeForce 7050 / nForce 610i0x07E3
GeForce 9100M G0x0844
GeForce 8200M G0x0845
GeForce 91000x0847
GeForce 83000x0848
GeForce 82000x0849
nForce 730a0x084A
GeForce 92000x084B
nForce 980a/780a SLI0x084C
nForce 750a SLI0x084D
GeForce 8100 / nForce 720a0x084F
GeForce 9400M G0x0862
GeForce 9400M0x0863
GeForce 9300 / nForce 730i0x086C
GeForce GT 230M0x0A2A
GeForce GT 240M0x0A34
GeForce G210M0x0A74
GeForce GTS 260M0x0CA8
GeForce GTS 250M0x0CA9
+
+

NVIDIA Quadro GPUs

+
+ +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NVIDIA GPU productDevice PCI ID
Quadro FX 40000x004E
Quadro FX 45000x009D
Quadro FX Go14000x00CC
Quadro FX 3450/4000 SDI0x00CD
Quadro FX 14000x00CE
Quadro FX 3400/Quadro FX 40000x00F8
Quadro NVS 4400x014A
Quadro FX 540M0x014C
Quadro FX 5500x014D
Quadro FX 5400x014E
Quadro NVS 2850x0165
Quadro FX 56000x019D
Quadro FX 46000x019E
Quadro NVS 110M0x01DA
Quadro NVS 120M0x01DB
Quadro FX 350M0x01DC
Quadro FX 3500x01DE
Quadro NVS 210S / GeForce 6150LE0x0245
Quadro NVS 510M0x0299
Quadro FX 2500M0x029A
Quadro FX 1500M0x029B
Quadro FX 55000x029C
Quadro FX 35000x029D
Quadro FX 15000x029E
Quadro FX 4500 X20x029F
Quadro FX 5600x039E
Quadro FX 3700x040A
Quadro NVS 320M0x040B
Quadro FX 570M0x040C
Quadro FX 1600M0x040D
Quadro FX 5700x040E
Quadro FX 17000x040F
Quadro NVS 140M0x0429
Quadro NVS 130M0x042A
Quadro NVS 135M0x042B
Quadro FX 360M0x042D
Quadro NVS 2900x042F
Quadro CX0x05F9
Quadro FX 58000x05FD
Quadro FX 48000x05FE
Quadro FX 38000x05FF
Quadro FX 37000x061A
Quadro FX 3600M0x061C
Quadro FX 3700M0x061E
Quadro FX 18000x0638
Quadro FX 2700M0x063A
Quadro FX 3800x0658
Quadro FX 5800x0659
Quadro FX 770M0x065C
Quadro NVS 150M0x06EA
Quadro NVS 160M0x06EB
Quadro NVS 4200x06F8
Quadro FX 370 LP0x06F9
Quadro NVS 4500x06FA
Quadro NVS 2950x06FD
Quadro FX 4700x087A
+
+

Below are the legacy GPUs that are no longer supported in the +unified driver. These GPUs will continue to be maintained through +the special legacy NVIDIA GPU driver releases.

+

The 173.14.xx driver supports the following set of GPUs:

+
+ +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NVIDIA GPU productDevice PCI ID
GeForce PCX 57500x00FA
GeForce PCX 59000x00FB
Quadro FX 330/GeForce PCX 53000x00FC
Quadro FX 330/Quadro NVS 280 PCI-E0x00FD
Quadro FX 13000x00FE
GeForce FX 5800 Ultra0x0301
GeForce FX 58000x0302
Quadro FX 20000x0308
Quadro FX 10000x0309
GeForce FX 5600 Ultra0x0311
GeForce FX 56000x0312
GeForce FX 5600XT0x0314
GeForce FX Go56000x031A
GeForce FX Go56500x031B
Quadro FX Go7000x031C
GeForce FX 52000x0320
GeForce FX 5200 Ultra0x0321
GeForce FX 52000x0322
GeForce FX 5200LE0x0323
GeForce FX Go52000x0324
GeForce FX Go52500x0325
GeForce FX 55000x0326
GeForce FX 51000x0327
GeForce FX Go5200 32M/64M0x0328
Quadro NVS 55/280 PCI0x032A
Quadro FX 500/FX 6000x032B
GeForce FX Go53xx0x032C
GeForce FX Go51000x032D
GeForce FX 5900 Ultra0x0330
GeForce FX 59000x0331
GeForce FX 5900XT0x0332
GeForce FX 5950 Ultra0x0333
GeForce FX 5900ZT0x0334
Quadro FX 30000x0338
Quadro FX 7000x033F
GeForce FX 5700 Ultra0x0341
GeForce FX 57000x0342
GeForce FX 5700LE0x0343
GeForce FX 5700VE0x0344
GeForce FX Go57000x0347
GeForce FX Go57000x0348
Quadro FX Go10000x034C
Quadro FX 11000x034E
+
+

The 96.43.xx driver supports the following set of GPUs:

+
+ +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NVIDIA GPU productDevice PCI ID
GeForce2 MX/MX 4000x0110
GeForce2 MX 100/2000x0111
GeForce2 Go0x0112
Quadro2 MXR/EX/Go0x0113
GeForce4 MX 4600x0170
GeForce4 MX 4400x0171
GeForce4 MX 4200x0172
GeForce4 MX 440-SE0x0173
GeForce4 440 Go0x0174
GeForce4 420 Go0x0175
GeForce4 420 Go 32M0x0176
GeForce4 460 Go0x0177
Quadro4 550 XGL0x0178
GeForce4 440 Go 64M0x0179
Quadro NVS 4000x017A
Quadro4 500 GoGL0x017C
GeForce4 410 Go 16M0x017D
GeForce4 MX 440 with AGP8X0x0181
GeForce4 MX 440SE with AGP8X0x0182
GeForce4 MX 420 with AGP8X0x0183
GeForce4 MX 40000x0185
Quadro4 580 XGL0x0188
Quadro NVS 280 SD0x018A
Quadro4 380 XGL0x018B
Quadro NVS 50 PCI0x018C
GeForce2 Integrated GPU0x01A0
GeForce4 MX Integrated GPU0x01F0
GeForce30x0200
GeForce3 Ti 2000x0201
GeForce3 Ti 5000x0202
Quadro DCC0x0203
GeForce4 Ti 46000x0250
GeForce4 Ti 44000x0251
GeForce4 Ti 42000x0253
Quadro4 900 XGL0x0258
Quadro4 750 XGL0x0259
Quadro4 700 XGL0x025B
GeForce4 Ti 48000x0280
GeForce4 Ti 4200 with AGP8X0x0281
GeForce4 Ti 4800 SE0x0282
GeForce4 4200 Go0x0286
Quadro4 980 XGL0x0288
Quadro4 780 XGL0x0289
Quadro4 700 GoGL0x028C
+
+

The 71.86.xx driver supports the following set of GPUs:

+
+ +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NVIDIA GPU productDevice PCI ID
RIVA TNT0x0020
RIVA TNT2/TNT2 Pro0x0028
RIVA TNT2 Ultra0x0029
Vanta/Vanta LT0x002C
RIVA TNT2 Model 64/Model 64 Pro0x002D
Aladdin TNT20x00A0
GeForce 2560x0100
GeForce DDR0x0101
Quadro0x0103
GeForce2 GTS/GeForce2 Pro0x0150
GeForce2 Ti0x0151
GeForce2 Ultra0x0152
Quadro2 Pro0x0153
-

Additionally, the kernel source tree must be installed in -/usr/src/sys (package 'ssys' installed)

-

Note that FreeBSD -STABLE versions older than FreeBSD 5.3 and -FreeBSD 6.x/7.x -CURRENT development snapshots are not -supported.

+"part-02.html">Prev  +"part-02.html">Up +"appendix-b.html">Next +Part II. Appendices  + Appendix B. X Config Options
Prev  Up  Next
-Chapter 1. Introduction  Home - Chapter 2. Installing the NVIDIA Driver
diff --git a/doc/html/appendix-b.html b/doc/html/appendix-b.html index 468265b..73e4123 100644 --- a/doc/html/appendix-b.html +++ b/doc/html/appendix-b.html @@ -5,31 +5,30 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Appendix B. Installed Components +Appendix B. X Config Options - - - + + +
- + - +"appendix-a.html">Prev  + +"appendix-c.html">Next
Appendix B. Installed -ComponentsAppendix B. X Config +Options
Prev Part I. Installation and -Configuration InstructionsPart II. Appendices  Next
@@ -37,14 +36,21 @@ Configuration Instructions
-

Appendix B. Installed -Components

+

Appendix B. X Config Options

-

The NVIDIA Accelerated FreeBSD Graphics Driver consists of the -following components.

+

The following driver options are supported by the NVIDIA X +driver. They may be specified either in the Screen or Device +sections of the X config file.

+
+

X Config Options

+
+
Option "NvAGP" "integer"
+
+

Configure AGP support. Integer argument can be one of:

@@ -52,174 +58,1597 @@ following components.

- - + + - - + + - - + + - - + + - - - - - - - - - - + + + +
Installed FileLocationValueBehavior
nvidia.ko/boot/modules0disable AGP
libGL.so/usr/lib/xorg1use NVIDIA internal AGP support, if possible
libGL.so.1/usr/lib/xorg2use AGPGART, if possible
libnvidia-tls.so/usr/lib/xorg
libnvidia-tls.so.1/usr/lib/xorg
libnvidia-cfg.so/usr/lib/xorg3use any AGP support (try AGPGART, then NVIDIA AGP)
+
+

Note that NVIDIA internal AGP support cannot work if AGPGART is +either statically compiled into your kernel or is built as a module +and loaded into your kernel. See Chapter 11, +Configuring AGP for details. Default: 3.

+
+
Option "NoLogo" +"boolean"
+
+

Disable drawing of the NVIDIA logo splash screen at X startup. +Default: the logo is drawn for screens with depth 24.

+
+
Option "LogoPath" +"string"
+
+

Sets the path to the PNG file to be used as the logo splash +screen at X startup. If the PNG file specified has a bKGD +(background color) chunk, then the screen is cleared to the color +it specifies. Otherwise, the screen is cleared to black. The logo +file must be owned by root and must not be writable by a non-root +group. Note that a logo is only displayed for screens with depth +24. Default: The built-in NVIDIA logo is used.

+
+
Option "RenderAccel" +"boolean"
+
+

Enable or disable hardware acceleration of the RENDER extension. +Default: hardware acceleration of the RENDER extension is +enabled.

+
+
Option "NoRenderExtension" +"boolean"
+
+

Disable the RENDER extension. Other than recompiling it, the X +server does not seem to have another way of disabling this. +Fortunately, we can control this from the driver so we export this +option. This is useful in depth 8 where RENDER would normally steal +most of the default colormap. Default: RENDER is offered when +possible.

+
+
Option "UBB" "boolean"
+
+

Enable or disable the Unified Back Buffer on Quadro-based GPUs +(Quadro4 NVS excluded); see Chapter 19, +Configuring Flipping and UBB for a description of UBB. +This option has no effect on non-Quadro GPU products. Default: UBB +is on for Quadro GPUs.

+
+
Option "NoFlip" +"boolean"
+
+

Disable OpenGL flipping; see Chapter 19, +Configuring Flipping and UBB for a description. Default: +OpenGL will swap by flipping when possible.

+
+
Option "Dac8Bit" +"boolean"
+
+

Most Quadro products by default use a 10-bit color look-up table +(LUT); setting this option to TRUE forces these GPUs to use an +8-bit (LUT). Default: a 10-bit LUT is used, when available.

+
+
Option "Overlay" +"boolean"
+
+

Enables RGB workstation overlay visuals. This is only supported +on Quadro GPUs (Quadro NVS GPUs excluded) in depth 24. This option +causes the server to advertise the SERVER_OVERLAY_VISUALS root +window property and GLX will report single- and double-buffered, +Z-buffered 16-bit overlay visuals. The transparency key is pixel +0x0000 (hex). There is no gamma correction support in the overlay +plane. This feature requires XFree86 version 4.2.0 or newer, or the +X.Org X server. When the X screen is either wider than 2046 pixels +or taller than 2047, the overlay may be emulated with a substantial +performance penalty. RGB workstation overlays are not supported +when the Composite extension is enabled.

+

UBB must be enabled when overlays are enabled (this is the +default behavior).

+
+
Option "CIOverlay" +"boolean"
+
+

Enables Color Index workstation overlay visuals with identical +restrictions to Option "Overlay" above. The server will offer +visuals both with and without a transparency key. These are depth 8 +PseudoColor visuals. Enabling Color Index overlays on X servers +older than XFree86 4.3 will force the RENDER extension to be +disabled due to bugs in the RENDER extension in older X servers. +Color Index workstation overlays are not supported when the +Composite extension is enabled. Default: off.

+

UBB must be enabled when overlays are enabled (this is the +default behavior).

+
+
Option "TransparentIndex" +"integer"
+
+

When color index overlays are enabled, use this option to choose +which pixel is used for the transparent pixel in visuals featuring +transparent pixels. This value is clamped between 0 and 255 (Note: +some applications such as Alias's Maya require this to be zero in +order to work correctly). Default: 0.

+
+
Option "OverlayDefaultVisual" +"boolean"
+
+

When overlays are used, this option sets the default visual to +an overlay visual thereby putting the root window in the overlay. +This option is not recommended for RGB overlays. Default: off.

+
+
Option "EmulatedOverlaysTimerMs" +"integer"
+
+

Enables the use of a timer within the X server to perform the +updates to the emulated overlay or CI overlay. This option can be +used to improve the performance of the emulated or CI overlays by +reducing the frequency of the updates. The value specified +indicates the desired number of milliseconds between overlay +updates. To disable the use of the timer either leave the option +unset or set it to 0. Default: off.

+
+
Option "EmulatedOverlaysThreshold" +"boolean"
+
+

Enables the use of a threshold within the X server to perform +the updates to the emulated overlay or CI overlay. The emulated or +CI overlay updates can be deferred but this threshold will limit +the number of deferred OpenGL updates allowed before the overlay is +updated. This option can be used to trade off performance and +animation quality. Default: on.

+
+
Option +"EmulatedOverlaysThresholdValue" "integer"
+
+

Controls the threshold used in updating the emulated or CI +overlays. This is used in conjunction with the +EmulatedOverlaysThreshold option to trade off performance and +animation quality. Higher values for this option favor performance +over quality. Setting low values of this option will not cause the +overlay to be updated more often than the frequence specified by +the EmulatedOverlaysTimerMs option. Default: 5.

+
+
Option "RandRRotation" +"boolean"
+
+

Enable rotation support for the XRandR extension. This allows +use of the XRandR X server extension for configuring the screen +orientation through rotation. This feature is supported using depth +24. This requires an X.Org X 6.8.1 or newer X server. This feature +does not work with hardware overlays; emulated overlays will be +used instead at a substantial performance penalty. See Chapter 16, +Using the XRandR Extension for details. Default: +off.

+
+
Option "Rotate" +"string"
+
+

Enable static rotation support. Unlike the RandRRotation option +above, this option takes effect as soon as the X server is started +and will work with older versions of X. This feature is supported +using depth 24. This feature does not work with hardware overlays; +emulated overlays will be used instead at a substantial performance +penalty. This option is not compatible with the RandR extension. +Valid rotations are "normal", "left", "inverted", and "right". +Default: off.

+
+
Option "AllowDDCCI" +"boolean"
+
+

Enables DDC/CI support in the NV-CONTROL X extension. DDC/CI is +a mechanism for communication between your computer and your +display device. This can be used to set the values normally +controlled through your display device's On Screen Display. See the +DDC/CI NV-CONTROL attributes in NVCtrl.h and functions in NVCtrlLib.h in the nvidia-settings source code. Default: off +(DDC/CI is disabled).

+

Note that support for DDC/CI within the NVIDIA X driver's +NV-CONTROL extension is deprecated, and will be removed in a future +release. Other mechanisms for DDC/CI, such as the kernel i2c +subsystem on Linux, are preferred over NV-CONTROL's DDC/CI +support.

+

If you would prefer that the NVIDIA X driver's NV-CONTROL X +extension not remove DDC/CI support, please make your concerns +known my emailing .

+
+
Option "SWCursor" +"boolean"
+
+

Enable or disable software rendering of the X cursor. Default: +off.

+
+
Option "HWCursor" +"boolean"
+
+

Enable or disable hardware rendering of the X cursor. Default: +on.

+
+
Option "CursorShadow" +"boolean"
+
+

Enable or disable use of a shadow with the hardware accelerated +cursor; this is a black translucent replica of your cursor shape at +a given offset from the real cursor. Default: off (no cursor +shadow).

+
+
Option "CursorShadowAlpha" +"integer"
+
+

The alpha value to use for the cursor shadow; only applicable if +CursorShadow is enabled. This value must be in the range [0, 255] +-- 0 is completely transparent; 255 is completely opaque. Default: +64.

+
+
Option "CursorShadowXOffset" +"integer"
+
+

The offset, in pixels, that the shadow image will be shifted to +the right from the real cursor image; only applicable if +CursorShadow is enabled. This value must be in the range [0, 32]. +Default: 4.

+
+
Option "CursorShadowYOffset" +"integer"
+
+

The offset, in pixels, that the shadow image will be shifted +down from the real cursor image; only applicable if CursorShadow is +enabled. This value must be in the range [0, 32]. Default: 2.

+
+
Option "ConnectedMonitor" +"string"
+
+

Allows you to override what the NVIDIA kernel module detects is +connected to your graphics card. This may be useful, for example, +if you use a KVM (keyboard, video, mouse) switch and you are +switched away when X is started. In such a situation, the NVIDIA +kernel module cannot detect which display devices are connected, +and the NVIDIA X driver assumes you have a single CRT.

+

Valid values for this option are "CRT" (cathode ray tube), "DFP" +(digital flat panel), or "TV" (television); if using TwinView, this +option may be a comma-separated list of display devices; e.g.: +"CRT, CRT" or "CRT, DFP".

+

It is generally recommended to not use this option, but instead +use the "UseDisplayDevice" option.

+

NOTE: anything attached to a 15 pin VGA connector is regarded by +the driver as a CRT. "DFP" should only be used to refer to digital +flat panels connected via a DVI port.

+

Default: string is NULL (the NVIDIA driver will detect the +connected display devices).

+
+
Option "UseDisplayDevice" +"string"
+
+

The "UseDisplayDevice" X configuration option is a list of one +or more display devices, which limits the display devices the +NVIDIA X driver will consider for an X screen. The display device +names used in the option may be either specific (with a numeric +suffix; e.g., "DFP-1") or general (without a numeric suffix; e.g., +"DFP").

+

When assigning display devices to X screens, the NVIDIA X driver +walks through the list of all (not already assigned) display +devices detected as connected. When the "UseDisplayDevice" X +configuration option is specified, the X driver will only consider +connected display devices which are also included in the +"UseDisplayDevice" list. This can be thought of as a "mask" against +the connected (and not already assigned) display devices.

+

Note the subtle difference between this option and the +"ConnectedMonitor" option: the "ConnectedMonitor" option overrides +which display devices are actually detected, while the +"UseDisplayDevice" option controls which of the detected display +devices will be used on this X screen.

+

Of the list of display devices considered for this X screen +(either all connected display devices, or a subset limited by the +"UseDisplayDevice" option), the NVIDIA X driver first looks at +CRTs, then at DFPs, and finally at TVs. For example, if both a CRT +and a DFP are connected, by default the X driver would assign the +CRT to this X screen. However, by specifying:

+
+    Option "UseDisplayDevice" "DFP"
+
+

the X screen would use the DFP instead. Or, if CRT-0, DFP-0, and +DFP-1 are connected and TwinView is enabled, the X driver would +assign CRT-0 and DFP-0 to the X screen. However, by specifying:

+
+    Option "UseDisplayDevice" "CRT-0, DFP-1"
+
+

the X screen would use CRT-0 and DFP-1 instead.

+

Additionally, the special value "none" can be specified for the +"UseDisplayDevice" option. When this value is given, any +programming of the display hardware is disabled. The NVIDIA driver +will not perform any mode validation or mode setting for this X +screen. This is intended for use in conjunction with CUDA or in +remote graphics solutions such as VNC or Hewlett Packard's Remote +Graphics Software (RGS). This functionality is only available on +Quadro and Tesla GPUs.

+

Note the following restrictions for setting the +"UseDisplayDevice" to "none":

+
+
    +
  • +

    OpenGL SyncToVBlank will have no effect.

    +
    • +
  • +

    None of Stereo, Overlay, CIOverlay, or SLI are allowed when +"UseDisplayDevice" is set to "none".

    +
    • +
+
+

+
+
Option "UseEdidFreqs" +"boolean"
+
+

This option controls whether the NVIDIA X driver will use the +HorizSync and VertRefresh ranges given in a display device's EDID, +if any. When UseEdidFreqs is set to True, EDID-provided range +information will override the HorizSync and VertRefresh ranges +specified in the Monitor section. If a display device does not +provide an EDID, or the EDID does not specify an hsync or vrefresh +range, then the X server will default to the HorizSync and +VertRefresh ranges specified in the Monitor section of your X +config file. These frequency ranges are used when validating modes +for your display device.

+

Default: True (EDID frequencies will be used)

+
+
Option "UseEDID" +"boolean"
+
+

By default, the NVIDIA X driver makes use of a display device's +EDID, when available, during construction of its mode pool. The +EDID is used as a source for possible modes, for valid frequency +ranges, and for collecting data on the physical dimensions of the +display device for computing the DPI (see Appendix E, +Dots Per Inch). However, if you wish to disable the +driver's use of the EDID, you can set this option to False:

+
+    Option "UseEDID" "FALSE"
+
+

Note that, rather than globally disable all uses of the EDID, +you can individually disable each particular use of the EDID; +e.g.,

+
+    Option "UseEDIDFreqs" "FALSE"
+    Option "UseEDIDDpi" "FALSE"
+    Option "ModeValidation" "NoEdidModes"
+
+

Default: True (use EDID).

+
+
Option "UseInt10Module" +"boolean"
+
+

Enable use of the X Int10 module to soft-boot all secondary +cards, rather than POSTing the cards through the NVIDIA kernel +module. Default: off (POSTing is done through the NVIDIA kernel +module).

+
+
Option "TwinView" +"boolean"
+
+

Enable or disable TwinView. See Chapter 12, +Configuring TwinView for details. Default: off (TwinView +is disabled).

+
+
Option "TwinViewOrientation" +"string"
+
+

Controls the relationship between the two display devices when +using TwinView. Takes one of the following values: "RightOf" +"LeftOf" "Above" "Below" "Clone". See Chapter 12, +Configuring TwinView for details. Default: string is +NULL.

+
+
Option "SecondMonitorHorizSync" +"range(s)"
+
+

This option is like the HorizSync entry in the Monitor section, +but is for the second monitor when using TwinView. See Chapter 12, +Configuring TwinView for details. Default: none.

+
+
Option "SecondMonitorVertRefresh" +"range(s)"
+
+

This option is like the VertRefresh entry in the Monitor +section, but is for the second monitor when using TwinView. See +Chapter 12, +Configuring TwinView for details. Default: none.

+
+
Option "MetaModes" +"string"
+
+

This option describes the combination of modes to use on each +monitor when using TwinView. See Chapter 12, +Configuring TwinView for details. Default: string is +NULL.

+
+
Option "NoTwinViewXineramaInfo" +"boolean"
+
+

When in TwinView, the NVIDIA X driver normally provides a +Xinerama extension that X clients (such as window managers) can use +to discover the current TwinView configuration, such as where each +display device is positioned within the X screen. Some window +mangers get confused by this information, so this option is +provided to disable this behavior. Default: false (TwinView +Xinerama information is provided).

+

Due to bugs in some older software, TwinView Xinerama +information is not provided by default on X.Org 7.1 and older when +the X server is started with only one display device connected.

+
+
Option "TwinViewXineramaInfoOrder" +"string"
+
+

When the NVIDIA X driver provides TwinViewXineramaInfo (see the +NoTwinViewXineramaInfo X config option), it by default reports the +currently enabled display devices in the order "CRT, DFP, TV". The +TwinViewXineramaInfoOrder X config option can be used to override +this order.

+

The option string is a comma-separated list of display device +names. The display device names can either be general (e.g, "CRT", +which identifies all CRTs), or specific (e.g., "CRT-1", which +identifies a particular CRT). Not all display devices need to be +identified in the option string; display devices that are not +listed will be implicitly appended to the end of the list, in their +default order.

+

Note that TwinViewXineramaInfoOrder tracks all display devices +that could possibly be connected to the GPU, not just the ones that +are currently enabled. When reporting the Xinerama information, the +NVIDIA X driver walks through the display devices in the order +specified, only reporting enabled display devices.

+

Examples:

+
+        "DFP"
+        "TV, DFP"
+        "DFP-1, DFP-0, TV, CRT"
+
+

In the first example, any enabled DFPs would be reported first +(any enabled CRTs or TVs would be reported afterwards). In the +second example, any enabled TVs would be reported first, then any +enabled DFPs (any enabled CRTs would be reported last). In the last +example, if DFP-1 were enabled, it would be reported first, then +DFP-0, then any enabled TVs, and then any enabled CRTs; finally, +any other enabled DFPs would be reported.

+

Default: "CRT, DFP, TV"

+
+
Option "TwinViewXineramaInfoOverride" +"string"
+
+

This option overrides the values reported by NVIDIA's TwinView +Xinerama implementation. This disregards the actual display devices +used by the X screen and any order specified in +TwinViewXineramaInfoOrder.

+

The option string is interpreted as a comma-separated list of +regions, specified as '[width]x[height]+[x-offset]+[y-offset]'. The +regions' sizes and offsets are not validated against the X screen +size, but are directly reported to any Xinerama client.

+

Examples:

+
+        "1600x1200+0+0, 1600x1200+1600+0"
+        "1024x768+0+0, 1024x768+1024+0, 1024x768+0+768, 1024x768+1024+768"
+
+

+
+
Option "TVStandard" +"string"
+
+

See Chapter 15, +Configuring TV-Out for details on configuring +TV-out.

+
+
Option "TVOutFormat" +"string"
+
+

See Chapter 15, +Configuring TV-Out for details on configuring +TV-out.

+
+
Option "TVOverScan" "Decimal +value in the range 0.0 to 1.0"
+
+

Valid values are in the range 0.0 through 1.0; See Chapter 15, +Configuring TV-Out for details on configuring +TV-out.

+
+
Option "Stereo" +"integer"
+
+

Enable offering of quad-buffered stereo visuals on Quadro. +Integer indicates the type of stereo equipment being used:

+
+ +++ + - - + + + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + + +
libnvidia-cfg.so.1/usr/lib/xorgValueEquipment
libGLcore.so/usr/lib/xorg1DDC glasses. The sync signal is sent to the glasses via the DDC +signal to the monitor. These usually involve a passthrough cable +between the monitor and the graphics card. This mode is not +available on G8xGL and higher GPUs.
libGLcore.so.1/usr/lib/xorg2"Blueline" glasses. These usually involve a passthrough cable +between the monitor and graphics card. The glasses know which eye +to display based on the length of a blue line visible at the bottom +of the screen. When in this mode, the root window dimensions are +one pixel shorter in the Y dimension than requested. This mode does +not work with virtual root window sizes larger than the visible +root window size (desktop panning). This mode is not available on +G8xGL and higher GPUs.
nvidia_drv.so/usr/lib/xorg/modules/drivers3Onboard stereo support. This is usually only found on +professional cards. The glasses connect via a DIN connector on the +back of the graphics card.
libnvidia-wfb.so (optional)/usr/lib/xorg/modules4TwinView clone mode stereo (also known as "passive" stereo). On +graphics cards that support TwinView, the left eye is displayed on +the first display, and the right eye is displayed on the second +display. This is normally used in conjunction with special +projectors to produce 2 polarized images which are then viewed with +polarized glasses. To use this stereo mode, you must also configure +TwinView in clone mode with the same resolution, panning offset, +and panning domains on each display.
libwfb.so/usr/lib/xorg/modules/drivers5Vertical interlaced stereo mode, for use with SeeReal Stereo +Digital Flat Panels.
libglx.so/usr/lib/xorg/modules/extensions6Color interleaved stereo mode, for use with Sharp3D Stereo +Digital Flat Panels.
libglx.so.1/usr/lib/xorg/modules/extensions7Horizontal interlaced stereo mode, for use with Arisawa, +Hyundai, Zalman, Pavione, and Miracube Digital Flat Panels.
libvdpau.so/usr/lib/xorg8Checkerboard pattern stereo mode, for use with 3D DLP Display +Devices.
libvdpau.so.1/usr/lib/xorg9Inverse checkerboard pattern stereo mode, for use with 3D DLP +Display Devices.
+
+

Stereo is only available on Quadro cards. Stereo options 1, 2, +and 3 (also known as "active" stereo) may be used with TwinView if +all modes within each MetaMode have identical timing values. See +Chapter 18, +Programming Modes for suggestions on making sure the +modes within your MetaModes are identical. The identical ModeLine +requirement is not necessary for Stereo options 4 through 9 +("passive" stereo). Default: 0 (Stereo is not enabled).

+

UBB must be enabled when stereo is enabled (this is the default +behavior).

+

Stereo options 1, 2, and 3 ("active" stereo) can be enabled on +digital display devices (connected via DVI, HDMI, or DisplayPort). +However, some digital display devices might not behave as desired +with active stereo:

+
+
    +
  • +

    Some digital display devices may not be able to toggle pixel +colors quickly enough when flipping between eyes on every +vblank.

    +
    • +
  • +

    Some digital display devices may have an optical polarization +that interferes with stereo goggles.

    +
    • +
  • +

    Active stereo requires high refresh rates, because a vertical +refresh is needed to display each eye. Some digital display devices +have a low refresh rate, which will result in flickering when used +for active stereo.

    +
    • +
  • +

    Some digital display devices might internally convert from other +refresh rates to their native refresh rate (e.g., 60Hz), resulting +in incompatible rates between the stereo glasses and stereo +displayed on screen.

    +
    • +
+
+

+

Stereo applies to an entire X screen, so it will apply to all +display devices on that X screen, whether or not they all support +the selected Stereo mode.

+

Stereo options 7, 8, and 9 are only supported on G8xGL and +higher GPUs.

+

Multi-GPU cards (such as the Quadro FX 4500 X2) provide a single +connector for onboard stereo support (option 3), which is tied to +the bottommost GPU. In order to synchronize onboard stereo with the +other GPU, you must use a G-Sync device (see Chapter 25, +Configuring Frame Lock and Genlock for details).

+
+
Option "ForceStereoFlipping" +"boolean"
+
+

Stereo flipping is the process by which left and right eyes are +displayed on alternating vertical refreshes. Normally, stereo +flipping is only performed when a stereo drawable is visible. This +option forces stereo flipping even when no stereo drawables are +visible.

+

This is to be used in conjunction with the "Stereo" option. If +"Stereo" is 0, the "ForceStereoFlipping" option has no effect. If +otherwise, the "ForceStereoFlipping" option will force the behavior +indicated by the "Stereo" option, even if no stereo drawables are +visible. This option is useful in a multiple-screen environment in +which a stereo application is run on a different screen than the +stereo master.

+

Possible values:

+
+ +++ + - - + + + + - - + + - - + + + +
libvdpau_trace.so/usr/lib/xorgValueBehavior
libvdpau_trace.so.1/usr/lib/xorg0Stereo flipping is not forced. The default behavior as +indicated by the "Stereo" option is used.
libvdpau_nvidia.so/usr/lib/xorg1Stereo flipping is forced. Stereo is running even if no stereo +drawables are visible. The stereo mode depends on the value of the +"Stereo" option.
+
+

Default: 0 (Stereo flipping is not forced). Note that active +stereo is not supported on digital flat panels.

+
+
Option "XineramaStereoFlipping" +"boolean"
+
+

By default, when using Stereo with Xinerama, all physical X +screens having a visible stereo drawable will stereo flip. Use this +option to allow only one physical X screen to stereo flip at a +time.

+

This is to be used in conjunction with the "Stereo" and +"Xinerama" options. If "Stereo" is 0 or "Xinerama" is 0, the +"XineramaStereoFlipping" option has no effect.

+

If you wish to have all X screens stereo flip all the time, see +the "ForceStereoFlipping" option.

+

Possible values:

+
+ +++ + - - + + + + - - + + - - + + + +
libvdpau_nvidia.so.1/usr/lib/xorgValueBehavior
nvidia-xconfig/usr/bin0Stereo flipping is enabled on one X screen at a time. Stereo is +enabled on the first X screen having the stereo drawable.
nvidia-xconfig.1/usr/man/man11Stereo flipping in enabled on all X screens.
+
+

Default: 1 (Stereo flipping is enabled on all X screens).

+
+
Option "NoBandWidthTest" +"boolean"
+
+

As part of mode validation, the X driver tests if a given mode +fits within the hardware's memory bandwidth constraints. This +option disables this test. Default: false (the memory bandwidth +test is performed).

+
+
Option "IgnoreDisplayDevices" +"string"
+
+

This option tells the NVIDIA kernel module to completely ignore +the indicated classes of display devices when checking which +display devices are connected. You may specify a comma-separated +list containing any of "CRT", "DFP", and "TV". For example:

+
+Option "IgnoreDisplayDevices" "DFP, TV"
+
+

will cause the NVIDIA driver to not attempt to detect if any +digital flat panels or TVs are connected. This option is not +normally necessary; however, some video BIOSes contain incorrect +information about which display devices may be connected, or which +i2c port should be used for detection. These errors can cause long +delays in starting X. If you are experiencing such delays, you may +be able to avoid this by telling the NVIDIA driver to ignore +display devices which you know are not connected. NOTE: anything +attached to a 15 pin VGA connector is regarded by the driver as a +CRT. "DFP" should only be used to refer to digital flat panels +connected via a DVI port.

+
+
Option "MultisampleCompatibility" +"boolean"
+
+

Enable or disable the use of separate front and back multisample +buffers. Enabling this will consume more memory but is necessary +for correct output when rendering to both the front and back +buffers of a multisample or FSAA drawable. This option is necessary +for correct operation of SoftImage XSI. Default: false (a single +multisample buffer is shared between the front and back +buffers).

+
+
Option "NoPowerConnectorCheck" +"boolean"
+
+

The NVIDIA X driver will abort X server initialization if it +detects that a GPU that requires an external power connector does +not have an external power connector plugged in. This option can be +used to bypass this test. Default: false (the power connector test +is performed).

+
+
Option "XvmcUsesTextures" +"boolean"
+
+

Forces XvMC to use the 3D engine for XvMCPutSurface requests +rather than the video overlay. Default: false (video overlay is +used when available).

+
+
Option "AllowGLXWithComposite" +"boolean"
+
+

Enables GLX even when the Composite X extension is loaded. +ENABLE AT YOUR OWN RISK. OpenGL applications will not display +correctly in many circumstances with this setting enabled.

+

This option is intended for use on X.Org X servers older than +X11R6.9.0. On X11R6.9.0 or newer X servers, the NVIDIA OpenGL +implementation interacts properly by default with the Composite X +extension and this option should not be needed. However, on +X11R6.9.0 or newer X servers, support for GLX with Composite can be +disabled by setting this option to False.

+

Default: false (GLX is disabled when Composite is enabled on X +servers older than X11R6.9.0).

+
+
Option "UseCompositeWrapper" +"boolean"
+
+

Enables the X server's "composite wrapper", which performs +coordinate translations necessary for the Composite extension.

+

Default: false (the NVIDIA X driver performs its own coordinate +translation).

+
+
Option "AddARGBGLXVisuals" +"boolean"
+
+

Adds a 32-bit ARGB visual for each supported OpenGL +configuration. This allows applications to use OpenGL to render +with alpha transparency into 32-bit windows and pixmaps. This +option requires the Composite extension. Default: ARGB GLX visuals +are enabled on X servers new enough to support them when the +Composite extension is also enabled.

+
+
Option "DisableGLXRootClipping" +"boolean"
+
+

If enabled, no clipping will be performed on rendering done by +OpenGL in the root window. This option is deprecated. It is needed +by older versions of OpenGL-based composite managers that draw the +contents of redirected windows directly into the root window using +OpenGL. Most OpenGL-based composite managers have been updated to +support the Composite Overlay Window, a feature introduced in Xorg +release 7.1. Using the Composite Overlay Window is the preferred +method for performing OpenGL-based compositing.

+
+
Option "DamageEvents" +"boolean"
+
+

Use OS-level events to efficiently notify X when a client has +performed direct rendering to a window that needs to be composited. +This will significantly improve performance and interactivity when +using GLX applications with a composite manager running. It will +also affect applications using GLX when rotation is enabled. This +option is currently incompatible with SLI and Multi-GPU modes and +will be disabled if either are used. Enabled by default.

+
+
Option "ExactModeTimingsDVI" +"boolean"
+
+

Forces the initialization of the X server with the exact timings +specified in the ModeLine. Default: false (for DVI devices, the X +server initializes with the closest mode in the EDID list).

+
+
Option "Coolbits" +"integer"
+
+

Enables various unsupported features, such as support for GPU +clock manipulation in the NV-CONTROL X extension. This option +accepts a bit mask of features to enable.

+

When "1" (Bit 0) is set in the "Coolbits" option value, the +nvidia-settings utility will contain a page labeled "Clock +Frequencies" through which clock settings can be manipulated. +"Coolbits" is only available on GeForce FX, Quadro FX and newer +desktop GPUs. On GeForce FX and newer mobile GPUs, limited clock +manipulation support is available when "1" is set in the "Coolbits" +option value: clocks can be lowered relative to the default +settings; overclocking is not supported due to the thermal +constraints of notebook designs.

+

WARNING: this may cause system damage and void warranties. This +utility can run your computer system out of the manufacturer's +design specifications, including, but not limited to: higher system +voltages, above normal temperatures, excessive frequencies, and +changes to BIOS that may corrupt the BIOS. Your computer's +operating system may hang and result in data loss or corrupted +images. Depending on the manufacturer of your computer system, the +computer system, hardware and software warranties may be voided, +and you may not receive any further manufacturer support. NVIDIA +does not provide customer service support for the Coolbits option. +It is for these reasons that absolutely no warranty or guarantee is +either express or implied. Before enabling and using, you should +determine the suitability of the utility for your intended use, and +you shall assume all responsibility in connection therewith.

+

When "2" (Bit 1) is set in the "Coolbits" option value, the +NVIDIA driver will attempt to initialize SLI when using GPUs with +different amounts of video memory.

+

The default for this option is 0 (unsupported features are +disabled).

+
+
Option "MultiGPU" +"string"
+
+

This option controls the configuration of Multi-GPU rendering in +supported configurations.

+
+ +++ + - - + + + + - - + + - - + + - - + + - - + + - - + + + +
nvidia-settings/usr/binValueBehavior
nvidia-settings.1/usr/man/man10, no, off, false, SingleUse only a single GPU when rendering
nvidia0/dev1, yes, on, true, AutoEnable Multi-GPU and allow the driver to automatically select +the appropriate rendering mode.
nvidia1/devAFREnable Multi-GPU and use the Alternate Frame Rendering +mode.
nvidia2/devSFREnable Multi-GPU and use the Split Frame Rendering mode.
nvidia3/devAAEnable Multi-GPU and use antialiasing. Use this in conjunction +with full scene antialiasing to improve visual quality.
+
+

+
+
Option "SLI" "string"
+
+

This option controls the configuration of SLI rendering in +supported configurations.

+
+ +++ + - - + + + + - - + + - - + + - - + + - - + + - - + + - - + +
nvidiactl/devValueBehavior
libGL.so.180.29/compat/linux/usr/lib0, no, off, false, SingleUse only a single GPU when rendering
libnvidia-tls.so.180.29/compat/linux/usr/lib1, yes, on, true, AutoEnable SLI and allow the driver to automatically select the +appropriate rendering mode.
libGLcore.so.180.29/compat/linux/usr/libAFREnable SLI and use the Alternate Frame Rendering mode.
libvdpau.so.180.29/compat/linux/usr/libSFREnable SLI and use the Split Frame Rendering mode.
libvdpau_trace.so.180.29/compat/linux/usr/libAAEnable SLI and use SLI Antialiasing. Use this in conjunction +with full scene antialiasing to improve visual quality.
libvdpau_nvidia.so.180.29/compat/linux/usr/libAFRofAAEnable SLI and use SLI Alternate Frame Rendering of +Antialiasing mode. Use this in conjunction with full scene +antialiasing to improve visual quality. This option is only valid +for SLI configurations with 4 GPUs.

+
+
Option "TripleBuffer" +"boolean"
+
+

Enable or disable the use of triple buffering. If this option is +enabled, OpenGL windows that sync to vblank and are double-buffered +will be given a third buffer. This decreases the time an +application stalls while waiting for vblank events, but increases +latency slightly (delay between user input and displayed +result).

+
+
Option "DPI" "string"
+
+

This option specifies the Dots Per Inch for the X screen; for +example:

+
+    Option "DPI" "75 x 85"
+
+

will set the horizontal DPI to 75 and the vertical DPI to 85. By +default, the X driver will compute the DPI of the X screen from the +EDID of any connected display devices. See Appendix E, Dots Per +Inch for details. Default: string is NULL (disabled).

+
+
Option "UseEdidDpi" +"string"
+
+

By default, the NVIDIA X driver computes the DPI of an X screen +based on the physical size of the display device, as reported in +the EDID, and the size in pixels of the first mode to be used on +the display device. If multiple display devices are used by the X +screen, then the NVIDIA X screen will choose which display device +to use. This option can be used to specify which display device to +use. The string argument can be a display device name, such as:

+
+    Option "UseEdidDpi" "DFP-0"
+
+

or the argument can be "FALSE" to disable use of EDID-based DPI +calculations:

+
+    Option "UseEdidDpi" "FALSE"
+
+

See Appendix E, Dots Per +Inch for details. Default: string is NULL (the driver +computes the DPI from the EDID of a display device and selects the +display device).

+
+
Option "ConstantDPI" +"boolean"
+
+

By default on X.Org 6.9 or newer X servers, the NVIDIA X driver +recomputes the size in millimeters of the X screen whenever the +size in pixels of the X screen is changed using XRandR, such that +the DPI remains constant.

+

This behavior can be disabled (which means that the size in +millimeters will not change when the size in pixels of the X screen +changes) by setting the "ConstantDPI" option to "FALSE"; e.g.,

+
+    Option "ConstantDPI" "FALSE"
+
+

ConstantDPI defaults to True.

+

On X servers older than X.Org 6.9, the NVIDIA X driver cannot +change the size in millimeters of the X screen. Therefore the DPI +of the X screen will change when XRandR changes the size in pixels +of the X screen. The driver will behave as if ConstantDPI was +forced to FALSE.

+
+
Option "CustomEDID" +"string"
+
+

This option forces the X driver to use the EDID specified in a +file rather than the display's EDID. You may specify a semicolon +separated list of display names and filename pairs. The display +name is any of "CRT-0", "CRT-1", "DFP-0", "DFP-1", "TV-0", "TV-1", +or one of the generic names "CRT", "DFP", "TV", which apply the +EDID to all devices of the specified type. The file contains a raw +EDID (e.g., a file generated by nvidia-settings).

+

For example:

+
+    Option "CustomEDID" "CRT-0:/tmp/edid1.bin; DFP-0:/tmp/edid2.bin"
+
+

will assign the EDID from the file /tmp/edid1.bin to the display +device CRT-0, and the EDID from the file /tmp/edid2.bin to the +display device DFP-0. Note that a display device name must always +be specified even if only one EDID is specified.

+

Caution: Specifying an EDID that doesn't exactly match your +display may damage your hardware, as it allows the driver to +specify timings beyond the capabilities of your display. Use with +care.

+
+
Option "ModeValidation" +"string"
+
+

This option provides fine-grained control over each stage of the +mode validation pipeline, disabling individual mode validation +checks. This option should only very rarely be used.

+

The option string is a semicolon-separated list of +comma-separated lists of mode validation arguments. Each list of +mode validation arguments can optionally be prepended with a +display device name.

+
+    "<dpy-0>: <tok>, <tok>; <dpy-1>: <tok>, <tok>, <tok>; ..."
+
+

+

Possible arguments:

+
+
    +
  • +

    "AllowNon60HzDFPModes": some lower quality TMDS encoders are +only rated to drive DFPs at 60Hz; the driver will determine when +only 60Hz DFP modes are allowed. This argument disables this stage +of the mode validation pipeline.

    +
    • +
  • +

    "NoMaxPClkCheck": each mode has a pixel clock; this pixel clock +is validated against the maximum pixel clock of the hardware (for a +DFP, this is the maximum pixel clock of the TMDS encoder, for a +CRT, this is the maximum pixel clock of the DAC). This argument +disables the maximum pixel clock checking stage of the mode +validation pipeline.

    +
    • +
  • +

    "NoEdidMaxPClkCheck": a display device's EDID can specify the +maximum pixel clock that the display device supports; a mode's +pixel clock is validated against this pixel clock maximum. This +argument disables this stage of the mode validation pipeline.

    +
    • +
  • +

    "AllowInterlacedModes": interlaced modes are not supported on +all NVIDIA GPUs; the driver will discard interlaced modes on GPUs +where interlaced modes are not supported; this argument disables +this stage of the mode validation pipeline.

    +
    • +
  • +

    "NoMaxSizeCheck": each NVIDIA GPU has a maximum resolution that +it can drive; this argument disables this stage of the mode +validation pipeline.

    +
    • +
  • +

    "NoHorizSyncCheck": a mode's horizontal sync is validated +against the range of valid horizontal sync values; this argument +disables this stage of the mode validation pipeline.

    +
    • +
  • +

    "NoVertRefreshCheck": a mode's vertical refresh rate is +validated against the range of valid vertical refresh rate values; +this argument disables this stage of the mode validation +pipeline.

    +
    • +
  • +

    "NoWidthAlignmentCheck": the alignment of a mode's visible width +is validated against the capabilities of the GPU; normally, a +mode's visible width must be a multiple of 8. This argument +disables this stage of the mode validation pipeline.

    +
    • +
  • +

    "NoDFPNativeResolutionCheck": when validating for a DFP, a +mode's size is validated against the native resolution of the DFP; +this argument disables this stage of the mode validation +pipeline.

    +
    • +
  • +

    "NoVirtualSizeCheck": if the X configuration file requests a +specific virtual screen size, a mode cannot be larger than that +virtual size; this argument disables this stage of the mode +validation pipeline.

    +
    • +
  • +

    "NoVesaModes": when constructing the mode pool for a display +device, the X driver uses a built-in list of VESA modes as one of +the mode sources; this argument disables use of these built-in VESA +modes.

    +
    • +
  • +

    "NoEdidModes": when constructing the mode pool for a display +device, the X driver uses any modes listed in the display device's +EDID as one of the mode sources; this argument disables use of +EDID-specified modes.

    +
    • +
  • +

    "NoXServerModes": when constructing the mode pool for a display +device, the X driver uses the built-in modes provided by the core +XFree86/Xorg X server as one of the mode sources; this argument +disables use of these modes. Note that this argument does not +disable custom ModeLines specified in the X config file; see the +"NoCustomModes" argument for that.

    +
    • +
  • +

    "NoCustomModes": when constructing the mode pool for a display +device, the X driver uses custom ModeLines specified in the X +config file (through the "Mode" or "ModeLine" entries in the +Monitor Section) as one of the mode sources; this argument disables +use of these modes.

    +
    • +
  • +

    "NoPredefinedModes": when constructing the mode pool for a +display device, the X driver uses additional modes predefined by +the NVIDIA X driver; this argument disables use of these modes.

    +
    • +
  • +

    "NoUserModes": additional modes can be added to the mode pool +dynamically, using the NV-CONTROL X extension; this argument +prohibits user-specified modes via the NV-CONTROL X extension.

    +
    • +
  • +

    "NoExtendedGpuCapabilitiesCheck": allow mode timings that may +exceed the GPU's extended capability checks.

    +
    • +
  • +

    "ObeyEdidContradictions": an EDID may contradict itself by +listing a mode as supported, but the mode may exceed an +EDID-specified valid frequency range (HorizSync, VertRefresh, or +maximum pixel clock). Normally, the NVIDIA X driver prints a +warning in this scenario, but does not invalidate an EDID-specified +mode just because it exceeds an EDID-specified valid frequency +range. However, the "ObeyEdidContradictions" argument instructs the +NVIDIA X driver to invalidate these modes.

    +
    • +
  • +

    "NoTotalSizeCheck": allow modes in which the individual visible +or sync pulse timings exceed the total raster size.

    +
    • +
  • +

    "DoubleScanPriority": on GPUs older than G80, doublescan modes +are sorted before non-doublescan modes of the same resolution for +purposes of mode pool sorting; but on G80 and later GPUs, +doublescan modes are sorted after non-doublescan modes of the same +resolution. This token inverts that priority (i.e., doublescan +modes will be sorted after on pre-G80 GPUs, and sorted before on +G80 and later GPUs).

    +
    • +
  • +

    "NoDualLinkDVICheck": for mode timings used on dual link DVI +DFPs, the driver must perform additional checks to ensure that the +correct pixels are sent on the correct link. For some of these +checks, the driver will invalidate the mode timings; for other +checks, the driver will implicitly modify the mode timings to meet +the GPU's dual link DVI requirements. This token disables this dual +link DVI checking.

    +
    • +
+
+

+

Examples:

+
+    Option "ModeValidation" "NoMaxPClkCheck"
+
+

disable the maximum pixel clock check when validating modes on +all display devices.

+
+    Option "ModeValidation" "CRT-0: NoEdidModes, NoMaxPClkCheck; DFP-0: NoVesaModes"
+
+

do not use EDID modes and do not perform the maximum pixel clock +check on CRT-0, and do not use VESA modes on DFP-0.

+
+
Option "ModeDebug" +"boolean"
+
+

This option causes the X driver to print verbose details about +mode validation to the X log file. Note that this option is applied +globally: setting this option to TRUE will enable verbose mode +validation logging for all NVIDIA X screens in the X server.

+
+
Option "UseEvents" +"boolean"
+
+

Enables the use of system events in some cases when the X driver +is waiting for the hardware. The X driver can briefly spin through +a tight loop when waiting for the hardware. With this option the X +driver instead sets an event handler and waits for the hardware +through the poll() +system call. Default: the use of the events is disabled.

+
+
Option "FlatPanelProperties" +"string"
+
+

This option requests particular properties for all or a subset +of the connected flat panels.

+

The option string is a semicolon-separated list of +comma-separated property=value pairs. Each list of property=value +pairs can optionally be prepended with a flat panel name.

+
+    "<DFP-0>: <property=value>, <property=value>; <DFP-1>: <property=value>; ..."
+
+

+

Recognized properties:

+
+
    +
  • +

    "Scaling": controls the flat panel scaling mode; possible values +are: 'Default' (the driver will use whichever scaling state is +current), 'Native' (the driver will use the flat panel's scaler, if +possible), 'Scaled' (the driver will use the NVIDIA GPU's scaler, +if possible), 'Centered' (the driver will center the image, if +possible), and 'aspect-scaled' (the X driver will scale with the +NVIDIA GPU's scaler, but keep the aspect ratio correct).

    +
    • +
  • +

    "Dithering": controls the flat panel dithering mode; possible +values are: 'Default' (the driver will decide when to dither), +'Enabled' (the driver will always dither, if possible), and +'Disabled' (the driver will never dither).

    +
    • +
+
+

+

Examples:

+
+    Option "FlatPanelProperties" "Scaling = Centered"
+
+

set the flat panel scaling mode to centered on all flat +panels.

+
+    Option "FlatPanelProperties" "DFP-0: Scaling = Centered; DFP-1: Scaling = Scaled, Dithering = Enabled"
+
+

set DFP-0's scaling mode to centered, set DFP-1's scaling mode +to scaled and its dithering mode to enabled.

+
+
Option "ProbeAllGpus" +"boolean"
+
+

When the NVIDIA X driver initializes, it probes all GPUs in the +system, even if no X screens are configured on them. This is done +so that the X driver can report information about all the system's +GPUs through the NV-CONTROL X extension. This option can be set to +FALSE to disable this behavior, such that only GPUs with X screens +configured on them will be probed. Default: all GPUs in the system +are probed.

+
+
Option "DynamicTwinView" +"boolean"
+
+

Enable or disable support for dynamically configuring TwinView +on this X screen. When DynamicTwinView is enabled (the default), +the refresh rate of a mode (reported through XF86VidMode or XRandR) +does not correctly report the refresh rate, but instead is a unique +number such that each MetaMode has a different value. This is to +guarantee that MetaModes can be uniquely identified by XRandR.

+

When DynamicTwinView is disabled, the refresh rate reported +through XRandR will be accurate, but NV-CONTROL clients such as +nvidia-settings will not be able to dynamically manipulate the X +screen's MetaModes. TwinView can still be configured from the X +config file when DynamicTwinView is disabled.

+

Default: DynamicTwinView is enabled.

+
+
Option "IncludeImplicitMetaModes" +"boolean"
+
+

When the X server starts, a mode pool is created per display +device, containing all the mode timings that the NVIDIA X driver +determined to be valid for the display device. However, the only +MetaModes that are made available to the X server are the ones +explicitly requested in the X configuration file.

+

It is convenient for fullscreen applications to be able to +change between the modes in the mode pool, even if a given target +mode was not explicitly requested in the X configuration file.

+

To facilitate this, the NVIDIA X driver will, if only one +display device is in use when the X server starts, implicitly add +MetaModes for all modes in the display device's mode pool. This +makes all the modes in the mode pool available to full screen +applications that use the XF86VidMode or XRandR X extensions.

+

To prevent this behavior, and only add MetaModes that are +explicitly requested in the X configuration file, set this option +to FALSE.

+

Default: IncludeImplicitMetaModes is enabled.

+
+
Option "AllowIndirectPixmaps" +"boolean"
+
+

Some graphics cards have more video memory than can be mapped at +once by the CPU (generally only 256 MB of video memory can be +CPU-mapped). On graphics cards based on G80 and higher with such a +memory configuration, this option allows the driver to place more +pixmaps in video memory which will improve hardware rendering +performance but will slow down software rendering. On some systems, +up to 768 megabytes of virtual address space will be reserved in +the X server for indirect pixmap access. This virtual memory does +not consume any physical resources.

+

Default: on (indirect pixmaps will be used, when available).

+
+
Option "OnDemandVBlankInterrupts" +"boolean"
+
+

Normally, VBlank interrupts are generated on every vertical +refresh of every display device connected to the GPU(s) installed +in a given system. This experimental option enables on-demand +VBlank control, allowing the driver to enable VBlank interrupt +generation only when it is required. This can help conserve +power.

+

Default: off (on-demand VBlank control is disabled).

+
+
Option "PixmapCacheSize" +"size"
+
+

This option controls how much video memory is reserved for +pixmap allocations. When the option is specified, size specifies the number of bytes to use +for the pixmap cache. Reserving this memory improves performance +when pixmaps are created and destroyed rapidly, but prevents this +memory from being used by OpenGL. When this cache is disabled or +space in the cache is exhausted, the driver will still allocate +pixmaps in video memory but pixmap creation and deletion +performance will not be improved.

+

NOTE: This option is deprecated in favor of the +PixmapCacheRoundSizeKB nvidia-settings attribute and will be +removed in a future driver release.

+

Example: Option "PixmapCacheSize" +"1048576" will allocate one megabyte for the pixmap +cache.

+

Default: off (no memory is reserved specifically for +pixmaps).

+
+
Option "AllowSHMPixmaps" +"boolean"
+
+

This option controls whether applications can use the MIT-SHM X +extension to create pixmaps whose contents are shared between the X +server and the client. These pixmaps prevent the NVIDIA driver from +performing a number of optimizations and degrade performance in +many circumstances.

+

Disabling this option disables only shared memory pixmaps. +Applications can still use the MIT-SHM extension to transfer data +to the X server through shared memory using XShmPutImage.

+

Default: off (shared memory pixmaps are not allowed).

+
+
Option +"InitializeWindowBackingPixmaps" "boolean"
+
+

This option controls whether the NVIDIA X Driver initializes +newly created redirected windows using the contents of their parent +window if the X server doesn't do it. Leaving redirected windows +uninitialized may cause new windows to flash with black or random +colors when some compositing managers are running.

+

This option will have no effect on X servers that already +initialize redirected window contents. In most distributions, the X +server is patched to skip that initialization. In this case, it is +recommended to leave this option on for a better user +experience.

+

Default: on (redirected windows are initialized).

+
+
Option "AllowUnofficialGLXProtocol" +"boolean"
+
+

By default, the NVIDIA GLX implementation will not expose GLX +protocol for GL commands if the protocol is not considered +complete. Protocol could be considered incomplete for a number of +reasons. The implementation could still be under development and +contain known bugs, or the protocol specification itself could be +under development or going through review. If users would like to +test the server-side portion of such protocol when using indirect +rendering, they can enable this option. If any X screen enables +this option, it will enable protocol on all screens in the +server.

+

When an NVIDIA GLX client is used, the related environment +variable __GL_ALLOW_UNOFFICIAL_PROTOCOL +will need to be set as well to enable support in the client.

+
+
Option "PanAllDisplays" +"boolean"
+
+

When this option is enabled, all displays in the current +MetaMode will pan as the pointer is moved. If disabled, only the +displays whose panning domain contains the pointer (at its new +location) are panned.

+

Default: enabled (all displays are panned when the pointer is +moved).

+
+
+
+

+"appendix-a.html">Prev  +"part-02.html">Up +"appendix-c.html">Next +Appendix A. Supported NVIDIA GPU Products  + Appendix C. Display Device Names
Prev  Up  Next
-Chapter 2. Installing the NVIDIA Driver  Home - Chapter 3. Using Linux Compatibility Support
diff --git a/doc/html/appendix-c.html b/doc/html/appendix-c.html index a547bd2..2fbdf71 100644 --- a/doc/html/appendix-c.html +++ b/doc/html/appendix-c.html @@ -5,29 +5,28 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Appendix C. The Sysctl Interface +Appendix C. Display Device Names - - + + +"Appendix D. GLX Support">
- + - +"appendix-b.html">Prev  + @@ -37,187 +36,55 @@ Configuration Instructions
-

Appendix C. The Sysctl -Interface

+

Appendix C. Display Device +Names

-

The sysctl interface allows you to obtain run-time information -about the driver, any installed NVIDIA graphics cards and the AGP -status. It also allows you to control low-level configuration -options and/or overrides.

-

The various pieces of information are held in a hierarchy under -hw.nvidia and are accessible with the sysctl(8) command.

-
-

NVIDIA sysctl Entries

-
-
hw.nvidia.version
-
-

Prints the installed driver revision

-
-
hw.nvidia.cards.n.*
-
-

These OIDs provide information about NVIDIA device 'n':

-
-
Appendix C. The Sysctl -InterfaceAppendix C. Display Device +Names
Prev Part I. Installation and -Configuration InstructionsPart II. Appendices  Next
--- - - - - - - - - - - - - - - - - - - - - - - - - -
IDDescription
modelthe device's product name
irqthe IRQ claimed by this device
vbiosthe device's Video BIOS revision
typethe bus type of this device
-
-

- -
hw.nvidia.agp.host-bridge.*, -hw.nvidia.agp.card.*,
-
-

These OIDs provide information about the AGP capabilities of the -installed AGP graphics card and host-bridge respectively. These -values are most likely to be correct after system boot and before -the X server is started (and the AGP subsystem initialized).

-
- --- - - - - - - - - - - - - - - - - - - - - - - - - -
IDDescription
ratesthe AGP rates supported by this device
fwif the device supports AGP fast-writes
sbaif the device supports AGP side-band-addressing
registersthe device's AGP registers, status:command
-
-

-
-
hw.nvidia.agp.status.*
-
-

Prints AGP status information based on the AGP command registers -of the host-bridge and of the AGP card.

-
- --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IDDescription
statusif AGP is enabled or disabled
driverwhich driver is being used
ratethe programmed AGP rate
fwif fast-writes are enabled or disabled
sbaif side-band-addressing is enabled or disabled
-
-

-
-
hw.nvidia.registry.*
-
-

Low-level kernel module configuration options. Changing these is -typically not necessary and potentially dangerous. If you do need -to change any of these options, you will need to do so before you start the X server.

-
- --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IDDescription
statusif AGP is enabled or disabled
driverwhich driver is being used
ratethe programmed AGP rate
fwif fast-writes are enabled or disabled
sbaif side-band-addressing is enabled or disabled
-
-

-
- - +

A "display device" refers to some piece of hardware capable of +displaying an image. There are three categories of display devices: +analog displays (i.e., CRTs), digital displays (i.e., digital flat +panels (DFPs)), and televisions. Note that analog flat panels are +considered the same as analog CRTs by the NVIDIA FreeBSD +driver.

+

A "display device name" is a string description that uniquely +identifies a display device; it follows the format +"<type>-<number>", for example: "CRT-0", "CRT-1", +"DFP-0", or "TV-0". Note that the number indicates how the display +device connector is wired on the graphics card, and has nothing to +do with how many of that kind of display device are present. This +means, for example, that you may have a "CRT-1", even if you do not +have a "CRT-0". To determine which display devices are currently +connected, you may check your X log file for a line similar to the +following:

+
+    (II) NVIDIA(0): Connected display device(s): CRT-0, DFP-0
+
+

Display device names can be used in the MetaMode, HorizSync, and +VertRefresh X config options to indicate which display device a +setting should be applied to. For example:

+
+    Option "MetaModes"   "CRT-0: 1600x1200,  DFP-0: 1024x768"
+    Option "HorizSync"   "CRT-0: 50-110;     DFP-0: 40-70"
+    Option "VertRefresh" "CRT-0: 60-120;     DFP-0: 60"
+
+

Specifying the display device name in these options is not +required; if display device names are not specified, then the +driver attempts to infer which display device a setting applies to. +In the case of MetaModes, for example, the first mode listed is +applied to the "first" display device, and the second mode listed +is applied to the "second" display device. Unfortunately, it is +often unclear which display device is the "first" or "second". That +is why specifying the display device name is preferable.

+

When specifying display device names, you may also omit the +number part of the name, though this is only useful if you only +have one of that type of display device. For example, if you have +one CRT and one DFP connected, you may reference them in the +MetaMode string as follows:

+
+    Option "MetaModes"   "CRT: 1600x1200,  DFP: 1024x768"
+

@@ -225,19 +92,19 @@ to change any of these options, you will need to do so Prev  +"appendix-b.html">Prev  Up +"part-02.html">Up  Next - -Chapter 17. Configuring Flipping and UBB  +Appendix B. X +Config Options  Home - Appendix D. Configuring Low-level Parameters + Appendix D. GLX Support
diff --git a/doc/html/appendix-d.html b/doc/html/appendix-d.html index 8452144..756c0f3 100644 --- a/doc/html/appendix-d.html +++ b/doc/html/appendix-d.html @@ -5,32 +5,30 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Appendix D. Configuring Low-level -Parameters +Appendix D. GLX Support - + - +"Appendix C. Display Device Names"> +
- + - + +"appendix-e.html">Next
Appendix D. Configuring -Low-level ParametersAppendix D. GLX +Support
Prev Part I. Installation and -Configuration InstructionsPart II. Appendices  Next
@@ -38,275 +36,63 @@ Configuration Instructions
-

Appendix D. Configuring Low-level -Parameters

+

Appendix D. GLX Support

-

The NVIDIA resource manager recognizes several low-level -configuration parameters that can be set using the sysctl driver -interface before the X -server is started. Normally you should not need to modify any of -these parameters, but it is sometimes necessary or desirable to do -so.

-

To view the current settings of these parameters, you need to -issue this sysctl command (nvidia.ko -needs to be loaded):

-
-    % sysctl -a hw.nvidia.registry
-
-

To change any of the parameters, you need to pass the complete -name of the OID followed by '=' and the new value, e.g.:

-
-    % sysctl hw.nvidia.registry.EnableVia4x=1
-
-

It is possible to automate setting these parameters by adding -them to the /etc/sysctl.conf file. -See man 5 -sysctl.conf for details.

-

The following parameters are recognized by nvidia.ko:

-
-

Resource Manager Parameters

-
-
VideoMemoryTypeOverride
-
-

We normally detect memory type on TNT cards by scanning the -embedded BIOS. Unfortunately, we've seen some cases where a TNT -card has been flashed with the wrong BIOS. For example, an SDRAM -based TNT has been flashed with an SGRAM BIOS, and therefore claims -to be an SGRAM TNT. We've therefore provided an override here. Make -sure to set the value toe the type of memory used on your card.

-
- --- - - - - - - - - - - - - - - - - -
ValueMeaning
1SDRAM
2SGRAM
-
-

Note that we can only do so much here. There are border cases -where even this fails. For example, if 2 TNT cards are in the same -system, one SGRAM, one SDRAM.

-

This option is disabled by default, see below for information on -how to enable it.

-
-
EnableVia4x
-
-

We've had problems with some Via chipsets in 4x mode, we need -force them back down to 2x mode. If you'd like to experiment with -retaining 4x mode, you may try setting this value to 1 If that -hangs the system, you're stuck with 2x mode; there's nothing we can -do about it.

-
- --- - - - - - - - - - - - - - - - - -
ValueMeaning
0disable AGP 4x on Via chipsets (default)
1enable AGP 4x on Via chipsets
-
-

-
-
EnableALiAGP
-
-

Some ALi chipsets (ALi1541, ALi1647) are known to cause severe -system stability problems with AGP enabled. To avoid lockups, we -disable AGP on systems with these chipsets by default. It appears -that updating the system BIOS and using recent versions of the -kernel AGP Gart driver can make such systems much more stable. If -you own a system with one of the aforementioned chipsets and had it -working reasonably well previously, or if you want to experiment -with BIOS and AGPGART revisions, you can re-enable AGP support by -setting this option to 1.

-
- --- - - - - - - - - - - - - - - - - -
ValueMeaning
0disable AGP on Ali1541 and ALi1647 (default)
1enable AGP on Ali1541 and ALi1647
-
-

-
-
NvAGP
-
-

This options controls which AGP GART driver is used when no -explicit request is made to change the default (X server).

-
- --- - - - - - - - - - - - - - - - - - - - - - - - - -
ValueMeaning
0disable AGP support
1use the NVIDIA builtin driver (if possible)
2use the kernel's AGPGART driver (if possible)
3use any available driver (try 2, then 1)
-
-

Note that the NVIDIA internal AGP GART driver will not be used -if AGPGART was either statically linked into your kernel or built -as a kernel module and loaded before the NVIDIA kernel module.

-
-
ReqAGPRate
-
-

Normally, the driver will compare speed modes of the chipset and -the card, picking the highest common rate. This key forces a -maximum limit, to limit the driver to lower speeds. The driver will -not attempt a speed beyond what the chipset and card claim they are -capable of.

-

Make sure you really know what you're doing before you enable -this override. By default, AGP drivers will enable the fastest AGP -rate your card and motherboard chipset are capable of. Then, in -some cases, our driver will force this rate down to work around -bugs in both our chipsets, and motherboard chipsets. Using this -variable will override our bug fixes. This may be desirable in some -cases, but not most. This is completely -unsupported!

-

This option expects a bitmask (7 = 1|2|3|4, 3=1|2, etc.)

-

This option is disabled by default, see below for information on -how to enable it.

-
-
EnableAGPSBA
-
-

For stability reasons, the driver will not use Side Band -Addressing even if both the host chipset and the AGP card support -it. You may override this behavior with the following registry key. -This is completely -unsupported!

-
- --- - - - - - - - - - - - - - - - - -
ValueMeaning
0disable Side Band Addressing (default on x86, see below)
1enable Side Band Addressing (if supported)
-
-

-
-
EnableAGPFW
-
-

Similar to Side Band Addressing, Fast Writes are disabled by -default. If you wish to enable them on systems that support them, -you can do so with this registry key. Note that this may render -your system unstable with many AGP chipsets. This is completely unsupported!

-
- --- - - - - - - - - - - - - - - - - -
ValueMeaning
0disable Fast Writes (default)
1enable Fast Writes
-
-

-
-
+

This release supports GLX 1.4.

+

Additionally, the following GLX extensions are supported on +appropriate GPUs:

+
+
    +
  • +

    GLX_EXT_visual_info

    +
    • +
  • +

    GLX_EXT_visual_rating

    +
    • +
  • +

    GLX_SGIX_fbconfig

    +
    • +
  • +

    GLX_SGIX_pbuffer

    +
    • +
  • +

    GLX_ARB_get_proc_address

    +
    • +
  • +

    GLX_SGI_video_sync

    +
    • +
  • +

    GLX_SGI_swap_control

    +
    • +
  • +

    GLX_ARB_multisample

    +
    • +
  • +

    GLX_NV_float_buffer

    +
    • +
  • +

    GLX_ARB_fbconfig_float

    +
    • +
  • +

    GLX_NV_swap_group

    +
    • +
  • +

    GLX_NV_video_out

    +
    • +
  • +

    GLX_EXT_texture_from_pixmap

    +
    • +
-

+

For a description of these extensions, see the OpenGL extension +registry at http://www.opengl.org/registry/

+

Some of the above extensions exist as part of core GLX 1.4 +functionality, however, they are also exported as extensions for +backwards compatibility.

@@ -315,17 +101,17 @@ your system unstable with many AGP chipsets. Prev  Up +"part-02.html">Up  Next +"appendix-e.html">Next -Appendix C. The -Sysctl Interface  + +Appendix C. Display Device Names  Home - Chapter 18. Using the X Composite Extension + Appendix E. Dots Per Inch
diff --git a/doc/html/appendix-e.html b/doc/html/appendix-e.html index 0b0e810..be993a6 100644 --- a/doc/html/appendix-e.html +++ b/doc/html/appendix-e.html @@ -5,27 +5,27 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Appendix E. Supported NVIDIA GPU Products +Appendix E. Dots Per Inch - + +"Appendix F. XvMC Support">
- + +"appendix-d.html">Prev  @@ -36,1441 +36,126 @@ NVIDIA GPU Products
-

Appendix E. Supported NVIDIA GPU -Products

+

Appendix E. Dots Per Inch

-

For the most complete and accurate listing of supported GPUs, -please see the Supported Products List, available from the NVIDIA -FreeBSD x86 Graphics Driver download page. Please go to http://www.nvidia.com/object/unix.html, follow the -Archive link under the FreeBSD x86 heading, follow the link for the -180.29 driver, and then go to the Supported Products List.

-

NVIDIA GeForce GPUs

-
-
Appendix E. Supported -NVIDIA GPU ProductsAppendix E. Dots Per +Inch
Prev  Part II. Appendices  Next
--- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NVIDIA GPU productDevice PCI ID
GeForce 6800 Ultra0x0040
GeForce 68000x0041
GeForce 6800 LE0x0042
GeForce 6800 XE0x0043
GeForce 6800 XT0x0044
GeForce 6800 GT0x0045
GeForce 6800 GT0x0046
GeForce 6800 GS0x0047
GeForce 6800 XT0x0048
GeForce 7800 GTX0x0090
GeForce 7800 GTX0x0091
GeForce 7800 GT0x0092
GeForce 7800 GS0x0093
GeForce 7800 SLI0x0095
GeForce Go 78000x0098
GeForce Go 7800 GTX0x0099
GeForce 6800 GS0x00C0
GeForce 68000x00C1
GeForce 6800 LE0x00C2
GeForce 6800 XT0x00C3
GeForce Go 68000x00C8
GeForce Go 6800 Ultra0x00C9
Unknown GPU0x00F0
GeForce 6600 GT0x00F1
GeForce 66000x00F2
GeForce 62000x00F3
GeForce 6600 LE0x00F4
GeForce 7800 GS0x00F5
GeForce 6800 GS0x00F6
GeForce 6800 Ultra0x00F9
GeForce 6600 GT0x0140
GeForce 66000x0141
GeForce 6600 LE0x0142
GeForce 6600 VE0x0143
GeForce Go 66000x0144
GeForce 6610 XL0x0145
GeForce Go 6600 TE/6200 TE0x0146
GeForce 6700 XL0x0147
GeForce Go 66000x0148
GeForce Go 6600 GT0x0149
GeForce 62000x014F
GeForce 65000x0160
GeForce 6200 TurboCache(TM)0x0161
GeForce 6200SE TurboCache(TM)0x0162
GeForce 6200 LE0x0163
GeForce Go 62000x0164
GeForce Go 64000x0166
GeForce Go 62000x0167
GeForce Go 64000x0168
GeForce 62500x0169
GeForce 7100 GS0x016A
GeForce 8800 GTX0x0191
GeForce 8800 GTS0x0193
GeForce 8800 Ultra0x0194
Tesla C8700x0197
GeForce 7350 LE0x01D0
GeForce 7300 LE0x01D1
GeForce 7300 SE/7200 GS0x01D3
GeForce Go 72000x01D6
GeForce Go 73000x01D7
GeForce Go 74000x01D8
GeForce 7500 LE0x01DD
GeForce 7300 GS0x01DF
GeForce 68000x0211
GeForce 6800 LE0x0212
GeForce 6800 GT0x0215
GeForce 6800 XT0x0218
GeForce 62000x0221
GeForce 6200 A-LE0x0222
GeForce 61500x0240
GeForce 6150 LE0x0241
GeForce 61000x0242
GeForce Go 61500x0244
GeForce Go 61000x0247
GeForce 7900 GTX0x0290
GeForce 7900 GT/GTO0x0291
GeForce 7900 GS0x0292
GeForce 7950 GX20x0293
GeForce 7950 GX20x0294
GeForce 7950 GT0x0295
GeForce Go 7950 GTX0x0297
GeForce Go 7900 GS0x0298
GeForce Go 7900 GTX0x0299
GeForce 7600 GT0x02E0
GeForce 7600 GS0x02E1
GeForce 7300 GT0x02E2
GeForce 7900 GS0x02E3
GeForce 7950 GT0x02E4
GeForce 7650 GS0x0390
GeForce 7600 GT0x0391
GeForce 7600 GS0x0392
GeForce 7300 GT0x0393
GeForce 7600 LE0x0394
GeForce 7300 GT0x0395
GeForce Go 77000x0397
GeForce Go 76000x0398
GeForce Go 7600 GT0x0399
GeForce 6150SE nForce 4300x03D0
GeForce 6100 nForce 4050x03D1
GeForce 6100 nForce 4000x03D2
GeForce 6100 nForce 4200x03D5
GeForce 8600 GTS0x0400
GeForce 8600 GT0x0401
GeForce 8600 GT0x0402
GeForce 8600GS0x0403
GeForce 8400 GS0x0404
GeForce 9500M GS0x0405
GeForce 8600M GT0x0407
GeForce 9650M GS0x0408
GeForce 8700M GT0x0409
GeForce 8400 SE0x0420
GeForce 8500 GT0x0421
GeForce 8400 GS0x0422
GeForce 8300 GS0x0423
GeForce 8400 GS0x0424
GeForce 8600M GS0x0425
GeForce 8400M GT0x0426
GeForce 8400M GS0x0427
GeForce 8400M G0x0428
GeForce 9400 GT0x042C
GeForce 9300M G0x042E
GeForce 7150M / nForce 630M0x0531
GeForce 7000M / nForce 610M0x0533
GeForce 7050 PV / NVIDIA nForce 630a0x053A
GeForce 7050 PV / NVIDIA nForce 630a0x053B
GeForce 7025 / NVIDIA nForce 630a0x053E
GeForce GTX 2950x05E0
GeForce GTX 2800x05E1
GeForce GTX 2600x05E2
GeForce GTX 2850x05E3
GeForce 8800 GTS 5120x0600
GeForce 9800 GT0x0601
GeForce 8800 GT0x0602
GeForce 9800 GX20x0604
GeForce 9800 GT0x0605
GeForce 8800 GS0x0606
GeForce 9800M GTX0x0608
GeForce 8800M GTS0x0609
GeForce 9800M GT0x060B
GeForce 8800M GTX0x060C
GeForce 8800 GS0x060D
GeForce 9600 GSO0x0610
GeForce 8800 GT0x0611
GeForce 9800 GTX/9800 GTX+0x0612
GeForce 9800 GTX+0x0613
GeForce 9800 GT0x0614
GeForce 9800M GTX0x0617
GeForce 9600 GT0x0622
GeForce 9600 GS0x0623
GeForce 9800M GTS0x0628
GeForce 9700M GTS0x062A
GeForce 9800M GS0x062B
GeForce 9800M GTS0x062C
GeForce 9500 GT0x0640
GeForce 9500 GT0x0643
GeForce 9600M GT0x0647
GeForce 9600M GS0x0648
GeForce 9600M GT0x0649
GeForce 9700M GT0x064A
GeForce 9500M G0x064B
GeForce 9650M GT0x064C
GeForce 9650 S0x0656
GeForce 9300 GE0x06E0
GeForce 9300 GS0x06E1
GeForce 8400 GS0x06E4
GeForce 9300M GS0x06E5
GeForce 9200M GS0x06E8
GeForce 9300M GS0x06E9
GeForce 7150 / NVIDIA nForce 630i0x07E0
GeForce 7100 / NVIDIA nForce 630i0x07E1
GeForce 7050 / NVIDIA nForce 610i0x07E3
GeForce 9100M G0x0844
GeForce 8200M G0x0845
GeForce 91000x0847
GeForce 83000x0848
GeForce 82000x0849
nForce 730a0x084A
GeForce 82000x084B
nForce 780a SLI0x084C
nForce 750a SLI0x084D
GeForce 8100 / nForce 720a0x084F
GeForce 9400M G0x0862
GeForce 9400M0x0863
+

DPI (Dots Per Inch), also known as PPI (Pixels Per Inch), is a +property of an X screen that describes the physical size of pixels. +Some X applications, such as xterm, can use the DPI of an X screen +to determine how large (in pixels) to draw an object in order for +that object to be displayed at the desired physical size on the +display device.

+

The DPI of an X screen is computed by dividing the size of the X +screen in pixels by the size of the X screen in inches:

+
+    DPI = SizeInPixels / SizeInInches
+
+

Since the X screen stores its physical size in millimeters +rather than inches (1 inch = 25.4 millimeters):

+
+    DPI = (SizeInPixels * 25.4) / SizeInMillimeters
+
+

The NVIDIA X driver reports the size of the X screen in pixels +and in millimeters. On X.Org 6.9 or newer, when the XRandR +extension resizes the X screen in pixels, the NVIDIA X driver +computes a new size in millimeters for the X screen, to maintain a +constant DPI (see the "Physical Size" column of the `xrandr -q` +output as an example). This is done because a changing DPI can +cause interaction problems for some applications. To disable this +behavior, and instead keep the same millimeter size for the X +screen (and therefore have a changing DPI), set the ConstantDPI +option to FALSE (see Appendix B, X +Config Options for details).

+

You can query the DPI of your X screen by running:

+
+    % xdpyinfo | grep -B1 dot
+
+

which should generate output like this:

+
+    dimensions:    1280x1024 pixels (382x302 millimeters)
+    resolution:    85x86 dots per inch
+
+

+

The NVIDIA X driver performs several steps during X screen +initialization to determine the DPI of each X screen:

+
+
    +
  • +

    If the display device provides an EDID, and the EDID contains +information about the physical size of the display device, that is +used to compute the DPI, along with the size in pixels of the first +mode to be used on the display device. If multiple display devices +are used by this X screen, then the NVIDIA X screen will choose +which display device to use. You can override this with the +"UseEdidDpi" X configuration option: you can specify a particular +display device to use; e.g.:

    +
    +    Option "UseEdidDpi" "DFP-1"
+
    +

    or disable EDID-computed DPI by setting this option to +false:

    +
    +    Option "UseEdidDpi" "FALSE"
+
    +

    EDID-based DPI computation is enabled by default when an EDID is +available.

    +
    • +
  • +

    If the "-dpi" commandline option to the X server is specified, +that is used to set the DPI (see `X -h` for details). This will +override the "UseEdidDpi" option.

    +
    • +
  • +

    If the "DPI" X configuration option is specified (see Appendix B, X +Config Options for details), that will be used to set the +DPI. This will override the "UseEdidDpi" option.

    +
    • +
  • +

    If none of the above are available, then the "DisplaySize" X +config file Monitor section information will be used to determine +the DPI, if provided; see the xorg.conf or XF86Config man pages for +details.

    +
    • +
  • +

    If none of the above are available, the DPI defaults to +75x75.

    +
    • +
-

NVIDIA Quadro GPUs

-
- --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NVIDIA GPU productDevice PCI ID
Quadro FX 40000x004E
Quadro FX 45000x009D
Quadro FX Go14000x00CC
Quadro FX 3450/4000 SDI0x00CD
Quadro FX 14000x00CE
Quadro FX 4400/Quadro FX 34000x00F8
Quadro NVS 4400x014A
Quadro FX 540M0x014C
Quadro FX 5500x014D
Quadro FX 5400x014E
Quadro NVS 2850x0165
Quadro FX 56000x019D
Quadro FX 46000x019E
Quadro NVS 110M0x01D7
Quadro NVS 110M0x01DA
Quadro NVS 120M0x01DB
Quadro FX 350M0x01DC
Quadro FX 3500x01DE
Quadro NVS 210S / NVIDIA GeForce 6150LE0x0245
Quadro FX 2500M0x029A
Quadro FX 1500M0x029B
Quadro FX 55000x029C
Quadro FX 35000x029D
Quadro FX 15000x029E
Quadro FX 4500 X20x029F
Quadro FX 5600x039E
Quadro FX 3700x040A
Quadro NVS 320M0x040B
Quadro FX 570M0x040C
Quadro FX 1600M0x040D
Quadro FX 5700x040E
Quadro FX 17000x040F
Quadro NVS 140M0x0429
Quadro NVS 130M0x042A
Quadro NVS 135M0x042B
Quadro FX 360M0x042D
Quadro NVS 2900x042F
Quadro CX0x05F9
Quadro FX 58000x05FD
Quadro FX 48000x05FE
Quadro FX 37000x061A
Quadro FX 3600M0x061C
Quadro FX 2700M0x063A
Quadro FX 770M0x065C
Quadro NVS 150M0x06EA
Quadro NVS 160M0x06EB
Quadro NVS 4200x06F8
Quadro FX 370 LP0x06F9
Quadro NVS 4500x06FA
Quadro NVS 2950x06FD
Quadro FX 4700x087A
Quadro FX 470M0x087F
-
-

Below are the legacy GPUs that are no longer supported in the -unified driver. These GPUs will continue to be maintained through -the special legacy NVIDIA GPU driver releases.

-

The 173.14.xx driver supports the following set of GPUs:

-
- --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NVIDIA GPU productDevice PCI ID
GeForce PCX 57500x00FA
GeForce PCX 59000x00FB
Quadro FX 330/GeForce PCX 53000x00FC
Quadro FX 330/Quadro NVS 280 PCI-E0x00FD
Quadro FX 13000x00FE
GeForce FX 5800 Ultra0x0301
GeForce FX 58000x0302
Quadro FX 20000x0308
Quadro FX 10000x0309
GeForce FX 5600 Ultra0x0311
GeForce FX 56000x0312
GeForce FX 5600XT0x0314
GeForce FX Go56000x031A
GeForce FX Go56500x031B
Quadro FX Go7000x031C
GeForce FX 52000x0320
GeForce FX 5200 Ultra0x0321
GeForce FX 52000x0322
GeForce FX 5200LE0x0323
GeForce FX Go52000x0324
GeForce FX Go52500x0325
GeForce FX 55000x0326
GeForce FX 51000x0327
GeForce FX Go5200 32M/64M0x0328
Quadro NVS 55/280 PCI0x032A
Quadro FX 500/FX 6000x032B
GeForce FX Go53xx0x032C
GeForce FX Go51000x032D
GeForce FX 5900 Ultra0x0330
GeForce FX 59000x0331
GeForce FX 5900XT0x0332
GeForce FX 5950 Ultra0x0333
GeForce FX 5900ZT0x0334
Quadro FX 30000x0338
Quadro FX 7000x033F
GeForce FX 5700 Ultra0x0341
GeForce FX 57000x0342
GeForce FX 5700LE0x0343
GeForce FX 5700VE0x0344
GeForce FX Go57000x0347
GeForce FX Go57000x0348
Quadro FX Go10000x034C
Quadro FX 11000x034E
-
-

The 96.43.xx driver supports the following set of GPUs:

-
- --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NVIDIA GPU productDevice PCI ID
GeForce2 MX/MX 4000x0110
GeForce2 MX 100/2000x0111
GeForce2 Go0x0112
Quadro2 MXR/EX/Go0x0113
GeForce4 MX 4600x0170
GeForce4 MX 4400x0171
GeForce4 MX 4200x0172
GeForce4 MX 440-SE0x0173
GeForce4 440 Go0x0174
GeForce4 420 Go0x0175
GeForce4 420 Go 32M0x0176
GeForce4 460 Go0x0177
Quadro4 550 XGL0x0178
GeForce4 440 Go 64M0x0179
Quadro NVS 4000x017A
Quadro4 500 GoGL0x017C
GeForce4 410 Go 16M0x017D
GeForce4 MX 440 with AGP8X0x0181
GeForce4 MX 440SE with AGP8X0x0182
GeForce4 MX 420 with AGP8X0x0183
GeForce4 MX 40000x0185
Quadro4 580 XGL0x0188
Quadro NVS 280 SD0x018A
Quadro4 380 XGL0x018B
Quadro NVS 50 PCI0x018C
GeForce2 Integrated GPU0x01A0
GeForce4 MX Integrated GPU0x01F0
GeForce30x0200
GeForce3 Ti 2000x0201
GeForce3 Ti 5000x0202
Quadro DCC0x0203
GeForce4 Ti 46000x0250
GeForce4 Ti 44000x0251
GeForce4 Ti 42000x0253
Quadro4 900 XGL0x0258
Quadro4 750 XGL0x0259
Quadro4 700 XGL0x025B
GeForce4 Ti 48000x0280
GeForce4 Ti 4200 with AGP8X0x0281
GeForce4 Ti 4800 SE0x0282
GeForce4 4200 Go0x0286
Quadro4 980 XGL0x0288
Quadro4 780 XGL0x0289
Quadro4 700 GoGL0x028C
-
-

The 71.86.xx driver supports the following set of GPUs:

-
- --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NVIDIA GPU productDevice PCI ID
RIVA TNT0x0020
RIVA TNT2/TNT2 Pro0x0028
RIVA TNT2 Ultra0x0029
Vanta/Vanta LT0x002C
RIVA TNT2 Model 64/Model 64 Pro0x002D
Aladdin TNT20x00A0
GeForce 2560x0100
GeForce DDR0x0101
Quadro0x0103
GeForce2 GTS/GeForce2 Pro0x0150
GeForce2 Ti0x0151
GeForce2 Ultra0x0152
Quadro2 Pro0x0153
+

You can find how the NVIDIA X driver determined the DPI by +looking in your X log file. There will be a line that looks +something like the following:

+
+    (--) NVIDIA(0): DPI set to (101, 101); computed from "UseEdidDpi" X config option
+
+

+

Note that the physical size of the X screen, as reported through +`xdpyinfo` is computed based on the DPI and the size of the X +screen in pixels.

+

The DPI of an X screen can be confusing when TwinView is +enabled: with TwinView, multiple display devices (possibly with +different DPIs) display portions of the same X screen, yet DPI can +only be advertised from the X server to the X application with X +screen granularity. Solutions for this include:

+
+
@@ -1478,19 +163,19 @@ the special legacy NVIDIA GPU driver releases.

+"appendix-d.html">Prev  - + + Appendix F. XvMC Support
Prev  Up  Next
-Part II. Appendices Appendix D. GLX +Support  Home - Appendix F. X Config Options
diff --git a/doc/html/appendix-f.html b/doc/html/appendix-f.html index 097f0dc..ff74fff 100644 --- a/doc/html/appendix-f.html +++ b/doc/html/appendix-f.html @@ -5,23 +5,23 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Appendix F. X Config Options +Appendix F. XvMC Support +"Appendix E. Dots Per Inch"> +"Appendix G. VDPAU Support">
- + +Appendix E. Dots Per Inch  + Appendix G. VDPAU Support
Appendix F. X Config -OptionsAppendix F. XvMC +Support
-

Appendix F. X Config Options

+

Appendix F. XvMC Support

-

The following driver options are supported by the NVIDIA X -driver. They may be specified either in the Screen or Device -sections of the X config file.

-
-

X Config Options

-
-
Option "NvAGP" "integer"
-
-

Configure AGP support. Integer argument can be one of:

-
- --- - - - - - - - - - - - - - - - - - - - - - - - - -
ValueBehavior
0disable AGP
1use NVIDIA internal AGP support, if possible
2use AGPGART, if possible
3use any AGP support (try AGPGART, then NVIDIA AGP)
-
-

Note that NVIDIA internal AGP support cannot work if AGPGART is -either statically compiled into your kernel or is built as a module -and loaded into your kernel. See Chapter 9, -Configuring AGP for details. Default: 3.

-
-
Option "NoLogo" -"boolean"
-
-

Disable drawing of the NVIDIA logo splash screen at X startup. -Default: the logo is drawn for screens with depth 24.

-
-
Option "LogoPath" -"string"
-
-

Sets the path to the PNG file to be used as the logo splash -screen at X startup. If the PNG file specified has a bKGD -(background color) chunk, then the screen is cleared to the color -it specifies. Otherwise, the screen is cleared to black. The logo -file must be owned by root and must not be writable by a non-root -group. Note that a logo is only displayed for screens with depth -24. Default: The built-in NVIDIA logo is used.

-
-
Option "RenderAccel" -"boolean"
-
-

Enable or disable hardware acceleration of the RENDER extension. -Default: hardware acceleration of the RENDER extension is -enabled.

-
-
Option "NoRenderExtension" -"boolean"
-
-

Disable the RENDER extension. Other than recompiling it, the X -server does not seem to have another way of disabling this. -Fortunately, we can control this from the driver so we export this -option. This is useful in depth 8 where RENDER would normally steal -most of the default colormap. Default: RENDER is offered when -possible.

-
-
Option "UBB" "boolean"
-
-

Enable or disable the Unified Back Buffer on Quadro-based GPUs -(Quadro4 NVS excluded); see Chapter 17, -Configuring Flipping and UBB for a description of UBB. -This option has no effect on non-Quadro GPU products. Default: UBB -is on for Quadro GPUs.

-
-
Option "NoFlip" -"boolean"
-
-

Disable OpenGL flipping; see Chapter 17, -Configuring Flipping and UBB for a description. Default: -OpenGL will swap by flipping when possible.

-
-
Option "Dac8Bit" -"boolean"
-
-

Most Quadro products by default use a 10-bit color look-up table -(LUT); setting this option to TRUE forces these GPUs to use an -8-bit (LUT). Default: a 10-bit LUT is used, when available.

-
-
Option "Overlay" -"boolean"
-
-

Enables RGB workstation overlay visuals. This is only supported -on Quadro GPUs (Quadro NVS GPUs excluded) in depth 24. This option -causes the server to advertise the SERVER_OVERLAY_VISUALS root -window property and GLX will report single- and double-buffered, -Z-buffered 16-bit overlay visuals. The transparency key is pixel -0x0000 (hex). There is no gamma correction support in the overlay -plane. This feature requires XFree86 version 4.2.0 or newer, or the -X.Org X server. When the X screen is either wider than 2046 pixels -or taller than 2047, the overlay may be emulated with a substantial -performance penalty. RGB workstation overlays are not supported -when the Composite extension is enabled.

-

UBB must be enabled when overlays are enabled (this is the -default behavior).

-
-
Option "CIOverlay" -"boolean"
-
-

Enables Color Index workstation overlay visuals with identical -restrictions to Option "Overlay" above. The server will offer -visuals both with and without a transparency key. These are depth 8 -PseudoColor visuals. Enabling Color Index overlays on X servers -older than XFree86 4.3 will force the RENDER extension to be -disabled due to bugs in the RENDER extension in older X servers. -Color Index workstation overlays are not supported when the -Composite extension is enabled. Default: off.

-

UBB must be enabled when overlays are enabled (this is the -default behavior).

-
-
Option "TransparentIndex" -"integer"
-
-

When color index overlays are enabled, use this option to choose -which pixel is used for the transparent pixel in visuals featuring -transparent pixels. This value is clamped between 0 and 255 (Note: -some applications such as Alias's Maya require this to be zero in -order to work correctly). Default: 0.

-
-
Option "OverlayDefaultVisual" -"boolean"
-
-

When overlays are used, this option sets the default visual to -an overlay visual thereby putting the root window in the overlay. -This option is not recommended for RGB overlays. Default: off.

-
-
Option "EmulatedOverlaysTimerMs" -"integer"
-
-

Enables the use of a timer within the X server to perform the -updates to the emulated overlay or CI overlay. This option can be -used to improve the performance of the emulated or CI overlays by -reducing the frequency of the updates. The value specified -indicates the desired number of milliseconds between overlay -updates. To disable the use of the timer either leave the option -unset or set it to 0. Default: off.

-
-
Option "EmulatedOverlaysThreshold" -"boolean"
-
-

Enables the use of a threshold within the X server to perform -the updates to the emulated overlay or CI overlay. The emulated or -CI overlay updates can be deferred but this threshold will limit -the number of deferred OpenGL updates allowed before the overlay is -updated. This option can be used to trade off performance and -animation quality. Default: on.

-
-
Option -"EmulatedOverlaysThresholdValue" "integer"
-
-

Controls the threshold used in updating the emulated or CI -overlays. This is used in conjunction with the -EmulatedOverlaysThreshold option to trade off performance and -animation quality. Higher values for this option favor performance -over quality. Setting low values of this option will not cause the -overlay to be updated more often than the frequence specified by -the EmulatedOverlaysTimerMs option. Default: 5.

-
-
Option "RandRRotation" -"boolean"
-
-

Enable rotation support for the XRandR extension. This allows -use of the XRandR X server extension for configuring the screen -orientation through rotation. This feature is supported using depth -24. This requires an X.Org X 6.8.1 or newer X server. This feature -does not work with hardware overlays; emulated overlays will be -used instead at a substantial performance penalty. See Chapter 14, -Using the XRandR Extension for details. Default: -off.

-
-
Option "Rotate" -"string"
-
-

Enable static rotation support. Unlike the RandRRotation option -above, this option takes effect as soon as the X server is started -and will work with older versions of X. This feature is supported -using depth 24. This feature does not work with hardware overlays; -emulated overlays will be used instead at a substantial performance -penalty. This option is not compatible with the RandR extension. -Valid rotations are "normal", "left", "inverted", and "right". -Default: off.

-
-
Option "AllowDDCCI" -"boolean"
-
-

Enables DDC/CI support in the NV-CONTROL X extension. DDC/CI is -a mechanism for communication between your computer and your -display device. This can be used to set the values normally -controlled through your display device's On Screen Display. See the -DDC/CI NV-CONTROL attributes in NVCtrl.h and functions in NVCtrlLib.h in the nvidia-settings source code. Default: off -(DDC/CI is disabled).

-

Note that support for DDC/CI within the NVIDIA X driver's -NV-CONTROL extension is deprecated, and will be removed in a future -release. Other mechanisms for DDC/CI, such as the kernel i2c -subsystem on Linux, are preferred over NV-CONTROL's DDC/CI -support.

-

If you would prefer that the NVIDIA X driver's NV-CONTROL X -extension not remove DDC/CI support, please make your concerns -known my emailing .

-
-
Option "SWCursor" -"boolean"
-
-

Enable or disable software rendering of the X cursor. Default: -off.

-
-
Option "HWCursor" -"boolean"
-
-

Enable or disable hardware rendering of the X cursor. Default: -on.

-
-
Option "CursorShadow" -"boolean"
-
-

Enable or disable use of a shadow with the hardware accelerated -cursor; this is a black translucent replica of your cursor shape at -a given offset from the real cursor. Default: off (no cursor -shadow).

-
-
Option "CursorShadowAlpha" -"integer"
-
-

The alpha value to use for the cursor shadow; only applicable if -CursorShadow is enabled. This value must be in the range [0, 255] --- 0 is completely transparent; 255 is completely opaque. Default: -64.

-
-
Option "CursorShadowXOffset" -"integer"
-
-

The offset, in pixels, that the shadow image will be shifted to -the right from the real cursor image; only applicable if -CursorShadow is enabled. This value must be in the range [0, 32]. -Default: 4.

-
-
Option "CursorShadowYOffset" -"integer"
-
-

The offset, in pixels, that the shadow image will be shifted -down from the real cursor image; only applicable if CursorShadow is -enabled. This value must be in the range [0, 32]. Default: 2.

-
-
Option "ConnectedMonitor" -"string"
-
-

Allows you to override what the NVIDIA kernel module detects is -connected to your graphics card. This may be useful, for example, -if you use a KVM (keyboard, video, mouse) switch and you are -switched away when X is started. In such a situation, the NVIDIA -kernel module cannot detect which display devices are connected, -and the NVIDIA X driver assumes you have a single CRT.

-

Valid values for this option are "CRT" (cathode ray tube), "DFP" -(digital flat panel), or "TV" (television); if using TwinView, this -option may be a comma-separated list of display devices; e.g.: -"CRT, CRT" or "CRT, DFP".

-

It is generally recommended to not use this option, but instead -use the "UseDisplayDevice" option.

-

NOTE: anything attached to a 15 pin VGA connector is regarded by -the driver as a CRT. "DFP" should only be used to refer to digital -flat panels connected via a DVI port.

-

Default: string is NULL (the NVIDIA driver will detect the -connected display devices).

-
-
Option "UseDisplayDevice" -"string"
-
-

The "UseDisplayDevice" X configuration option is a list of one -or more display devices, which limits the display devices the -NVIDIA X driver will consider for an X screen. The display device -names used in the option may be either specific (with a numeric -suffix; e.g., "DFP-1") or general (without a numeric suffix; e.g., -"DFP").

-

When assigning display devices to X screens, the NVIDIA X driver -walks through the list of all (not already assigned) display -devices detected as connected. When the "UseDisplayDevice" X -configuration option is specified, the X driver will only consider -connected display devices which are also included in the -"UseDisplayDevice" list. This can be thought of as a "mask" against -the connected (and not already assigned) display devices.

-

Note the subtle difference between this option and the -"ConnectedMonitor" option: the "ConnectedMonitor" option overrides -which display devices are actually detected, while the -"UseDisplayDevice" option controls which of the detected display -devices will be used on this X screen.

-

Of the list of display devices considered for this X screen -(either all connected display devices, or a subset limited by the -"UseDisplayDevice" option), the NVIDIA X driver first looks at -CRTs, then at DFPs, and finally at TVs. For example, if both a CRT -and a DFP are connected, by default the X driver would assign the -CRT to this X screen. However, by specifying:

-
-    Option "UseDisplayDevice" "DFP"
-
-

the X screen would use the DFP instead. Or, if CRT-0, DFP-0, and -DFP-1 are connected and TwinView is enabled, the X driver would -assign CRT-0 and DFP-0 to the X screen. However, by specifying:

-
-    Option "UseDisplayDevice" "CRT-0, DFP-1"
-
-

the X screen would use CRT-0 and DFP-1 instead.

-

Additionally, the special value "none" can be specified for the -"UseDisplayDevice" option. When this value is given, any -programming of the display hardware is disabled. The NVIDIA driver -will not perform any mode validation or mode setting for this X -screen. This is intended for use in conjunction with CUDA or in -remote graphics solutions such as VNC or Hewlett Packard's Remote -Graphics Software (RGS). This functionality is only available on -Quadro and Tesla GPUs.

-

Note the following restrictions for setting the -"UseDisplayDevice" to "none":

-
-
    -
  • -

    OpenGL SyncToVBlank will have no effect.

    -
    • -
  • -

    None of Stereo, Overlay, CIOverlay, or SLI are allowed when -"UseDisplayDevice" is set to "none".

    -
    • -
-
-

-
-
Option "UseEdidFreqs" -"boolean"
-
-

This option controls whether the NVIDIA X driver will use the -HorizSync and VertRefresh ranges given in a display device's EDID, -if any. When UseEdidFreqs is set to True, EDID-provided range -information will override the HorizSync and VertRefresh ranges -specified in the Monitor section. If a display device does not -provide an EDID, or the EDID does not specify an hsync or vrefresh -range, then the X server will default to the HorizSync and -VertRefresh ranges specified in the Monitor section of your X -config file. These frequency ranges are used when validating modes -for your display device.

-

Default: True (EDID frequencies will be used)

-
-
Option "UseEDID" -"boolean"
-
-

By default, the NVIDIA X driver makes use of a display device's -EDID, when available, during construction of its mode pool. The -EDID is used as a source for possible modes, for valid frequency -ranges, and for collecting data on the physical dimensions of the -display device for computing the DPI (see Appendix I, -Dots Per Inch). However, if you wish to disable the -driver's use of the EDID, you can set this option to False:

-
-    Option "UseEDID" "FALSE"
-
-

Note that, rather than globally disable all uses of the EDID, -you can individually disable each particular use of the EDID; -e.g.,

-
-    Option "UseEDIDFreqs" "FALSE"
-    Option "UseEDIDDpi" "FALSE"
-    Option "ModeValidation" "NoEdidModes"
-
-

Default: True (use EDID).

-
-
Option "IgnoreEDID" -"boolean"
-
-

This option is deprecated, and no longer affects behavior of the -X driver. See the "UseEDID" option for details.

-
-
Option "NoDDC" "boolean"
-
-

Synonym for "IgnoreEDID". This option is deprecated, and no -longer affects behavior of the X driver. See the "UseEDID" option -for details.

-
-
Option "UseInt10Module" -"boolean"
-
-

Enable use of the X Int10 module to soft-boot all secondary -cards, rather than POSTing the cards through the NVIDIA kernel -module. Default: off (POSTing is done through the NVIDIA kernel -module).

-
-
Option "TwinView" -"boolean"
-
-

Enable or disable TwinView. See Chapter 10, -Configuring TwinView for details. Default: off (TwinView -is disabled).

-
-
Option "TwinViewOrientation" -"string"
-
-

Controls the relationship between the two display devices when -using TwinView. Takes one of the following values: "RightOf" -"LeftOf" "Above" "Below" "Clone". See Chapter 10, -Configuring TwinView for details. Default: string is -NULL.

-
-
Option "SecondMonitorHorizSync" -"range(s)"
-
-

This option is like the HorizSync entry in the Monitor section, -but is for the second monitor when using TwinView. See Chapter 10, -Configuring TwinView for details. Default: none.

-
-
Option "SecondMonitorVertRefresh" -"range(s)"
-
-

This option is like the VertRefresh entry in the Monitor -section, but is for the second monitor when using TwinView. See -Chapter 10, -Configuring TwinView for details. Default: none.

-
-
Option "MetaModes" -"string"
-
-

This option describes the combination of modes to use on each -monitor when using TwinView. See Chapter 10, -Configuring TwinView for details. Default: string is -NULL.

-
-
Option "NoTwinViewXineramaInfo" -"boolean"
-
-

When in TwinView, the NVIDIA X driver normally provides a -Xinerama extension that X clients (such as window managers) can use -to discover the current TwinView configuration, such as where each -display device is positioned within the X screen. Some window -mangers get confused by this information, so this option is -provided to disable this behavior. Default: false (TwinView -Xinerama information is provided).

-

Due to bugs in some older software, TwinView Xinerama -information is not provided by default on X.Org 7.1 and older when -the X server is started with only one display device connected.

-
-
Option "TwinViewXineramaInfoOrder" -"string"
-
-

When the NVIDIA X driver provides TwinViewXineramaInfo (see the -NoTwinViewXineramaInfo X config option), it by default reports the -currently enabled display devices in the order "CRT, DFP, TV". The -TwinViewXineramaInfoOrder X config option can be used to override -this order.

-

The option string is a comma-separated list of display device -names. The display device names can either be general (e.g, "CRT", -which identifies all CRTs), or specific (e.g., "CRT-1", which -identifies a particular CRT). Not all display devices need to be -identified in the option string; display devices that are not -listed will be implicitly appended to the end of the list, in their -default order.

-

Note that TwinViewXineramaInfoOrder tracks all display devices -that could possibly be connected to the GPU, not just the ones that -are currently enabled. When reporting the Xinerama information, the -NVIDIA X driver walks through the display devices in the order -specified, only reporting enabled display devices.

-

Examples:

-
-        "DFP"
-        "TV, DFP"
-        "DFP-1, DFP-0, TV, CRT"
-
-

In the first example, any enabled DFPs would be reported first -(any enabled CRTs or TVs would be reported afterwards). In the -second example, any enabled TVs would be reported first, then any -enabled DFPs (any enabled CRTs would be reported last). In the last -example, if DFP-1 were enabled, it would be reported first, then -DFP-0, then any enabled TVs, and then any enabled CRTs; finally, -any other enabled DFPs would be reported.

-

Default: "CRT, DFP, TV"

-
-
Option "TwinViewXineramaInfoOverride" -"string"
-
-

This option overrides the values reported by NVIDIA's TwinView -Xinerama implementation. This disregards the actual display devices -used by the X screen and any order specified in -TwinViewXineramaInfoOrder.

-

The option string is interpreted as a comma-separated list of -regions, specified as '[width]x[height]+[x-offset]+[y-offset]'. The -regions' sizes and offsets are not validated against the X screen -size, but are directly reported to any Xinerama client.

-

Examples:

-
-        "1600x1200+0+0, 1600x1200+1600+0"
-        "1024x768+0+0, 1024x768+1024+0, 1024x768+0+768, 1024x768+1024+768"
-
-

-
-
Option "TVStandard" -"string"
-
-

See Chapter 13, -Configuring TV-Out for details on configuring -TV-out.

-
-
Option "TVOutFormat" -"string"
-
-

See Chapter 13, -Configuring TV-Out for details on configuring -TV-out.

-
-
Option "TVOverScan" "Decimal -value in the range 0.0 to 1.0"
-
-

Valid values are in the range 0.0 through 1.0; See Chapter 13, -Configuring TV-Out for details on configuring -TV-out.

-
-
Option "Stereo" -"integer"
-
-

Enable offering of quad-buffered stereo visuals on Quadro. -Integer indicates the type of stereo equipment being used:

-
- --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ValueEquipment
1DDC glasses. The sync signal is sent to the glasses via the DDC -signal to the monitor. These usually involve a passthrough cable -between the monitor and the graphics card. This mode is not -available on G8xGL and higher GPUs.
2"Blueline" glasses. These usually involve a passthrough cable -between the monitor and graphics card. The glasses know which eye -to display based on the length of a blue line visible at the bottom -of the screen. When in this mode, the root window dimensions are -one pixel shorter in the Y dimension than requested. This mode does -not work with virtual root window sizes larger than the visible -root window size (desktop panning). This mode is not available on -G8xGL and higher GPUs.
3Onboard stereo support. This is usually only found on -professional cards. The glasses connect via a DIN connector on the -back of the graphics card.
4TwinView clone mode stereo (also known as "passive" stereo). On -graphics cards that support TwinView, the left eye is displayed on -the first display, and the right eye is displayed on the second -display. This is normally used in conjunction with special -projectors to produce 2 polarized images which are then viewed with -polarized glasses. To use this stereo mode, you must also configure -TwinView in clone mode with the same resolution, panning offset, -and panning domains on each display.
5Vertical interlaced stereo mode, for use with SeeReal Stereo -Digital Flat Panels.
6Color interleaved stereo mode, for use with Sharp3D Stereo -Digital Flat Panels.
-
-

Stereo is only available on Quadro cards. Stereo options 1, 2, -and 3 (also known as "active" stereo) may be used with TwinView if -all modes within each MetaMode have identical timing values. See -Chapter 16, -Programming Modes for suggestions on making sure the -modes within your MetaModes are identical. The identical ModeLine -requirement is not necessary for Stereo option 4 ("passive" -stereo). Default: 0 (Stereo is not enabled).

-

UBB must be enabled when stereo is enabled (this is the default -behavior).

-

Stereo options 1, 2, and 3 ("active" stereo) are not supported -on digital flat panels.

-

Multi-GPU cards (such as the Quadro FX 4500 X2) provide a single -connector for onboard stereo support (option 3), which is tied to -the bottommost GPU. In order to synchronize onboard stereo with the -other GPU, you must use a G-Sync device (see Chapter 21, -Configuring Frame Lock and Genlock for details).

-
-
Option "AllowDFPStereo" -"boolean"
-
-

By default, the NVIDIA X driver performs a check which disables -active stereo (stereo options 1, 2, and 3) if the X screen is -driving a DFP. The "AllowDFPStereo" option bypasses this check.

-
-
Option "ForceStereoFlipping" -"boolean"
-
-

Stereo flipping is the process by which left and right eyes are -displayed on alternating vertical refreshes. Normally, stereo -flipping is only performed when a stereo drawable is visible. This -option forces stereo flipping even when no stereo drawables are -visible.

-

This is to be used in conjunction with the "Stereo" option. If -"Stereo" is 0, the "ForceStereoFlipping" option has no effect. If -otherwise, the "ForceStereoFlipping" option will force the behavior -indicated by the "Stereo" option, even if no stereo drawables are -visible. This option is useful in a multiple-screen environment in -which a stereo application is run on a different screen than the -stereo master.

-

Possible values:

-
- --- - - - - - - - - - - - - - - - - -
ValueBehavior
0Stereo flipping is not forced. The default behavior as -indicated by the "Stereo" option is used.
1Stereo flipping is forced. Stereo is running even if no stereo -drawables are visible. The stereo mode depends on the value of the -"Stereo" option.
-
-

Default: 0 (Stereo flipping is not forced). Note that active -stereo is not supported on digital flat panels.

-
-
Option "XineramaStereoFlipping" -"boolean"
-
-

By default, when using Stereo with Xinerama, all physical X -screens having a visible stereo drawable will stereo flip. Use this -option to allow only one physical X screen to stereo flip at a -time.

-

This is to be used in conjunction with the "Stereo" and -"Xinerama" options. If "Stereo" is 0 or "Xinerama" is 0, the -"XineramaStereoFlipping" option has no effect.

-

If you wish to have all X screens stereo flip all the time, see -the "ForceStereoFlipping" option.

-

Possible values:

-
- --- - - - - - - - - - - - - - - - - -
ValueBehavior
0Stereo flipping is enabled on one X screen at a time. Stereo is -enabled on the first X screen having the stereo drawable.
1Stereo flipping in enabled on all X screens.
-
-

Default: 1 (Stereo flipping is enabled on all X screens).

-
-
Option "NoBandWidthTest" -"boolean"
-
-

As part of mode validation, the X driver tests if a given mode -fits within the hardware's memory bandwidth constraints. This -option disables this test. Default: false (the memory bandwidth -test is performed).

-
-
Option "IgnoreDisplayDevices" -"string"
-
-

This option tells the NVIDIA kernel module to completely ignore -the indicated classes of display devices when checking which -display devices are connected. You may specify a comma-separated -list containing any of "CRT", "DFP", and "TV". For example:

-
-Option "IgnoreDisplayDevices" "DFP, TV"
-
-

will cause the NVIDIA driver to not attempt to detect if any -digital flat panels or TVs are connected. This option is not -normally necessary; however, some video BIOSes contain incorrect -information about which display devices may be connected, or which -i2c port should be used for detection. These errors can cause long -delays in starting X. If you are experiencing such delays, you may -be able to avoid this by telling the NVIDIA driver to ignore -display devices which you know are not connected. NOTE: anything -attached to a 15 pin VGA connector is regarded by the driver as a -CRT. "DFP" should only be used to refer to digital flat panels -connected via a DVI port.

-
-
Option "MultisampleCompatibility" -"boolean"
-
-

Enable or disable the use of separate front and back multisample -buffers. Enabling this will consume more memory but is necessary -for correct output when rendering to both the front and back -buffers of a multisample or FSAA drawable. This option is necessary -for correct operation of SoftImage XSI. Default: false (a single -multisample buffer is shared between the front and back -buffers).

-
-
Option "NoPowerConnectorCheck" -"boolean"
-
-

The NVIDIA X driver will abort X server initialization if it -detects that a GPU that requires an external power connector does -not have an external power connector plugged in. This option can be -used to bypass this test. Default: false (the power connector test -is performed).

-
-
Option "XvmcUsesTextures" -"boolean"
-
-

Forces XvMC to use the 3D engine for XvMCPutSurface requests -rather than the video overlay. Default: false (video overlay is -used when available).

-
-
Option "AllowGLXWithComposite" -"boolean"
-
-

Enables GLX even when the Composite X extension is loaded. -ENABLE AT YOUR OWN RISK. OpenGL applications will not display -correctly in many circumstances with this setting enabled.

-

This option is intended for use on X.Org X servers older than -X11R6.9.0. On X11R6.9.0 or newer X servers, the NVIDIA OpenGL -implementation interacts properly by default with the Composite X -extension and this option should not be needed. However, on -X11R6.9.0 or newer X servers, support for GLX with Composite can be -disabled by setting this option to False.

-

Default: false (GLX is disabled when Composite is enabled on X -servers older than X11R6.9.0).

-
-
Option "UseCompositeWrapper" -"boolean"
-
-

Enables the X server's "composite wrapper", which performs -coordinate translations necessary for the Composite extension.

-

Default: false (the NVIDIA X driver performs its own coordinate -translation).

-
-
Option "AddARGBGLXVisuals" -"boolean"
-
-

Adds a 32-bit ARGB visual for each supported OpenGL -configuration. This allows applications to use OpenGL to render -with alpha transparency into 32-bit windows and pixmaps. This -option requires the Composite extension. Default: ARGB GLX visuals -are enabled on X servers new enough to support them when the -Composite extension is also enabled.

-
-
Option "DisableGLXRootClipping" -"boolean"
-
-

If enabled, no clipping will be performed on rendering done by -OpenGL in the root window. This option is deprecated. It is needed -by older versions of OpenGL-based composite managers that draw the -contents of redirected windows directly into the root window using -OpenGL. Most OpenGL-based composite managers have been updated to -support the Composite Overlay Window, a feature introduced in Xorg -release 7.1. Using the Composite Overlay Window is the preferred -method for performing OpenGL-based compositing.

-
-
Option "DamageEvents" -"boolean"
-
-

Use OS-level events to efficiently notify X when a client has -performed direct rendering to a window that needs to be composited. -This will significantly improve performance and interactivity when -using GLX applications with a composite manager running. It will -also affect applications using GLX when rotation is enabled. This -option is currently incompatible with SLI and Multi-GPU modes and -will be disabled if either are used. Enabled by default.

-
-
Option "ExactModeTimingsDVI" -"boolean"
-
-

Forces the initialization of the X server with the exact timings -specified in the ModeLine. Default: false (for DVI devices, the X -server initializes with the closest mode in the EDID list).

-
-
Option "Coolbits" -"integer"
-
-

Enables various unsupported features, such as support for GPU -clock manipulation in the NV-CONTROL X extension. This option -accepts a bit mask of features to enable.

-

When "1" (Bit 0) is set in the "Coolbits" option value, the -nvidia-settings utility will contain a page labeled "Clock -Frequencies" through which clock settings can be manipulated. -"Coolbits" is only available on GeForce FX, Quadro FX and newer -desktop GPUs. On GeForce FX and newer mobile GPUs, limited clock -manipulation support is available when "1" is set in the "Coolbits" -option value: clocks can be lowered relative to the default -settings; overclocking is not supported due to the thermal -constraints of notebook designs.

-

WARNING: this may cause system damage and void warranties. This -utility can run your computer system out of the manufacturer's -design specifications, including, but not limited to: higher system -voltages, above normal temperatures, excessive frequencies, and -changes to BIOS that may corrupt the BIOS. Your computer's -operating system may hang and result in data loss or corrupted -images. Depending on the manufacturer of your computer system, the -computer system, hardware and software warranties may be voided, -and you may not receive any further manufacturer support. NVIDIA -does not provide customer service support for the Coolbits option. -It is for these reasons that absolutely no warranty or guarantee is -either express or implied. Before enabling and using, you should -determine the suitability of the utility for your intended use, and -you shall assume all responsibility in connection therewith.

-

When "2" (Bit 1) is set in the "Coolbits" option value, the -NVIDIA driver will attempt to initialize SLI when using GPUs with -different amounts of video memory.

-

The default for this option is 0 (unsupported features are -disabled).

-
-
Option "MultiGPU" -"string"
-
-

This option controls the configuration of Multi-GPU rendering in -supported configurations.

-
- --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ValueBehavior
0, no, off, false, SingleUse only a single GPU when rendering
1, yes, on, true, AutoEnable Multi-GPU and allow the driver to automatically select -the appropriate rendering mode.
AFREnable Multi-GPU and use the Alternate Frame Rendering -mode.
SFREnable Multi-GPU and use the Split Frame Rendering mode.
AAEnable Multi-GPU and use antialiasing. Use this in conjunction -with full scene antialiasing to improve visual quality.
-
-

-
-
Option "SLI" "string"
-
-

This option controls the configuration of SLI rendering in -supported configurations.

-
- --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ValueBehavior
0, no, off, false, SingleUse only a single GPU when rendering
1, yes, on, true, AutoEnable SLI and allow the driver to automatically select the -appropriate rendering mode.
AFREnable SLI and use the Alternate Frame Rendering mode.
SFREnable SLI and use the Split Frame Rendering mode.
AAEnable SLI and use SLI Antialiasing. Use this in conjunction -with full scene antialiasing to improve visual quality.
AFRofAAEnable SLI and use SLI Alternate Frame Rendering of -Antialiasing mode. Use this in conjunction with full scene -antialiasing to improve visual quality. This option is only valid -for SLI configurations with 4 GPUs.
-
-

-
-
Option "TripleBuffer" -"boolean"
-
-

Enable or disable the use of triple buffering. If this option is -enabled, OpenGL windows that sync to vblank and are double-buffered -will be given a third buffer. This decreases the time an -application stalls while waiting for vblank events, but increases -latency slightly (delay between user input and displayed -result).

-
-
Option "DPI" "string"
-
-

This option specifies the Dots Per Inch for the X screen; for -example:

-
-    Option "DPI" "75 x 85"
-
-

will set the horizontal DPI to 75 and the vertical DPI to 85. By -default, the X driver will compute the DPI of the X screen from the -EDID of any connected display devices. See Appendix I, Dots Per -Inch for details. Default: string is NULL (disabled).

-
-
Option "UseEdidDpi" -"string"
-
-

By default, the NVIDIA X driver computes the DPI of an X screen -based on the physical size of the display device, as reported in -the EDID, and the size in pixels of the first mode to be used on -the display device. If multiple display devices are used by the X -screen, then the NVIDIA X screen will choose which display device -to use. This option can be used to specify which display device to -use. The string argument can be a display device name, such as:

-
-    Option "UseEdidDpi" "DFP-0"
-
-

or the argument can be "FALSE" to disable use of EDID-based DPI -calculations:

-
-    Option "UseEdidDpi" "FALSE"
-
-

See Appendix I, Dots Per -Inch for details. Default: string is NULL (the driver -computes the DPI from the EDID of a display device and selects the -display device).

-
-
Option "ConstantDPI" -"boolean"
-
-

By default on X.Org 6.9 or newer X servers, the NVIDIA X driver -recomputes the size in millimeters of the X screen whenever the -size in pixels of the X screen is changed using XRandR, such that -the DPI remains constant.

-

This behavior can be disabled (which means that the size in -millimeters will not change when the size in pixels of the X screen -changes) by setting the "ConstantDPI" option to "FALSE"; e.g.,

-
-    Option "ConstantDPI" "FALSE"
-
-

ConstantDPI defaults to True.

-

On X servers older than X.Org 6.9, the NVIDIA X driver cannot -change the size in millimeters of the X screen. Therefore the DPI -of the X screen will change when XRandR changes the size in pixels -of the X screen. The driver will behave as if ConstantDPI was -forced to FALSE.

-
-
Option "CustomEDID" -"string"
-
-

This option forces the X driver to use the EDID specified in a -file rather than the display's EDID. You may specify a semicolon -separated list of display names and filename pairs. The display -name is any of "CRT-0", "CRT-1", "DFP-0", "DFP-1", "TV-0", "TV-1", -or one of the generic names "CRT", "DFP", "TV", which apply the -EDID to all devices of the specified type. The file contains a raw -EDID (e.g., a file generated by nvidia-settings).

-

For example:

-
-    Option "CustomEDID" "CRT-0:/tmp/edid1.bin; DFP-0:/tmp/edid2.bin"
-
-

will assign the EDID from the file /tmp/edid1.bin to the display -device CRT-0, and the EDID from the file /tmp/edid2.bin to the -display device DFP-0. Note that a display device name must always -be specified even if only one EDID is specified.

-

Caution: Specifying an EDID that doesn't exactly match your -display may damage your hardware, as it allows the driver to -specify timings beyond the capabilities of your display. Use with -care.

-
-
Option "ModeValidation" -"string"
-
-

This option provides fine-grained control over each stage of the -mode validation pipeline, disabling individual mode validation -checks. This option should only very rarely be used.

-

The option string is a semicolon-separated list of -comma-separated lists of mode validation arguments. Each list of -mode validation arguments can optionally be prepended with a -display device name.

-
-    "<dpy-0>: <tok>, <tok>; <dpy-1>: <tok>, <tok>, <tok>; ..."
-
-

-

Possible arguments:

-
-
    -
  • -

    "AllowNon60HzDFPModes": some lower quality TMDS encoders are -only rated to drive DFPs at 60Hz; the driver will determine when -only 60Hz DFP modes are allowed. This argument disables this stage -of the mode validation pipeline.

    -
    • -
  • -

    "NoMaxPClkCheck": each mode has a pixel clock; this pixel clock -is validated against the maximum pixel clock of the hardware (for a -DFP, this is the maximum pixel clock of the TMDS encoder, for a -CRT, this is the maximum pixel clock of the DAC). This argument -disables the maximum pixel clock checking stage of the mode -validation pipeline.

    -
    • -
  • -

    "NoEdidMaxPClkCheck": a display device's EDID can specify the -maximum pixel clock that the display device supports; a mode's -pixel clock is validated against this pixel clock maximum. This -argument disables this stage of the mode validation pipeline.

    -
    • -
  • -

    "AllowInterlacedModes": interlaced modes are not supported on -all NVIDIA GPUs; the driver will discard interlaced modes on GPUs -where interlaced modes are not supported; this argument disables -this stage of the mode validation pipeline.

    -
    • -
  • -

    "NoMaxSizeCheck": each NVIDIA GPU has a maximum resolution that -it can drive; this argument disables this stage of the mode -validation pipeline.

    -
    • -
  • -

    "NoHorizSyncCheck": a mode's horizontal sync is validated -against the range of valid horizontal sync values; this argument -disables this stage of the mode validation pipeline.

    -
    • -
  • -

    "NoVertRefreshCheck": a mode's vertical refresh rate is -validated against the range of valid vertical refresh rate values; -this argument disables this stage of the mode validation -pipeline.

    -
    • -
  • -

    "NoWidthAlignmentCheck": the alignment of a mode's visible width -is validated against the capabilities of the GPU; normally, a -mode's visible width must be a multiple of 8. This argument -disables this stage of the mode validation pipeline.

    -
    • -
  • -

    "NoDFPNativeResolutionCheck": when validating for a DFP, a -mode's size is validated against the native resolution of the DFP; -this argument disables this stage of the mode validation -pipeline.

    -
    • -
  • -

    "NoVirtualSizeCheck": if the X configuration file requests a -specific virtual screen size, a mode cannot be larger than that -virtual size; this argument disables this stage of the mode -validation pipeline.

    -
    • -
  • -

    "NoVesaModes": when constructing the mode pool for a display -device, the X driver uses a built-in list of VESA modes as one of -the mode sources; this argument disables use of these built-in VESA -modes.

    -
    • -
  • -

    "NoEdidModes": when constructing the mode pool for a display -device, the X driver uses any modes listed in the display device's -EDID as one of the mode sources; this argument disables use of -EDID-specified modes.

    -
    • -
  • -

    "NoXServerModes": when constructing the mode pool for a display -device, the X driver uses the built-in modes provided by the core -XFree86/Xorg X server as one of the mode sources; this argument -disables use of these modes. Note that this argument does not -disable custom ModeLines specified in the X config file; see the -"NoCustomModes" argument for that.

    -
    • -
  • -

    "NoCustomModes": when constructing the mode pool for a display -device, the X driver uses custom ModeLines specified in the X -config file (through the "Mode" or "ModeLine" entries in the -Monitor Section) as one of the mode sources; this argument disables -use of these modes.

    -
    • -
  • -

    "NoPredefinedModes": when constructing the mode pool for a -display device, the X driver uses additional modes predefined by -the NVIDIA X driver; this argument disables use of these modes.

    -
    • -
  • -

    "NoUserModes": additional modes can be added to the mode pool -dynamically, using the NV-CONTROL X extension; this argument -prohibits user-specified modes via the NV-CONTROL X extension.

    -
    • -
  • -

    "NoExtendedGpuCapabilitiesCheck": allow mode timings that may -exceed the GPU's extended capability checks.

    -
    • -
  • -

    "ObeyEdidContradictions": an EDID may contradict itself by -listing a mode as supported, but the mode may exceed an -EDID-specified valid frequency range (HorizSync, VertRefresh, or -maximum pixel clock). Normally, the NVIDIA X driver prints a -warning in this scenario, but does not invalidate an EDID-specified -mode just because it exceeds an EDID-specified valid frequency -range. However, the "ObeyEdidContradictions" argument instructs the -NVIDIA X driver to invalidate these modes.

    -
    • -
  • -

    "NoTotalSizeCheck": allow modes in which the individual visible -or sync pulse timings exceed the total raster size.

    -
    • -
  • -

    "DoubleScanPriority": on GPUs older than G80, doublescan modes -are sorted before non-doublescan modes of the same resolution for -purposes of mode pool sorting; but on G80 and later GPUs, -doublescan modes are sorted after non-doublescan modes of the same -resolution. This token inverts that priority (i.e., doublescan -modes will be sorted after on pre-G80 GPUs, and sorted before on -G80 and later GPUs).

    -
    • -
  • -

    "NoDualLinkDVICheck": for mode timings used on dual link DVI -DFPs, the driver must perform additional checks to ensure that the -correct pixels are sent on the correct link. For some of these -checks, the driver will invalidate the mode timings; for other -checks, the driver will implicitly modify the mode timings to meet -the GPU's dual link DVI requirements. This token disables this dual -link DVI checking.

    -
    • -
-
-

-

Examples:

-
-    Option "ModeValidation" "NoMaxPClkCheck"
-
-

disable the maximum pixel clock check when validating modes on -all display devices.

-
-    Option "ModeValidation" "CRT-0: NoEdidModes, NoMaxPClkCheck; DFP-0: NoVesaModes"
-
-

do not use EDID modes and do not perform the maximum pixel clock -check on CRT-0, and do not use VESA modes on DFP-0.

-
-
Option "ModeDebug" -"boolean"
-
-

This option causes the X driver to print verbose details about -mode validation to the X log file. Note that this option is applied -globally: setting this option to TRUE will enable verbose mode -validation logging for all NVIDIA X screens in the X server.

-
-
Option "UseEvents" -"boolean"
-
-

Enables the use of system events in some cases when the X driver -is waiting for the hardware. The X driver can briefly spin through -a tight loop when waiting for the hardware. With this option the X -driver instead sets an event handler and waits for the hardware -through the poll() -system call. Default: the use of the events is disabled.

-
-
Option "FlatPanelProperties" -"string"
-
-

This option requests particular properties for all or a subset -of the connected flat panels.

-

The option string is a semicolon-separated list of -comma-separated property=value pairs. Each list of property=value -pairs can optionally be prepended with a flat panel name.

-
-    "<DFP-0>: <property=value>, <property=value>; <DFP-1>: <property=value>; ..."
-
-

-

Recognized properties:

-
-
    -
  • -

    "Scaling": controls the flat panel scaling mode; possible values -are: 'Default' (the driver will use whichever scaling state is -current), 'Native' (the driver will use the flat panel's scaler, if -possible), 'Scaled' (the driver will use the NVIDIA GPU's scaler, -if possible), 'Centered' (the driver will center the image, if -possible), and 'aspect-scaled' (the X driver will scale with the -NVIDIA GPU's scaler, but keep the aspect ratio correct).

    -
    • -
  • -

    "Dithering": controls the flat panel dithering mode; possible -values are: 'Default' (the driver will decide when to dither), -'Enabled' (the driver will always dither, if possible), and -'Disabled' (the driver will never dither).

    -
    • -
-
-

-

Examples:

-
-    Option "FlatPanelProperties" "Scaling = Centered"
-
-

set the flat panel scaling mode to centered on all flat -panels.

-
-    Option "FlatPanelProperties" "DFP-0: Scaling = Centered; DFP-1: Scaling = Scaled, Dithering = Enabled"
-
-

set DFP-0's scaling mode to centered, set DFP-1's scaling mode -to scaled and its dithering mode to enabled.

-
-
Option "ProbeAllGpus" -"boolean"
-
-

When the NVIDIA X driver initializes, it probes all GPUs in the -system, even if no X screens are configured on them. This is done -so that the X driver can report information about all the system's -GPUs through the NV-CONTROL X extension. This option can be set to -FALSE to disable this behavior, such that only GPUs with X screens -configured on them will be probed. Default: all GPUs in the system -are probed.

-
-
Option "DynamicTwinView" -"boolean"
-
-

Enable or disable support for dynamically configuring TwinView -on this X screen. When DynamicTwinView is enabled (the default), -the refresh rate of a mode (reported through XF86VidMode or XRandR) -does not correctly report the refresh rate, but instead is a unique -number such that each MetaMode has a different value. This is to -guarantee that MetaModes can be uniquely identified by XRandR.

-

When DynamicTwinView is disabled, the refresh rate reported -through XRandR will be accurate, but NV-CONTROL clients such as -nvidia-settings will not be able to dynamically manipulate the X -screen's MetaModes. TwinView can still be configured from the X -config file when DynamicTwinView is disabled.

-

Default: DynamicTwinView is enabled.

-
-
Option "IncludeImplicitMetaModes" -"boolean"
-
-

When the X server starts, a mode pool is created per display -device, containing all the mode timings that the NVIDIA X driver -determined to be valid for the display device. However, the only -MetaModes that are made available to the X server are the ones -explicitly requested in the X configuration file.

-

It is convenient for fullscreen applications to be able to -change between the modes in the mode pool, even if a given target -mode was not explicitly requested in the X configuration file.

-

To facilitate this, the NVIDIA X driver will, if only one -display device is in use when the X server starts, implicitly add -MetaModes for all modes in the display device's mode pool. This -makes all the modes in the mode pool available to full screen -applications that use the XF86VidMode or XRandR X extensions.

-

To prevent this behavior, and only add MetaModes that are -explicitly requested in the X configuration file, set this option -to FALSE.

-

Default: IncludeImplicitMetaModes is enabled.

-
-
Option "AllowIndirectPixmaps" -"boolean"
-
-

Some graphics cards have more video memory than can be mapped at -once by the CPU (generally only 256 MB of video memory can be -CPU-mapped). On graphics cards based on G80 and higher with such a -memory configuration, this option allows the driver to place more -pixmaps in video memory which will improve hardware rendering -performance but will slow down software rendering. On some systems, -up to 768 megabytes of virtual address space will be reserved in -the X server for indirect pixmap access. This virtual memory does -not consume any physical resources.

-

Default: on (indirect pixmaps will be used, when available).

-
-
Option "OnDemandVBlankInterrupts" -"boolean"
-
-

Normally, VBlank interrupts are generated on every vertical -refresh of every display device connected to the GPU(s) installed -in a given system. This experimental option enables on-demand -VBlank control, allowing the driver to enable VBlank interrupt -generation only when it is required. This can help conserve -power.

-

Default: off (on-demand VBlank control is disabled).

-
-
Option "PixmapCacheSize" -"size"
-
-

This option controls how much video memory is reserved for -pixmap allocations. When the option is specified, size specifies the number of bytes to use -for the pixmap cache. Reserving this memory improves performance -when pixmaps are created and destroyed rapidly, but prevents this -memory from being used by OpenGL. When this cache is disabled or -space in the cache is exhausted, the driver will still allocate -pixmaps in video memory but pixmap creation and deletion -performance will not be improved.

-

NOTE: This option is deprecated in favor of the -PixmapCacheRoundSizeKB nvidia-settings attribute and will be -removed in a future driver release.

-

Example: Option "PixmapCacheSize" -"1048576" will allocate one megabyte for the pixmap -cache.

-

Default: off (no memory is reserved specifically for -pixmaps).

-
-
Option "AllowSHMPixmaps" -"boolean"
-
-

This option controls whether applications can use the MIT-SHM X -extension to create pixmaps whose contents are shared between the X -server and the client. These pixmaps prevent the NVIDIA driver from -performing a number of optimizations and degrade performance in -many circumstances.

-

Disabling this option disables only shared memory pixmaps. -Applications can still use the MIT-SHM extension to transfer data -to the X server through shared memory using XShmPutImage.

-

Default: off (shared memory pixmaps are not allowed).

-
-
Option -"InitializeWindowBackingPixmaps" "boolean"
-
-

This option controls whether the NVIDIA X Driver initializes -newly created redirected windows using the contents of their parent -window if the X server doesn't do it. Leaving redirected windows -uninitialized may cause new windows to flash with black or random -colors when some compositing managers are running.

-

This option will have no effect on X servers that already -initialize redirected window contents. In most distributions, the X -server is patched to skip that initialization. In this case, it is -recommended to leave this option on for a better user -experience.

-

Default: on (redirected windows are initialized).

-
-
-
-

+

This release includes support for the XVideo Motion Compensation +(XvMC) version 1.0 API on GeForce 6 series and GeForce 7 series +add-in cards, as well as motherboard chipsets with integrated +graphics that have PureVideo support based on these GPUs. There is +a static library, "libXvMCNVIDIA.a", and a dynamic one, +"libXvMCNVIDIA_dynamic.so", which is suitable for dlopening. XvMC's +"IDCT" and "motion-compensation" levels of acceleration, AI44 and +IA44 subpictures, and 4:2:0 Surfaces up to 2032x2032 are +supported.

+

libXvMCNVIDIA observes the XVMC_DEBUG environment variable and +will provide some debug output to stderr when set to an appropriate +integer value. '0' disables debug output. '1' enables debug output +for failure conditions. '2' or higher enables output of warning +messages.

@@ -1587,11 +69,11 @@ experience.

-Appendix E. Supported NVIDIA GPU Products  Home - Appendix G. Display Device Names
diff --git a/doc/html/appendix-k-section-02.html b/doc/html/appendix-g-section-02.html similarity index 58% rename from doc/html/appendix-k-section-02.html rename to doc/html/appendix-g-section-02.html index ef36c05..f2ce41d 100644 --- a/doc/html/appendix-k-section-02.html +++ b/doc/html/appendix-g-section-02.html @@ -9,11 +9,11 @@ - - - + + @@ -24,11 +24,11 @@ Prev  -Appendix K. VDPAU +"appendix-g.html">Prev  +Appendix G. VDPAU Support  Next +"appendix-g-section-03.html">Next
@@ -36,32 +36,33 @@ Support
-

Performance Levels

+

Performance Levels

-

This documentation describes the capabilities of the NVIDA VDPAU -implementation. Hardware performance may vary significantly between -cards. No guarantees are made, nor implied, that any particular -combination of system configuration, GPU configuration, VDPAU -feature set, VDPAU API usage, application, video stream, etc., will -be able to decode streams at any particular frame rate.

+

This documentation describes the capabilities of the NVIDIA +VDPAU implementation. Hardware performance may vary significantly +between cards. No guarantees are made, nor implied, that any +particular combination of system configuration, GPU configuration, +VDPAU feature set, VDPAU API usage, application, video stream, +etc., will be able to decode streams at any particular frame +rate.

+"appendix-g.html">Prev  +"appendix-g.html">Up +"appendix-g-section-03.html">Next +Appendix G. VDPAU Support  - +"appendix-g-section-04.html">Next
Prev  Up  Next
-Appendix K. VDPAU Support  Home  Getting the Best diff --git a/doc/html/appendix-k-section-03.html b/doc/html/appendix-g-section-03.html similarity index 70% rename from doc/html/appendix-k-section-03.html rename to doc/html/appendix-g-section-03.html index af18259..a37cb28 100644 --- a/doc/html/appendix-k-section-03.html +++ b/doc/html/appendix-g-section-03.html @@ -9,11 +9,11 @@ - - + - @@ -25,11 +25,11 @@ the API
Prev Appendix K. VDPAU +"appendix-g-section-02.html">Prev  +Appendix G. VDPAU Support  Next
@@ -37,8 +37,8 @@ Support
-

Getting the Best Performance from the API

+

Getting the Best Performance from the API

@@ -66,38 +66,44 @@ for post-processing, and eventual display, this will "lock" the surfaces for even longer, since the video mixer needs to read the data from the surface, which prevents any subsequent decode operations from writing to the surface. Recall that when advanced -deinterlacing techniques are used, a history of video surfaces must -be provided to the video mixer, thus necessitating that even more -video surfaces be allocated.

+de-interlacing techniques are used, a history of video surfaces +must be provided to the video mixer, thus necessitating that even +more video surfaces be allocated.

For this reason, NVIDIA recommends the following number of video surfaces be allocated:

  • -

    (num_ref + 3) for progressive content, and no deinterlacing.

    +

    (num_ref + 3) for progressive content, and no +de-interlacing.

  • (num_ref + 5) for interlaced content using advanced -deinterlacing.

    +de-interlacing.

-

For applications that perform significant amounts of rendering -between bitmaps and output surfaces, a similar argument may apply -to the number of output surfaces allocated.

-

Finally, consider the display path via the presentation queue. -This portion of the pipeline requires at least 2 output surfaces; -one that is being actively displayed by the presentation queue, and -one being rendered to for subsequent display. As before, using this +

Next, consider the display path via the presentation queue. This +portion of the pipeline requires at least 2 output surfaces; one +that is being actively displayed by the presentation queue, and one +being rendered to for subsequent display. As before, using this minimum number of surfaces may not be optimal. For some video streams, the hardware may only achieve real-time decoding on -average, not for each individual frame. Similarly, system level -issues such as scheduler algorithms and system load may prevent the -CPU portion of the driver from operating for short periods of time. -Both of these potential issues may be solved by allocating more -output surfaces, and queuing more than one outstanding output -surface into the presentation queue.

+average, not for each individual frame. Using compositing APIs to +render OSD, GUIs, etc., may introduce extra jitter and latency into +the pipeline. Similarly, system level issues such as scheduler +algorithms and system load may prevent the CPU portion of the +driver from operating for short periods of time. All of these +potential issues may be solved by allocating more output surfaces, +and queuing more than one outstanding output surface into the +presentation queue.

+

The reason for using more than the minimum number of video +surfaces is to ensure that the decoding and post-processing +pipeline is not stalled, and hence is kept busy for the maximum +amount of time possible. In contrast, the reason for using more +than the minimum number of output surfaces is to hide jitter and +latency in various GPU and CPU operations.

The choice of exactly how many surfaces to allocate is a resource usage v.s. performance trade-off; Allocating more than the minimum number of surfaces will increase performance, but use @@ -127,11 +133,11 @@ performance.

+"appendix-g-section-02.html">Prev  +"appendix-g.html">Up +"appendix-g-section-04.html">Next - +"appendix-g-section-05.html">Next
Prev  Up  Next
Performance diff --git a/doc/html/appendix-k-section-04.html b/doc/html/appendix-g-section-04.html similarity index 74% rename from doc/html/appendix-k-section-04.html rename to doc/html/appendix-g-section-04.html index 272f347..2b83073 100644 --- a/doc/html/appendix-k-section-04.html +++ b/doc/html/appendix-g-section-04.html @@ -9,11 +9,11 @@ - - + - @@ -24,11 +24,11 @@
Prev Appendix K. VDPAU +"appendix-g-section-03.html">Prev  +Appendix G. VDPAU Support  Next
@@ -36,8 +36,8 @@ Support
-

Additional Notes

+

Additional Notes

@@ -51,11 +51,11 @@ input to any function.

+"appendix-g-section-03.html">Prev  +"appendix-g.html">Up +"appendix-g-section-05.html">Next - +"appendix-h.html">Next
Prev  Up  Next
Getting the Best diff --git a/doc/html/appendix-k-section-05.html b/doc/html/appendix-g-section-05.html similarity index 81% rename from doc/html/appendix-k-section-05.html rename to doc/html/appendix-g-section-05.html index 15b11c4..8e057f2 100644 --- a/doc/html/appendix-k-section-05.html +++ b/doc/html/appendix-g-section-05.html @@ -9,12 +9,12 @@ - - + - +
@@ -24,11 +24,11 @@
Prev Appendix K. VDPAU +"appendix-g-section-04.html">Prev  +Appendix G. VDPAU Support  Next
@@ -36,8 +36,8 @@ Support
-

Debugging and Tracing

+

Debugging and Tracing

@@ -80,11 +80,11 @@ information, which may be needed to diagnose some problems.

+"appendix-g-section-04.html">Prev  +"appendix-g.html">Up +"appendix-h.html">Next + Appendix H. Tips for New FreeBSD Users
Prev  Up  Next
Additional @@ -92,7 +92,7 @@ Notes  Home - Appendix L. Tips for New FreeBSD Users
diff --git a/doc/html/appendix-g.html b/doc/html/appendix-g.html index 198bf6f..bbff1e0 100644 --- a/doc/html/appendix-g.html +++ b/doc/html/appendix-g.html @@ -5,30 +5,30 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Appendix G. Display Device Names +Appendix G. VDPAU Support - +"Appendix F. XvMC Support"> +
- + +"appendix-g-section-02.html">Next
Appendix G. Display Device -NamesAppendix G. VDPAU +Support
Prev  Part II. Appendices  Next
@@ -36,56 +36,494 @@ Names
-

Appendix G. Display Device -Names

-
-
-
-

A "display device" refers to some piece of hardware capable of -displaying an image. There are three categories of display devices: -analog displays (i.e., CRTs), digital displays (i.e., digital flat -panels (DFPs)), and televisions. Note that analog flat panels are -considered the same as analog CRTs by the NVIDIA FreeBSD -driver.

-

A "display device name" is a string description that uniquely -identifies a display device; it follows the format -"<type>-<number>", for example: "CRT-0", "CRT-1", -"DFP-0", or "TV-0". Note that the number indicates how the display -device connector is wired on the graphics card, and has nothing to -do with how many of that kind of display device are present. This -means, for example, that you may have a "CRT-1", even if you do not -have a "CRT-0". To determine which display devices are currently -connected, you may check your X log file for a line similar to the -following:

-
-    (II) NVIDIA(0): Connected display device(s): CRT-0, DFP-0
-
-

Display device names can be used in the MetaMode, HorizSync, and -VertRefresh X config options to indicate which display device a -setting should be applied to. For example:

-
-    Option "MetaModes"   "CRT-0: 1600x1200,  DFP-0: 1024x768"
-    Option "HorizSync"   "CRT-0: 50-110;     DFP-0: 40-70"
-    Option "VertRefresh" "CRT-0: 60-120;     DFP-0: 60"
-
-

Specifying the display device name in these options is not -required; if display device names are not specified, then the -driver attempts to infer which display device a setting applies to. -In the case of MetaModes, for example, the first mode listed is -applied to the "first" display device, and the second mode listed -is applied to the "second" display device. Unfortunately, it is -often unclear which display device is the "first" or "second". That -is why specifying the display device name is preferable.

-

When specifying display device names, you may also omit the -number part of the name, though this is only useful if you only -have one of that type of display device. For example, if you have -one CRT and one DFP connected, you may reference them in the -MetaMode string as follows:

-
-    Option "MetaModes"   "CRT: 1600x1200,  DFP: 1024x768"
-
+

Appendix G. VDPAU Support

+ + + +
+

Table of Contents

+
+
Implementation Limits
+
+
+
VdpVideoSurface
+
VdpBitmapSurface
+
VdpOutputSurface
+
VdpDecoder
+
VdpVideoMixer
+
VdpPresentationQueue
+
+
+
Performance Levels
+
Getting the Best Performance from the +API
+
Additional Notes
+
Debugging and Tracing
+
+
+

This release includes support for the Video Decode and +Presentation API for Unix-like systems (VDPAU) on most GeForce 8 +series and newer add-in cards, as well as motherboard chipsets with +integrated graphics that have PureVideo support based on these +GPUs.

+
+
+
+
+

Implementation Limits

+
+
+
+

VDPAU is specified as a generic API - the choice of which +features to support, and performance levels of those features, is +left up to individual implementations. The details of NVIDIA's +implementation are provided below.

+
+
+
+
+

VdpVideoSurface

+
+
+
+

The maximum supported resolution is 4096x4096.

+

The following surface formats and get-/put-bits combinations are +supported:

+
+
    +
  • +

    VDP_CHROMA_TYPE_420 (Supported get-/put-bits formats are +VDP_YCBCR_FORMAT_NV12, VDP_YCBCR_FORMAT_YV12)

    +
    • +
  • +

    VDP_CHROMA_TYPE_422 (Supported get-/put-bits formats are +VDP_YCBCR_FORMAT_UYVY, VDP_YCBCR_FORMAT_YUYV)

    +
    • +
+
+

+
+
+
+
+
+

VdpBitmapSurface

+
+
+
+

The maximum supported resolution is 8192x8192.

+

The following surface formats are supported:

+
+
    +
  • +

    VDP_RGBA_FORMAT_B8G8R8A8

    +
    • +
  • +

    VDP_RGBA_FORMAT_R8G8B8A8

    +
    • +
  • +

    VDP_RGBA_FORMAT_B10G10R10A2

    +
    • +
  • +

    VDP_RGBA_FORMAT_R10G10B10A2

    +
    • +
  • +

    VDP_RGBA_FORMAT_A8

    +
    • +
+
+

+

Note that VdpBitmapSurfaceCreate's frequently_accessed parameter +directly controls whether the bitmap data will be placed into video +RAM (VDP_TRUE) or system memory (VDP_FALSE). Note that if the +bitmap data cannot be placed into video RAM when requested due to +resource constraints, the implementation will automatically fall +back to placing the data into system RAM.

+
+
+
+
+
+

VdpOutputSurface

+
+
+
+

The maximum supported resolution is 8192x8192.

+

The following surface formats are supported:

+
+
    +
  • +

    VDP_RGBA_FORMAT_B8G8R8A8

    +
    • +
  • +

    VDP_RGBA_FORMAT_R10G10B10A2

    +
    • +
+
+

+

For all surface formats, the following get-/put-bits indexed +formats are supported:

+
+
    +
  • +

    VDP_INDEXED_FORMAT_A4I4

    +
    • +
  • +

    VDP_INDEXED_FORMAT_I4A4

    +
    • +
  • +

    VDP_INDEXED_FORMAT_A8I8

    +
    • +
  • +

    VDP_INDEXED_FORMAT_I8A8

    +
    • +
+
+

+

For all surface formats, the following get-/put-bits YCbCr +formats are supported:

+
+
    +
  • +

    VDP_YCBCR_FORMAT_Y8U8V8A8

    +
    • +
  • +

    VDP_YCBCR_FORMAT_V8U8Y8A8

    +
    • +
+
+

+
+
+
+
+
+

VdpDecoder

+
+
+
+

In all cases, VdpDecoder objects solely support 8-bit 4:2:0 +streams, and only support writing to VDP_CHROMA_TYPE_420 +surfaces.

+

The exact set of supported VdpDecoderProfile values depends on +the hardware model in use. Hardware-specific support is listed +below. When reading these lists, please note that VC1_SIMPLE and +VC1_MAIN may be referred to as WMV, WMV3, or WMV9 in other +contexts. Partial acceleration means that VLD (bitstream) decoding +is performed on the CPU, with the GPU performing IDCT and motion +compensation. Complete acceleration means that the GPU performs all +of VLD, IDCT, and motion compensation.

+
+
+
+
+

G84, G86, +G92, G94, G96, GT200

+
+
+
+

These chips support the following VdpDecoderProfile values:

+
+
    +
  • +

    VDP_DECODER_PROFILE_MPEG1, VDP_DECODER_PROFILE_MPEG2_SIMPLE, +VDP_DECODER_PROFILE_MPEG2_MAIN:

    +
    +
      +
    • +

      Partial acceleration.

      +
      • +
    • +

      Minimum width or height: 3 macroblocks (48 pixels).

      +
      • +
    • +

      Maximum width or height: 128 macroblocks (2048 pixels).

      +
      • +
    • +

      Maximum macroblocks: 8192

      +
      • +
    +
    +

    +
    • +
  • +

    VDP_DECODER_PROFILE_H264_MAIN, +VDP_DECODER_PROFILE_H264_HIGH:

    +
    +
      +
    • +

      Complete acceleration.

      +
      • +
    • +

      Minimum width or height: 3 macroblocks (48 pixels).

      +
      • +
    • +

      Maximum width or height: 128 macroblocks (2048 pixels).

      +
      • +
    • +

      Maximum macroblocks: 8192

      +
      • +
    +
    +

    +
    • +
  • +

    VDP_DECODER_PROFILE_VC1_SIMPLE, VDP_DECODER_PROFILE_VC1_MAIN, +VDP_DECODER_PROFILE_VC1_ADVANCED:

    +
    +
      +
    • +

      Partial acceleration.

      +
      • +
    • +

      Minimum width or height: 3 macroblocks (48 pixels).

      +
      • +
    • +

      Maximum width or height: 128 macroblocks (2048 pixels).

      +
      • +
    • +

      Maximum macroblocks: 8190

      +
      • +
    +
    +

    +
    • +
+
+

+
+
+
+
+
+

G98, +MCP77, MCP78, MCP79, MCP7A

+
+
+
+

These chips support the following VdpDecoderProfile values:

+
+
    +
  • +

    VDP_DECODER_PROFILE_MPEG1, VDP_DECODER_PROFILE_MPEG2_SIMPLE, +VDP_DECODER_PROFILE_MPEG2_MAIN:

    +
    +
      +
    • +

      Complete acceleration.

      +
      • +
    • +

      Minimum width or height: 3 macroblocks (48 pixels).

      +
      • +
    • +

      Maximum width or height: 128 macroblocks (2048 pixels).

      +
      • +
    • +

      Maximum macroblocks: 8192

      +
      • +
    +
    +

    +
    • +
  • +

    VDP_DECODER_PROFILE_H264_MAIN, +VDP_DECODER_PROFILE_H264_HIGH:

    +
    +
      +
    • +

      Complete acceleration.

      +
      • +
    • +

      Minimum width or height: 3 macroblocks (48 pixels).

      +
      • +
    • +

      Maximum width: 127 macroblocks (2032 pixels).

      +
      • +
    • +

      Maximum height: 128 macroblocks (2048 pixels).

      +
      • +
    • +

      Maximum macroblocks: 8190

      +
      • +
    • +

      Unsupported widths: 49, 54, 59, 64, 113, 118, 123 macroblocks +(784, 864, 944, 1024, 1808, 1888 pixels).

      +
      • +
    +
    +

    +
    • +
  • +

    VDP_DECODER_PROFILE_VC1_SIMPLE, VDP_DECODER_PROFILE_VC1_MAIN, +VDP_DECODER_PROFILE_VC1_ADVANCED:

    +
    +
      +
    • +

      Complete acceleration.

      +
      • +
    • +

      Minimum width or height: 3 macroblocks (48 pixels).

      +
      • +
    • +

      Maximum width or height: 128 macroblocks (2048 pixels).

      +
      • +
    • +

      Maximum macroblocks: 8190

      +
      • +
    +
    +

    +
    • +
+
+

+
+
+
+
+
+
+

VdpVideoMixer

+
+
+
+

The maximum supported resolution is 4096x4096.

+

The video mixer supports all video and output surface +resolutions and formats that the implementation supports.

+

The video mixer supports at most 4 auxiliary layers.

+

The following features are supported:

+
+
    +
  • +

    VDP_VIDEO_MIXER_FEATURE_DEINTERLACE_TEMPORAL

    +
    • +
  • +

    VDP_VIDEO_MIXER_FEATURE_DEINTERLACE_TEMPORAL_SPATIAL

    +
    • +
  • +

    VDP_VIDEO_MIXER_FEATURE_INVERSE_TELECINE

    +
    • +
  • +

    VDP_VIDEO_MIXER_FEATURE_NOISE_REDUCTION

    +
    • +
  • +

    VDP_VIDEO_MIXER_FEATURE_SHARPNESS

    +
    • +
  • +

    VDP_VIDEO_MIXER_FEATURE_LUMA_KEY

    +
    • +
+
+

+

In order for either VDP_VIDEO_MIXER_FEATURE_DEINTERLACE_TEMPORAL +or VDP_VIDEO_MIXER_FEATURE_DEINTERLACE_TEMPORAL_SPATIAL to operate +correctly, the application must supply at least 2 past and 1 future +fields to each VdpMixerRender call. If those fields are not +provided, the VdpMixer will fall back to bob de-interlacing.

+

Both regular de-interlacing and half-rate de-interlacing are +supported. Both have the same requirements in terms of the number +of past/future fields required. Both modes should produce +equivalent results.

+

In order for VDP_VIDEO_MIXER_FEATURE_INVERSE_TELECINE to have +any effect, one of VDP_VIDEO_MIXER_FEATURE_DEINTERLACE_TEMPORAL or +VDP_VIDEO_MIXER_FEATURE_DEINTERLACE_TEMPORAL_SPATIAL must be +requested and enabled. Inverse telecine has the same requirement on +the minimum number of past/future fields that must be provided. +Inverse telecine will not operate when "half-rate" de-interlacing +is used.

+

Whilst is is possible to apply de-interlacing algorithms to +progressive streams using the techniques outlined in the VDPAU +documentation, NVIDIA does not recommend doing so. One is likely to +introduce more artifacts due to the inverse telecine process than +are removed by detection of bad edits etc.

+
+
+
+
+
+

VdpPresentationQueue

+
+
+
+

The resolution of VdpTime is approximately 10 nanoseconds. At +some arbitrary point during system startup, the initial value of +this clock is synchronized to the system's real-time clock, as +represented by nanoseconds since since Jan 1, 1970. However, no +attempt is made to keep the two time-bases synchronized after this +point. Divergence can and will occur.

+

NVIDIA's VdpPresentationQueue supports two mechanisms for +displaying surfaces; overlay and blit-based. The overlay path will +be used wherever possible, with the blit path acting as a more +general fallback. At present, the selection of overlay v.s. blit +path is made at the time of presentation queue creation.

+

The following conditions or system configurations will prevent +usage of the overlay path:

+
+
    +
  • +

    Overlay hardware already in use, e.g. by another VDPAU, GL, or +X11 application, or by SDI output.

    +
    • +
  • +

    SLI or Multi-GPU enabled on the given X screen.

    +
    • +
  • +

    Desktop rotation enabled on the given screen.

    +
    • +
  • +

    X composite extension enabled on the given screen. Note that +simply having the extension enabled is enough to prevent overlay +usage; running an actual compositing manager is not required.

    +
    • +
  • +

    The environment variable VDPAU_NVIDIA_NO_OVERLAY is set to a +string representation of a non-zero integer.

    +
    • +
  • +

    The driver determines that the performance requirements of +overlay usage cannot be met by the current hardware +configuration.

    +
    • +
+

+

Both the overlay and blit path sync to VBLANK.

+

When TwinView is enabled, the blit path can only sync to one of +the display devices; this may cause tearing corruption on the +display device to which VDPAU is not syncing. You can use the +environment variable VDPAU_NVIDIA_SYNC_DISPLAY_DEVICE to specify +the display device to which VDPAU should sync. You should set this +environment variable to the name of a display device; for example +"CRT-1". Look for the line "Connected display device(s):" in your X +log file for a list of the display devices present and their names. +You may also find it useful to review Chapter 12, +Configuring TwinView "Configuring Twinview" and the +section on Ensuring Identical Mode Timings in Chapter 18, +Programming Modes.

+
+
@@ -96,15 +534,15 @@ MetaMode string as follows:

Up  Next +"appendix-g-section-02.html">Next -Appendix F. X -Config Options  + +Appendix F. XvMC Support  Home - - Appendix H. GLX Support + Performance +Levels
diff --git a/doc/html/appendix-h.html b/doc/html/appendix-h.html index 7175c72..2eebf42 100644 --- a/doc/html/appendix-h.html +++ b/doc/html/appendix-h.html @@ -5,30 +5,27 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Appendix H. GLX Support +Appendix H. Tips for New FreeBSD Users - - +
- + +"appendix-g-section-05.html">Prev  - +
Appendix H. GLX -SupportAppendix H. Tips for New +FreeBSD Users
Prev  Part II. Appendices Next 
@@ -36,82 +33,333 @@ Support
-

Appendix H. GLX Support

+

Appendix H. Tips for New FreeBSD +Users

-

This release supports GLX 1.4.

-

Additionally, the following GLX extensions are supported on -appropriate GPUs:

-
-
    -
  • -

    GLX_EXT_visual_info

    -
    • -
  • -

    GLX_EXT_visual_rating

    -
    • -
  • -

    GLX_SGIX_fbconfig

    -
    • -
  • -

    GLX_SGIX_pbuffer

    -
    • -
  • -

    GLX_ARB_get_proc_address

    -
    • -
  • -

    GLX_SGI_video_sync

    -
    • -
  • -

    GLX_SGI_swap_control

    -
    • -
  • -

    GLX_ARB_multisample

    -
    • -
  • -

    GLX_NV_float_buffer

    -
    • -
  • -

    GLX_ARB_fbconfig_float

    -
    • -
  • -

    GLX_NV_swap_group

    -
    • -
  • -

    GLX_NV_video_out

    -
    • -
  • -

    GLX_EXT_texture_from_pixmap

    -
    • -
-
-

For a description of these extensions, see the OpenGL extension -registry at http://www.opengl.org/registry/

-

Some of the above extensions exist as part of core GLX 1.4 -functionality, however, they are also exported as extensions for -backwards compatibility.

+

This installation guide assumes that the user has at least a +basic understanding of FreeBSD techniques and terminology. In this +section we provide tips that the new user may find helpful. While +the these tips are meant to clarify and assist users in installing +and configuring the NVIDIA FreeBSD Driver, it is by no means a +tutorial on the use or administration of the FreeBSD operating +system. Unlike many desktop operating systems, it is relatively +easy to cause irreparable damage to your FreeBSD system. If you are +unfamiliar with the use of FreeBSD, we strongly recommend that you +seek a tutorial through your distributor before proceeding.

+

The command prompt

+

While newer releases of FreeBSD bring new desktop interfaces to +the user, much of the work in FreeBSD takes place at the command +prompt. If you are familiar with the Windows operating system, the +FreeBSD command prompt is analogous to the Windows command prompt, +although the syntax and use varies somewhat. All of the commands in +this section are performed at the command prompt. Some systems are +configured to boot into console mode, in which case the user is +presented with a prompt at login. Other systems are configured to +start the X window system, in which case the user must open a +terminal or console window in order to get a command prompt. This +can usually be done by searching the desktop menus for a terminal +or console program. While it is customizable, the basic prompt +usually consists of a short string of information, one of the +characters #, $, or %, and a cursor +(possibly flashing) that indicates where the user's input will be +displayed.

+

Navigating the directory structure

+

FreeBSD has a hierarchical directory structure. From anywhere in +the directory structure, the ls command will list the contents of that +directory. The file +command will print the type of files in a directory. For +example,

+
+    % file filename
+
+

will print the type of the file filename. Changing directories is done with the +cd command.

+
+    % cd dirname
+
+

will change the current directory to dirname. From anywhere in the directory +structure, the command pwd will print the name of the current +directory. There are two special directories, . and .., which +refer to the current directory and the next directory up the +hierarchy, respectively. For any commands that require a file name +or directory name as an argument, you may specify the absolute or +the relative paths to those elements. An absolute path begins with +the "/" character, referring to the top or root of the directory +structure. A relative path begins with a directory in the current +working directory. The relative path may begin with . or ... Elements +of a path are separated with the "/" character. As an example, if +the current directory is /home/jesse +and the user wants to change to the /usr/local directory, he can use either of the +following commands to do so:

+
+    % cd /usr/local
+
+

or

+
+    % cd ../../usr/local
+
+

+

File permissions and ownership

+

All files and directories have permissions and ownership +associated with them. This is useful for preventing +non-administrative users from accidentally (or maliciously) +corrupting the system. The permissions and ownership for a file or +directory can be determined by passing the -l option to the ls command. For example:

+
+% ls -l
+drwxr-xr-x     2    jesse    users    4096    Feb     8 09:32 bin
+drwxrwxrwx    10    jesse    users    4096    Feb    10 12:04 pub
+-rw-r--r--     1    jesse    users      45    Feb     4 03:55 testfile
+-rwx------     1    jesse    users      93    Feb     5 06:20 myprogram
+-rw-rw-rw-     1    jesse    users     112    Feb     5 06:20 README
+% 
+
+

The first character column in the first output field states the +file type, where 'd' is a directory and '-' is a regular file. The +next nine columns specify the permissions (see paragraph below) of +the element. The second field indicates the number of files +associated with the element, the third field indicates the owner, +the fourth field indicates the group that the file is associated +with, the fifth field indicates the size of the element in bytes, +the sixth, seventh and eighth fields indicate the time at which the +file was last modified and the ninth field is the name of the +element.

+

As stated, the last nine columns in the first field indicate the +permissions of the element. These columns are grouped into threes, +the first grouping indicating the permissions for the owner of the +element (jesse in this case), the +second grouping indicating the permissions for the group associated +with the element, and the third grouping indicating the permissions +associated with the rest of the world. The r, w, and +x indicate read, write and execute +permissions, respectively, for each of these associations. For +example, user jesse has read and +write permissions for testfile, users +in the group users have read +permission only, and the rest of the world also has read +permissions only. However, for the file myprogram, user jesse has read, write and execute permissions +(suggesting that myprogram is a +program that can be executed), while the group users and the rest of the world have no +permissions (suggesting that the owner doesn't want anyone else to +run his program). The permissions, ownership and group associated +with an element can be changed with the commands +chmod, +chown and +chgrp, respectively. +If a user with the appropriate permissions wanted to change the +user/group ownership of README from +jesse/users to joe/admin, he would do the following:

+
+    # chown joe README
+    # chgrp admin README
+
+

The syntax for chmod is slightly more complicated and has +several variations. The most concise way of setting the permissions +for a single element uses a triplet of numbers, one for each of +user, group and world. The value for each number in the triplet +corresponds to a combination of read, write and execute +permissions. Execute only is represented as 1, write only is +represented as 2, and read only is represented as 4. Combinations +of these permissions are represented as sums of the individual +permissions. Read and execute is represented as 5, where as read, +write and execute is represented as 7. No permissions is +represented as 0. Thus, to give the owner read, write and execute +permissions, the group read and execute permissions and the world +no permissions, a user would do as follows:

+
+    % chmod 750 myprogram
+
+

+

The shell

+

The shell provides an interface between the user and the +operating system. It is the job of the shell to interpret the input +that the user gives at the command prompt and call upon the system +to do something in response. There are several different shells +available, each with somewhat different syntax and capabilities. +The two most common flavors of shells used on FreeBSD stem from the +Bourne shell (sh) and +the C-shell (csh) +Different users have preferences and biases towards one shell or +the other, and some certainly make it easier (or at least more +intuitive) to do some things than others. You can determine your +current shell by printing the value of the SHELL environment variable from the command prompt +with

+
+    % echo $SHELL
+
+

You can start a new shell simply by entering the name of the +shell from the command prompt:

+
+    % csh
+
+

or

+
+    % sh
+
+

and you can run a program from within a specific shell by +preceding the name of the executable with the name of the shell in +which it will be run:

+
+    % sh myprogram
+
+

The user's default shell at login is determined by whoever set +up his account. While there are many syntactic differences between +shells, perhaps the one that is encountered most frequently is the +way in which environment variables are set.

+

Setting environment variables

+

Every session has associated with it environment variables, +which consist of name/value pairs and control the way in which the +shell and programs run from the shell behave. An example of an +environment variable is the PATH +variable, which tells the shell which directories to search when +trying to locate an executable file that the user has entered at +the command line. If you are certain that a command exists, but the +shell complains that it cannot be found when you try to execute it, +there is likely a problem with the PATH +variable. Environment variables are set differently depending on +the shell being used. For the Bourne shell (sh), it is done as:

+
+    % export MYVARIABLE="avalue"
+
+

for the C-shell, it is done as:

+
+    % setenv MYVARIABLE "avalue"
+
+

In both cases the quotation marks are only necessary if the +value contains spaces. The echo command can be used to examine the +value of an environment variable:

+
+    % echo $MYVARIABLE
+
+

Commands to set environment variables can also include +references to other environment variables (prepended with the "$" +character), including themselves. In order to add the path +/usr/local/bin to the beginning of +the search path, and the current directory . to the end of the search path, a user would +enter

+
+    % export PATH=/usr/local/bin:$PATH:.
+
+

in the Bourne shell, and

+
+    % setenv PATH /usr/local/bin:${PATH}:.
+
+

in C-shell. Note the curly braces are required to protect the +variable name in C-shell.

+

Editing text files

+

There are several text editors available for the FreeBSD +operating system. Some of these editors require the X window +system, while others are designed to operate in a console or +terminal. It is generally a good thing to be competent with a +terminal-based text editor, as there are times when the files +necessary for X to run are the ones that must be edited. Three +popular editors are vi, pico and emacs, each of which can be started from +the command line, optionally supplying the name of a file to be +edited. vi is +arguably the most ubiquitous as well as the least intuitive of the +three. pico is +relatively straightforward for a new user, though not as often +installed on systems. If you don't have pico, you may have a similar editor +called nano. +emacs is highly +extensible and fairly widely available, but can be somewhat +unwieldy in a non-X environment. The newer versions each come with +online help, and offline help can be found in the manual and info +pages for each (see the section on FreeBSD Manual and Info pages). +Many programs use the EDITOR environment +variable to determine which text editor to start when editing is +required.

+

Root user

+

Upon installation, almost all distributions set up the default +administrative user with the username root. There are many things on the system that +only root (or a similarly +privileged user) can do, one of which is installing the NVIDIA +FreeBSD Driver. We must emphasize that +assuming the identity of root is +inherently risky and as root it is +relatively easy to corrupt your system or otherwise render it +unusable. There are three ways to become root. You may log in as root as you would any other user, you may use +the switch user command (su) at the command prompt, or, on some +systems, use the sudo +utility, which allows users to run programs as root while keeping a log of their actions. This +last method is useful in case a user inadvertently causes damage to +the system and cannot remember what he has done (or prefers not to +admit what he has done). It is generally a good practice to remain +root only as long as is necessary +to accomplish the task requiring root privileges (another useful feature of the +sudo utility).

+

FreeBSD Manual and Info pages

+

System manual or info pages are usually installed during +installation. These pages are typically up-to-date and generally +contain a comprehensive listing of the use of programs and +utilities on the system. Also, many programs include the +--help option, which usually prints a +list of common options for that program. To view the manual page +for a command, enter

+
+    % man commandname
+
+

at the command prompt, where commandname refers to the command in which you are +interested. Similarly, entering

+
+    % info commandname
+
+

will bring up the info page for the command. Depending on the +application, one or the other may be more up-to-date. The interface +for the info system is interactive and navigable. If you are unable +to locate the man page for the command you are interested in, you +may need to add additional elements to your MANPATH environment variable. See the section on +environment variables.

+"appendix-g-section-05.html">Prev  - + - + - +
Prev  Up Next 
-Appendix G. Display Device Names Debugging and +Tracing  Home - Appendix I. Dots Per Inch 
diff --git a/doc/html/appendix-i.html b/doc/html/appendix-i.html deleted file mode 100644 index e310b91..0000000 --- a/doc/html/appendix-i.html +++ /dev/null @@ -1,183 +0,0 @@ - - - - - -Appendix I. Dots Per Inch - - - - - - - -
- - - - - - - - - -
Appendix I. Dots Per -Inch
Prev Part II. Appendices Next
-
-
-
-
-
-

Appendix I. Dots Per Inch

-
-
-
-

DPI (Dots Per Inch), also known as PPI (Pixels Per Inch), is a -property of an X screen that describes the physical size of pixels. -Some X applications, such as xterm, can use the DPI of an X screen -to determine how large (in pixels) to draw an object in order for -that object to be displayed at the desired physical size on the -display device.

-

The DPI of an X screen is computed by dividing the size of the X -screen in pixels by the size of the X screen in inches:

-
-    DPI = SizeInPixels / SizeInInches
-
-

Since the X screen stores its physical size in millimeters -rather than inches (1 inch = 25.4 millimeters):

-
-    DPI = (SizeInPixels * 25.4) / SizeInMillimeters
-
-

The NVIDIA X driver reports the size of the X screen in pixels -and in millimeters. On X.Org 6.9 or newer, when the XRandR -extension resizes the X screen in pixels, the NVIDIA X driver -computes a new size in millimeters for the X screen, to maintain a -constant DPI (see the "Physical Size" column of the `xrandr -q` -output as an example). This is done because a changing DPI can -cause interaction problems for some applications. To disable this -behavior, and instead keep the same millimeter size for the X -screen (and therefore have a changing DPI), set the ConstantDPI -option to FALSE (see Appendix F, X -Config Options for details).

-

You can query the DPI of your X screen by running:

-
-    % xdpyinfo | grep -B1 dot
-
-

which should generate output like this:

-
-    dimensions:    1280x1024 pixels (382x302 millimeters)
-    resolution:    85x86 dots per inch
-
-

-

The NVIDIA X driver performs several steps during X screen -initialization to determine the DPI of each X screen:

-
-
    -
  • -

    If the display device provides an EDID, and the EDID contains -information about the physical size of the display device, that is -used to compute the DPI, along with the size in pixels of the first -mode to be used on the display device. If multiple display devices -are used by this X screen, then the NVIDIA X screen will choose -which display device to use. You can override this with the -"UseEdidDpi" X configuration option: you can specify a particular -display device to use; e.g.:

    -
    -    Option "UseEdidDpi" "DFP-1"
-
    -

    or disable EDID-computed DPI by setting this option to -false:

    -
    -    Option "UseEdidDpi" "FALSE"
-
    -

    EDID-based DPI computation is enabled by default when an EDID is -available.

    -
    • -
  • -

    If the "-dpi" commandline option to the X server is specified, -that is used to set the DPI (see `X -h` for details). This will -override the "UseEdidDpi" option.

    -
    • -
  • -

    If the "DPI" X configuration option is specified (see Appendix F, X -Config Options for details), that will be used to set the -DPI. This will override the "UseEdidDpi" option.

    -
    • -
  • -

    If none of the above are available, then the "DisplaySize" X -config file Monitor section information will be used to determine -the DPI, if provided; see the xorg.conf or XF86Config man pages for -details.

    -
    • -
  • -

    If none of the above are available, the DPI defaults to -75x75.

    -
    • -
-
-

You can find how the NVIDIA X driver determined the DPI by -looking in your X log file. There will be a line that looks -something like the following:

-
-    (--) NVIDIA(0): DPI set to (101, 101); computed from "UseEdidDpi" X config option
-
-

-

Note that the physical size of the X screen, as reported through -`xdpyinfo` is computed based on the DPI and the size of the X -screen in pixels.

-

The DPI of an X screen can be confusing when TwinView is -enabled: with TwinView, multiple display devices (possibly with -different DPIs) display portions of the same X screen, yet DPI can -only be advertised from the X server to the X application with X -screen granularity. Solutions for this include:

-
- -
-
-
-
- - - - - - - - - - - -
Prev Up Next
Appendix H. GLX -Support Home - Appendix J. XvMC Support
-
- - diff --git a/doc/html/appendix-j.html b/doc/html/appendix-j.html deleted file mode 100644 index 3e2cb55..0000000 --- a/doc/html/appendix-j.html +++ /dev/null @@ -1,81 +0,0 @@ - - - - - -Appendix J. XvMC Support - - - - - - - -
- - - - - - - - - -
Appendix J. XvMC -Support
Prev Part II. Appendices Next
-
-
-
-
-
-

Appendix J. XvMC Support

-
-
-
-

This release includes support for the XVideo Motion Compensation -(XvMC) version 1.0 API on GeForce 6 series and GeForce 7 series -add-in cards, as well as motherboard chipsets with integrated -graphics that have PureVideo support based on these GPUs. There is -a static library, "libXvMCNVIDIA.a", and a dynamic one, -"libXvMCNVIDIA_dynamic.so", which is suitable for dlopening. XvMC's -"IDCT" and "motion-compensation" levels of acceleration, AI44 and -IA44 subpictures, and 4:2:0 Surfaces up to 2032x2032 are -supported.

-

libXvMCNVIDIA observes the XVMC_DEBUG environment variable and -will provide some debug output to stderr when set to an appropriate -integer value. '0' disables debug output. '1' enables debug output -for failure conditions. '2' or higher enables output of warning -messages.

-
-
-
- - - - - - - - - - - -
Prev Up Next
-Appendix I. Dots Per Inch Home - Appendix K. VDPAU Support
-
- - diff --git a/doc/html/appendix-k.html b/doc/html/appendix-k.html deleted file mode 100644 index 1ef355d..0000000 --- a/doc/html/appendix-k.html +++ /dev/null @@ -1,493 +0,0 @@ - - - - - -Appendix K. VDPAU Support - - - - - - - -
- - - - - - - - - -
Appendix K. VDPAU -Support
Prev Part II. Appendices Next
-
-
-
-
-
-

Appendix K. VDPAU Support

-
-
-
-
-

Table of Contents

-
-
Implementation Limits
-
-
-
VdpVideoSurface
-
VdpBitmapSurface
-
VdpOutputSurface
-
VdpDecoder
-
VdpVideoMixer
-
VdpPresentationQueue
-
-
-
Performance Levels
-
Getting the Best Performance from the -API
-
Additional Notes
-
Debugging and Tracing
-
-
-

This release includes support for the Video Decode and -Presentation API for Unix-like systems (VDPAU) on most GeForce 8 -series and newer add-in cards, as well as motherboard chipsets with -integrated graphics that have PureVideo support based on these -GPUs.

-
-
-
-
-

Implementation Limits

-
-
-
-

VDPAU is specified as a generic API - the choice of which -features to support, and performance levels of those features, is -left up to individual implementations. The details of NVIDIA's -implementation are provided below.

-
-
-
-
-

VdpVideoSurface

-
-
-
-

The maximum supported resolution is 4096x4096.

-

The following surface formats and get-/put-bits combinations are -supported:

-
-
    -
  • -

    VDP_CHROMA_TYPE_420 (Supported get-/put-bits formats are -VDP_YCBCR_FORMAT_NV12, VDP_YCBCR_FORMAT_YV12)

    -
    • -
  • -

    VDP_CHROMA_TYPE_422 (Supported get-/put-bits formats are -VDP_YCBCR_FORMAT_UYVY, VDP_YCBCR_FORMAT_YUYV)

    -
    • -
-
-

-
-
-
-
-
-

VdpBitmapSurface

-
-
-
-

The maximum supported resolution is 8192x8192.

-

The following surface formats are supported:

-
-
    -
  • -

    VDP_RGBA_FORMAT_B8G8R8A8

    -
    • -
  • -

    VDP_RGBA_FORMAT_R8G8B8A8

    -
    • -
  • -

    VDP_RGBA_FORMAT_B10G10R10A2

    -
    • -
  • -

    VDP_RGBA_FORMAT_R10G10B10A2

    -
    • -
  • -

    VDP_RGBA_FORMAT_A8

    -
    • -
-
-

-

Note that VdpBitmapSurfaceCreate's frequently_accessed parameter -directly controls whether the bitmap data will be placed into video -RAM (VDP_TRUE) or system memory (VDP_FALSE). Note that if the -bitmap data cannot be placed into video RAM when requested due to -resource constraints, the implementation will automatically fall -back to placing the data into system RAM.

-
-
-
-
-
-

VdpOutputSurface

-
-
-
-

The maximum supported resolution is 8192x8192.

-

The following surface formats are supported:

-
-
    -
  • -

    VDP_RGBA_FORMAT_B8G8R8A8

    -
    • -
  • -

    VDP_RGBA_FORMAT_R10G10B10A2

    -
    • -
-
-

-

For all surface formats, the following get-/put-bits indexed -formats are supported:

-
-
    -
  • -

    VDP_INDEXED_FORMAT_A4I4

    -
    • -
  • -

    VDP_INDEXED_FORMAT_I4A4

    -
    • -
  • -

    VDP_INDEXED_FORMAT_A8I8

    -
    • -
  • -

    VDP_INDEXED_FORMAT_I8A8

    -
    • -
-
-

-

For all surface formats, the following get-/put-bits YCbCr -formats are supported:

-
-
    -
  • -

    VDP_YCBCR_FORMAT_Y8U8V8A8

    -
    • -
  • -

    VDP_YCBCR_FORMAT_V8U8Y8A8

    -
    • -
-
-

-
-
-
-
-
-

VdpDecoder

-
-
-
-

In all cases, VdpDecoder objects solely support 8-bit 4:2:0 -streams, and only support writing to VDP_CHROMA_TYPE_420 -surfaces.

-

The exact set of supported VdpDecoderProfile values depends on -the hardware model in use.

-
-
-
-
-

G84, G86, -G92, G94, G96, GT200

-
-
-
-

These chips support the following VdpDecoderProfile values:

-
-
    -
  • -

    VDP_DECODER_PROFILE_MPEG1, VDP_DECODER_PROFILE_MPEG2_SIMPLE, -VDP_DECODER_PROFILE_MPEG2_MAIN:

    -
    -
      -
    • -

      Partial acceleration.

      -
      • -
    • -

      Minimum width or height: 3 macroblocks (48 pixels).

      -
      • -
    • -

      Maximum width or height: 128 macroblocks (2048 pixels).

      -
      • -
    • -

      Maximum macroblocks: 8192

      -
      • -
    -
    -

    -
    • -
  • -

    VDP_DECODER_PROFILE_H264_MAIN, -VDP_DECODER_PROFILE_H264_HIGH:

    -
    -
      -
    • -

      Complete acceleration.

      -
      • -
    • -

      Minimum width or height: 3 macroblocks (48 pixels).

      -
      • -
    • -

      Maximum width or height: 128 macroblocks (2048 pixels).

      -
      • -
    • -

      Maximum macroblocks: 8192

      -
      • -
    -
    -

    -
    • -
-
-

-
-
-
-
-
-

G98, -MCP77, MCP78, MCP79, MCP7A

-
-
-
-

These chips support the following VdpDecoderProfile values:

-
-
    -
  • -

    VDP_DECODER_PROFILE_MPEG1, VDP_DECODER_PROFILE_MPEG2_SIMPLE, -VDP_DECODER_PROFILE_MPEG2_MAIN:

    -
    -
      -
    • -

      Complete acceleration.

      -
      • -
    • -

      Minimum width or height: 3 macroblocks (48 pixels).

      -
      • -
    • -

      Maximum width or height: 128 macroblocks (2048 pixels).

      -
      • -
    • -

      Maximum macroblocks: 8192

      -
      • -
    -
    -

    -
    • -
  • -

    VDP_DECODER_PROFILE_H264_MAIN, -VDP_DECODER_PROFILE_H264_HIGH:

    -
    -
      -
    • -

      Complete acceleration.

      -
      • -
    • -

      Minimum width or height: 3 macroblocks (48 pixels).

      -
      • -
    • -

      Maximum width: 127 macroblocks (2032 pixels).

      -
      • -
    • -

      Maximum height: 128 macroblocks (2048 pixels).

      -
      • -
    • -

      Maximum macroblocks: 8190

      -
      • -
    • -

      Unsupported widths: 49, 54, 59, 64, 113, 118, 123 macroblocks -(784, 864, 944, 1024, 1808, 1888 pixels).

      -
      • -
    -
    -

    -
    • -
  • -

    VDP_DECODER_PROFILE_VC1_SIMPLE, VDP_DECODER_PROFILE_VC1_MAIN, -VDP_DECODER_PROFILE_VC1_ADVANCED:

    -
    -
      -
    • -

      Complete acceleration.

      -
      • -
    • -

      Minimum width or height: 3 macroblocks (48 pixels).

      -
      • -
    • -

      Maximum width or height: 128 macroblocks (2048 pixels).

      -
      • -
    • -

      Maximum macroblocks: 8190

      -
      • -
    -
    -

    -
    • -
-
-

-
-
-
-
-
-
-

VdpVideoMixer

-
-
-
-

The maximum supported resolution is 4096x4096.

-

The video mixer supports all video and output surface -resolutions and formats that the implementation supports.

-

The video mixer supports at most 4 auxiliary layers.

-

The following features are supported:

-
-
    -
  • -

    VDP_VIDEO_MIXER_FEATURE_DEINTERLACE_TEMPORAL

    -
    • -
  • -

    VDP_VIDEO_MIXER_FEATURE_DEINTERLACE_TEMPORAL_SPATIAL

    -
    • -
  • -

    VDP_VIDEO_MIXER_FEATURE_INVERSE_TELECINE

    -
    • -
  • -

    VDP_VIDEO_MIXER_FEATURE_NOISE_REDUCTION

    -
    • -
  • -

    VDP_VIDEO_MIXER_FEATURE_SHARPNESS

    -
    • -
  • -

    VDP_VIDEO_MIXER_FEATURE_LUMA_KEY

    -
    • -
-
-

-

In order for either VDP_VIDEO_MIXER_FEATURE_DEINTERLACE_TEMPORAL -or VDP_VIDEO_MIXER_FEATURE_DEINTERLACE_TEMPORAL_SPATIAL to operate -correctly, the application must supply at least 2 past and 1 future -fields to each VdpMixerRender call. If those fields are not -provided, the VdpMixer will fall back to bob deinterlacing.

-

In order for VDP_VIDEO_MIXER_FEATURE_INVERSE_TELECINE to have -any effect, one of VDP_VIDEO_MIXER_FEATURE_DEINTERLACE_TEMPORAL or -VDP_VIDEO_MIXER_FEATURE_DEINTERLACE_TEMPORAL_SPATIAL must be -requested and enabled. Inverse telecine has the same requirement on -the minimum number of past/future fields that must be provided.

-
-
-
-
-
-

VdpPresentationQueue

-
-
-
-

The resolution of VdpTime is approximately 10ns. At some -arbitrary point during system startup, the initial value of this -clock is synchronized to the system's real-time clock, as -represented by ns since since Jan 1, 1970. However, no attempt is -made to keep the two time-bases synchronized after this point. -Divergence can and will occur.

-

NVIDIA's VdpPresentationQueue supports two mechanisms for -displaying surfaces; overlay and blit-based. The overlay path will -be used wherever possible, with the blit path acting as a more -general fallback. At present, the selection of overlay v.s. blit -path is made at the time of presentation queue creation.

-

The following conditions or system configurations will prevent -usage of the overlay path:

-
-
    -
  • -

    Overlay hardware already in use, e.g. by another VDPAU, GL, or -X11 application, or by SDI output.

    -
    • -
  • -

    SLI or Multi-GPU enabled on the given X screen.

    -
    • -
  • -

    Desktop rotation enabled on the given screen.

    -
    • -
  • -

    X composite extension enabled on the given screen. Note that -simply having the extension enabled is enough to prevent overlay -usage; running an actual compositing manager is not required.

    -
    • -
  • -

    The environment variable VDPAU_NVIDIA_NO_OVERLAY is set to a -string representation of a non-zero integer.

    -
    • -
-
-

-

At present, the overlay path always syncs to vblank, whereas the -blit path never syncs to vblank.

-
-
-
-
-
- - - - - - - - - - - -
Prev Up Next
-Appendix J. XvMC Support Home Performance -Levels
-
- - diff --git a/doc/html/appendix-l.html b/doc/html/appendix-l.html deleted file mode 100644 index d939366..0000000 --- a/doc/html/appendix-l.html +++ /dev/null @@ -1,367 +0,0 @@ - - - - - -Appendix L. Tips for New FreeBSD Users - - - - - - -
- - - - - - - - - -
Appendix L. Tips for New -FreeBSD Users
Prev Part II. Appendices 
-
-
-
-
-
-

Appendix L. Tips for New FreeBSD -Users

-
-
-
-

This installation guide assumes that the user has at least a -basic understanding of FreeBSD techniques and terminology. In this -section we provide tips that the new user may find helpful. While -the these tips are meant to clarify and assist users in installing -and configuring the NVIDIA FreeBSD Driver, it is by no means a -tutorial on the use or administration of the FreeBSD operating -system. Unlike many desktop operating systems, it is relatively -easy to cause irreparable damage to your FreeBSD system. If you are -unfamiliar with the use of FreeBSD, we strongly recommend that you -seek a tutorial through your distributor before proceeding.

-

The command prompt

-

While newer releases of FreeBSD bring new desktop interfaces to -the user, much of the work in FreeBSD takes place at the command -prompt. If you are familiar with the Windows operating system, the -FreeBSD command prompt is analogous to the Windows command prompt, -although the syntax and use varies somewhat. All of the commands in -this section are performed at the command prompt. Some systems are -configured to boot into console mode, in which case the user is -presented with a prompt at login. Other systems are configured to -start the X window system, in which case the user must open a -terminal or console window in order to get a command prompt. This -can usually be done by searching the desktop menus for a terminal -or console program. While it is customizable, the basic prompt -usually consists of a short string of information, one of the -characters #, $, or %, and a cursor -(possibly flashing) that indicates where the user's input will be -displayed.

-

Navigating the directory structure

-

FreeBSD has a hierarchical directory structure. From anywhere in -the directory structure, the ls command will list the contents of that -directory. The file -command will print the type of files in a directory. For -example,

-
-    % file filename
-
-

will print the type of the file filename. Changing directories is done with the -cd command.

-
-    % cd dirname
-
-

will change the current directory to dirname. From anywhere in the directory -structure, the command pwd will print the name of the current -directory. There are two special directories, . and .., which -refer to the current directory and the next directory up the -hierarchy, respectively. For any commands that require a file name -or directory name as an argument, you may specify the absolute or -the relative paths to those elements. An absolute path begins with -the "/" character, referring to the top or root of the directory -structure. A relative path begins with a directory in the current -working directory. The relative path may begin with . or ... Elements -of a path are separated with the "/" character. As an example, if -the current directory is /home/jesse -and the user wants to change to the /usr/local directory, he can use either of the -following commands to do so:

-
-    % cd /usr/local
-
-

or

-
-    % cd ../../usr/local
-
-

-

File permissions and ownership

-

All files and directories have permissions and ownership -associated with them. This is useful for preventing -non-administrative users from accidentally (or maliciously) -corrupting the system. The permissions and ownership for a file or -directory can be determined by passing the -l option to the ls command. For example:

-
-% ls -l
-drwxr-xr-x     2    jesse    users    4096    Feb     8 09:32 bin
-drwxrwxrwx    10    jesse    users    4096    Feb    10 12:04 pub
--rw-r--r--     1    jesse    users      45    Feb     4 03:55 testfile
--rwx------     1    jesse    users      93    Feb     5 06:20 myprogram
--rw-rw-rw-     1    jesse    users     112    Feb     5 06:20 README
-% 
-
-

The first character column in the first output field states the -file type, where 'd' is a directory and '-' is a regular file. The -next nine columns specify the permissions (see paragraph below) of -the element. The second field indicates the number of files -associated with the element, the third field indicates the owner, -the fourth field indicates the group that the file is associated -with, the fifth field indicates the size of the element in bytes, -the sixth, seventh and eighth fields indicate the time at which the -file was last modified and the ninth field is the name of the -element.

-

As stated, the last nine columns in the first field indicate the -permissions of the element. These columns are grouped into threes, -the first grouping indicating the permissions for the owner of the -element (jesse in this case), the -second grouping indicating the permissions for the group associated -with the element, and the third grouping indicating the permissions -associated with the rest of the world. The r, w, and -x indicate read, write and execute -permissions, respectively, for each of these associations. For -example, user jesse has read and -write permissions for testfile, users -in the group users have read -permission only, and the rest of the world also has read -permissions only. However, for the file myprogram, user jesse has read, write and execute permissions -(suggesting that myprogram is a -program that can be executed), while the group users and the rest of the world have no -permissions (suggesting that the owner doesn't want anyone else to -run his program). The permissions, ownership and group associated -with an element can be changed with the commands -chmod, -chown and -chgrp, respectively. -If a user with the appropriate permissions wanted to change the -user/group ownership of README from -jesse/users to joe/admin, he would do the following:

-
-    # chown joe README
-    # chgrp admin README
-
-

The syntax for chmod is slightly more complicated and has -several variations. The most concise way of setting the permissions -for a single element uses a triplet of numbers, one for each of -user, group and world. The value for each number in the triplet -corresponds to a combination of read, write and execute -permissions. Execute only is represented as 1, write only is -represented as 2, and read only is represented as 4. Combinations -of these permissions are represented as sums of the individual -permissions. Read and execute is represented as 5, where as read, -write and execute is represented as 7. No permissions is -represented as 0. Thus, to give the owner read, write and execute -permissions, the group read and execute permissions and the world -no permissions, a user would do as follows:

-
-    % chmod 750 myprogram
-
-

-

The shell

-

The shell provides an interface between the user and the -operating system. It is the job of the shell to interpret the input -that the user gives at the command prompt and call upon the system -to do something in response. There are several different shells -available, each with somewhat different syntax and capabilities. -The two most common flavors of shells used on FreeBSD stem from the -Bourne shell (sh) and -the C-shell (csh) -Different users have preferences and biases towards one shell or -the other, and some certainly make it easier (or at least more -intuitive) to do some things than others. You can determine your -current shell by printing the value of the SHELL environment variable from the command prompt -with

-
-    % echo $SHELL
-
-

You can start a new shell simply by entering the name of the -shell from the command prompt:

-
-    % csh
-
-

or

-
-    % sh
-
-

and you can run a program from within a specific shell by -preceding the name of the executable with the name of the shell in -which it will be run:

-
-    % sh myprogram
-
-

The user's default shell at login is determined by whoever set -up his account. While there are many syntactic differences between -shells, perhaps the one that is encountered most frequently is the -way in which environment variables are set.

-

Setting environment variables

-

Every session has associated with it environment variables, -which consist of name/value pairs and control the way in which the -shell and programs run from the shell behave. An example of an -environment variable is the PATH -variable, which tells the shell which directories to search when -trying to locate an executable file that the user has entered at -the command line. If you are certain that a command exists, but the -shell complains that it cannot be found when you try to execute it, -there is likely a problem with the PATH -variable. Environment variables are set differently depending on -the shell being used. For the Bourne shell (sh), it is done as:

-
-    % export MYVARIABLE="avalue"
-
-

for the C-shell, it is done as:

-
-    % setenv MYVARIABLE "avalue"
-
-

In both cases the quotation marks are only necessary if the -value contains spaces. The echo command can be used to examine the -value of an environment variable:

-
-    % echo $MYVARIABLE
-
-

Commands to set environment variables can also include -references to other environment variables (prepended with the "$" -character), including themselves. In order to add the path -/usr/local/bin to the beginning of -the search path, and the current directory . to the end of the search path, a user would -enter

-
-    % export PATH=/usr/local/bin:$PATH:.
-
-

in the Bourne shell, and

-
-    % setenv PATH /usr/local/bin:${PATH}:.
-
-

in C-shell. Note the curly braces are required to protect the -variable name in C-shell.

-

Editing text files

-

There are several text editors available for the FreeBSD -operating system. Some of these editors require the X window -system, while others are designed to operate in a console or -terminal. It is generally a good thing to be competent with a -terminal-based text editor, as there are times when the files -necessary for X to run are the ones that must be edited. Three -popular editors are vi, pico and emacs, each of which can be started from -the command line, optionally supplying the name of a file to be -edited. vi is -arguably the most ubiquitous as well as the least intuitive of the -three. pico is -relatively straightforward for a new user, though not as often -installed on systems. If you don't have pico, you may have a similar editor -called nano. -emacs is highly -extensible and fairly widely available, but can be somewhat -unwieldy in a non-X environment. The newer versions each come with -online help, and offline help can be found in the manual and info -pages for each (see the section on FreeBSD Manual and Info pages). -Many programs use the EDITOR environment -variable to determine which text editor to start when editing is -required.

-

Root user

-

Upon installation, almost all distributions set up the default -administrative user with the username root. There are many things on the system that -only root (or a similarly -privileged user) can do, one of which is installing the NVIDIA -FreeBSD Driver. We must emphasize that -assuming the identity of root is -inherently risky and as root it is -relatively easy to corrupt your system or otherwise render it -unusable. There are three ways to become root. You may log in as root as you would any other user, you may use -the switch user command (su) at the command prompt, or, on some -systems, use the sudo -utility, which allows users to run programs as root while keeping a log of their actions. This -last method is useful in case a user inadvertently causes damage to -the system and cannot remember what he has done (or prefers not to -admit what he has done). It is generally a good practice to remain -root only as long as is necessary -to accomplish the task requiring root privileges (another useful feature of the -sudo utility).

-

FreeBSD Manual and Info pages

-

System manual or info pages are usually installed during -installation. These pages are typically up-to-date and generally -contain a comprehensive listing of the use of programs and -utilities on the system. Also, many programs include the ---help option, which usually prints a -list of common options for that program. To view the manual page -for a command, enter

-
-    % man commandname
-
-

at the command prompt, where commandname refers to the command in which you are -interested. Similarly, entering

-
-    % info commandname
-
-

will bring up the info page for the command. Depending on the -application, one or the other may be more up-to-date. The interface -for the info system is interactive and navigable. If you are unable -to locate the man page for the command you are interested in, you -may need to add additional elements to your MANPATH environment variable. See the section on -environment variables.

-
-
-
- - - - - - - - - - - -
Prev Up 
Debugging and -Tracing Home 
-
- - diff --git a/doc/html/chapter-01.html b/doc/html/chapter-01.html index a9c3a82..6fd1f4a 100644 --- a/doc/html/chapter-01.html +++ b/doc/html/chapter-01.html @@ -13,8 +13,8 @@ "Part I. Installation and Configuration Instructions"> - +
@@ -29,7 +29,7 @@ Chapter 1. Introduction Part I. Installation and Configuration Instructions  Next +"chapter-02.html">Next
@@ -49,30 +49,30 @@ FreeBSD x86 with the use of NVIDIA graphics processing units (GPUs).

These drivers provide optimized hardware acceleration for OpenGL and X applications and support nearly all recent NVIDIA GPU -products (see Appendix E, +products (see Appendix A, Supported NVIDIA GPU Products for a complete list of supported GPUs). TwinView, TV-Out and flat panel displays are also supported.

About this Document

This document provides instructions for the installation and use of the NVIDIA Accelerated FreeBSD Graphics Driver. Chapter 2, -Installing the NVIDIA Driver, Chapter 3, +Installing the NVIDIA Driver, Chapter 3, +"Chapter 5. Using Linux Compatibility Support">Chapter 5, Using Linux Compatibility Support and Chapter 4, +"chapter-06.html" title= +"Chapter 6. Configuring X for the NVIDIA Driver">Chapter 6, Configuring X for the NVIDIA Driver walk the user through the process of downloading, installing and configuring the -driver. Chapter 5, +driver. Chapter 7, Frequently Asked Questions addresses frequently asked questions about the installation process, and Chapter 6, Common +"chapter-08.html" title= +"Chapter 8. Common Problems">Chapter 8, Common Problems provides solutions to common problems. The remaining chapters include details on different features of the NVIDIA FreeBSD Driver. Frequently asked questions about specific @@ -80,16 +80,16 @@ tasks are included in the relevant chapters.

About the Audience

It is assumed that the user and reader of this document has at least a basic understanding of FreeBSD techniques and terminology. -However, new FreeBSD users can refer to Appendix L, +"Appendix H. Tips for New FreeBSD Users">Appendix H, Tips for New FreeBSD Users for details on parts of the installation process.

Additional Information

In case additional information is required, -Chapter 24, NVIDIA Contact Info and Additional +"chapter-28.html" title= +"Chapter 28. NVIDIA Contact Info and Additional Resources"> +Chapter 28, NVIDIA Contact Info and Additional Resources provides contact information for NVIDIA FreeBSD driver resources, as well as a brief listing of external resources.

@@ -103,7 +103,7 @@ resources.

Up  Next +"chapter-02.html">Next @@ -112,7 +112,7 @@ Instructions  Home - Appendix A. Minimum Software Requirements + Chapter 2. Minimum Software Requirements diff --git a/doc/html/chapter-02.html b/doc/html/chapter-02.html index 6e3a204..587d477 100644 --- a/doc/html/chapter-02.html +++ b/doc/html/chapter-02.html @@ -5,31 +5,31 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Chapter 2. Installing the NVIDIA Driver +Chapter 2. Minimum Software Requirements - - + +
- + +"chapter-01.html">Prev  +"chapter-03.html">Next
Chapter 2. Installing the -NVIDIA DriverChapter 2. Minimum +Software Requirements
Prev  Part I. Installation and Configuration Instructions  Next
@@ -37,48 +37,61 @@ Configuration Instructions
-

Chapter 2. Installing the NVIDIA -Driver

+

Chapter 2. Minimum Software +Requirements

-

This installation procedure will likely be simplified further in -the future, but for the moment you will need to download the NVIDIA -FreeBSD Graphics Driver archives from the NVIDIA website, extract -them to a temporary location of your choice, and run the following -from the root of the extracted directory hierarchy:

-
-    % make install
-
-

This will compile the NVIDIA FreeBSD kernel module, install it, -and kldload it. It will also remove any conflicting OpenGL -libraries, and install the NVIDIA OpenGL libraries. The -/dev/nvidia device files will be -created (unless the system is using devfs), and your /boot/loader.conf file will be updated to -automatically load the NVIDIA kernel module on boot, as well as the -Linux ABI compatibility module should you not have it compiled into -your kernel.

+

The official minimum software requirements for the NVIDIA +FreeBSD Graphics Driver are as follows:

+
+ +++ + + + + + + + + + + + + + + + + +
Software ElementMin Requirement
KernelFreeBSD 5-STABLE (5.3 or later)
XFree86/X.Org4.2/6.7.0
+
+

Additionally, the kernel source tree must be installed in +/usr/src/sys (package 'ssys' installed)

+

Note that FreeBSD -STABLE versions older than FreeBSD 5.3 and +FreeBSD 6.x/7.x -CURRENT development snapshots are not +supported.

+"chapter-01.html">Prev  +"chapter-03.html">Next +Chapter 1. Introduction  + Chapter 3. Installing the NVIDIA Driver
Prev  Up  Next
-Appendix A. Minimum Software Requirements  Home - Appendix B. Installed Components
diff --git a/doc/html/chapter-03.html b/doc/html/chapter-03.html index 4f9966c..0bc1994 100644 --- a/doc/html/chapter-03.html +++ b/doc/html/chapter-03.html @@ -5,28 +5,27 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Chapter 3. Using Linux Compatibility -Support +Chapter 3. Installing the NVIDIA Driver - + +"Chapter 4. Installed Components">
- + +"chapter-02.html">Prev  +"chapter-06-section-02.html">Next +Chapter 5. Using Linux Compatibility Support  - +
Chapter 3. Using Linux -Compatibility SupportChapter 3. Installing the +NVIDIA Driver
Prev  Part I. Installation and Configuration Instructions  
-

Chapter 3. Using Linux Compatibility -Support

+

Chapter 3. Installing the NVIDIA +Driver

-

If you wish to run Linux OpenGL applications on your FreeBSD -computer, you will need to make sure that several prerequisites are -met.

-

First, you should follow the basic Linux compatibility -installation guide in the FreeBSD Handbook (install the linux_base -package, etc). Once the basic components are in place, you will -need to install the NVIDIA Linux OpenGL libraries in /compat/linux/usr/lib (do not brandelf them!); if -the /compat/linux/usr/lib/ directory -exists when you install the FreeBSD driver, the Linux compatibility -OpenGL libraries will automatically be installed.

-

Additionally, the nvidia.ko kernel -module needs to be built with support for the Linux ABI -compatibility layer. This is the case by default; as a consequence, -the nvidia.ko kernel module requires -the linux.ko module to be loaded.

-

Note: If you have no need for Linux ABI compatibility and do not -wish to load linux.ko, you can build -the nvidia.ko kernel module without -support for the Linux ABI compatibility layer (see nv-freebsd.h for details).

+

This installation procedure will likely be simplified further in +the future, but for the moment you will need to download the NVIDIA +FreeBSD Graphics Driver archives from the NVIDIA website, extract +them to a temporary location of your choice, and run the following +from the root of the extracted directory hierarchy:

+
+    % make install
+
+

This will compile the NVIDIA FreeBSD kernel module, install it, +and kldload it. It will also remove any conflicting OpenGL +libraries, and install the NVIDIA OpenGL libraries. The +/dev/nvidia device files will be +created (unless the system is using devfs), and your /boot/loader.conf file will be updated to +automatically load the NVIDIA kernel module on boot, as well as the +Linux ABI compatibility module should you not have it compiled into +your kernel.

+"chapter-02.html">Prev  +Chapter 2. Minimum Software Requirements  + Chapter 4. Installed Components
Prev  Up  
-Appendix B. Installed Components  Home - Chapter 4. Configuring X for the NVIDIA Driver
diff --git a/doc/html/chapter-04.html b/doc/html/chapter-04.html index 01d05c3..3595279 100644 --- a/doc/html/chapter-04.html +++ b/doc/html/chapter-04.html @@ -5,24 +5,23 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Chapter 4. Configuring X for the NVIDIA -Driver +Chapter 4. Installed Components - +"Chapter 3. Installing the NVIDIA Driver"> +
- + +"chapter-05.html">Next
Chapter 4. Configuring X -for the NVIDIA DriverChapter 4. Installed +Components
Part I. Installation and Configuration Instructions  Next
@@ -38,56 +37,171 @@ Configuration Instructions
-

Chapter 4. Configuring X for the NVIDIA -Driver

+

Chapter 4. Installed +Components

-
-

Table of Contents

-
-
Using -nvidia-xconfig to configure the X server
-
Manually Editing the Configuration -File
-
-
-

The X configuration file provides a means to configure the X -server. This section describes the settings necessary to enable the -NVIDIA driver. A comprehensive list of parameters is provided in -Appendix F, X -Config Options.

-

The NVIDIA Driver includes a utility called nvidia-xconfig, -which is designed to make editing the X configuration file easy. -You can also edit it by hand.

-
-
-
-
-

Using nvidia-xconfig to configure the X server

-
-
+

The NVIDIA Accelerated FreeBSD Graphics Driver consists of the +following components.

+
+ +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Installed FileLocation
nvidia.ko/boot/modules
libGL.so/usr/lib/xorg
libGL.so.1/usr/lib/xorg
libnvidia-tls.so/usr/lib/xorg
libnvidia-tls.so.1/usr/lib/xorg
libnvidia-cfg.so/usr/lib/xorg
libnvidia-cfg.so.1/usr/lib/xorg
libGLcore.so/usr/lib/xorg
libGLcore.so.1/usr/lib/xorg
nvidia_drv.so/usr/lib/xorg/modules/drivers
libnvidia-wfb.so (optional)/usr/lib/xorg/modules
libwfb.so/usr/lib/xorg/modules/drivers
libglx.so/usr/lib/xorg/modules/extensions
libglx.so.1/usr/lib/xorg/modules/extensions
libvdpau.so/usr/lib/xorg
libvdpau.so.1/usr/lib/xorg
libvdpau_trace.so/usr/lib/xorg
libvdpau_trace.so.1/usr/lib/xorg
libvdpau_nvidia.so/usr/lib/xorg
libvdpau_nvidia.so.1/usr/lib/xorg
nvidia-xconfig/usr/bin
nvidia-xconfig.1/usr/man/man1
nvidia-settings/usr/bin
nvidia-settings.1/usr/man/man1
nvidia0/dev
nvidia1/dev
nvidia2/dev
nvidia3/dev
nvidiactl/dev
libGL.so.185.18.36/compat/linux/usr/lib
libnvidia-tls.so.185.18.36/compat/linux/usr/lib
libGLcore.so.185.18.36/compat/linux/usr/lib
libvdpau.so.185.18.36/compat/linux/usr/lib
libvdpau_trace.so.185.18.36/compat/linux/usr/lib
libvdpau_nvidia.so.185.18.36/compat/linux/usr/lib
-

nvidia-xconfig will find the X configuration file and modify it -to use the NVIDIA X driver. In most cases, you can simply answer -"Yes" when the installer asks if it should run it. If you need to -reconfigure your X server later, you can run nvidia-xconfig again -from a terminal. nvidia-xconfig will make a backup copy of your -configuration file before modifying it.

-

Note that the X server must be restarted for any changes to its -configuration file to take effect.

-

More information about nvidia-xconfig can be found in the -nvidia-xconfig manual page by running.

-
-    % man nvidia-xconfig
-

-
@@ -97,15 +211,15 @@ nvidia-xconfig manual page by running.

+"chapter-05.html">Next +Chapter 3. Installing the NVIDIA Driver  - +
Up  Next
-Chapter 3. Using Linux Compatibility Support  Home Manually Editing -the Configuration File + Chapter 5. Using Linux Compatibility Support
diff --git a/doc/html/chapter-05.html b/doc/html/chapter-05.html index 702e01e..ebd6209 100644 --- a/doc/html/chapter-05.html +++ b/doc/html/chapter-05.html @@ -5,27 +5,28 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Chapter 5. Frequently Asked Questions +Chapter 5. Using Linux Compatibility +Support - + +"Chapter 6. Configuring X for the NVIDIA Driver">
- + +"chapter-04.html">Prev  - +"chapter-07.html">Next
Chapter 5. Frequently -Asked QuestionsChapter 5. Using Linux +Compatibility Support
Prev  Part I. Installation and Configuration Instructions  
-

Chapter 5. Frequently Asked Questions

+

Chapter 5. Using Linux Compatibility +Support

-

This section provides answers to frequently asked questions -associated with the NVIDIA FreeBSD x86 Driver and its installation. -Common problem diagnoses can be found in Chapter 6, -Common Problems and tips for new users can be found in -Appendix L, -Tips for New FreeBSD Users. Also, detailed information -for specific setups is provided in the Appendices.

-
- -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-

5.1. -NVIDIA Driver

-
-

Where should I start when diagnosing display -problems?

-
-

One of the most useful tools for diagnosing problems is the X -log file in /var/log. Lines that -begin with (II) are -information, (WW) are warnings, -and (EE) are errors. You should -make sure that the correct config file (i.e. the config file you -are editing) is being used; look for the line that begins with:

-
-    (==) Using config file:
-
-

Also make sure that the NVIDIA driver is being used, rather than -the “nv” or -“vesa” driver. Search -for

-
-    (II) LoadModule: "nvidia"
-
-

Lines from the driver should begin with:

-
-    (II) NVIDIA(0)
-
-

-
-

How can I increase the amount of data printed in the X log -file?

-
-

By default, the NVIDIA X driver prints relatively few messages -to stderr and the X log file. If you need to troubleshoot, then it -may be helpful to enable more verbose output by using the X command -line options -verbose and -logverbose, which can be used to set the verbosity -level for the stderr and log file -messages, respectively. The NVIDIA X driver will output more -messages when the verbosity level is at or above 5 (X defaults to -verbosity level 1 for stderr and -level 3 for the log file). So, to enable verbose messaging from the -NVIDIA X driver to both the log file and stderr, you could start X with the verbosity -level set to 5, by doing the following

-
-    % startx -- -verbose 5 -logverbose 5
-
-

-
-

I have read that the NVIDIA FreeBSD Driver is not a native -driver, but sits on top of the Linux ABI compatibility layer. Is -this true?

-
-

No, the NVIDIA FreeBSD Graphics Driver is a native driver. It -does provide Linux OpenGL libraries in addition to the native, -FreeBSD libraries to enable users to run Linux OpenGL -applications.

-
-

Is the NVIDIA FreeBSD Accelerated Graphics Driver -thread-safe?

-
-

This release is thread-safe on FreeBSD 5.3 or later systems -making use of the libpthread or libthr KSE threading libraries. On -these systems, the NVIDIA Linux ABI compatibility libraries are -fully thread-safe as well.

-
-

Why can't the Linux compatibility libraries correctly -determine if they are used in a multithreaded application?

-
-

The Linux compatibility libraries are not able to correctly -determine if they are used in a multithreaded application because -the %gs segment register is not initialized correctly for Linux -compatibility.

-

The __GL_SINGLE_THREADED environment -variable (set to "1") can be used to work around this issue, but at -the cost of thread-safeness.

-
-

Why do applications that use DGA graphics fail?

-
-

The NVIDIA driver does not support the graphics component of the -XFree86-DGA (Direct Graphics Access) extension. Applications can -use the XDGASelectInput() function to acquire relative pointer -motion, but graphics-related functions such as XDGASetMode() and -XDGAOpenFramebuffer() will fail.

-

The graphics component of XFree86-DGA is not supported because -it requires a CPU mapping of framebuffer memory. As graphics cards -ship with increasing quantities of video memory, the NVIDIA X -driver has had to switch to a more dynamic memory mapping scheme -that is incompatible with DGA. Furthermore, DGA does not cooperate -with other graphics rendering libraries such as Xlib and OpenGL -because it accesses GPU resources directly.

-

NVIDIA recommends that applications use OpenGL or Xlib, rather -than DGA, for graphics rendering. Using rendering libraries other -than DGA will yield better performance and improve interoperability -with other X applications.

-
-

My kernel log contains messages that are prefixed with "Xid"; -what do these messages mean?

-
-

"Xid" messages indicate that a general GPU error occurred, most -often due to the driver misprogramming the GPU or to corruption of -the commands sent to the GPU. These messages provide diagnostic -information that can be used by NVIDIA to aid in debugging reported -problems.

-
-

On what NVIDIA hardware is the EXT_framebuffer_object OpenGL -extension supported?

-
-

EXT_framebuffer_object is supported on GeForce FX, Quadro FX, -and newer GPUs.

-
-

I use the Coolbits overclocking interface to adjust my -graphics card's clock frequencies, but the defaults are reset -whenever X is restarted. How do I make my changes -persistent?

-
-

Clock frequency settings are not saved/restored automatically by -default to avoid potential stability and other problems that may be -encountered if the chosen frequency settings differ from the -defaults qualified by the manufacturer. You can use the command -line below in ~/.xinitrc to -automatically apply custom clock frequency settings when the X -server is started:

-
-    # nvidia-settings -a GPUOverclockingState=1 -a GPU2DClockFreqs=<GPU>,<MEM> -a GPU3DClockFreqs=<GPU>,<MEM>
-
-

Here <GPU> and <MEM> are the desired GPU and video memory -frequencies (in MHz), respectively.

-
-

Why is the refresh rate not reported correctly by utilities -that use the XRandR X extension (e.g., the GNOME "Screen Resolution -Preferences" panel, `xrandr -q`, etc)?

-
-

The XRandR X extension is not presently aware of multiple -display devices on a single X screen; it only sees the MetaMode -bounding box, which may contain one or more actual modes. This -means that if multiple MetaModes have the same bounding box, XRandR -will not be able to distinguish between them.

-

In order to support DynamicTwinView, the NVIDIA X driver must -make each MetaMode appear to be unique to XRandR. Presently, the -NVIDIA X driver accomplishes this by using the refresh rate as a -unique identifier.

-

You can use `nvidia-settings -q RefreshRate` to query the actual -refresh rate on each display device.

-

This behavior can be disabled by setting the X configuration -option "DynamicTwinView" to FALSE.

-

For details, see Chapter 10, -Configuring TwinView.

-
-

Why does starting certain applications result in Xlib error -messages indicating extensions like "XFree86-VidModeExtension" or -"SHAPE" are missing?

-
-

If your X config file has a Module section that does not list the -"extmod" module, some X server extensions may be missing, resulting -in error messages of the form:

-
-Xlib: extension "SHAPE" missing on display ":0.0"
-Xlib: extension "XFree86-VidModeExtension" missing on display ":0.0"
-Xlib: extension "XFree86-DGA" missing on display ":0.0"
-
-

You can solve this problem by adding the line below to your X -config file's Module -section:

-
-    Load "extmod"
-
-

-
-
+

If you wish to run Linux OpenGL applications on your FreeBSD +computer, you will need to make sure that several prerequisites are +met.

+

First, you should follow the basic Linux compatibility +installation guide in the FreeBSD Handbook (install the linux_base +package, etc). Once the basic components are in place, you will +need to install the NVIDIA Linux OpenGL libraries in /compat/linux/usr/lib (do not brandelf them!); if +the /compat/linux/usr/lib/ directory +exists when you install the FreeBSD driver, the Linux compatibility +OpenGL libraries will automatically be installed.

+

Additionally, the nvidia.ko kernel +module needs to be built with support for the Linux ABI +compatibility layer. This is the case by default; as a consequence, +the nvidia.ko kernel module requires +the linux.ko module to be loaded.

+

Note: If you have no need for Linux ABI compatibility and do not +wish to load linux.ko, you can build +the nvidia.ko kernel module without +support for the Linux ABI compatibility layer (see nv-freebsd.h for details).

+"chapter-04.html">Prev  - + + Chapter 6. Configuring X for the NVIDIA Driver
Prev  Up  Next
Manually Editing the -Configuration File  +Chapter 4. Installed Components  Home - Chapter 6. Common Problems
diff --git a/doc/html/chapter-04-section-02.html b/doc/html/chapter-06-section-02.html similarity index 85% rename from doc/html/chapter-04-section-02.html rename to doc/html/chapter-06-section-02.html index 801cd05..8129b21 100644 --- a/doc/html/chapter-04-section-02.html +++ b/doc/html/chapter-06-section-02.html @@ -9,12 +9,12 @@ - - - + + +
@@ -25,11 +25,11 @@ File
Prev Chapter 4. Configuring X +"chapter-06.html">Prev  +Chapter 6. Configuring X for the NVIDIA Driver  Next
@@ -127,16 +127,16 @@ Section "Module" EndSection

There are numerous options that may be added to the X config -file to tune the NVIDIA X driver. See Appendix F, +file to tune the NVIDIA X driver. See Appendix B, X Config Options for a complete list of these options.

Once you have completed these edits to the X config file, you may restart X and begin using the accelerated OpenGL libraries. After restarting X, any OpenGL application should automatically use the new NVIDIA libraries. (NOTE: If you encounter any problems, see -Chapter 6, Common +Chapter 8, Common Problems for common problem diagnoses.)

@@ -144,19 +144,19 @@ Problems for common problem diagnoses.)

+"chapter-06.html">Prev  +"chapter-06.html">Up +"chapter-07.html">Next +Chapter 6. Configuring X for the NVIDIA Driver  + Chapter 7. Frequently Asked Questions
Prev  Up  Next
-Chapter 4. Configuring X for the NVIDIA Driver  Home - Chapter 5. Frequently Asked Questions
diff --git a/doc/html/chapter-06.html b/doc/html/chapter-06.html index 920e14d..f19a2d6 100644 --- a/doc/html/chapter-06.html +++ b/doc/html/chapter-06.html @@ -5,23 +5,24 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Chapter 6. Common Problems +Chapter 6. Configuring X for the NVIDIA +Driver - +"Chapter 5. Using Linux Compatibility Support"> +
- + +"chapter-06-section-02.html">Next
Chapter 6. Common -ProblemsChapter 6. Configuring X +for the NVIDIA Driver
Part I. Installation and Configuration Instructions  Next
@@ -37,588 +38,54 @@ Configuration Instructions
-

Chapter 6. Common Problems

+

Chapter 6. Configuring X for the NVIDIA +Driver

-

This section provides solutions to common problems associated -with the NVIDIA FreeBSD x86 Driver.

-
- -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-

My X server fails to start, and my X log file contains the -error:

-
-(EE) NVIDIA(0): The NVIDIA kernel module does not appear to
-(EE) NVIDIA(0):      be receiving interrupts generated by the NVIDIA graphics
-(EE) NVIDIA(0):      device PCI:x:x:x. Please see the COMMON PROBLEMS
-(EE) NVIDIA(0):      section in the README for additional information.
-
-

This can be caused by a variety of problems, such as PCI IRQ -routing errors, I/O APIC problems or conflicts with other devices -sharing the IRQ (or their drivers).

-

If possible, configure your system such that your graphics card -does not share its IRQ with other devices (try moving the graphics -card to another slot if applicable, unload/disable the driver(s) -for the device(s) sharing the card's IRQ, or remove/disable the -device(s)).

-
-

My X server fails to start, and my X log file contains the -error:

-
-(EE) NVIDIA(0): The interrupt for NVIDIA graphics device PCI:x:x:x
-(EE) NVIDIA(0):      appears to be edge-triggered. Please see the COMMON
-(EE) NVIDIA(0):      PROBLEMS section in the README for additional information.
-
-

An edge-triggered interrupt means that the kernel has programmed -the interrupt as edge-triggered rather than level-triggered in the -Advanced Programmable Interrupt Controller (APIC). Edge-triggered -interrupts are not intended to be used for sharing an interrupt -line between multiple devices; level-triggered interrupts are the -intended trigger for such usage. When using edge-triggered -interrupts, it is common for device drivers using that interrupt -line to stop receiving interrupts. This would appear to the end -user as those devices no longer working, and potentially as a full -system hang. These problems tend to be more common when multiple -devices are sharing that interrupt line.

-
-

X starts for me, but OpenGL applications terminate -immediately.

-
-

If X starts but you have trouble with OpenGL, you most likely -have a problem with other libraries in the way, or there are stale -symlinks. See Appendix B, -Installed Components for details.

-

You should also check that the correct extensions are -present;

-
-    % xdpyinfo
-
-

should show the “GLX” and -“NV-GLX” extensions present. -If these two extensions are not present, then there is most likely -a problem loading the glx module, or it is unable to implicitly -load GLcore. Check your X config file and make sure that you are -loading glx (see Chapter 4, -Configuring X for the NVIDIA Driver). If your X config -file is correct, then check the X log file for warnings/errors -pertaining to GLX. Also check that all of the necessary symlinks -are in place (refer to Appendix B, -Installed Components).

-
-

When Xinerama is enabled, my stereo glasses are shuttering -only when the stereo application is displayed on one specific X -screen. When the application is displayed on the other X screens, -the stereo glasses stop shuttering.

-
-

This problem occurs with DDC and "blue line" stereo glasses, -that get the stereo signal from one video port of the graphics -card. When a X screen does not display any stereo drawable the -stereo signal is disabled on the associated video port.

-

Forcing stereo flipping allows the stereo glasses to shutter -continuously. This can be done by enabling the OpenGL control -"Force Stereo Flipping" in nvidia-settings, or by setting the X -configuration option "ForceStereoFlipping" to "1".

-
-

Stereo is not in sync across multiple displays.

-
-

There are two cases where this may occur. If the displays are -attached to the same GPU, and one of them is out of sync with the -stereo glasses, you will need to reconfigure your monitors to drive -identical mode timings; see Chapter 16, -Programming Modes for details.

-

If the displays are attached to different GPUs, the only way to -synchronize stereo across the displays is with a G-Sync device, -which is only supported by certain Quadro cards. See Chapter 21, -Configuring Frame Lock and Genlock for details. This -applies to seperate GPUs on seperate cards as well as seperate GPUs -on the same card, such as Quadro FX 4500 X2. Note that the Quadro -FX 4500 X2 only provides a single DIN connector for stereo, tied to -the bottommost GPU. In order to synchronize onboard stereo on the -other GPU you must use a G-Sync device.

-
-

X fails to start, and during boot up time I get error -messages

-
-nvidia0: NVRM: NVIDIA REG resource alloc failed.
-
-

or

-
-nvidia0: NVRM: NVIDIA IRQ resource alloc failed.
-
-

The system BIOS has not properly set up your graphics card; -FreeBSD can't currently set up PCI devices that the BIOS leaves -unconfigured. Uncheck "PNP-OS" in your system BIOS.

-
-

X fails to start, and during boot up time I get the following -error message:

-
-nvidia0: NVRM: NVIDIA MEM resource alloc failed.
-
-

On certain FreeBSD kernels, it may be necessary to add the -following line to /boot/loader.conf:

-
-hw.pci.allow_unsupported_io_range="1"
-
-

This should allow the NVIDIA kernel module to attach.

-
-

Some OpenGL applications fail to start, and my X log file -contains error messages of the form:

-
-(EE) NVIDIA(0): Failed to obtain a shared memory identifier...
-
-

and/or

-
-(EE) NVIDIA(0): Failed to attach to shared memory segment...
-
-

The NVIDIA driver may require more IPC resources than are -allocated by default. If this happens, you may be able to work -around this problem by increasing your system's resource limits by -editing the file /boot/loader.conf -and adding:

-
-kern.ipc.shmseg=1024
-kern.ipc.shmmni=1024
-
-

The values above were chosen conservatively, you may need to -tweak them to meet your requirements.

-
-

My X server fails to start, and my X log file contains the -error:

-
-(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module!
-
-

Nothing will work if the NVIDIA kernel module does not function -properly. If you see anything in the X log file like

-
-(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module!
-
-

then there is most likely a problem with the NVIDIA kernel -module.

-

The NVIDIA kernel module may print error messages indicating a -problem -- to view these messages check the output of -dmesg, /var/log/messages, or wherever syslog is directed -to place kernel messages. These messages are prepended with -"NVRM".

-
-

When I attempt to start `nvidia-settings`, I get an error -message of the form:

-
- Shared object "libgtk-x11-2.0.so.400" not found, required by nvidia-settings
-
-

Due to differences between the gtk+-2.x ports packages included -with different FreeBSD 5.x releases, the prebuilt nvidia-settings -binary shipped with the NVIDIA driver may not work with FreeBSD -releases more recent than FreeBSD 5.3.

-

If you have a recent ports package of gtk+-2.x and gmake -installed on your system, you can build the nvidia-installer -utility from source to solve this problem.

-

Download nvidia-settings-1.0.tar.gz (or the latest version) from -ftp://download.nvidia.com/XFree86/nvidia-settings You -can then extract, build and install it (to /usr/local/bin) with:

-
-    % gmake install
-
-

-
-

When I attempt to run `nvidia-xconfig` after the NVIDIA -FreeBSD graphics driver installation, I get an error message of the -form:

-
-nvidia-xconfig: Command not found.
-
-

Depending on the shell you are using, you may need to force it -to recompute its internal table of executable files present in the -directories listed in the $PATH -variable. Assuming you are using the FreeBSD default shell you can -do so by issuing the command:

-
-    % rehash
-
-

-
-

When I attempt to start a Linux application as 'root', I get -the error message:

-
-NVIDIA: failed to execute '/sbin/modprobe': No such file or directory.
-
-

When initialized by an application executed with 'root' -privileges, the NVIDIA Linux OpenGL library, shipped with the -NVIDIA FreeBSD graphics driver for Linux ABI compatibility, will -attempt to load the NVIDIA Linux kernel module and fail because -/sbin/modprobe is absent. You can work around this problem by -creating a symbolic link from /usr/bin/true to /compat/linux/sbin/modprobe:

-
-    % ln -s /usr/bin/true /compat/linux/sbin/modprobe
-
-

-
-

My system runs, but seems unstable.

-
-

Your stability problems may be AGP-related. See Chapter 9, -Configuring AGP for details.

-
-

OpenGL applications are running slowly

-
-

The application is probably using a different library that still -remains on your system, rather than the NVIDIA supplied OpenGL -library. See Appendix B, -Installed Components for details.

-
-

There are problems running Quake2.

-
-

Quake2 requires some minor setup to get it going. First, in the -Quake2 directory, the install creates a symlink called libGL.so that points at libMesaGL.so. This symlink should be removed or -renamed. Second, in order to run Quake2 in OpenGL mode, you must -type

-
-    % quake2 +set vid_ref glx +set gl_driver libGL.so
-
-

Quake2 does not seem to support any kind of full-screen mode, -but you can run your X server at the same resolution as Quake2 to -emulate full-screen mode.

-
-

I am using either nForce of nForce2 internal graphics, and I -see warnings like this in my X log file:

-
-Not using mode "1600x1200" (exceeds valid memory bandwidth usage)
-
-

Integrated graphics have more strict memory bandwidth -limitations that limit the resolution and refresh rate of the modes -you request. To work around this, you can reduce the maximum -refresh rate by lowering the upper value of the VertRefresh range in the Monitor section of your X config file. Though -not recommended, you can disable the memory bandwidth test with the -NoBandWidthTest X config file -option.

-
-

X takes a long time to start (possibly several -minutes).

-
-

Most of the X startup delay problems we have found are caused by -incorrect data in video BIOSes about what display devices are -possibly connected or what i2c port should be used for detection. -You can work around these problems with the X config option -IgnoreDisplayDevices (see the -description in Appendix F, X -Config Options).

-
-

Fonts are incorrectly sized after installing the NVIDIA -driver.

-
-

Incorrectly sized fonts are generally caused by incorrect DPI -(Dots Per Inch) information. You can check what X thinks the -physical size of your monitor is, by running:

-
- % xdpyinfo | grep dimensions
-
-

This will report the size in pixels, and in millimeters.

-

If these numbers are wrong, you can correct them by modifying -the X server's DPI setting. See Appendix I, Dots Per -Inch for details.

-
-

General problems with ALi chipsets

-
-

There are some known timing and signal integrity issues on ALi -chipsets. The following tips may help stabilize problematic ALI -systems:

-
-
    -
  • -

    Disable TURBO AGP MODE in the BIOS.

    -
    • -
  • -

    When using a P5A upgrade to BIOS Revision 1002 BETA 2.

    -
    • -
  • -

    When using 1007, 1007A or 1009 adjust the IO Recovery Time to 4 -cycles.

    -
    • -
  • -

    AGP is disabled by default on some ALi chipsets (ALi1541, -ALi1647) to work around severe system stability problems with these -chipsets. See the comments for EnableALiAGP in nv-reg.h to force AGP on anyway.

    -
    • -
+
+

Table of Contents

+
+
Using +nvidia-xconfig to configure the X server
+
Manually Editing the Configuration +File
+
-

-
-

Using GNOME configuration utilities, I am unable to get a -resolution above 800x600.

-
-

The installation of GNOME provided in operating systems such as -Red Hat Enterprise Linux 4 and Solaris 10 Update 2 contain several -competing interfaces for specifying resolution:

-
-    'System Settings' -> 'Display'
-
-

which will update the X configuration file, and

-
-    'Applications' -> 'Preferences' -> 'Screen Resolution'
+
The X configuration file provides a means to configure the X
+server. This section describes the settings necessary to enable the
+NVIDIA driver. A comprehensive list of parameters is provided in
+Appendix B, X
+Config Options.

+
The NVIDIA Driver includes a utility called nvidia-xconfig,
+which is designed to make editing the X configuration file easy.
+You can also edit it by hand.

+

+

+

+

+
Using nvidia-xconfig to configure the X server

+

+

+

+
nvidia-xconfig will find the X configuration file and modify it
+to use the NVIDIA X driver. In most cases, you can simply answer
+"Yes" when the installer asks if it should run it. If you need to
+reconfigure your X server later, you can run nvidia-xconfig again
+from a terminal. nvidia-xconfig will make a backup copy of your
+configuration file before modifying it.

+
Note that the X server must be restarted for any changes to its
+configuration file to take effect.

+
More information about nvidia-xconfig can be found in the
+nvidia-xconfig manual page by running.

+
+    % man nvidia-xconfig
 

-
which will update the per-user screen resolution using the
-XRandR extension. Your desktop resolution will be limited to the
-smaller of the two settings. Be sure to check the setting of
-each.

-
-

X does not restore the VGA console when run on a TV. I get -this error message in my X log file:

-
-Unable to initialize the X int10 module; the console may not be
-restored correctly on your TV.
-
-

The NVIDIA X driver uses the X Int10 module to save and restore -console state on TV out, and will not be able to restore the -console correctly if it cannot use the Int10 module. If you have -built the X server yourself, please be sure you have built the -Int10 module. If you are using a build of the X server provided by -your operating system and are missing the Int10 module, contact -your operating system distributor.

-
-

OpenGL applications don't work, and my X log file contains -the error:

-
-(EE) NVIDIA(0): Unable to map device node /dev/zero with read, write, and
-(EE) NVIDIA(0):     execute privileges.  The GLX extension will be disabled
-(EE) NVIDIA(0):     on this X screen.  Please see the COMMON PROBLEMS
-(EE) NVIDIA(0):     section in the README for more information.
-
-

The NVIDIA OpenGL driver must be able to map the /dev/zero device node with read, write, and -execute privileges in order to function correctly. The driver needs -this ability to allocate executable memory, which is used for -optimizations that require generating code at run-time. Currently, -GLX cannot run without these optimizations.

-

Check that your /dev filesystem is -set up correctly. In particular, mounting the /dev file system with the 'noexec' option will -cause this to happen. If you haven't changed the configuration of -your /dev filesystem, please contact -your operating system distributor.

-
+

@@ -630,15 +97,15 @@ your operating system distributor.

Up  Next
-Chapter 5. Frequently Asked Questions  Home - Chapter 7. Known Issues Manually Editing +the Configuration File
diff --git a/doc/html/chapter-07.html b/doc/html/chapter-07.html index 3918270..27496a0 100644 --- a/doc/html/chapter-07.html +++ b/doc/html/chapter-07.html @@ -5,27 +5,27 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Chapter 7. Known Issues +Chapter 7. Frequently Asked Questions - + +"Chapter 8. Common Problems">
- + +"chapter-06-section-02.html">Prev 
Chapter 7. Known -IssuesChapter 7. Frequently +Asked Questions
Prev  Part I. Installation and Configuration Instructions  
-

Chapter 7. Known Issues

+

Chapter 7. Frequently Asked Questions

-

The following problems still exist in this release and are in -the process of being resolved.

-
-

Known Issues

-
-
Notebooks
-
-

If you are using a notebook see the "Known Notebook Issues" in -Chapter 15, -Configuring a Notebook.

-
-
FSAA
-
-

When FSAA is enabled (the __GL_FSAA_MODE environment variable is -set to a value that enables FSAA and a multisample visual is -chosen), the rendering may be corrupted when resizing the -window.

-
-
libGL DSO finalizer and pthreads
-
-

When a multithreaded OpenGL application exits, it is possible -for libGL's DSO finalizer (also known as the destructor, or -"_fini") to be called while other threads are executing OpenGL -code. The finalizer needs to free resources allocated by libGL. -This can cause problems for threads that are still using these -resources. Setting the environment variable "__GL_NO_DSO_FINALIZER" -to "1" will work around this problem by forcing libGL's finalizer -to leave its resources in place. These resources will still be -reclaimed by the operating system when the process exits. Note that -the finalizer is also executed as part of dlclose(3), so if you -have an application that dlopens(3) and dlcloses(3) libGL -repeatedly, "__GL_NO_DSO_FINALIZER" will cause libGL to leak -resources until the process exits. Using this option can improve -stability in some multithreaded applications, including Java3D +

This section provides answers to frequently asked questions +associated with the NVIDIA FreeBSD x86 Driver and its installation. +Common problem diagnoses can be found in Chapter 8, +Common Problems and tips for new users can be found in +Appendix H, +Tips for New FreeBSD Users. Also, detailed information +for specific setups is provided in the Appendices.

+
+ ++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

7.1. +NVIDIA Driver

+
+

Where should I start when diagnosing display +problems?

+
+

One of the most useful tools for diagnosing problems is the X +log file in /var/log. Lines that +begin with (II) are +information, (WW) are warnings, +and (EE) are errors. You should +make sure that the correct config file (i.e. the config file you +are editing) is being used; look for the line that begins with:

+
+    (==) Using config file:
+
+

Also make sure that the NVIDIA driver is being used, rather than +the “nv” or +“vesa” driver. Search +for

+
+    (II) LoadModule: "nvidia"
+
+

Lines from the driver should begin with:

+
+    (II) NVIDIA(0)
+
+

+
+

How can I increase the amount of data printed in the X log +file?

+
+

By default, the NVIDIA X driver prints relatively few messages +to stderr and the X log file. If you need to troubleshoot, then it +may be helpful to enable more verbose output by using the X command +line options -verbose and -logverbose, which can be used to set the verbosity +level for the stderr and log file +messages, respectively. The NVIDIA X driver will output more +messages when the verbosity level is at or above 5 (X defaults to +verbosity level 1 for stderr and +level 3 for the log file). So, to enable verbose messaging from the +NVIDIA X driver to both the log file and stderr, you could start X with the verbosity +level set to 5, by doing the following

+
+    % startx -- -verbose 5 -logverbose 5
+
+

+
+

I have read that the NVIDIA FreeBSD Driver is not a native +driver, but sits on top of the Linux ABI compatibility layer. Is +this true?

+
+

No, the NVIDIA FreeBSD Graphics Driver is a native driver. It +does provide Linux OpenGL libraries in addition to the native, +FreeBSD libraries to enable users to run Linux OpenGL applications.

- -
XVideo and the Composite X -extension
-
-

XVideo will not work correctly when Composite is enabled unless -using X.Org 7.1 or later. See Chapter 18, -Using the X Composite Extension.

-
-
GLX visuals in Xinerama
-
-

X servers prior to version 1.5.0 have a limitation in the number -of visuals that can be available when Xinerama is enabled. -Specifically, visuals with ID values over 255 will cause the server -to corrupt memory, leading to incorrect behavior or crashes. In -some configurations where many GLX features are enabled at once, -the number of GLX visuals will exceed this limit. To avoid a crash, -the NVIDIA X driver will discard visuals above the limit. To see -which visuals are being discarded, run the X server with the --logverbose 6 option and then check the -X server log file.

-
- - -

This section describes problems that will not be fixed. Usually, -the source of the problem is beyond the control of NVIDIA. -Following is the list of problems:

-
-

Problems that Will Not Be Fixed

-
-
Gigabyte GA-6BX Motherboard
-
-

This motherboard uses a LinFinity regulator on the 3.3 V rail -that is only rated to 5 A -- less than the AGP specification, which -requires 6 A. When diagnostics or applications are running, the -temperature of the regulator rises, causing the voltage to the -NVIDIA GPU to drop as low as 2.2 V. Under these circumstances, the -regulator cannot supply the current on the 3.3 V rail that the -NVIDIA GPU requires.

-

This problem does not occur when the graphics card has a -switching regulator or when an external power supply is connected -to the 3.3 V rail.

-
-
VIA KX133 and 694X Chip sets with AGP -2x
-
-

On Athlon motherboards with the VIA KX133 or 694X chip set, such -as the ASUS K7V motherboard, NVIDIA drivers default to AGP 2x mode -to work around insufficient drive strength on one of the -signals.

-
-
Irongate Chip sets with AGP 1x
-
-

AGP 1x transfers are used on Athlon motherboards with the -Irongate chipset to work around a problem with signal -integrity.

-
-
ALi chipsets, ALi1541 and -ALi1647
-
-

On ALi1541 and ALi1647 chipsets, NVIDIA drivers disable AGP to -work around timing issues and signal integrity issues. See Chapter 6, Common -Problems for more information on ALi chipsets.

-
-
NV-CONTROL versions 1.8 and 1.9
-
-

Version 1.8 of the NV-CONTROL X Extension introduced target -types for setting and querying attributes as well as receiving -event notification on targets. Targets are objects like X Screens, -GPUs and G-Sync devices. Previously, all attributes were described -relative to an X Screen. These new bits of information (target type -and target id) were packed in a non-compatible way in the protocol -stream such that addressing X Screen 1 or higher would generate an -X protocol error when mixing NV-CONTROL client and server -versions.

-

This packing problem has been fixed in the NV-CONTROL 1.10 -protocol, making it possible for the older (1.7 and prior) clients -to communicate with NV-CONTROL 1.10 servers. Furthermore, the -NV-CONTROL 1.10 client library has been updated to accommodate the -target protocol packing bug when communicating with a 1.8 or 1.9 -NV-CONTROL server. This means that the NV-CONTROL 1.10 client -library should be able to communicate with any version of the -NV-CONTROL server.

-

NVIDIA recommends that NV-CONTROL client applications relink -with version 1.10 or later of the NV-CONTROL client library -(libXNVCtrl.a, in the nvidia-settings-1.0.tar.gz tarball). The -version of the client library can be determined by checking the -NV_CONTROL_MAJOR and NV_CONTROL_MINOR definitions in the -accompanying nv_control.h.

-

The only web released NVIDIA FreeBSD driver that is affected by -this problem (i.e., the only driver to use either version 1.8 or -1.9 of the NV-CONTROL X extension) is 1.0-8756.

-
-
-
+
+

Is the NVIDIA FreeBSD Accelerated Graphics Driver +thread-safe?

+
+

This release is thread-safe on FreeBSD 5.3 or later systems +making use of the libpthread or libthr KSE threading libraries. On +these systems, the NVIDIA Linux ABI compatibility libraries are +fully thread-safe as well.

+
+

Why can't the Linux compatibility libraries correctly +determine if they are used in a multithreaded application?

+
+

The Linux compatibility libraries are not able to correctly +determine if they are used in a multithreaded application because +the %gs segment register is not initialized correctly for Linux +compatibility.

+

The __GL_SINGLE_THREADED environment +variable (set to "1") can be used to work around this issue, but at +the cost of thread-safeness.

+
+

Why do applications that use DGA graphics fail?

+
+

The NVIDIA driver does not support the graphics component of the +XFree86-DGA (Direct Graphics Access) extension. Applications can +use the XDGASelectInput() function to acquire relative pointer +motion, but graphics-related functions such as XDGASetMode() and +XDGAOpenFramebuffer() will fail.

+

The graphics component of XFree86-DGA is not supported because +it requires a CPU mapping of framebuffer memory. As graphics cards +ship with increasing quantities of video memory, the NVIDIA X +driver has had to switch to a more dynamic memory mapping scheme +that is incompatible with DGA. Furthermore, DGA does not cooperate +with other graphics rendering libraries such as Xlib and OpenGL +because it accesses GPU resources directly.

+

NVIDIA recommends that applications use OpenGL or Xlib, rather +than DGA, for graphics rendering. Using rendering libraries other +than DGA will yield better performance and improve interoperability +with other X applications.

+
+

My kernel log contains messages that are prefixed with "Xid"; +what do these messages mean?

+
+

"Xid" messages indicate that a general GPU error occurred, most +often due to the driver misprogramming the GPU or to corruption of +the commands sent to the GPU. These messages provide diagnostic +information that can be used by NVIDIA to aid in debugging reported +problems.

+
+

On what NVIDIA hardware is the EXT_framebuffer_object OpenGL +extension supported?

+
+

EXT_framebuffer_object is supported on GeForce FX, Quadro FX, +and newer GPUs.

+
+

I use the Coolbits overclocking interface to adjust my +graphics card's clock frequencies, but the defaults are reset +whenever X is restarted. How do I make my changes +persistent?

+
+

Clock frequency settings are not saved/restored automatically by +default to avoid potential stability and other problems that may be +encountered if the chosen frequency settings differ from the +defaults qualified by the manufacturer. You can use the command +line below in ~/.xinitrc to +automatically apply custom clock frequency settings when the X +server is started:

+
+    # nvidia-settings -a GPUOverclockingState=1 -a GPU2DClockFreqs=<GPU>,<MEM> -a GPU3DClockFreqs=<GPU>,<MEM>
+
+

Here <GPU> and <MEM> are the desired GPU and video memory +frequencies (in MHz), respectively.

+
+

Why is the refresh rate not reported correctly by utilities +that use the XRandR X extension (e.g., the GNOME "Screen Resolution +Preferences" panel, `xrandr -q`, etc)?

+
+

The XRandR X extension is not presently aware of multiple +display devices on a single X screen; it only sees the MetaMode +bounding box, which may contain one or more actual modes. This +means that if multiple MetaModes have the same bounding box, XRandR +will not be able to distinguish between them.

+

In order to support DynamicTwinView, the NVIDIA X driver must +make each MetaMode appear to be unique to XRandR. Presently, the +NVIDIA X driver accomplishes this by using the refresh rate as a +unique identifier.

+

You can use `nvidia-settings -q RefreshRate` to query the actual +refresh rate on each display device.

+

This behavior can be disabled by setting the X configuration +option "DynamicTwinView" to FALSE.

+

For details, see Chapter 12, +Configuring TwinView.

+
+

Why does starting certain applications result in Xlib error +messages indicating extensions like "XFree86-VidModeExtension" or +"SHAPE" are missing?

+
+

If your X config file has a Module section that does not list the +"extmod" module, some X server extensions may be missing, resulting +in error messages of the form:

+
+Xlib: extension "SHAPE" missing on display ":0.0"
+Xlib: extension "XFree86-VidModeExtension" missing on display ":0.0"
+Xlib: extension "XFree86-DGA" missing on display ":0.0"
+
+

You can solve this problem by adding the line below to your X +config file's Module +section:

+
+    Load "extmod"
+

+
+
+"chapter-06-section-02.html">Prev  - + + Chapter 8. Common Problems
Prev  Up  Next
-Chapter 6. Common Problems Manually Editing the +Configuration File  Home - Chapter 8. Specifying OpenGL Environment Variable -Settings
diff --git a/doc/html/chapter-08.html b/doc/html/chapter-08.html index f6ee96d..5662b88 100644 --- a/doc/html/chapter-08.html +++ b/doc/html/chapter-08.html @@ -5,24 +5,23 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Chapter 8. Specifying OpenGL Environment Variable -Settings +Chapter 8. Common Problems +"Chapter 7. Frequently Asked Questions"> +"Chapter 9. Known Issues">
- + +"chapter-18.html">Next +Chapter 16. Using the XRandR Extension  + Chapter 18. Programming Modes
Chapter 8. Specifying -OpenGL Environment Variable SettingsChapter 8. Common +Problems
-

Chapter 8. Specifying OpenGL -Environment Variable Settings

+

Chapter 8. Common Problems

-

Full scene antialiasing

-

Antialiasing is a technique used to smooth the edges of objects -in a scene to reduce the jagged "stairstep" effect that sometimes -appears. By setting the appropriate environment variable, you can -enable full-scene antialiasing in any OpenGL application on these -GPUs.

-

Several antialiasing methods are available and you can select -between them by setting the __GL_FSAA_MODE environment variable -appropriately. Note that increasing the number of samples taken -during FSAA rendering may decrease performance.

-

To see the available values for __GL_FSAA_MODE along with their -descriptions, run:

-
-nvidia-settings --query=fsaa --verbose
+
This section provides solutions to common problems associated
+with the NVIDIA FreeBSD x86 Driver.

+

+
++
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Chapter 7. Frequently Asked Questions 
+ Chapter 9. Known Issues



+
My X server fails to start, and my X log file contains the
+error:

+
+(EE) NVIDIA(0): The NVIDIA kernel module does not appear to
+(EE) NVIDIA(0):      be receiving interrupts generated by the NVIDIA graphics
+(EE) NVIDIA(0):      device PCI:x:x:x. Please see the COMMON PROBLEMS
+(EE) NVIDIA(0):      section in the README for additional information.
+

+
This can be caused by a variety of problems, such as PCI IRQ
+routing errors, I/O APIC problems or conflicts with other devices
+sharing the IRQ (or their drivers).

+
If possible, configure your system such that your graphics card
+does not share its IRQ with other devices (try moving the graphics
+card to another slot if applicable, unload/disable the driver(s)
+for the device(s) sharing the card's IRQ, or remove/disable the
+device(s)).

+

+
My X server fails to start, and my X log file contains the
+error:

+
+(EE) NVIDIA(0): The interrupt for NVIDIA graphics device PCI:x:x:x
+(EE) NVIDIA(0):      appears to be edge-triggered. Please see the COMMON
+(EE) NVIDIA(0):      PROBLEMS section in the README for additional information.
+

+
An edge-triggered interrupt means that the kernel has programmed
+the interrupt as edge-triggered rather than level-triggered in the
+Advanced Programmable Interrupt Controller (APIC). Edge-triggered
+interrupts are not intended to be used for sharing an interrupt
+line between multiple devices; level-triggered interrupts are the
+intended trigger for such usage. When using edge-triggered
+interrupts, it is common for device drivers using that interrupt
+line to stop receiving interrupts. This would appear to the end
+user as those devices no longer working, and potentially as a full
+system hang. These problems tend to be more common when multiple
+devices are sharing that interrupt line.

+

+
X starts for me, but OpenGL applications terminate
+immediately.

+

+
If X starts but you have trouble with OpenGL, you most likely
+have a problem with other libraries in the way, or there are stale
+symlinks. See Chapter 4,
+Installed Components for details.

+
You should also check that the correct extensions are
+present;

+
+    % xdpyinfo
 

-
The __GL_FSAA_MODE environment variable uses the same integer
-values that are used to configure FSAA through nvidia-settings and
-the NV-CONTROL X extension.

-
Anisotropic texture filtering

-
Automatic anisotropic texture filtering can be enabled by
-setting the environment variable __GL_LOG_MAX_ANISO. The possible
-values are:

-

-
---
-
-
-
-
+
should show the “GLX” and
+“NV-GLX” extensions present.
+If these two extensions are not present, then there is most likely
+a problem loading the glx module, or it is unable to implicitly
+load GLcore. Check your X config file and make sure that you are
+loading glx (see Chapter 6,
+Configuring X for the NVIDIA Driver). If your X config
+file is correct, then check the X log file for warnings/errors
+pertaining to GLX. Also check that all of the necessary symlinks
+are in place (refer to Chapter 4,
+Installed Components).

+
-
-
-
-
-
+
+
+
-
-
-
+
+
+
-
-
-
+
+
+
-
-
-
+
+
+
-
-
-
+
+
+
-
-



__GL_LOG_MAX_ANISOFiltering Type
 
0No anisotropic filtering

+
When Xinerama is enabled, my stereo glasses are shuttering
+only when the stereo application is displayed on one specific X
+screen. When the application is displayed on the other X screens,
+the stereo glasses stop shuttering.

+		
 
12x anisotropic filtering

+
This problem occurs with DDC and "blue line" stereo glasses,
+that get the stereo signal from one video port of the graphics
+card. When a X screen does not display any stereo drawable the
+stereo signal is disabled on the associated video port.

+
Forcing stereo flipping allows the stereo glasses to shutter
+continuously. This can be done by enabling the OpenGL control
+"Force Stereo Flipping" in nvidia-settings, or by setting the X
+configuration option "ForceStereoFlipping" to "1".

+		
 
24x anisotropic filtering

+
Stereo is not in sync across multiple displays.

+		
 
38x anisotropic filtering

+
There are two cases where this may occur. If the displays are
+attached to the same GPU, and one of them is out of sync with the
+stereo glasses, you will need to reconfigure your monitors to drive
+identical mode timings; see Chapter 18,
+Programming Modes for details.

+
If the displays are attached to different GPUs, the only way to
+synchronize stereo across the displays is with a G-Sync device,
+which is only supported by certain Quadro cards. See Chapter 25,
+Configuring Frame Lock and Genlock for details. This
+applies to seperate GPUs on seperate cards as well as seperate GPUs
+on the same card, such as Quadro FX 4500 X2. Note that the Quadro
+FX 4500 X2 only provides a single DIN connector for stereo, tied to
+the bottommost GPU. In order to synchronize onboard stereo on the
+other GPU you must use a G-Sync device.

+		
 
416x anisotropic filtering

+
X fails to start, and during boot up time I get error
+messages

+
+nvidia0: NVRM: NVIDIA REG resource alloc failed.
+

+
or

+
+nvidia0: NVRM: NVIDIA IRQ resource alloc failed.
+

 

+

+
The system BIOS has not properly set up your graphics card;
+FreeBSD can't currently set up PCI devices that the BIOS leaves
+unconfigured. Uncheck "PNP-OS" in your system BIOS.

+

+
X fails to start, and during boot up time I get the following
+error message:

+
+nvidia0: NVRM: NVIDIA MEM resource alloc failed.
+

+
On certain FreeBSD kernels, it may be necessary to add the
+following line to /boot/loader.conf:

+
+hw.pci.allow_unsupported_io_range="1"
+

+
This should allow the NVIDIA kernel module to attach.

+

+
Some OpenGL applications fail to start, and my X log file
+contains error messages of the form:

+
+(EE) NVIDIA(0): Failed to obtain a shared memory identifier...
+

+
and/or

+
+(EE) NVIDIA(0): Failed to attach to shared memory segment...
+

+
The NVIDIA driver may require more IPC resources than are
+allocated by default. If this happens, you may be able to work
+around this problem by increasing your system's resource limits by
+editing the file /boot/loader.conf
+and adding:

+
+kern.ipc.shmseg=1024
+kern.ipc.shmmni=1024
+

+
The values above were chosen conservatively, you may need to
+tweak them to meet your requirements.

+

+
My X server fails to start, and my X log file contains the
+error:

+
+(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module!
+

+
Nothing will work if the NVIDIA kernel module does not function
+properly. If you see anything in the X log file like

+
+(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module!
+

+
then there is most likely a problem with the NVIDIA kernel
+module.

+
The NVIDIA kernel module may print error messages indicating a
+problem -- to view these messages check the output of
+dmesg, /var/log/messages, or wherever syslog is directed
+to place kernel messages. These messages are prepended with
+"NVRM".

+

+
When I attempt to start `nvidia-settings`, I get an error
+message of the form:

+
+ Shared object "libgtk-x11-2.0.so.400" not found, required by nvidia-settings
+

+
Due to differences between the gtk+-2.x ports packages included
+with different FreeBSD 5.x releases, the prebuilt nvidia-settings
+binary shipped with the NVIDIA driver may not work with FreeBSD
+releases more recent than FreeBSD 5.3.

+
If you have a recent ports package of gtk+-2.x and gmake
+installed on your system, you can build the nvidia-installer
+utility from source to solve this problem.

+
Download nvidia-settings-1.0.tar.gz (or the latest version) from
+ftp://download.nvidia.com/XFree86/nvidia-settings You
+can then extract, build and install it (to /usr/local/bin) with:

+
+    % gmake install
+

+

+

+
When I attempt to run `nvidia-xconfig` after the NVIDIA
+FreeBSD graphics driver installation, I get an error message of the
+form:

+
+nvidia-xconfig: Command not found.
+

+
Depending on the shell you are using, you may need to force it
+to recompute its internal table of executable files present in the
+directories listed in the $PATH
+variable. Assuming you are using the FreeBSD default shell you can
+do so by issuing the command:

+
+    % rehash
+

+

+

+
When I attempt to start a Linux application as 'root', I get
+the error message:

+
+NVIDIA: failed to execute '/sbin/modprobe': No such file or directory.
+

+
When initialized by an application executed with 'root'
+privileges, the NVIDIA Linux OpenGL library, shipped with the
+NVIDIA FreeBSD graphics driver for Linux ABI compatibility, will
+attempt to load the NVIDIA Linux kernel module and fail because
+/sbin/modprobe is absent. You can work around this problem by
+creating a symbolic link from /usr/bin/true to /compat/linux/sbin/modprobe:

+
+    % ln -s /usr/bin/true /compat/linux/sbin/modprobe
+

+

+

+
My system runs, but seems unstable.

+

+
Your stability problems may be AGP-related. See Chapter 11,
+Configuring AGP for details.

+

+
OpenGL applications are running slowly

+

+
The application is probably using a different library that still
+remains on your system, rather than the NVIDIA supplied OpenGL
+library. See Chapter 4,
+Installed Components for details.

+

+
There are problems running Quake2.

+

+
Quake2 requires some minor setup to get it going. First, in the
+Quake2 directory, the install creates a symlink called libGL.so that points at libMesaGL.so. This symlink should be removed or
+renamed. Second, in order to run Quake2 in OpenGL mode, you must
+type

+
+    % quake2 +set vid_ref glx +set gl_driver libGL.so
+

+
Quake2 does not seem to support any kind of full-screen mode,
+but you can run your X server at the same resolution as Quake2 to
+emulate full-screen mode.

+

+
I am using either nForce of nForce2 internal graphics, and I
+see warnings like this in my X log file:

+
+Not using mode "1600x1200" (exceeds valid memory bandwidth usage)
+

+
Integrated graphics have more strict memory bandwidth
+limitations that limit the resolution and refresh rate of the modes
+you request. To work around this, you can reduce the maximum
+refresh rate by lowering the upper value of the VertRefresh range in the Monitor section of your X config file. Though
+not recommended, you can disable the memory bandwidth test with the
+NoBandWidthTest X config file
+option.

+

+
X takes a long time to start (possibly several
+minutes).

+

+
Most of the X startup delay problems we have found are caused by
+incorrect data in video BIOSes about what display devices are
+possibly connected or what i2c port should be used for detection.
+You can work around these problems with the X config option
+IgnoreDisplayDevices (see the
+description in Appendix B, X
+Config Options).

+

+
Fonts are incorrectly sized after installing the NVIDIA
+driver.

+

+
Incorrectly sized fonts are generally caused by incorrect DPI
+(Dots Per Inch) information. You can check what X thinks the
+physical size of your monitor is, by running:

+
+ % xdpyinfo | grep dimensions
+

+
This will report the size in pixels, and in millimeters.

+
If these numbers are wrong, you can correct them by modifying
+the X server's DPI setting. See Appendix E, Dots Per
+Inch for details.

+

+
General problems with ALi chipsets

+

+
There are some known timing and signal integrity issues on ALi
+chipsets. The following tips may help stabilize problematic ALI
+systems:

+

+
    
+
  • 
+
    Disable TURBO AGP MODE in the BIOS.
    
+
    • 
+
  • 
+
    When using a P5A upgrade to BIOS Revision 1002 BETA 2.
    
+
    • 
+
  • 
+
    When using 1007, 1007A or 1009 adjust the IO Recovery Time to 4
+cycles.
    
+
    • 
+
  • 
+
    AGP is disabled by default on some ALi chipsets (ALi1541,
+ALi1647) to work around severe system stability problems with these
+chipsets. See the comments for EnableALiAGP in nv-reg.h to force AGP on anyway.
    
+
    • 
+

 

-
4x and greater are only available on GeForce3 or newer GPUs; 16x
-is only available on GeForce 6800 or newer GPUs.

-
Vblank syncing

-
Setting the environment variable __GL_SYNC_TO_VBLANK to a
-non-zero value will force glXSwapBuffers to sync to your monitor's
-vertical refresh (perform a swap only during the vertical blanking
-period).

-
When using __GL_SYNC_TO_VBLANK with TwinView, OpenGL can only
-sync to one of the display devices; this may cause tearing
-corruption on the display device to which OpenGL is not syncing.
-You can use the environment variable __GL_SYNC_DISPLAY_DEVICE to
-specify to which display device OpenGL should sync. You should set
-this environment variable to the name of a display device; for
-example "CRT-1". Look for the line "Connected display device(s):"
-in your X log file for a list of the display devices present and
-their names. You may also find it useful to review Chapter 10,
-Configuring TwinView "Configuring Twinview" and the
-section on Ensuring Identical Mode Timings in Chapter 16,
-Programming Modes.

-
Controlling the sorting of OpenGL FBConfigs

-
The NVIDIA GLX implementation sorts FBConfigs returned by
-glXChooseFBConfig() as described in the GLX specification. To
-disable this behavior set __GL_SORT_FBCONFIGS to 0 (zero), then
-FBConfigs will be returned in the order they were received from the
-X server. To examine the order in which FBConfigs are returned by
-the X server run:

-
-nvidia-settings --glxinfo
+

+

+
Using GNOME configuration utilities, I am unable to get a
+resolution above 800x600.

+

+
The installation of GNOME provided in operating systems such as
+Red Hat Enterprise Linux 4 and Solaris 10 Update 2 contain several
+competing interfaces for specifying resolution:

+
+    'System Settings' -> 'Display'
 

-
This option may be be useful to work around problems in which
-applications pick an unexpected FBConfig.

-
OpenGL yield behavior

-
There are several cases where the NVIDIA OpenGL driver needs to
-wait for external state to change before continuing. To avoid
-consuming too much CPU time in these cases, the driver will
-sometimes yield so the kernel can schedule other processes to run
-while the driver waits. For example, when waiting for free space in
-a command buffer, if the free space has not become available after
-a certain number of iterations, the driver will yield before it
-continues to loop.

-
By default, the driver calls sched_yield() to do this. However,
-this can cause the calling process to be scheduled out for a
-relatively long period of time if there are other, same-priority
-processes competing for time on the CPU. One example of this is
-when an OpenGL-based composite manager is moving and repainting a
-window and the X server is trying to update the window as it moves,
-which are both CPU-intensive operations.

-
You can use the __GL_YIELD environment variable to work around
-these scheduling problems. This variable allows the user to specify
-what the driver should do when it wants to yield. The possible
-values are:

-

-
---
-
-
-
-
+
which will update the X configuration file, and

+
+    'Applications' -> 'Preferences' -> 'Screen Resolution'
+

+
which will update the per-user screen resolution using the
+XRandR extension. Your desktop resolution will be limited to the
+smaller of the two settings. Be sure to check the setting of
+each.

+
-
-
-
-
-
+
+
+
-
-
-
+
+
+
-
-
-
+
+
+
+
+
+
+



__GL_YIELDBehavior
 
<unset>By default, OpenGL will call sched_yield() to yield.

+
X does not restore the VGA console when run on a TV. I get
+this error message in my X log file:

+
+Unable to initialize the X int10 module; the console may not be
+restored correctly on your TV.
+

 
"NOTHING"OpenGL will never yield.

+
The NVIDIA X driver uses the X Int10 module to save and restore
+console state on TV out, and will not be able to restore the
+console correctly if it cannot use the Int10 module. If you have
+built the X server yourself, please be sure you have built the
+Int10 module. If you are using a build of the X server provided by
+your operating system and are missing the Int10 module, contact
+your operating system distributor.

+		
 
"USLEEP"OpenGL will call usleep(0) to yield.

+
OpenGL applications don't work, and my X log file contains
+the error:

+
+(EE) NVIDIA(0): Unable to map device node /dev/zero with read, write, and
+(EE) NVIDIA(0):     execute privileges.  The GLX extension will be disabled
+(EE) NVIDIA(0):     on this X screen.  Please see the COMMON PROBLEMS
+(EE) NVIDIA(0):     section in the README for more information.
+

+
The NVIDIA OpenGL driver must be able to map the /dev/zero device node with read, write, and
+execute privileges in order to function correctly. The driver needs
+this ability to allocate executable memory, which is used for
+optimizations that require generating code at run-time. Currently,
+GLX cannot run without these optimizations.

+
Check that your /dev filesystem is
+set up correctly. In particular, mounting the /dev file system with the 'noexec' option will
+cause this to happen. If you haven't changed the configuration of
+your /dev filesystem, please contact
+your operating system distributor.

+		
 

 
 

 

-

-
Controlling which OpenGL FBConfigs are available

-
The NVIDIA GLX implementation will hide FBConfigs that are
-associated with a 32-bit ARGB visual when the
-XLIB_SKIP_ARGB_VISUALS environment variable is defined. This
-matches the behavior of libX11, which will hide those visuals from
-XGetVisualInfo and XMatchVisualInfo. This environment variable is
-useful when applications are confused by the presence of these
-FBConfigs.

 
 

 

@@ -206,11 +634,11 @@ FBConfigs.

 

 

 
-Chapter 7. Known Issues 
 Home
 
- Chapter 9. Configuring AGP
 

 

 

diff --git a/doc/html/chapter-09.html b/doc/html/chapter-09.html
index 104727c..3bee45c 100644
--- a/doc/html/chapter-09.html
+++ b/doc/html/chapter-09.html
@@ -5,23 +5,23 @@
 "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org">
 
-Chapter 9. Configuring AGP
+Chapter 9. Known Issues
 
 
 
 
+"Chapter 8. Common Problems">
 
+"Chapter 10. Specifying OpenGL Environment Variable Settings">
 
 
 

 
-
+
+Chapter 8. Common Problems 
+ Chapter 10. Specifying OpenGL Environment Variable
+Settings

 
Chapter 9. Configuring
-AGPChapter 9. Known
+Issues
 

 

 
 

 

 

-
Chapter 9. Configuring AGP

+
Chapter 9. Known Issues

 

 

 

-
There are several choices for configuring the NVIDIA kernel
-module's use of AGP: you can choose to either use the NVIDIA AGP
-module (NVAGP), or the AGP module that comes with the FreeBSD
-kernel (AGPGART). This is controlled through the "NvAGP" option in
-your X config file:

-
-    Option "NvAgp" "0"  ... disables AGP support
-    Option "NvAgp" "1"  ... use NVAGP, if possible
-    Option "NvAgp" "2"  ... use AGPGART, if possible
-    Option "NvAGP" "3"  ... try AGPGART; if that fails, try NVAGP
-

-
Unlike other operating systems such as Linux, this option is not
-the only controlling factor at this point; because of known
-problems, nvidia.ko is built without
-support for FreeBSD's AGP driver by default. This behavior can be
-changed, see nv-freebsd.h for
-details.

-
Note that if you built nvidia.ko with support for the FreeBSD
-driver it will not load unless agp.ko
-is loaded. agp.ko is special in that
-you can not load it after the system boot is complete, you need to
-append the following line to /boot/loader.conf to make sure it is
-pre-loaded:

+
The following problems still exist in this release and are in
+the process of being resolved.

+

+
Known Issues

+

+
Notebooks

+

+
If you are using a notebook see the "Known Notebook Issues" in
+Chapter 17,
+Configuring a Notebook.

+

+
FSAA

+

+
When FSAA is enabled (the __GL_FSAA_MODE environment variable is
+set to a value that enables FSAA and a multisample visual is
+chosen), the rendering may be corrupted when resizing the
+window.

+

+
libGL DSO finalizer and pthreads

+

+
When a multithreaded OpenGL application exits, it is possible
+for libGL's DSO finalizer (also known as the destructor, or
+"_fini") to be called while other threads are executing OpenGL
+code. The finalizer needs to free resources allocated by libGL.
+This can cause problems for threads that are still using these
+resources. Setting the environment variable "__GL_NO_DSO_FINALIZER"
+to "1" will work around this problem by forcing libGL's finalizer
+to leave its resources in place. These resources will still be
+reclaimed by the operating system when the process exits. Note that
+the finalizer is also executed as part of dlclose(3), so if you
+have an application that dlopens(3) and dlcloses(3) libGL
+repeatedly, "__GL_NO_DSO_FINALIZER" will cause libGL to leak
+resources until the process exits. Using this option can improve
+stability in some multithreaded applications, including Java3D
+applications.

+

+
XVideo and the Composite X
+extension

+

+
XVideo will not work correctly when Composite is enabled unless
+using X.Org 7.1 or later. See Chapter 22,
+Using the X Composite Extension.

+

+
GLX visuals in Xinerama

+

+
X servers prior to version 1.5.0 have a limitation in the number
+of visuals that can be available when Xinerama is enabled.
+Specifically, visuals with ID values over 255 will cause the server
+to corrupt memory, leading to incorrect behavior or crashes. In
+some configurations where many GLX features are enabled at once,
+the number of GLX visuals will exceed this limit. To avoid a crash,
+the NVIDIA X driver will discard visuals above the limit. To see
+which visuals are being discarded, run the X server with the
+-logverbose 6 option and then check the
+X server log file.

+

+
Some X servers have
+trouble with multiple GPUs

+

+
Some versions of the X.Org server version 1.5.0 and higher have
+a bug that causes X to fail with an error similar to the following
+when there is more than one GPU in the computer:

 
-    # -- load FreeBSD AGP GART driver -- #
-    agp_load="YES"
+(!!) More than one possible primary device found
+(II) Primary Device is:
+(EE) No devices detected.
+
+Fatal server error:
+no screens found
 

-
Also note that if agp.ko is
-loaded, it could conflict with the NVIDIA AGP GART driver (NvAGP),
-resulting in stability problems; for this reason, the NVIDIA driver
-will abort NvAGP initialization when it detects agp.ko.

-
Current FreeBSD releases are shipped with agp.ko built into the kernel; in order to allow
-NvAGP to work, the kernel can be rebuilt without 'device agp' or
-the following entry added to /boot/device.hints:

+
You can work around this problem by specifying the bus ID of the
+device you wish to use. For more details, please search the
+xorg.conf manual page for "BusID". You can configure the X server
+with an X screen on each NVIDIA GPU by running:

 
-    hint.agp.0.disabled="1"
+nvidia-xconfig --enable-all-gpus
 

-
When built with support for the FreeBSD AGP driver, nvidia.ko will fall back to using NvAGP when it
-doesn't detect agp.ko (this will be
-the case when agp.ko does not support
-your AGP chipset or was explicitly disabled with device hints).

-
It is highly recommended that you use the NVIDIA AGP driver.

-
The following AGP chipsets are supported by the NVIDIA AGP
-driver; for all other chipsets it is recommended that you use the
-AGPGART module.

-

-
--
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-


Supported AGP Chipsets
Intel 440LX
Intel 440BX
Intel 440GX
Intel 815 ("Solano")
Intel 820 ("Camino")
Intel 830M
Intel 840 ("Carmel")
Intel 845 ("Brookdale")
Intel 845G
Intel 850 ("Tehama")
Intel 855 ("Odem")
Intel 860 ("Colusa")
Intel 865G ("Springdale")
Intel 875P ("Canterwood")
Intel E7205 ("Granite Bay")
Intel E7505 ("Placer")
AMD 751 ("Irongate")
AMD 761 ("IGD4")
AMD 762 ("IGD4 MP")
AMD 8151 ("Lokar")
VIA 8371
VIA 82C694X
VIA KT133
VIA KT266
VIA KT400
VIA P4M266
VIA P4M266A
VIA P4X400
VIA K8T800
VIA K8N800
VIA PT880
VIA KT880
RCC CNB20LE
RCC 6585HE
Micron SAMDDR ("Samurai")
Micron SCIDDR ("Scimitar")
NVIDIA nForce
NVIDIA nForce2
NVIDIA nForce3
ALi 1621
ALi 1631
ALi 1647
ALi 1651
ALi 1671
SiS 630
SiS 633
SiS 635
SiS 645
SiS 646
SiS 648
SiS 648FX
SiS 650
SiS 651
SiS 655
SiS 655FX
SiS 661
SiS 730
SiS 733
SiS 735
SiS 745
SiS 755
ATI RS200M

-

 

-
If you are experiencing AGP stability problems, you should be
-aware of the following:

+
Please see Bugzilla bug #18321 for more details on this X server
+problem.

+

+

+

+
This section describes problems that will not be fixed. Usually,
+the source of the problem is beyond the control of NVIDIA.
+Following is the list of problems:

 

-
Additional AGP Information

+
Problems that Will Not Be Fixed

 

-
AGP drive strength BIOS setting (Via-based
-motherboards)

+
Gigabyte GA-6BX Motherboard

 

-
Many Via-based motherboards allow adjusting the AGP drive
-strength in the system BIOS. The setting of this option largely
-affects system stability, the range between 0xEA and 0xEE seems to
-work best for NVIDIA hardware. Setting either nibble to 0xF
-generally results in severe stability problems.

-
If you decide to experiment with this, you need to be aware of
-the fact that you are doing so at your own risk and that you may
-render your system unbootable with improper settings until you
-reset the setting to a working value (w/ a PCI graphics card or by
-resetting the BIOS to its default values).

+
This motherboard uses a LinFinity regulator on the 3.3 V rail
+that is only rated to 5 A -- less than the AGP specification, which
+requires 6 A. When diagnostics or applications are running, the
+temperature of the regulator rises, causing the voltage to the
+NVIDIA GPU to drop as low as 2.2 V. Under these circumstances, the
+regulator cannot supply the current on the 3.3 V rail that the
+NVIDIA GPU requires.

+
This problem does not occur when the graphics card has a
+switching regulator or when an external power supply is connected
+to the 3.3 V rail.

 

-
System BIOS version

+
VIA KX133 and 694X Chip sets with AGP
+2x

+

+
On Athlon motherboards with the VIA KX133 or 694X chip set, such
+as the ASUS K7V motherboard, NVIDIA drivers default to AGP 2x mode
+to work around insufficient drive strength on one of the
+signals.

+

+
Irongate Chip sets with AGP 1x

+

+
AGP 1x transfers are used on Athlon motherboards with the
+Irongate chipset to work around a problem with signal
+integrity.

+

+
ALi chipsets, ALi1541 and
+ALi1647

 

-
Make sure you have the latest system BIOS provided by the
-motherboard manufacturer.

 
On ALi1541 and ALi1647 chipsets, NVIDIA drivers disable AGP to
-work around timing and signal integrity problems. You can force AGP
-to be enabled on these chipsets by setting NVreg_EnableALiAGP to 1.
-Note that this may cause the system to become unstable.

-
Early system BIOS revisions for the ASUS A7V8X-X KT400
-motherboard misconfigure the chipset when an AGP 2.x graphics card
-is installed; if X hangs on your ASUS KT400 system with NvAGP
-enabled and the installed graphics card is not an AGP 8x device,
-make sure that you have the latest system BIOS installed.

+work around timing issues and signal integrity issues. See Chapter 8, Common
+Problems for more information on ALi chipsets.

+

+
NV-CONTROL versions 1.8 and 1.9

+

+
Version 1.8 of the NV-CONTROL X Extension introduced target
+types for setting and querying attributes as well as receiving
+event notification on targets. Targets are objects like X Screens,
+GPUs and G-Sync devices. Previously, all attributes were described
+relative to an X Screen. These new bits of information (target type
+and target id) were packed in a non-compatible way in the protocol
+stream such that addressing X Screen 1 or higher would generate an
+X protocol error when mixing NV-CONTROL client and server
+versions.

+
This packing problem has been fixed in the NV-CONTROL 1.10
+protocol, making it possible for the older (1.7 and prior) clients
+to communicate with NV-CONTROL 1.10 servers. Furthermore, the
+NV-CONTROL 1.10 client library has been updated to accommodate the
+target protocol packing bug when communicating with a 1.8 or 1.9
+NV-CONTROL server. This means that the NV-CONTROL 1.10 client
+library should be able to communicate with any version of the
+NV-CONTROL server.

+
NVIDIA recommends that NV-CONTROL client applications relink
+with version 1.10 or later of the NV-CONTROL client library
+(libXNVCtrl.a, in the nvidia-settings-1.0.tar.gz tarball). The
+version of the client library can be determined by checking the
+NV_CONTROL_MAJOR and NV_CONTROL_MINOR definitions in the
+accompanying nv_control.h.

+
The only web released NVIDIA FreeBSD driver that is affected by
+this problem (i.e., the only driver to use either version 1.8 or
+1.9 of the NV-CONTROL X extension) is 1.0-8756.

+

+
CPU throttling reducing memory bandwidth on
+IGP systems

+

+
For some models of CPU, the CPU throttling technology may affect
+not only CPU core frequency, but also memory frequency/bandwidth.
+On systems using integrated graphics, any reduction in memory
+bandwidth will affect the GPU as well as the CPU. This can
+negatively affect applications that use significant memory
+bandwidth, such as video decoding using VDPAU, or certain OpenGL
+operations. This may cause such applications to run with lower
+performance than desired.

+
To work around this problem, NVIDIA recommends configuring your
+CPU throttling implementation to avoid reducing memory bandwidth.
+This may be as simple as setting a certain minimum frequency for
+the CPU.

+
Depending on your operating system and/or distribution, this may
+be as simple as writing to a configuration file in the /sys or
+/proc filesystems, or other system configuration file. Please read,
+or search the Internet for, documentation regarding CPU throttling
+on your operating system.

+

+
VDPAU initialization failures on supported
+GPUs

+

+
If VDPAU gives the VDP_STATUS_NO_IMPLEMENTATION error message on
+a GPU which was labeled or specified as supporting PureVideo or
+PureVideo HD, one possible reason is a hardware defect. After
+ruling out any other software problems, NVIDIA recommends returning
+the GPU to the manufacturer for a replacement.

 

 

 

@@ -342,12 +248,12 @@ make sure that you have the latest system BIOS installed.

 

 

 
-Chapter 8. Specifying OpenGL Environment Variable
-Settings 
 Home
 
- Chapter 10. Configuring TwinView
 

 

 

diff --git a/doc/html/chapter-10.html b/doc/html/chapter-10.html
index c67ad10..869d4a8 100644
--- a/doc/html/chapter-10.html
+++ b/doc/html/chapter-10.html
@@ -5,23 +5,24 @@
 "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org">
 
-Chapter 10. Configuring TwinView
+Chapter 10. Specifying OpenGL Environment Variable
+Settings
 
 
 
 
+"Chapter 9. Known Issues">
 
+"Chapter 11. Configuring AGP">
 
 
 

 
-
+
+Chapter 9. Known Issues 
+ Chapter 11. Configuring AGP

 
Chapter 10. Configuring
-TwinViewChapter 10. Specifying
+OpenGL Environment Variable Settings
 

 

 
 

 

 

-
Chapter 10. Configuring
-TwinView

+
Chapter 10. Specifying OpenGL
+Environment Variable Settings

 

 

 

-
TwinView is a mode of operation where two display devices
-(digital flat panels, CRTs, and TVs) can display the contents of a
-single X screen in any arbitrary configuration. This method of
-multiple monitor use has several distinct advantages over other
-techniques (such as Xinerama):

-

-
    
-
  • 
-
    A single X screen is used. The NVIDIA driver conceals all
-information about multiple display devices from the X server; as
-far as X is concerned, there is only one screen.
    
-
    • 
-
  • 
-
    Both display devices share one frame buffer. Thus, all the
-functionality present on a single display (e.g., accelerated
-OpenGL) is available with TwinView.
    
-
    • 
-
  • 
-
    No additional overhead is needed to emulate having a single
-desktop.
    
-
    • 
-

-

-
If you are interested in using each display device as a separate
-X screen, see Chapter 12,
-Configuring Multiple X Screens on One Card.

-
X Config TwinView Options

-
To enable TwinView, you must specify the following option in the
-Device section of your X Config file:

-
-    Option "TwinView"
-

-
You may also use any of the following options, though they are
-not required:

-
-    Option "MetaModes"                "<list of MetaModes>"
-
-    Option "SecondMonitorHorizSync"   "<hsync range(s)>"
-    Option "SecondMonitorVertRefresh" "<vrefresh range(s)>"
+
Full scene antialiasing

+
Antialiasing is a technique used to smooth the edges of objects
+in a scene to reduce the jagged "stairstep" effect that sometimes
+appears. By setting the appropriate environment variable, you can
+enable full-scene antialiasing in any OpenGL application on these
+GPUs.

+
Several antialiasing methods are available and you can select
+between them by setting the __GL_FSAA_MODE environment variable
+appropriately. Note that increasing the number of samples taken
+during FSAA rendering may decrease performance.

+
To see the available values for __GL_FSAA_MODE along with their
+descriptions, run:

+
+    nvidia-settings --query=fsaa --verbose
+

+
The __GL_FSAA_MODE environment variable uses the same integer
+values that are used to configure FSAA through nvidia-settings and
+the NV-CONTROL X extension. In other words, these two commands are
+equivalent:

+
+    export __GL_FSAA_MODE=5
 
-    Option "HorizSync"                "<hsync range(s)>"
-    Option "VertRefresh"              "<vrefresh range(s)>"
-
-    Option "TwinViewOrientation"      "<relationship of head 1 to head 0>"
-    Option "ConnectedMonitor"         "<list of connected display devices>"
-

-
See detailed descriptions of each option below.

-
Alternatively, you can enable TwinView by running

-
-    nvidia-xconfig --twinview
-

-
and restarting your X server. Or, you can configure TwinView
-dynamically in the "Display Configuration" page in
-nvidia-settings.

-
Detailed Description of Options

-

-

-
TwinView

-

-
This option is required to enable TwinView; without it, all
-other TwinView related options are ignored.

-

-
SecondMonitorHorizSync, SecondMonitorVertRefresh,

-

-
You specify the constraints of the second monitor through these
-options. The values given should follow the same convention as the
-"HorizSync" and "VertRefresh" entries in the Monitor section. As
-the XF86Config man page explains it: the ranges may be a comma
-separated list of distinct values and/or ranges of values, where a
-range is given by two distinct values separated by a dash. The
-HorizSync is given in kHz, and the VertRefresh is given in Hz.

-
These options are normally not needed: by default, the NVIDIA X
-driver retrieves the valid frequency ranges from the display
-device's EDID (see Appendix F, X
-Config Options for a description of the "UseEdidFreqs"
-option). The SecondMonitor options will override any frequency
-ranges retrieved from the EDID.

-

-
HorizSync, VertRefresh,

-

-
Which display device is "first" and which is "second" is often
-unclear. For this reason, you may use these options instead of the
-SecondMonitor versions. With these options, you can specify a
-semicolon-separated list of frequency ranges, each optionally
-prepended with a display device name. For example:

-
-    Option "HorizSync"   "CRT-0: 50-110;  DFP-0: 40-70"
-    Option "VertRefresh" "CRT-0: 60-120;  DFP-0: 60"
+    nvidia-settings --assign FSAA=5
 

-
See Appendix G,
-Display Device Names on Display Device Names for more
-information.

-
These options are normally not needed: by default, the NVIDIA X
-driver retrieves the valid frequency ranges from the display
-device's EDID (see Appendix F, X
-Config Options for a description of the "UseEdidFreqs"
-option). The "HorizSync" and "VertRefresh" options override any
-frequency ranges retrieved from the EDID or any frequency ranges
-specified with the "SecondMonitorHorizSync" and
-"SecondMonitorVertRefresh" options.

-

-
MetaModes

-

-
MetaModes are "containers" that store information about what
-mode should be used on each display device at any given time. Even
-if only one display device is actively in use, the NVIDIA X driver
-always uses a MetaMode to encapsulate the mode information per
-display device, so that it can support dynamically enabling
-TwinView.

-
Multiple MetaModes list the combinations of modes and the
-sequence in which they should be used. When the NVIDIA driver tells
-X what modes are available, it is really the minimal bounding box
-of the MetaMode that is communicated to X, while the "per display
-device" mode is kept internal to the NVIDIA driver. In MetaMode
-syntax, modes within a MetaMode are comma separated, and multiple
-MetaModes are separated by semicolons. For example:

+
Note that there are three FSAA related configuration attributes
+(FSAA, FSAAAppControlled and FSAAAppEnhanced) which together
+determine how a GL application will behave. If FSAAAppControlled is
+1, the FSAA specified through nvidia-settings will be ignored, in
+favor of what the application requests through FBConfig selection.
+If FSAAAppControlled is 0 but FSAAAppEnhanced is 1, then the FSAA
+value specified through nvidia-settings will only be applied if the
+application selected a multisample FBConfig.

+
Therefore, to be completely correct, the nvidia-settings command
+line to unconditionally assign FSAA should be:

 
-    "<mode name 0>, <mode name 1>; <mode name 2>, <mode name 3>"
-

-
Where <mode name 0> is the name of the mode to be used on
-display device 0 concurrently with <mode name 1> used on
-display device 1. A mode switch will then cause <mode name 2>
-to be used on display device 0 and <mode name 3> to be used
-on display device 1. Here is an example MetaMode:

-
-    Option "MetaModes" "1280x1024,1280x1024; 1024x768,1024x768"
-

-
If you want a display device to not be active for a certain
-MetaMode, you can use the mode name "NULL", or simply omit the mode
-name entirely:

-
-    "1600x1200, NULL; NULL, 1024x768"
-

-
or

-
-    "1600x1200; , 1024x768"
-

-
Optionally, mode names can be followed by offset information to
-control the positioning of the display devices within the virtual
-screen space; e.g.,

-
-    "1600x1200 +0+0, 1024x768 +1600+0; ..."
-

-
Offset descriptions follow the conventions used in the X
-"-geometry" command line option; i.e., both positive and negative
-offsets are valid, though negative offsets are only allowed when a
-virtual screen size is explicitly given in the X config file.

-
When no offsets are given for a MetaMode, the offsets will be
-computed following the value of the TwinViewOrientation option (see
-below). Note that if offsets are given for any one of the modes in
-a single MetaMode, then offsets will be expected for all modes
-within that single MetaMode; in such a case offsets will be assumed
-to be +0+0 when not given.

-
When not explicitly given, the virtual screen size will be
-computed as the the bounding box of all MetaMode bounding boxes.
-MetaModes with a bounding box larger than an explicitly given
-virtual screen size will be discarded.

-
A MetaMode string can be further modified with a "Panning
-Domain" specification; e.g.,

-
-    "1024x768 @1600x1200, 800x600 @1600x1200"
-

-
A panning domain is the area in which a display device's
-viewport will be panned to follow the mouse. Panning actually
-happens on two levels with TwinView: first, an individual display
-device's viewport will be panned within its panning domain, as long
-as the viewport is contained by the bounding box of the MetaMode.
-Once the mouse leaves the bounding box of the MetaMode, the entire
-MetaMode (i.e., all display devices) will be panned to follow the
-mouse within the virtual screen. Note that individual display
-devices' panning domains default to being clamped to the position
-of the display devices' viewports, thus the default behavior is
-just that viewports remain "locked" together and only perform the
-second type of panning.

-
The most beneficial use of panning domains is probably to
-eliminate dead areas -- regions of the virtual screen that are
-inaccessible due to display devices with different resolutions. For
-example:

-
-    "1600x1200, 1024x768"
-

-
produces an inaccessible region below the 1024x768 display.
-Specifying a panning domain for the second display device:

-
-    "1600x1200, 1024x768 @1024x1200"
-

-
provides access to that dead area by allowing you to pan the
-1024x768 viewport up and down in the 1024x1200 panning domain.

-
Offsets can be used in conjunction with panning domains to
-position the panning domains in the virtual screen space (note that
-the offset describes the panning domain, and only affects the
-viewport in that the viewport must be contained within the panning
-domain). For example, the following describes two modes, each with
-a panning domain width of 1900 pixels, and the second display is
-positioned below the first:

-
-    "1600x1200 @1900x1200 +0+0, 1024x768 @1900x768 +0+1200"
-

-
Because it is often unclear which mode within a MetaMode will be
-used on each display device, mode descriptions within a MetaMode
-can be prepended with a display device name. For example:

-
-    "CRT-0: 1600x1200,  DFP-0: 1024x768"
-

-
If no MetaMode string is specified, then the X driver uses the
-modes listed in the relevant "Display" subsection, attempting to
-place matching modes on each display device.

-

-
TwinViewOrientation

-

-
This option controls the positioning of the second display
-device relative to the first within the virtual X screen, when
-offsets are not explicitly given in the MetaModes. The possible
-values are:

-
-    "RightOf"  (the default)
-    "LeftOf"
-    "Above"
-    "Below"
-    "Clone"
-

-
When "Clone" is specified, both display devices will be assigned
-an offset of 0,0.

-
Because it is often unclear which display device is "first" and
-which is "second", TwinViewOrientation can be confusing. You can
-further clarify the TwinViewOrientation with display device names
-to indicate which display device is positioned relative to which
-display device. For example:

-
-    "CRT-0 LeftOf DFP-0"
+    nvidia-settings --assign FSAA=5 --assign FSAAAppControlled=0 --assign FSAAAppEnhanced=0
 

 

-

-
ConnectedMonitor

-

-
With this option you can override what the NVIDIA kernel module
-detects is connected to your graphics card. This may be useful, for
-example, if any of your display devices do not support detection
-using Display Data Channel (DDC) protocols. Valid values are a
-comma-separated list of display device names; for example:

-
-    "CRT-0, CRT-1"
-    "CRT"
-    "CRT-1, DFP-0"
-

-
WARNING: this option overrides what display devices are detected
-by the NVIDIA kernel module, and is very seldom needed. You really
-only need this if a display device is not detected, either because
-it does not provide DDC information, or because it is on the other
-side of a KVM (Keyboard-Video-Mouse) switch. In most other cases,
-it is best not to specify this option.

-

-

-

-
Just as in all X config entries, spaces are ignored and all
-entries are case insensitive.

-
Dynamic TwinView

-
Using the NV-CONTROL X extension, the display devices in use by
-an X screen, the mode pool for each display device, and the
-MetaModes for each X screen can be dynamically manipulated. The
-"Display Configuration" page in nvidia-settings uses this
-functionality to modify the MetaMode list and then uses XRandR to
-switch between MetaModes. This gives the ability to dynamically
-configure TwinView.

-
The details of how this works are documented in the
-nv-control-dpy.c sample NV-CONTROL client in the nvidia-settings
-source tarball.

-
Because the NVIDIA X driver can now transition into and out of
-TwinView dynamically, MetaModes are always used internally by the
-NVIDIA X driver, regardless of how many display devices are
-currently in use by the X screen and regardless of whether the
-TwinView X configuration option was specified.

-
One implication of this implementation is that each MetaMode
-must be uniquely identifiable to the XRandR X extension.
-Unfortunately, two MetaModes with the same bounding box will look
-the same to XRandR. For example, two MetaModes with different
-orientations:

-
-    "CRT: 1600x1200 +0+0, DFP: 1600x1200 +1600+0"
-    "CRT: 1600x1200 +1600+0, DFP: 1600x1200 +0+0"
-

-
will look identical to the XRandR or XF86VidMode X extensions,
-because they have the same total size (3200x1200), and
-nvidia-settings would not be able to use XRandR to switch between
-these MetaModes. To work around this limitation, the NVIDIA X
-driver "lies" about the refresh rate of each MetaMode, using the
-refresh rate of the MetaMode as a unique identifier.

-
The XRandR extension is currently being redesigned by the X.Org
-community, so the refresh rate workaround may be removed at some
-point in the future. This workaround can also be disabled by
-setting the "DynamicTwinView" X configuration option to FALSE,
-which will disable NV-CONTROL support for manipulating MetaModes,
-but will cause the XRandR and XF86VidMode visible refresh rate to
-be accurate.

-

-
--
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
Anisotropic texture filtering

+
Automatic anisotropic texture filtering can be enabled by
+setting the environment variable __GL_LOG_MAX_ANISO. The possible
+values are:

+

+



-
10.1.
-Frequently Asked TwinView Questions

-

-
Nothing gets displayed on my second monitor; what is
-wrong?

-

-
Monitors that do not support monitor detection using Display
-Data Channel (DDC) protocols (this includes most older monitors)
-are not detectable by your NVIDIA card. You need to explicitly tell
-the NVIDIA X driver what you have connected using the
-"ConnectedMonitor" option; e.g.,

-
-    Option "ConnectedMonitor" "CRT, CRT"
-

-

-

-
Will window managers be able to appropriately place windows
-(e.g., avoiding placing windows across both display devices, or in
-inaccessible regions of the virtual desktop)?

-

+++
+
+
+
+
-
-
-
+
+
+
+
+
-
-
-
+
+
+
-
-
-
+
+
+
-
-
-
+
+
+
-
-
-
+
+
+
-
-
-
+
+



__GL_LOG_MAX_ANISOFiltering Type
 

-
Yes. The NVIDIA X driver provides a Xinerama extension that X
-clients (such as window managers) can use to discover the current
-TwinView configuration. Note that the Xinerama protocol provides no
-way to notify clients when a configuration change occurs, so if you
-modeswitch to a different MetaMode, your window manager will still
-think you have the previous configuration. Using the Xinerama
-extension, in conjunction with the XF86VidMode extension to get
-modeswitch events, window managers should be able to determine the
-TwinView configuration at any given time.

-
Unfortunately, the data provided by XineramaQueryScreens()
-appears to confuse some window managers; to work around such broken
-window mangers, you can disable communication of the TwinView
-screen layout with the "NoTwinViewXineramaInfo" X config Option
-(see Appendix F, X
-Config Options for details).

-
The order that display devices are reported in via the TwinView
-Xinerama information can be configured with the
-TwinViewXineramaInfoOrder X configuration option.

-
Be aware that the NVIDIA driver cannot provide the Xinerama
-extension if the X server's own Xinerama extension is being used.
-Explicitly specifying Xinerama in the X config file or on the X
-server commandline will prohibit NVIDIA's Xinerama extension from
-installing, so make sure that the X server's log file does not
-contain:

-
-    (++) Xinerama: enabled
-

-
if you want the NVIDIA driver to be able to provide the Xinerama
-extension while in TwinView.

-
Another solution is to use panning domains to eliminate
-inaccessible regions of the virtual screen (see the MetaMode
-description above).

-
A third solution is to use two separate X screens, rather than
-use TwinView. See Chapter 12,
-Configuring Multiple X Screens on One Card.

-
0No anisotropic filtering
 

-
Why can I not get a resolution of 1600x1200 on the second
-display device when using a GeForce2 MX?

-
12x anisotropic filtering
 

-
Because the second display device on the GeForce2 MX was
-designed to be a digital flat panel, the Pixel Clock for the second
-display device is only 150 MHz. This effectively limits the
-resolution on the second display device to somewhere around
-1280x1024 (for a description of how Pixel Clock frequencies limit
-the programmable modes, see the XFree86 Video Timings HOWTO). This
-constraint is not present on GeForce4 or GeForce FX GPUs -- the
-maximum pixel clock is the same on both heads.

-
24x anisotropic filtering
 

-
Do video overlays work across both display devices?

-
38x anisotropic filtering
 

-
Hardware video overlays only work on the first display device.
-The current solution is that blitted video is used instead on
-TwinView.

-
416x anisotropic filtering
 

-
How are virtual screen dimensions determined in
-TwinView?

-

+

+
4x and greater are only available on GeForce3 or newer GPUs; 16x
+is only available on GeForce 6800 or newer GPUs.

+
Vblank syncing

+
Setting the environment variable __GL_SYNC_TO_VBLANK to a
+non-zero value will force glXSwapBuffers to sync to your monitor's
+vertical refresh (perform a swap only during the vertical blanking
+period).

+
When using __GL_SYNC_TO_VBLANK with TwinView, OpenGL can only
+sync to one of the display devices; this may cause tearing
+corruption on the display device to which OpenGL is not syncing.
+You can use the environment variable __GL_SYNC_DISPLAY_DEVICE to
+specify to which display device OpenGL should sync. You should set
+this environment variable to the name of a display device; for
+example "CRT-1". Look for the line "Connected display device(s):"
+in your X log file for a list of the display devices present and
+their names. You may also find it useful to review Chapter 12,
+Configuring TwinView "Configuring Twinview" and the
+section on Ensuring Identical Mode Timings in Chapter 18,
+Programming Modes.

+
Controlling the sorting of OpenGL FBConfigs

+
The NVIDIA GLX implementation sorts FBConfigs returned by
+glXChooseFBConfig() as described in the GLX specification. To
+disable this behavior set __GL_SORT_FBCONFIGS to 0 (zero), then
+FBConfigs will be returned in the order they were received from the
+X server. To examine the order in which FBConfigs are returned by
+the X server run:

+
+nvidia-settings --glxinfo
+

+
This option may be be useful to work around problems in which
+applications pick an unexpected FBConfig.

+
OpenGL yield behavior

+
There are several cases where the NVIDIA OpenGL driver needs to
+wait for external state to change before continuing. To avoid
+consuming too much CPU time in these cases, the driver will
+sometimes yield so the kernel can schedule other processes to run
+while the driver waits. For example, when waiting for free space in
+a command buffer, if the free space has not become available after
+a certain number of iterations, the driver will yield before it
+continues to loop.

+
By default, the driver calls sched_yield() to do this. However,
+this can cause the calling process to be scheduled out for a
+relatively long period of time if there are other, same-priority
+processes competing for time on the CPU. One example of this is
+when an OpenGL-based composite manager is moving and repainting a
+window and the X server is trying to update the window as it moves,
+which are both CPU-intensive operations.

+
You can use the __GL_YIELD environment variable to work around
+these scheduling problems. This variable allows the user to specify
+what the driver should do when it wants to yield. The possible
+values are:

+

+
+++
+
+
+
+
-
-
-
+
+
+
+
+
-
-
-
+
+
+
-
-
-
+
+
+



__GL_YIELDBehavior
 

-
After all requested modes have been validated, and the offsets
-for each MetaMode's viewports have been computed, the NVIDIA driver
-computes the bounding box of the panning domains for each MetaMode.
-The maximum bounding box width and height is then found.

-
Note that one side effect of this is that the virtual width and
-virtual height may come from different MetaModes. Given the
-following MetaMode string:

-
-    "1600x1200,NULL; 1024x768+0+0, 1024x768+0+768"
-

-
the resulting virtual screen size will be 1600 x 1536.

-
<unset>By default, OpenGL will call sched_yield() to yield.
 

-
Can I play full screen games across both display
-devices?

-
"NOTHING"OpenGL will never yield.
 

-
Yes. While the details of configuration will vary from game to
-game, the basic idea is that a MetaMode presents X with a mode
-whose resolution is the bounding box of the viewports for that
-MetaMode. For example, the following:

-
-    Option "MetaModes" "1024x768,1024x768; 800x600,800x600"
-    Option "TwinViewOrientation" "RightOf"
-

-
produce two modes: one whose resolution is 2048x768, and another
-whose resolution is 1600x600. Games such as Quake 3 Arena use the
-VidMode extension to discover the resolutions of the modes
-currently available. To configure Quake 3 Arena to use the above
-MetaMode string, add the following to your q3config.cfg file:

-
-    seta r_customaspect "1"
-    seta r_customheight "600"
-    seta r_customwidth  "1600"
-    seta r_fullscreen   "1"
-    seta r_mode         "-1"
-

-
Note that, given the above configuration, there is no mode with
-a resolution of 800x600 (remember that the MetaMode "800x600,
-800x600" has a resolution of 1600x600"), so if you change Quake 3
-Arena to use a resolution of 800x600, it will display in the lower
-left corner of your screen, with the rest of the screen grayed out.
-To have single head modes available as well, an appropriate
-MetaMode string might be something like:

-
-    "800x600,800x600; 1024x768,NULL; 800x600,NULL; 640x480,NULL"
-

-
More precise configuration information for specific games is
-beyond the scope of this document, but the above examples coupled
-with numerous online sources should be enough to point you in the
-right direction.

-
"USLEEP"OpenGL will call usleep(0) to yield.
 

 
 

 

+

+
Controlling which OpenGL FBConfigs are available

+
The NVIDIA GLX implementation will hide FBConfigs that are
+associated with a 32-bit ARGB visual when the
+XLIB_SKIP_ARGB_VISUALS environment variable is defined. This
+matches the behavior of libX11, which will hide those visuals from
+XGetVisualInfo and XMatchVisualInfo. This environment variable is
+useful when applications are confused by the presence of these
+FBConfigs.

+

+
Using Unofficial GLX protocol

+
By default, the NVIDIA GLX implementation will not expose GLX
+protocol for GL commands if the protocol is not considered
+complete. Protocol could be considered incomplete for a number of
+reasons. The implementation could still be under development and
+contain known bugs, or the protocol specification itself could be
+under development or going through review. If users would like to
+test the client-side portion of such protocol when using indirect
+rendering, they can set the __GL_ALLOW_UNOFFICIAL_PROTOCOL
+environment variable to a non-zero value before starting their GLX
+application. When an NVIDIA GLX server is used, the related X
+Config option AllowUnofficialGLXProtocol
+will need to be set as well to enable support in the server.

 
 

 

@@ -550,11 +241,11 @@ right direction.

 

 

 
-Chapter 9. Configuring AGP 
 Home
 
- Chapter 11. Configuring GLX in Xinerama
 

 

 

diff --git a/doc/html/chapter-11.html b/doc/html/chapter-11.html
index 295e47b..09b9fd4 100644
--- a/doc/html/chapter-11.html
+++ b/doc/html/chapter-11.html
@@ -5,23 +5,23 @@
 "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org">
 
-Chapter 11. Configuring GLX in Xinerama
+Chapter 11. Configuring AGP
 
 
 
 
+"Chapter 10. Specifying OpenGL Environment Variable Settings">
 
+"Chapter 12. Configuring TwinView">
 
 
 

 
+AGP
+Chapter 10. Specifying OpenGL Environment Variable
+Settings 
+ Chapter 12. Configuring TwinView

 

 Chapter 11. Configuring
-GLX in Xinerama
 

 

 
 

 

 

-
Chapter 11. Configuring GLX in
-Xinerama

+
Chapter 11. Configuring AGP

 

 

 

-
The NVIDIA FreeBSD Driver supports GLX when Xinerama is enabled
-on similar GPUs. The Xinerama extension takes multiple physical X
-screens (possibly spanning multiple GPUs), and binds them into one
-logical X screen. This allows windows to be dragged between GPUs
-and to span across multiple GPUs. The NVIDIA driver supports
-hardware accelerated OpenGL rendering across all NVIDIA GPUs when
-Xinerama is enabled.

-
To configure Xinerama

-

-
    
-
  1. 
-
    Configure multiple X screens (refer to the XF86Config(5x) or
-xorg.conf(5x) man pages for details).
    
-
    2. 
-
  2. 
-
    Enable Xinerama by adding the line
    
+
    There are several choices for configuring the NVIDIA kernel
+module's use of AGP: you can choose to either use the NVIDIA AGP
+module (NVAGP), or the AGP module that comes with the FreeBSD
+kernel (AGPGART). This is controlled through the "NvAGP" option in
+your X config file:
    
 
    -    Option "Xinerama" "True"
+    Option "NvAgp" "0"  ... disables AGP support
+    Option "NvAgp" "1"  ... use NVAGP, if possible
+    Option "NvAgp" "2"  ... use AGPGART, if possible
+    Option "NvAGP" "3"  ... try AGPGART; if that fails, try NVAGP
 
    
-
    to the "ServerFlags" section of your X config file.
    
-
    3. 
-

-

-

-
Requirements:

-

-
    
-
  • 
-
    Using identical GPUs is recommended. Some combinations of
-non-identical, but similar, GPUs are supported. If a GPU is
-incompatible with the rest of a Xinerama desktop then no OpenGL
-rendering will appear on the screens driven by that GPU. Rendering
-will still appear normally on screens connected to other supported
-GPUs. In this situation the X log file will include a message of
-the form:
    
+
    Unlike other operating systems such as Linux, this option is not
+the only controlling factor at this point; because of known
+problems, nvidia.ko is built without
+support for FreeBSD's AGP driver by default. This behavior can be
+changed, see nv-freebsd.h for
+details.
    
+
    Note that if you built nvidia.ko with support for the FreeBSD
+driver it will not load unless agp.ko
+is loaded. agp.ko is special in that
+you can not load it after the system boot is complete, you need to
+append the following line to /boot/loader.conf to make sure it is
+pre-loaded:
    
 
    -(WW) NVIDIA(2): The GPU driving screen 2 is incompatible with the rest of
-(WW) NVIDIA(2):      the GPUs composing the desktop.  OpenGL rendering will
-(WW) NVIDIA(2):      be disabled on screen 2.
-
    • 
-
  • 
-
    The NVIDIA X driver must be used for all X screens in the
-server.
    
-
    • 
-
  • 
-
    Only the intersection of capabilities across all GPUs will be
-advertised.
    
-
    The maximum OpenGL viewport size depends on the hardware used,
-and is described by the following table. If an OpenGL window is
-larger than the maximum viewport, regions beyond the viewport will
-be blank.
    
+    # -- load FreeBSD AGP GART driver -- #
+    agp_load="YES"
+
+
    Also note that if agp.ko is
+loaded, it could conflict with the NVIDIA AGP GART driver (NvAGP),
+resulting in stability problems; for this reason, the NVIDIA driver
+will abort NvAGP initialization when it detects agp.ko.
    
+
    Current FreeBSD releases are shipped with agp.ko built into the kernel; in order to allow
+NvAGP to work, the kernel can be rebuilt without 'device agp' or
+the following entry added to /boot/device.hints:
    
+
    +    hint.agp.0.disabled="1"
+
    
+
    When built with support for the FreeBSD AGP driver, nvidia.ko will fall back to using NvAGP when it
+doesn't detect agp.ko (this will be
+the case when agp.ko does not support
+your AGP chipset or was explicitly disabled with device hints).
    
+
    It is highly recommended that you use the NVIDIA AGP driver.
    
+
    The following AGP chipsets are supported by the NVIDIA AGP
+driver; for all other chipsets it is recommended that you use the
+AGPGART module.
    
 
    
 
-
+
-
    
 
 
 
 
    OpenGL Viewport Maximums in XineramaSupported AGP Chipsets
 
    
 
    
-
---
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
-
+
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    


 
 
    GeForce GPUs before GeForce 8:4096 x 4096 pixelsIntel 440LX
    Intel 440BX
    Intel 440GX
    Intel 815 ("Solano")
    Intel 820 ("Camino")
    Intel 830M
    Intel 840 ("Carmel")
    Intel 845 ("Brookdale")
    Intel 845G
    Intel 850 ("Tehama")
    Intel 855 ("Odem")
    Intel 860 ("Colusa")
    Intel 865G ("Springdale")
    Intel 875P ("Canterwood")
    Intel E7205 ("Granite Bay")
    Intel E7505 ("Placer")
    AMD 751 ("Irongate")
    AMD 761 ("IGD4")
    AMD 762 ("IGD4 MP")
    AMD 8151 ("Lokar")
    VIA 8371
    VIA 82C694X
    VIA KT133
    VIA KT266
    VIA KT400
    VIA P4M266
    VIA P4M266A
    VIA P4X400
    VIA K8T800
 
    
 
    GeForce 8 and newer GPUs:8192 x 8192 pixelsVIA K8N800
 
    
 
    Quadro:as large as the Xinerama desktopVIA PT880
    VIA KT880
    RCC CNB20LE
    RCC 6585HE
    Micron SAMDDR ("Samurai")
    Micron SCIDDR ("Scimitar")
    NVIDIA nForce
    NVIDIA nForce2
    NVIDIA nForce3
    ALi 1621
    ALi 1631
    ALi 1647
    ALi 1651
    ALi 1671
    SiS 630
    SiS 633
    SiS 635
    SiS 645
    SiS 646
    SiS 648
    SiS 648FX
    SiS 650
    SiS 651
    SiS 655
    SiS 655FX
    SiS 661
    SiS 730
    SiS 733
    SiS 735
    SiS 745
    SiS 755
    ATI RS200M
 
    
     
 
    
 
    
 
    
-
    • 
-
  • 
-
    X configuration options that affect GLX operation (e.g.: stereo,
-overlays) should be set consistently across all X screens in the X
-server.
    
-
    • 
-

-

-

-
Known Issues:

-

-
    
-
  • 
-
    Versions of XFree86 prior to 4.5 and versions of X.Org prior to
-6.8.0 lack the required interfaces to properly implement overlays
-with the Xinerama extension. On earlier server versions mixing
-overlays and Xinerama will result in rendering corruption. If you
-are using the Xinerama extension with overlays, it is recommended
-that you upgrade to XFree86 4.5, X.Org 6.8.0, or newer.
    
-
    • 
-

+
If you are experiencing AGP stability problems, you should be
+aware of the following:

+

+
Additional AGP Information

+

+
AGP drive strength BIOS setting (Via-based
+motherboards)

+

+
Many Via-based motherboards allow adjusting the AGP drive
+strength in the system BIOS. The setting of this option largely
+affects system stability, the range between 0xEA and 0xEE seems to
+work best for NVIDIA hardware. Setting either nibble to 0xF
+generally results in severe stability problems.

+
If you decide to experiment with this, you need to be aware of
+the fact that you are doing so at your own risk and that you may
+render your system unbootable with improper settings until you
+reset the setting to a working value (w/ a PCI graphics card or by
+resetting the BIOS to its default values).

+

+
System BIOS version

+

+
Make sure you have the latest system BIOS provided by the
+motherboard manufacturer.

+
On ALi1541 and ALi1647 chipsets, NVIDIA drivers disable AGP to
+work around timing and signal integrity problems. You can force AGP
+to be enabled on these chipsets by setting NVreg_EnableALiAGP to 1.
+Note that this may cause the system to become unstable.

+
Early system BIOS revisions for the ASUS A7V8X-X KT400
+motherboard misconfigure the chipset when an AGP 2.x graphics card
+is installed; if X hangs on your ASUS KT400 system with NvAGP
+enabled and the installed graphics card is not an AGP 8x device,
+make sure that you have the latest system BIOS installed.

+

+

 

 

 

@@ -162,12 +342,12 @@ that you upgrade to XFree86 4.5, X.Org 6.8.0, or newer.

 

 

 
-Chapter 10. Configuring TwinView 
 Home
 
- Chapter 12. Configuring Multiple X Screens on One
-Card
 

 

 

diff --git a/doc/html/chapter-12.html b/doc/html/chapter-12.html
index 3442984..6dfcc2b 100644
--- a/doc/html/chapter-12.html
+++ b/doc/html/chapter-12.html
@@ -5,24 +5,23 @@
 "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org">
 
-Chapter 12. Configuring Multiple X Screens on One
-Card
+Chapter 12. Configuring TwinView
 
 
 
 
+"Chapter 11. Configuring AGP">
 
+"Chapter 13. Configuring GLX in Xinerama">
 
 
 

 
+TwinView
+Chapter 11. Configuring AGP 
+ Chapter 13. Configuring GLX in Xinerama

 

 Chapter 12. Configuring
-Multiple X Screens on One Card
 

 

 
 

 

 

-
Chapter 12. Configuring Multiple
-X Screens on One Card

+
Chapter 12. Configuring
+TwinView

 

 

 

-
GPUs that support TwinView (Chapter 10,
-Configuring TwinView) can also be configured to treat
-each connected display device as a separate X screen.

-
While there are several disadvantages to this approach as
-compared to TwinView (e.g.: windows cannot be dragged between X
-screens, hardware accelerated OpenGL cannot span the two X
-screens), it does offer several advantages over TwinView:

+
TwinView is a mode of operation where two display devices
+(digital flat panels, CRTs, and TVs) can display the contents of a
+single X screen in any arbitrary configuration. This method of
+multiple monitor use has several distinct advantages over other
+techniques (such as Xinerama):

 

 
    
 
  • 
-
    If each display device is a separate X screen, then properties
-that may vary between X screens may vary between displays (e.g.:
-depth, root window size, etc).
    
+
    A single X screen is used. The NVIDIA driver conceals all
+information about multiple display devices from the X server; as
+far as X is concerned, there is only one screen.
    
 
    • 
 
  • 
-
    Hardware that can only be used on one display at a time (e.g.:
-video overlays, hardware accelerated RGB overlays), and which
-consequently cannot be used at all when in TwinView, can be exposed
-on the first X screen when each display is a separate X screen.
    
+
    Both display devices share one frame buffer. Thus, all the
+functionality present on a single display (e.g., accelerated
+OpenGL) is available with TwinView.
    
 
    • 
 
  • 
-
    TwinView is a fairly new feature. X has historically used one
-screen per display device.
    
+
    No additional overhead is needed to emulate having a single
+desktop.
    
 
    • 
 

 

-

-
To configure two separate X screens to share one graphics card,
-here is what you will need to do:

-
First, create two separate Device sections, each listing the
-BusID of the graphics card to be shared and listing the driver as
-"nvidia", and assign each a separate screen:

-
-    Section "Device"
-        Identifier  "nvidia0"
-        Driver      "nvidia"
-        # Edit the BusID with the location of your graphics card
-        BusID       "PCI:2:0:0"
-        Screen      0
-    EndSection
+
If you are interested in using each display device as a separate
+X screen, see Chapter 14,
+Configuring Multiple X Screens on One Card.

+
X Config TwinView Options

+
To enable TwinView, you must specify the following option in the
+Device section of your X Config file:

+
+    Option "TwinView"
+

+
You may also use any of the following options, though they are
+not required:

+
+    Option "MetaModes"                "<list of MetaModes>"
+
+    Option "SecondMonitorHorizSync"   "<hsync range(s)>"
+    Option "SecondMonitorVertRefresh" "<vrefresh range(s)>"
 
-    Section "Device"
-        Identifier  "nvidia1"
-        Driver      "nvidia"
-        # Edit the BusID with the location of your graphics card
-        BusId       "PCI:2:0:0"
-        Screen      1
-    EndSection
-

-
Then, create two Screen sections, each using one of the Device
-sections:

-
-    Section "Screen"
-        Identifier  "Screen0"
-        Device      "nvidia0"
-        Monitor     "Monitor0"
-        DefaultDepth 24
-        Subsection "Display"
-            Depth       24
-            Modes       "1600x1200" "1024x768" "800x600" "640x480" 
-        EndSubsection
-    EndSection
+    Option "HorizSync"                "<hsync range(s)>"
+    Option "VertRefresh"              "<vrefresh range(s)>"
 
-    Section "Screen"
-        Identifier  "Screen1"
-        Device      "nvidia1"
-        Monitor     "Monitor1"
-        DefaultDepth 24
-        Subsection "Display"
-            Depth       24
-            Modes       "1600x1200" "1024x768" "800x600" "640x480" 
-        EndSubsection
-    EndSection
-

-
(Note: You'll also need to create a second Monitor section)
-Finally, update the ServerLayout section to use and position both
-Screen sections:

-
-    Section "ServerLayout"
-        ...
-        Screen         0 "Screen0" 
-        Screen         1 "Screen1" leftOf "Screen0"
-        ...
-    EndSection
-

-
For further details, refer to the XF86Config(5x) or
-xorg.conf(5x) man pages.

+    Option "TwinViewOrientation"      "<relationship of head 1 to head 0>"
+    Option "ConnectedMonitor"         "<list of connected display devices>"
+

+
See detailed descriptions of each option below.

+
Alternatively, you can enable TwinView by running

+
+    nvidia-xconfig --twinview
+

+
and restarting your X server. Or, you can configure TwinView
+dynamically in the "Display Configuration" page in
+nvidia-settings.

+
Detailed Description of Options

+

+

+
TwinView

+

+
This option is required to enable TwinView; without it, all
+other TwinView related options are ignored.

+

+
SecondMonitorHorizSync, SecondMonitorVertRefresh,

+

+
You specify the constraints of the second monitor through these
+options. The values given should follow the same convention as the
+"HorizSync" and "VertRefresh" entries in the Monitor section. As
+the XF86Config man page explains it: the ranges may be a comma
+separated list of distinct values and/or ranges of values, where a
+range is given by two distinct values separated by a dash. The
+HorizSync is given in kHz, and the VertRefresh is given in Hz.

+
These options are normally not needed: by default, the NVIDIA X
+driver retrieves the valid frequency ranges from the display
+device's EDID (see Appendix B, X
+Config Options for a description of the "UseEdidFreqs"
+option). The SecondMonitor options will override any frequency
+ranges retrieved from the EDID.

+

+
HorizSync, VertRefresh,

+

+
Which display device is "first" and which is "second" is often
+unclear. For this reason, you may use these options instead of the
+SecondMonitor versions. With these options, you can specify a
+semicolon-separated list of frequency ranges, each optionally
+prepended with a display device name. For example:

+
+    Option "HorizSync"   "CRT-0: 50-110;  DFP-0: 40-70"
+    Option "VertRefresh" "CRT-0: 60-120;  DFP-0: 60"
+

+
See Appendix C,
+Display Device Names on Display Device Names for more
+information.

+
These options are normally not needed: by default, the NVIDIA X
+driver retrieves the valid frequency ranges from the display
+device's EDID (see Appendix B, X
+Config Options for a description of the "UseEdidFreqs"
+option). The "HorizSync" and "VertRefresh" options override any
+frequency ranges retrieved from the EDID or any frequency ranges
+specified with the "SecondMonitorHorizSync" and
+"SecondMonitorVertRefresh" options.

+

+
MetaModes

+

+
MetaModes are "containers" that store information about what
+mode should be used on each display device at any given time. Even
+if only one display device is actively in use, the NVIDIA X driver
+always uses a MetaMode to encapsulate the mode information per
+display device, so that it can support dynamically enabling
+TwinView.

+
Multiple MetaModes list the combinations of modes and the
+sequence in which they should be used. When the NVIDIA driver tells
+X what modes are available, it is really the minimal bounding box
+of the MetaMode that is communicated to X, while the "per display
+device" mode is kept internal to the NVIDIA driver. In MetaMode
+syntax, modes within a MetaMode are comma separated, and multiple
+MetaModes are separated by semicolons. For example:

+
+    "<mode name 0>, <mode name 1>; <mode name 2>, <mode name 3>"
+

+
Where <mode name 0> is the name of the mode to be used on
+display device 0 concurrently with <mode name 1> used on
+display device 1. A mode switch will then cause <mode name 2>
+to be used on display device 0 and <mode name 3> to be used
+on display device 1. Here is an example MetaMode:

+
+    Option "MetaModes" "1280x1024,1280x1024; 1024x768,1024x768"
+

+
If you want a display device to not be active for a certain
+MetaMode, you can use the mode name "NULL", or simply omit the mode
+name entirely:

+
+    "1600x1200, NULL; NULL, 1024x768"
+

+
or

+
+    "1600x1200; , 1024x768"
+

+
Optionally, mode names can be followed by offset information to
+control the positioning of the display devices within the virtual
+screen space; e.g.,

+
+    "1600x1200 +0+0, 1024x768 +1600+0; ..."
+

+
Offset descriptions follow the conventions used in the X
+"-geometry" command line option; i.e., both positive and negative
+offsets are valid, though negative offsets are only allowed when a
+virtual screen size is explicitly given in the X config file.

+
When no offsets are given for a MetaMode, the offsets will be
+computed following the value of the TwinViewOrientation option (see
+below). Note that if offsets are given for any one of the modes in
+a single MetaMode, then offsets will be expected for all modes
+within that single MetaMode; in such a case offsets will be assumed
+to be +0+0 when not given.

+
When not explicitly given, the virtual screen size will be
+computed as the the bounding box of all MetaMode bounding boxes.
+MetaModes with a bounding box larger than an explicitly given
+virtual screen size will be discarded.

+
A MetaMode string can be further modified with a "Panning
+Domain" specification; e.g.,

+
+    "1024x768 @1600x1200, 800x600 @1600x1200"
+

+
A panning domain is the area in which a display device's
+viewport will be panned to follow the mouse. Panning actually
+happens on two levels with TwinView: first, an individual display
+device's viewport will be panned within its panning domain, as long
+as the viewport is contained by the bounding box of the MetaMode.
+Once the mouse leaves the bounding box of the MetaMode, the entire
+MetaMode (i.e., all display devices) will be panned to follow the
+mouse within the virtual screen, unless the "PanAllDisplays" X
+configuration option is disabled. Note that individual display
+devices' panning domains default to being clamped to the position
+of the display devices' viewports, thus the default behavior is
+just that viewports remain "locked" together and only perform the
+second type of panning.

+
The most beneficial use of panning domains is probably to
+eliminate dead areas -- regions of the virtual screen that are
+inaccessible due to display devices with different resolutions. For
+example:

+
+    "1600x1200, 1024x768"
+

+
produces an inaccessible region below the 1024x768 display.
+Specifying a panning domain for the second display device:

+
+    "1600x1200, 1024x768 @1024x1200"
+

+
provides access to that dead area by allowing you to pan the
+1024x768 viewport up and down in the 1024x1200 panning domain.

+
Offsets can be used in conjunction with panning domains to
+position the panning domains in the virtual screen space (note that
+the offset describes the panning domain, and only affects the
+viewport in that the viewport must be contained within the panning
+domain). For example, the following describes two modes, each with
+a panning domain width of 1900 pixels, and the second display is
+positioned below the first:

+
+    "1600x1200 @1900x1200 +0+0, 1024x768 @1900x768 +0+1200"
+

+
Because it is often unclear which mode within a MetaMode will be
+used on each display device, mode descriptions within a MetaMode
+can be prepended with a display device name. For example:

+
+    "CRT-0: 1600x1200,  DFP-0: 1024x768"
+

+
If no MetaMode string is specified, then the X driver uses the
+modes listed in the relevant "Display" subsection, attempting to
+place matching modes on each display device.

+

+
TwinViewOrientation

+

+
This option controls the positioning of the second display
+device relative to the first within the virtual X screen, when
+offsets are not explicitly given in the MetaModes. The possible
+values are:

+
+    "RightOf"  (the default)
+    "LeftOf"
+    "Above"
+    "Below"
+    "Clone"
+

+
When "Clone" is specified, both display devices will be assigned
+an offset of 0,0.

+
Because it is often unclear which display device is "first" and
+which is "second", TwinViewOrientation can be confusing. You can
+further clarify the TwinViewOrientation with display device names
+to indicate which display device is positioned relative to which
+display device. For example:

+
+    "CRT-0 LeftOf DFP-0"
+

+

+

+
ConnectedMonitor

+

+
With this option you can override what the NVIDIA kernel module
+detects is connected to your graphics card. This may be useful, for
+example, if any of your display devices do not support detection
+using Display Data Channel (DDC) protocols. Valid values are a
+comma-separated list of display device names; for example:

+
+    "CRT-0, CRT-1"
+    "CRT"
+    "CRT-1, DFP-0"
+

+
WARNING: this option overrides what display devices are detected
+by the NVIDIA kernel module, and is very seldom needed. You really
+only need this if a display device is not detected, either because
+it does not provide DDC information, or because it is on the other
+side of a KVM (Keyboard-Video-Mouse) switch. In most other cases,
+it is best not to specify this option.

+

+

+

+
Just as in all X config entries, spaces are ignored and all
+entries are case insensitive.

+
Dynamic TwinView

+
Using the NV-CONTROL X extension, the display devices in use by
+an X screen, the mode pool for each display device, and the
+MetaModes for each X screen can be dynamically manipulated. The
+"Display Configuration" page in nvidia-settings uses this
+functionality to modify the MetaMode list and then uses XRandR to
+switch between MetaModes. This gives the ability to dynamically
+configure TwinView.

+
The details of how this works are documented in the
+nv-control-dpy.c sample NV-CONTROL client in the nvidia-settings
+source tarball.

+
Because the NVIDIA X driver can now transition into and out of
+TwinView dynamically, MetaModes are always used internally by the
+NVIDIA X driver, regardless of how many display devices are
+currently in use by the X screen and regardless of whether the
+TwinView X configuration option was specified.

+
One implication of this implementation is that each MetaMode
+must be uniquely identifiable to the XRandR X extension.
+Unfortunately, two MetaModes with the same bounding box will look
+the same to XRandR. For example, two MetaModes with different
+orientations:

+
+    "CRT: 1600x1200 +0+0, DFP: 1600x1200 +1600+0"
+    "CRT: 1600x1200 +1600+0, DFP: 1600x1200 +0+0"
+

+
will look identical to the XRandR or XF86VidMode X extensions,
+because they have the same total size (3200x1200), and
+nvidia-settings would not be able to use XRandR to switch between
+these MetaModes. To work around this limitation, the NVIDIA X
+driver "lies" about the refresh rate of each MetaMode, using the
+refresh rate of the MetaMode as a unique identifier.

+
The XRandR extension is currently being redesigned by the X.Org
+community, so the refresh rate workaround may be removed at some
+point in the future. This workaround can also be disabled by
+setting the "DynamicTwinView" X configuration option to FALSE,
+which will disable NV-CONTROL support for manipulating MetaModes,
+but will cause the XRandR and XF86VidMode visible refresh rate to
+be accurate.

+

+
++
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+



+
12.1.
+Frequently Asked TwinView Questions

+

+
Nothing gets displayed on my second monitor; what is
+wrong?

+

+
Monitors that do not support monitor detection using Display
+Data Channel (DDC) protocols (this includes most older monitors)
+are not detectable by your NVIDIA card. You need to explicitly tell
+the NVIDIA X driver what you have connected using the
+"ConnectedMonitor" option; e.g.,

+
+    Option "ConnectedMonitor" "CRT, CRT"
+

+

+

+
Will window managers be able to appropriately place windows
+(e.g., avoiding placing windows across both display devices, or in
+inaccessible regions of the virtual desktop)?

+

+
Yes. The NVIDIA X driver provides a Xinerama extension that X
+clients (such as window managers) can use to discover the current
+TwinView configuration. Note that the Xinerama protocol provides no
+way to notify clients when a configuration change occurs, so if you
+modeswitch to a different MetaMode, your window manager will still
+think you have the previous configuration. Using the Xinerama
+extension, in conjunction with the XF86VidMode extension to get
+modeswitch events, window managers should be able to determine the
+TwinView configuration at any given time.

+
Unfortunately, the data provided by XineramaQueryScreens()
+appears to confuse some window managers; to work around such broken
+window mangers, you can disable communication of the TwinView
+screen layout with the "NoTwinViewXineramaInfo" X config Option
+(see Appendix B, X
+Config Options for details).

+
The order that display devices are reported in via the TwinView
+Xinerama information can be configured with the
+TwinViewXineramaInfoOrder X configuration option.

+
Be aware that the NVIDIA driver cannot provide the Xinerama
+extension if the X server's own Xinerama extension is being used.
+Explicitly specifying Xinerama in the X config file or on the X
+server commandline will prohibit NVIDIA's Xinerama extension from
+installing, so make sure that the X server's log file does not
+contain:

+
+    (++) Xinerama: enabled
+

+
if you want the NVIDIA driver to be able to provide the Xinerama
+extension while in TwinView.

+
Another solution is to use panning domains to eliminate
+inaccessible regions of the virtual screen (see the MetaMode
+description above).

+
A third solution is to use two separate X screens, rather than
+use TwinView. See Chapter 14,
+Configuring Multiple X Screens on One Card.

+

+
Why can I not get a resolution of 1600x1200 on the second
+display device when using a GeForce2 MX?

+

+
Because the second display device on the GeForce2 MX was
+designed to be a digital flat panel, the Pixel Clock for the second
+display device is only 150 MHz. This effectively limits the
+resolution on the second display device to somewhere around
+1280x1024 (for a description of how Pixel Clock frequencies limit
+the programmable modes, see the XFree86 Video Timings HOWTO). This
+constraint is not present on GeForce4 or GeForce FX GPUs -- the
+maximum pixel clock is the same on both heads.

+

+
Do video overlays work across both display devices?

+

+
Hardware video overlays only work on the first display device.
+The current solution is that blitted video is used instead on
+TwinView.

+

+
How are virtual screen dimensions determined in
+TwinView?

+

+
After all requested modes have been validated, and the offsets
+for each MetaMode's viewports have been computed, the NVIDIA driver
+computes the bounding box of the panning domains for each MetaMode.
+The maximum bounding box width and height is then found.

+
Note that one side effect of this is that the virtual width and
+virtual height may come from different MetaModes. Given the
+following MetaMode string:

+
+    "1600x1200,NULL; 1024x768+0+0, 1024x768+0+768"
+

+
the resulting virtual screen size will be 1600 x 1536.

+

+
Can I play full screen games across both display
+devices?

+

+
Yes. While the details of configuration will vary from game to
+game, the basic idea is that a MetaMode presents X with a mode
+whose resolution is the bounding box of the viewports for that
+MetaMode. For example, the following:

+
+    Option "MetaModes" "1024x768,1024x768; 800x600,800x600"
+    Option "TwinViewOrientation" "RightOf"
+

+
produce two modes: one whose resolution is 2048x768, and another
+whose resolution is 1600x600. Games such as Quake 3 Arena use the
+VidMode extension to discover the resolutions of the modes
+currently available. To configure Quake 3 Arena to use the above
+MetaMode string, add the following to your q3config.cfg file:

+
+    seta r_customaspect "1"
+    seta r_customheight "600"
+    seta r_customwidth  "1600"
+    seta r_fullscreen   "1"
+    seta r_mode         "-1"
+

+
Note that, given the above configuration, there is no mode with
+a resolution of 800x600 (remember that the MetaMode "800x600,
+800x600" has a resolution of 1600x600"), so if you change Quake 3
+Arena to use a resolution of 800x600, it will display in the lower
+left corner of your screen, with the rest of the screen grayed out.
+To have single head modes available as well, an appropriate
+MetaMode string might be something like:

+
+    "800x600,800x600; 1024x768,NULL; 800x600,NULL; 640x480,NULL"
+

+
More precise configuration information for specific games is
+beyond the scope of this document, but the above examples coupled
+with numerous online sources should be enough to point you in the
+right direction.

+

+

 
 

 

@@ -146,11 +551,11 @@ xorg.conf(5x) man pages.

 

 

 
-Chapter 11. Configuring GLX in Xinerama 
 Home
 
- Chapter 13. Configuring TV-Out
 

 

 

diff --git a/doc/html/chapter-13.html b/doc/html/chapter-13.html
index 8af38d5..f90427b 100644
--- a/doc/html/chapter-13.html
+++ b/doc/html/chapter-13.html
@@ -5,23 +5,23 @@
 "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org">
 
-Chapter 13. Configuring TV-Out
+Chapter 13. Configuring GLX in Xinerama
 
 
 
 
+"Chapter 12. Configuring TwinView">
 
+"Chapter 14. Configuring Multiple X Screens on One Card">
 
 
 

 
+GLX in Xinerama
+Chapter 12. Configuring TwinView 
+ Chapter 14. Configuring Multiple X Screens on One
+Card

 

 Chapter 13. Configuring
-TV-Out
 

 

 
 

 

 

-
Chapter 13. Configuring TV-Out

+
Chapter 13. Configuring GLX in
+Xinerama

 

 

 

-
NVIDIA GPU-based graphics cards with a TV-Out connector can use
-a television as another display device (the same way that it would
-use a CRT or digital flat panel). The TV can be used by itself, or
-in conjunction with another display device in a TwinView or
-multiple X screen configuration. If a TV is the only display device
-connected to your graphics card, it will be used as the primary
-display when you boot your system (i.e. the console will come up on
-the TV just as if it were a CRT).

-
The NVIDIA X driver populates the mode pool for the TV with all
-the mode sizes that the driver supports with the given TV standard
-and the TV encoder on the graphics card. These modes are given
-names that correspond to their resolution; e.g., "800x600".

-
Because these TV modes only depend on the TV encoder and the TV
-standard, TV modes do not go through normal mode validation. The X
-configuration options HorizSync and VertRefresh are not used for TV
-mode validation.

-
Additionally, the NVIDIA driver contains a hardcoded list of
-mode sizes that it can drive for each combination of TV encoder and
-TV standard. Therefore, custom modelines in your X configuration
-file are ignored for TVs.

-
To use your TV with X, there are several relevant X
-configuration options:

-

-
    
+
    The NVIDIA FreeBSD Driver supports GLX when Xinerama is enabled
+on similar GPUs. The Xinerama extension takes multiple physical X
+screens (possibly spanning multiple GPUs), and binds them into one
+logical X screen. This allows windows to be dragged between GPUs
+and to span across multiple GPUs. The NVIDIA driver supports
+hardware accelerated OpenGL rendering across all NVIDIA GPUs when
+Xinerama is enabled.
    
+
    To configure Xinerama
    
+
    
+
      
 
    1. 
-
      The Modes in the screen section of your X configuration file;
-you can use these to request any of the modes in the mode pool
-which the X driver created for this combination of TV standard and
-TV encoder. Examples include "640x480" and "800x600". If in doubt,
-use "nvidia-auto-select".
      
+
      Configure multiple X screens (refer to the XF86Config(5x) or
+xorg.conf(5x) man pages for details).
      
 
      2. 
 
    2. 
-
      The "TVStandard" option should be added to your screen section;
-valid values are:
      
-
      
-
---
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
      


      TVStandardDescription
      "PAL-B"used in Belgium, Denmark, Finland, Germany, Guinea, Hong Kong,
-India, Indonesia, Italy, Malaysia, The Netherlands, Norway,
-Portugal, Singapore, Spain, Sweden, and Switzerland
      "PAL-D"used in China and North Korea
      "PAL-G"used in Denmark, Finland, Germany, Italy, Malaysia, The
-Netherlands, Norway, Portugal, Spain, Sweden, and Switzerland
      "PAL-H"used in Belgium
      "PAL-I"used in Hong Kong and The United Kingdom
      "PAL-K1"used in Guinea
      "PAL-M"used in Brazil
      "PAL-N"used in France, Paraguay, and Uruguay
      "PAL-NC"used in Argentina
      "NTSC-J"used in Japan
      "NTSC-M"used in Canada, Chile, Colombia, Costa Rica, Ecuador, Haiti,
-Honduras, Mexico, Panama, Puerto Rico, South Korea, Taiwan, United
-States of America, and Venezuela
      "HD480i"480 line interlaced
      "HD480p"480 line progressive
      "HD720p"720 line progressive
      "HD1080i"1080 line interlaced
      "HD1080p"1080 line progressive
      "HD576i"576 line interlace
      "HD576p"576 line progressive
      
-
      
-
      The line in your X config file should be something like:
      
+
      Enable Xinerama by adding the line
      
 
      -    Option "TVStandard" "NTSC-M"
+    Option "Xinerama" "True"
 
      
-
      If you do not specify a TVStandard, or you specify an invalid
-value, the default "NTSC-M" will be used. Note: if your country is
-not in the above list, select the country closest to your
-location.
      
+
      to the "ServerFlags" section of your X config file.
      
 
      3. 
+
    
+
    
+
    
+
    Requirements:
    
+
    
+
      
 
    • 
-
      The "UseDisplayDevice" option can be used if there are multiple
-display devices connected, and you want the connected TV to be used
-instead of the connected CRTs and/or DFPs. E.g.,
      
+
      Using identical GPUs is recommended. Some combinations of
+non-identical, but similar, GPUs are supported. If a GPU is
+incompatible with the rest of a Xinerama desktop then no OpenGL
+rendering will appear on the screens driven by that GPU. Rendering
+will still appear normally on screens connected to other supported
+GPUs. In this situation the X log file will include a message of
+the form:
      
 
      -    Option "UseDisplayDevice" "TV"
-
      
-
      Using the "UseDisplayDevice" option, rather than the
-"ConnectedMonitor" option, is recommended.
      
+(WW) NVIDIA(2): The GPU driving screen 2 is incompatible with the rest of
+(WW) NVIDIA(2):      the GPUs composing the desktop.  OpenGL rendering will
+(WW) NVIDIA(2):      be disabled on screen 2.
+
      • 
+
    • 
+
      The NVIDIA X driver must be used for all X screens in the
+server.
      
 
      • 
 
    • 
-
      The "TVOutFormat" option can be used to force the output format.
-Without this option, the driver autodetects the output format.
-Unfortunately, it does not always do this correctly. The output
-format can be forced with the "TVOutFormat" option; valid values
-are:
      
+
      Only the intersection of capabilities across all GPUs will be
+advertised.
      
+
      The maximum OpenGL viewport size depends on the hardware used,
+and is described by the following table. If an OpenGL window is
+larger than the maximum viewport, regions beyond the viewport will
+be blank.
      
 
      
 -
-
-
-
+
+
      
 

 
 
 
      TVOutFormatDescriptionSupported TV standardsOpenGL Viewport Maximums in Xinerama
 
      
 
      
+
+++
-
-
-
+
+
-
-
-
+
+
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
      


 
 
      "AUTOSELECT"The driver autodetects the output format (default value).PAL, NTSC, HDGeForce GPUs before GeForce 8:4096 x 4096 pixels
 
      
 
      "COMPOSITE"Force Composite output formatPAL, NTSCGeForce 8 and newer GPUs:8192 x 8192 pixels
 
      
 
      "SVIDEO"Force S-Video output formatPAL, NTSC
      "COMPONENT"Force Component output format, also called YPbPrHD
      "SCART"Force Scart output format, also called PeritelPAL, NTSCQuadro:as large as the Xinerama desktop
 
      
       
 
      
 
      
-
      The line in your X config file should be something like:
      
-
      -    Option "TVOutFormat" "SVIDEO"
-
      
 
      
 
      • 
 
    • 
-
      The "TVOverScan" option can be used to enable Overscan, when the
-TV encoder supports it. Valid values are decimal values in the
-range 1.0 (which means overscan as much as possible: make the image
-as large as possible) and 0.0 (which means disable overscanning:
-make the image as small as possible). Overscanning is disabled
-(0.0) by default.
      
+
      X configuration options that affect GLX operation (e.g.: stereo,
+overlays) should be set consistently across all X screens in the X
+server.
      
 
      • 
 
    
 
    
-
    The NVIDIA X driver may not restore the console correctly with
-XFree86 versions older than 4.3 when the console is a TV. This is
-due to binary incompatibilities between XFree86 int10 modules. If
-you use a TV as your console it is recommended that you upgrade to
-XFree86 4.3 or later.
    
+
    
+
    Known Issues:
    
+
    
+
      
+
    • 
+
      Versions of XFree86 prior to 4.5 and versions of X.Org prior to
+6.8.0 lack the required interfaces to properly implement overlays
+with the Xinerama extension. On earlier server versions mixing
+overlays and Xinerama will result in rendering corruption. If you
+are using the Xinerama extension with overlays, it is recommended
+that you upgrade to XFree86 4.5, X.Org 6.8.0, or newer.
      
+
      • 
+
    
+
    
+
    
 

 

 

@@ -269,12 +162,12 @@ XFree86 4.3 or later.

 

 

 
-Chapter 12. Configuring Multiple X Screens on One
-Card 
 Home
 
- Chapter 14. Using the XRandR Extension
 

 

 

diff --git a/doc/html/chapter-14.html b/doc/html/chapter-14.html
index 6059038..059ddc5 100644
--- a/doc/html/chapter-14.html
+++ b/doc/html/chapter-14.html
@@ -5,23 +5,24 @@
 "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org">
 
-Chapter 14. Using the XRandR Extension
+Chapter 14. Configuring Multiple X Screens on One
+Card
 
 
 
 
+"Chapter 13. Configuring GLX in Xinerama">
 
+"Chapter 15. Configuring TV-Out">
 
 
 

 
-
+
+Chapter 13. Configuring GLX in Xinerama 
+ Chapter 15. Configuring TV-Out

 
Chapter 14. Using the
-XRandR ExtensionChapter 14. Configuring
+Multiple X Screens on One Card
 

 

 
 

 

 

-
Chapter 14. Using the XRandR
-Extension

+
Chapter 14. Configuring Multiple
+X Screens on One Card

 

 

 

-
X.Org version X11R6.8.1 contains support for the rotation
-component of the XRandR extension, which allows screens to be
-rotated at 90 degree increments.

-
The driver supports rotation with the extension when 'Option
-"RandRRotation"' is enabled in the X config file.

-
Workstation RGB or CI overlay visuals will function at lower
-performance and the video overlay will not be available when
-RandRRotation is enabled.

-
You can query the available rotations using the 'xrandr' command
-line interface to the RandR extension by running:

+
GPUs that support TwinView (Chapter 12,
+Configuring TwinView) can also be configured to treat
+each connected display device as a separate X screen.

+
While there are several disadvantages to this approach as
+compared to TwinView (e.g.: windows cannot be dragged between X
+screens, hardware accelerated OpenGL cannot span the two X
+screens), it does offer several advantages over TwinView:

+

+
    
+
  • 
+
    If each display device is a separate X screen, then properties
+that may vary between X screens may vary between displays (e.g.:
+depth, root window size, etc).
    
+
    • 
+
  • 
+
    Hardware that can only be used on one display at a time (e.g.:
+video overlays, hardware accelerated RGB overlays), and which
+consequently cannot be used at all when in TwinView, can be exposed
+on the first X screen when each display is a separate X screen.
    
+
    • 
+
  • 
+
    TwinView is a fairly new feature. X has historically used one
+screen per display device.
    
+
    • 
+

+

+

+
To configure two separate X screens to share one graphics card,
+here is what you will need to do:

+
First, create two separate Device sections, each listing the
+BusID of the graphics card to be shared and listing the driver as
+"nvidia", and assign each a separate screen:

+
+    Section "Device"
+        Identifier  "nvidia0"
+        Driver      "nvidia"
+        # Edit the BusID with the location of your graphics card
+        BusID       "PCI:2:0:0"
+        Screen      0
+    EndSection
+
+    Section "Device"
+        Identifier  "nvidia1"
+        Driver      "nvidia"
+        # Edit the BusID with the location of your graphics card
+        BusId       "PCI:2:0:0"
+        Screen      1
+    EndSection
+

+
Then, create two Screen sections, each using one of the Device
+sections:

 
-    xrandr -q
+    Section "Screen"
+        Identifier  "Screen0"
+        Device      "nvidia0"
+        Monitor     "Monitor0"
+        DefaultDepth 24
+        Subsection "Display"
+            Depth       24
+            Modes       "1600x1200" "1024x768" "800x600" "640x480" 
+        EndSubsection
+    EndSection
+
+    Section "Screen"
+        Identifier  "Screen1"
+        Device      "nvidia1"
+        Monitor     "Monitor1"
+        DefaultDepth 24
+        Subsection "Display"
+            Depth       24
+            Modes       "1600x1200" "1024x768" "800x600" "640x480" 
+        EndSubsection
+    EndSection
 

-
You can set the rotation orientation of the screen by running
-any of:

+
(Note: You'll also need to create a second Monitor section)
+Finally, update the ServerLayout section to use and position both
+Screen sections:

 
-    xrandr -o left
-    xrandr -o right
-    xrandr -o inverted
-    xrandr -o normal
+    Section "ServerLayout"
+        ...
+        Screen         0 "Screen0" 
+        Screen         1 "Screen1" leftOf "Screen0"
+        ...
+    EndSection
 

-
Rotation may also be set through the nvidia-settings
-configuration utility in the "Rotation Settings" panel.

-
SLI and rotation are incompatible. Rotation will be disabled
-when SLI is enabled.

-
TwinView and rotation can be used together, but rotation affects
-the entire desktop. This means that the same rotation setting will
-apply to both display devices in a TwinView pair. Note also that
-the TwinViewOrientation option
-applies before rotation does. For example, if you have two screens
-side-by-side and you want to rotate them, you should set
-TwinViewOrientation to
-Above or Below.

+
For further details, refer to the XF86Config(5x) or
+xorg.conf(5x) man pages.

 
 

 

@@ -91,11 +146,11 @@ side-by-side and you want to rotate them, you should set
 

 

 
-Chapter 13. Configuring TV-Out 
 Home
 
- Chapter 15. Configuring a Notebook
 

 

 

diff --git a/doc/html/chapter-15.html b/doc/html/chapter-15.html
index 45d9da8..116c645 100644
--- a/doc/html/chapter-15.html
+++ b/doc/html/chapter-15.html
@@ -5,23 +5,23 @@
 "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org">
 
-Chapter 15. Configuring a Notebook
+Chapter 15. Configuring TV-Out
 
 
 
 
+"Chapter 14. Configuring Multiple X Screens on One Card">
 
+"Chapter 16. Using the XRandR Extension">
 
 
 

 
-
+
+Chapter 14. Configuring Multiple X Screens on One
+Card 
+ Chapter 16. Using the XRandR Extension

 
Chapter 15. Configuring a
-NotebookChapter 15. Configuring
+TV-Out
 

 

 
 

 

 

-
Chapter 15. Configuring a
-Notebook

+
Chapter 15. Configuring TV-Out

 

 

 

-
Installation and configuration

-
Installation and configuration of the NVIDIA FreeBSD Driver Set
-on a notebook is the same as for any desktop environment, with a
-few additions, as described below.

-
Power Management

-
All notebook NVIDIA GPUs support power management, both S3 (also
-known as "Standby" or "Suspend to RAM") and S4 (also known as
-"Hibernate", "Suspend to Disk" or "SWSUSP"). Power management is
-system-specific and is dependent upon all the components in the
-system; some systems may be more problematic than other
-systems.

-
Most recent notebook NVIDIA GPUs also support PowerMizer, which
-monitors application work load to adjust system parameters to
-deliver the optimal balance of performance and battery life.
-However, PowerMizer is only enabled by default on some notebooks.
-Please see the known issues below for more details.

-
Hotkey Switching of Display Devices

-
Mobile NVIDIA GPUs also have the capacity to react to a display
-change hotkey event, toggling between each of the connected display
-devices and each possible combination of the connected display
-devices (note that only 2 display devices may be active at a
-time).

-
Hotkey switching dynamically changes the TwinView configuration;
-a given hotkey event will indicate which display devices should be
-in use at that time, and all MetaModes currently configured on the
-X screen will be updated to use the new configuration of display
-devices.

-
Another important aspect of hotkey functionality is that you can
-dynamically connect and remove display devices to/from your
-notebook and use the hotkey to activate and deactivate them without
-restarting X.

-
Note that there are two approaches to implementing this hotkey
-support: ACPI events and polling.

-
Most recent notebooks use ACPI events to deliver hotkeys from
-the System BIOS to the graphics driver. This is the preferred
-method of delivering hotkey events, but is still a new feature
-under most UNIX platforms and may not always function
-correctly.

-
The polling mechanism requires checking during the vertical
-blanking interval for a hotkey status change. It is an older
-mechanism for handling hotkeys, and is therefore not supported on
-all notebooks and is not tested by notebook manufacturers. It also
-does not always report the same combinations of display devices
-that are reported by ACPI hotkey events.

-
The NVIDIA FreeBSD Driver will attempt to use ACPI hotkey
-events, if possible. In the case that ACPI hotkey event support is
-not available, the driver will revert back to trying hotkey
-polling. In the case that the notebook does not support hotkey
-polling, hotkeys will not work. Please see the known issues section
-below for more details.

-
When switching away from X to a virtual terminal, the VGA
-console will always be restored to the display device on which it
-was present when X was started. Similarly, when switching back into
-X, the same display device configuration will be used as when you
-switched away, regardless of what display change hotkey activity
-occurred while the virtual terminal was active.

-
Docking Events

-
All notebook NVIDIA GPUs support docking, however support may be
-limited by the OS or system. There are three types of notebook
-docking (hot, warm, and cold), which refer to the state of the
-system when the docking event occurs. hot refers to a powered on
-system with a live desktop, warm refers to a system that has
-entered a suspended power management state, and cold refers to a
-system that has been powered off. Only warm and cold docking are
-supported by the NVIDIA driver.

-
TwinView

-
All notebook NVIDIA GPUs support TwinView. TwinView on a
-notebook can be configured in the same way as on a desktop computer
-(refer to Chapter 10,
-Configuring TwinView ); note that in a TwinView
-configuration using the notebook's internal flat panel and an
-external CRT, the CRT is the primary display device (specify its
-HorizSync and VertRefresh in the Monitor section of your X config
-file) and the flat panel is the secondary display device (specify
-its HorizSync and VertRefresh through the SecondMonitorHorizSync
-and SecondMonitorVertRefresh options).

-
The "UseEdidFreqs" X config option is enabled by default, so
-normally you should not need to specify the
-"SecondMonitorHorizSync" and "SecondMonitorVertRefresh" options.
-See the description of the UseEdidFreqs option in Appendix F, X
-Config Options for details).

-
Known Notebook Issues

-
There are a few known issues associated with notebooks:

+
NVIDIA GPU-based graphics cards with a TV-Out connector can use
+a television as another display device (the same way that it would
+use a CRT or digital flat panel). The TV can be used by itself, or
+in conjunction with another display device in a TwinView or
+multiple X screen configuration. If a TV is the only display device
+connected to your graphics card, it will be used as the primary
+display when you boot your system (i.e. the console will come up on
+the TV just as if it were a CRT).

+
The NVIDIA X driver populates the mode pool for the TV with all
+the mode sizes that the driver supports with the given TV standard
+and the TV encoder on the graphics card. These modes are given
+names that correspond to their resolution; e.g., "800x600".

+
Because these TV modes only depend on the TV encoder and the TV
+standard, TV modes do not go through normal mode validation. The X
+configuration options HorizSync and VertRefresh are not used for TV
+mode validation.

+
Additionally, the NVIDIA driver contains a hardcoded list of
+mode sizes that it can drive for each combination of TV encoder and
+TV standard. Therefore, custom modelines in your X configuration
+file are ignored for TVs.

+
To use your TV with X, there are several relevant X
+configuration options:

 

 
    
 
  • 
-
    Display change hotkey switching is not available on all
-notebooks. In some cases, the ACPI infrastructure is not fully
-supported by the NVIDIA FreeBSD Driver. Work is ongoing to increase
-the robustness of NVIDIA's support in this area. Toshiba and Lenovo
-notebooks are known to be problematic.
    
+
    The Modes in the screen section of your X configuration file;
+you can use these to request any of the modes in the mode pool
+which the X driver created for this combination of TV standard and
+TV encoder. Examples include "640x480" and "800x600". If in doubt,
+use "nvidia-auto-select".
    
 
    • 
 
  • 
-
    ACPI Display change hotkey switching is not supported by X.Org X
-servers earlier than 1.2.0; see EnableACPIHotkeys in Appendix F, X
-Config Options for details.
    
-
    • 
-
  • 
-
    In many cases, suspending and/or resuming will fail. As
-mentioned above, this functionality is very system-specific. There
-are still many cases that are problematic. Here are some tips that
-may help:
    
-
    
-
      
-
    • 
-
      In some cases, hibernation can have bad interactions with the
-PCI Express bus clocks, which can lead to system hangs when
-entering hibernation. This issue is still being investigated, but a
-known workaround is to leave an OpenGL application running when
-hibernating.
      
-
      • 
-
    
+
    The "TVStandard" option should be added to your screen section;
+valid values are:
    
+
    
+
+++
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    


    TVStandardDescription
    "PAL-B"used in Belgium, Denmark, Finland, Germany, Guinea, Hong Kong,
+India, Indonesia, Italy, Malaysia, The Netherlands, Norway,
+Portugal, Singapore, Spain, Sweden, and Switzerland
    "PAL-D"used in China and North Korea
    "PAL-G"used in Denmark, Finland, Germany, Italy, Malaysia, The
+Netherlands, Norway, Portugal, Spain, Sweden, and Switzerland
    "PAL-H"used in Belgium
    "PAL-I"used in Hong Kong and The United Kingdom
    "PAL-K1"used in Guinea
    "PAL-M"used in Brazil
    "PAL-N"used in France, Paraguay, and Uruguay
    "PAL-NC"used in Argentina
    "NTSC-J"used in Japan
    "NTSC-M"used in Canada, Chile, Colombia, Costa Rica, Ecuador, Haiti,
+Honduras, Mexico, Panama, Puerto Rico, South Korea, Taiwan, United
+States of America, and Venezuela
    "HD480i"480 line interlaced
    "HD480p"480 line progressive
    "HD720p"720 line progressive
    "HD1080i"1080 line interlaced
    "HD1080p"1080 line progressive
    "HD576i"576 line interlace
    "HD576p"576 line progressive
    
 
    
-
    
+
    The line in your X config file should be something like:
    
+
    +    Option "TVStandard" "NTSC-M"
+
    
+
    If you do not specify a TVStandard, or you specify an invalid
+value, the default "NTSC-M" will be used. Note: if your country is
+not in the above list, select the country closest to your
+location.
    
 
    • 
 
  • 
-
    On some notebooks, PowerMizer is not enabled by default. This
-issue is being investigated, and there is no known workaround.
    
+
    The "UseDisplayDevice" option can be used if there are multiple
+display devices connected, and you want the connected TV to be used
+instead of the connected CRTs and/or DFPs. E.g.,
    
+
    +    Option "UseDisplayDevice" "TV"
+
    
+
    Using the "UseDisplayDevice" option, rather than the
+"ConnectedMonitor" option, is recommended.
    
 
    • 
 
  • 
-
    ACPI is not currently supported on FreeBSD As a result, ACPI
-hotkey events are not supported.
    
+
    The "TVOutFormat" option can be used to force the output format.
+Without this option, the driver autodetects the output format.
+Unfortunately, it does not always do this correctly. The output
+format can be forced with the "TVOutFormat" option; valid values
+are:
    
+
    
+
+++
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    


    TVOutFormatDescriptionSupported TV standards
    "AUTOSELECT"The driver autodetects the output format (default value).PAL, NTSC, HD
    "COMPOSITE"Force Composite output formatPAL, NTSC
    "SVIDEO"Force S-Video output formatPAL, NTSC
    "COMPONENT"Force Component output format, also called YPbPrHD
    "SCART"Force Scart output format, also called PeritelPAL, NTSC
    
+
    
+
    The line in your X config file should be something like:
    
+
    +    Option "TVOutFormat" "SVIDEO"
+
    
+
    
 
    • 
 
  • 
-
    The video overlay only works on the first display device on
-which you started X. For example, if you start X on the internal
-LCD, run a video application that uses the video overlay (uses the
-"Video Overlay" adapter advertised through the XV extension), and
-then hotkey switch to add a second display device, the video will
-not appear on the second display device. To work around this, you
-can either configure the video application to use the "Video
-Blitter" adapter advertised through the XV extension (this is
-always available), or hotkey switch to the display device on which
-you want to use the video overlay *before* starting X.
    
+
    The "TVOverScan" option can be used to enable Overscan, when the
+TV encoder supports it. Valid values are decimal values in the
+range 1.0 (which means overscan as much as possible: make the image
+as large as possible) and 0.0 (which means disable overscanning:
+make the image as small as possible). Overscanning is disabled
+(0.0) by default.
    
 
    • 
 

 

-

+
The NVIDIA X driver may not restore the console correctly with
+XFree86 versions older than 4.3 when the console is a TV. This is
+due to binary incompatibilities between XFree86 int10 modules. If
+you use a TV as your console it is recommended that you upgrade to
+XFree86 4.3 or later.

 
 

 

@@ -200,11 +269,12 @@ you want to use the video overlay *before* starting X.

 

 

 
-Chapter 14. Using the XRandR Extension 
 Home
 
- Chapter 16. Programming Modes
 

 

 

diff --git a/doc/html/chapter-16.html b/doc/html/chapter-16.html
index 5e48b5f..cb8108a 100644
--- a/doc/html/chapter-16.html
+++ b/doc/html/chapter-16.html
@@ -5,23 +5,23 @@
 "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org">
 
-Chapter 16. Programming Modes
+Chapter 16. Using the XRandR Extension
 
 
 
 
+"Chapter 15. Configuring TV-Out">
 
+"Chapter 17. Configuring a Notebook">
 
 
 

 
-
+
+Chapter 15. Configuring TV-Out 
+ Chapter 17. Configuring a Notebook

 
Chapter 16. Programming
-ModesChapter 16. Using the
+XRandR Extension
 

 

 
 

 

 

-
Chapter 16. Programming Modes

+
Chapter 16. Using the XRandR
+Extension

 

 

 

-
The NVIDIA Accelerated FreeBSD Graphics Driver supports all
-standard VGA and VESA modes, as well as most user-written custom
-mode lines; double-scan modes are supported on all hardware.
-Interlaced modes are supported on all GeForce FX/Quadro FX and
-newer GPUs, and certain older GPUs; the X log file will contain a
-message "Interlaced video modes are supported on this GPU" if
-interlaced modes are supported.

-
To request one or more standard modes for use in X, you can
-simply add a "Modes" line such as:

+
X.Org version X11R6.8.1 contains support for the rotation
+component of the XRandR extension, which allows screens to be
+rotated at 90 degree increments.

+
The driver supports rotation with the extension when 'Option
+"RandRRotation"' is enabled in the X config file.

+
Workstation RGB or CI overlay visuals will function at lower
+performance and the video overlay will not be available when
+RandRRotation is enabled.

+
You can query the available rotations using the 'xrandr' command
+line interface to the RandR extension by running:

 
-    Modes "1600x1200" "1024x768" "640x480"
+    xrandr -q
 

-
in the appropriate Display subsection of your X config file (see
-the XF86Config(5x) or xorg.conf(5x) man pages for details). Or, the
-nvidia-xconfig(1) utility can be used to request additional modes;
-for example:

+
You can set the rotation orientation of the screen by running
+any of:

 
-    nvidia-xconfig --mode 1600x1200
+    xrandr -o left
+    xrandr -o right
+    xrandr -o inverted
+    xrandr -o normal
 

-
See the nvidia-xconfig(1) man page for details.

-
Depth, Bits per Pixel, and Pitch

-
While not directly a concern when programming modes, the bits
-used per pixel is an issue when considering the maximum
-programmable resolution; for this reason, it is worthwhile to
-address the confusion surrounding the terms "depth" and "bits per
-pixel". Depth is how many bits of data are stored per pixel.
-Supported depths are 8, 15, 16, and 24. Most video hardware,
-however, stores pixel data in sizes of 8, 16, or 32 bits; this is
-the amount of memory allocated per pixel. When you specify your
-depth, X selects the bits per pixel (bpp) size in which to store
-the data. Below is a table of what bpp is used for each possible
-depth:

-

-
---
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-



DepthBPP
88
1516
1616
2432

-

-
Lastly, the "pitch" is how many bytes in the linear frame buffer
-there are between one pixel's data, and the data of the pixel
-immediately below. You can think of this as the horizontal
-resolution multiplied by the bytes per pixel (bits per pixel
-divided by 8). In practice, the pitch may be more than this product
-due to alignment constraints.

-
Maximum Resolutions

-
The NVIDIA Accelerated FreeBSD Graphics Driver and NVIDIA
-GPU-based graphics cards support resolutions up to 8192x8192 pixels
-for the GeForce 8 series and above, and up to 4096x4096 pixels for
-the GeForce 7 series and below, though the maximum resolution your
-system can support is also limited by the amount of video memory
-(see USEFUL FORMULAS for details) and the maximum supported
-resolution of your display device (monitor/flat panel/television).
-Also note that while use of a video overlay does not limit the
-maximum resolution or refresh rate, video memory bandwidth used by
-a programmed mode does affect the overlay quality.

-
Useful Formulas

-
The maximum resolution is a function both of the amount of video
-memory and the bits per pixel you elect to use:

-

-
HR * VR * (bpp/8) = Video Memory
-Used

-

-
In other words, the amount of video memory used is equal to the
-horizontal resolution (HR) multiplied by the vertical resolution
-(VR) multiplied by the bytes per pixel (bits per pixel divided by
-eight). Technically, the video memory used is actually the pitch
-times the vertical resolution, and the pitch may be slightly
-greater than (HR *
-(bpp/8)) to accommodate the hardware requirement that
-the pitch be a multiple of some value.

-
Note that this is just memory usage for the frame buffer; video
-memory is also used by other things, such as OpenGL and pixmap
-caching.

-
Another important relationship is that between the resolution,
-the pixel clock (also known as the dot clock) and the vertical
-refresh rate:

-

-
RR = PCLK / (HFL * VFL)

-

-
In other words, the refresh rate (RR) is equal to the pixel
-clock (PCLK) divided by the total number of pixels: the horizontal
-frame length (HFL) multiplied by the vertical frame length (VFL)
-(note that these are the frame lengths, and not just the visible
-resolutions). As described in the XFree86 Video Timings HOWTO, the
-above formula can be rewritten as:

-

-
PCLK = RR * HFL * VFL

-

-
Given a maximum pixel clock, you can adjust the RR, HFL and VFL
-as desired, as long as the product of the three is consistent. The
-pixel clock is reported in the log file. Your X log should contain
-a line like this:

-
-    (--) NVIDIA(0): ViewSonic VPD150 (DFP-1): 165 MHz maximum pixel clock
-

-
which indicates the maximum pixel clock for that display
-device.

-
How Modes Are Validated

-
In traditional XFree86/X.Org mode validation, the X server takes
-as a starting point the X server's internal list of VESA standard
-modes, plus any modes specified with special ModeLines in the X
-configuration file's Monitor section. These modes are validated
-against criteria such as the valid HorizSync/VertRefresh frequency
-ranges for the user's monitor (as specified in the Monitor section
-of the X configuration file), as well as the maximum pixel clock of
-the GPU.

-
Once the X server has determined the set of valid modes, it
-takes the list of user requested modes (i.e., the set of modes
-named in the "Modes" line in the Display subsection of the Screen
-section of X configuration file), and finds the "best" validated
-mode with the requested name.

-
The NVIDIA X driver uses a variation on the above approach to
-perform mode validation. During X server initialization, the NVIDIA
-X driver builds a pool of valid modes for each display device. It
-gathers all possible modes from several sources:

-

-
    
-
  • 
-
    The display device's EDID
    
-
    • 
-
  • 
-
    The X server's built-in list
    
-
    • 
-
  • 
-
    Any user-specified ModeLines in the X configuration file
    
-
    • 
-
  • 
-
    The VESA standard modes
    
-
    • 
-

-

-
For every possible mode, the mode is run through mode
-validation. The core of mode validation is still performed
-similarly to traditional XFree86/X.Org mode validation: the mode
-timings are checked against things such as the valid HorizSync and
-VertRefresh ranges and the maximum pixelclock. Note that each
-individual stage of mode validation can be independently controlled
-through the "ModeValidation" X configuration option.

-
Note that when validating interlaced mode timings, VertRefresh
-specifies the field rate, rather than the frame rate. For example,
-the following modeline has a vertical refresh rate of 87 Hz:

-
- # 1024x768i @ 87Hz (industry standard)
- ModeLine "1024x768"  44.9  1024 1032 1208 1264  768 768 776 817 +hsync +vsync Interlace
-

-

-
Invalid modes are discarded; valid modes are inserted into the
-mode pool. See MODE VALIDATION REPORTING for how to get more
-details on mode validation results for each considered mode.

-
Valid modes are given a unique name that is guaranteed to be
-unique across the whole mode pool for this display device. This
-mode name is constructed approximately like this:

-
-    <width>x<height>_<refreshrate>
-

-
(e.g., "1600x1200_85")

-
The name may also be prepended with another number to ensure the
-mode is unique; e.g., "1600x1200_85_0".

-
As validated modes are inserted into the mode pool, duplicate
-modes are removed, and the mode pool is sorted, such that the
-"best" modes are at the beginning of the mode pool. The sorting is
-based roughly on:

-

-
    
-
  • 
-
    Resolution
    
-
    • 
-
  • 
-
    Source (EDID-provided modes are prioritized higher than
-VESA-provided modes, which are prioritized higher than modes that
-were in the X server's built-in list)
    
-
    • 
-
  • 
-
    Refresh rate
    
-
    • 
-

-

-
Once modes from all mode sources are validated and the mode pool
-is constructed, all modes with the same resolution are compared;
-the best mode with that resolution is added to the mode pool a
-second time, using just the resolution as its unique modename
-(e.g., "1600x1200"). In this way, when you request a mode using the
-traditional names (e.g., "1600x1200"), you still get what you got
-before (the 'best' 1600x1200 mode); the added benefit is that all
-modes in the mode pool can be addressed by a unique name.

-
When verbose logging is enabled (see the FAQ section on increasing the
-amount of data printed in the X log file), the mode pool for each
-display device is printed to the X log file.

-
After the mode pool is built for all display devices, the
-requested modes (as specified in the X configuration file), are
-looked up from the mode pool. Each requested mode that can be
-matched against a mode in the mode pool is then advertised to the X
-server and is available to the user through the X server's mode
-switching hotkeys (ctrl-alt-plus/minus) and the XRandR and
-XF86VidMode X extensions.

-
If only one display device is in use by the X screen when the X
-server starts, all modes in the mode pool are implicitly made
-available to the X server. See the "IncludeImplicitMetaModes" X
-configuration option in Appendix F, X
-Config Options for details.

-
The NVIDIA-Auto-Select Mode

-
You can request a special mode by name in the X config file,
-named "nvidia-auto-select". When the X driver builds the mode pool
-for a display device, it selects one of the modes as the
-"nvidia-auto-select" mode; a new entry is made in the mode pool,
-and "nvidia-auto-select" is used as the unique name for the
-mode.

-
The "nvidia-auto-select" mode is intended to be a reasonable
-mode for the display device in question. For example, the
-"nvidia-auto-select" mode is normally the native resolution for
-flatpanels, as reported by the flatpanel's EDID, or one of the
-detailed timings from the EDID. The "nvidia-auto-select" mode is
-guaranteed to always be present, and to always be defined as
-something considered valid by the X driver for this display
-device.

-
Note that the "nvidia-auto-select" mode is not necessarily the
-largest possible resolution, nor is it necessarily the mode with
-the highest refresh rate. Rather, the "nvidia-auto-select" mode is
-selected such that it is a reasonable default. The selection
-process is roughly:

-

-
    
-
  • 
-
    If the EDID for the display device reported a preferred mode
-timing, and that mode timing is considered a valid mode, then that
-mode is used as the "nvidia-auto-select" mode. You can check if the
-EDID reported a preferred timing by starting X with logverbosity
-greater than or equal to 5 (see the FAQ section on increasing the
-amount of data printed in the X log file), and looking at the EDID
-printout; if the EDID contains a line:
    
-
    -    Prefer first detailed timing : Yes
-
    
-
    Then the first mode listed under the "Detailed Timings" in the
-EDID will be used.
    
-
    • 
-
  • 
-
    If the EDID did not provide a preferred timing, the best
-detailed timing from the EDID is used as the "nvidia-auto-select"
-mode.
    
-
    • 
-
  • 
-
    If the EDID did not provide any detailed timings (or there was
-no EDID at all), the best valid mode not larger than 1024x768 is
-used as the "nvidia-auto-select" mode. The 1024x768 limit is
-imposed here to restrict use of modes that may have been validated,
-but may be too large to be considered a reasonable default, such as
-2048x1536.
    
-
    • 
-
  • 
-
    If all else fails, the X driver will use a built-in 800 x 600
-60Hz mode as the "nvidia-auto-select" mode.
    
-
    • 
-

-

-
If no modes are requested in the X configuration file, or none
-of the requested modes can be found in the mode pool, then the X
-driver falls back to the "nvidia-auto-select" mode, so that X can
-always start. Appropriate warning messages will be printed to the X
-log file in these fallback scenarios.

-
You can add the "nvidia-auto-select" mode to your X
-configuration file by running the command

-
-    nvidia-xconfig --mode nvidia-auto-select
-

-
and restarting your X server.

-
The X driver can generally do a much better job of selecting the
-"nvidia-auto-select" mode if the display device's EDID is
-available. This is one reason why the "IgnoreEDID" X configuration
-option has been deprecated, and that it is recommended to only use
-the "UseEDID" X configuration option sparingly. Note that, rather
-than globally disable all uses of the EDID with the "UseEDID"
-option, you can individually disable each particular use of the
-EDID using the "UseEDIDFreqs", "UseEDIDDpi", and/or the
-"NoEDIDModes" argument in the "ModeValidation" X configuration
-option.

-
Mode Validation Reporting

-
When log verbosity is set to 6 or higher (see FAQ section on increasing the
-amount of data printed in the X log file), the X log will record
-every mode that is considered for each display device's mode pool,
-and report whether the mode passed or failed. For modes that were
-considered invalid, the log will report why the mode was considered
-invalid.

-
Ensuring Identical Mode Timings

-
Some functionality, such as Active Stereo with TwinView,
-requires control over exactly which mode timings are used. For
-explicit control over which mode timings are used on each display
-device, you can specify the ModeLine you want to use (using one of
-the ModeLine generators available), and using a unique name. For
-example, if you wanted to use 1024x768 at 120 Hz on each monitor in
-TwinView with active stereo, you might add something like this to
-the monitor section of your X configuration file:

-
-    # 1024x768 @ 120.00 Hz (GTF) hsync: 98.76 kHz; pclk: 139.05 MHz
-    Modeline "1024x768_120"  139.05  1024 1104 1216 1408  768 769 772 823 -HSync +Vsync
-

-
Then, in the Screen section of your X config file, specify a
-MetaMode like this:

-
-    Option "MetaModes" "1024x768_120, 1024x768_120"
-

-

-
Additional Information

-
An XFree86 ModeLine generator, conforming to the GTF Standard is
-available at http://gtf.sourceforge.net/. Additional generators can
-be found by searching for "modeline" on freshmeat.net.

+
Rotation may also be set through the nvidia-settings
+configuration utility in the "Rotation Settings" panel.

+
SLI and rotation are incompatible. Rotation will be disabled
+when SLI is enabled.

+
TwinView and rotation can be used together, but rotation affects
+the entire desktop. This means that the same rotation setting will
+apply to both display devices in a TwinView pair. Note also that
+the TwinViewOrientation option
+applies before rotation does. For example, if you have two screens
+side-by-side and you want to rotate them, you should set
+TwinViewOrientation to
+Above or Below.

 
 

 

@@ -392,11 +91,11 @@ be found by searching for "modeline" on freshmeat.net.

 

 

 
-Chapter 15. Configuring a Notebook 
 Home
 
- Chapter 17. Configuring Flipping and UBB
 

 

 

diff --git a/doc/html/chapter-17.html b/doc/html/chapter-17.html
index 7e8bd61..ceda3fd 100644
--- a/doc/html/chapter-17.html
+++ b/doc/html/chapter-17.html
@@ -5,23 +5,23 @@
 "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org">
 
-Chapter 17. Configuring Flipping and UBB
+Chapter 17. Configuring a Notebook
 
 
 
 
-
+"Chapter 16. Using the XRandR Extension">
+
 
 
 

 
-
+
+"chapter-18.html">Next

 
Chapter 17. Configuring
-Flipping and UBBChapter 17. Configuring a
+Notebook
 

 

 
 Part I. Installation and
 Configuration Instructions
  Next
 

 

 

@@ -37,45 +37,151 @@ Configuration Instructions
 

 

 

-
Chapter 17. Configuring Flipping and
-UBB

+
Chapter 17. Configuring a
+Notebook

 

 

 

-
The NVIDIA Accelerated FreeBSD Graphics Driver supports Unified
-Back Buffer (UBB) and OpenGL Flipping. These features can provide
-performance gains in certain situations.

+
Installation and configuration

+
Installation and configuration of the NVIDIA FreeBSD Driver Set
+on a notebook is the same as for any desktop environment, with a
+few additions, as described below.

+
Power Management

+
All notebook NVIDIA GPUs support power management, both S3 (also
+known as "Standby" or "Suspend to RAM") and S4 (also known as
+"Hibernate", "Suspend to Disk" or "SWSUSP"). Power management is
+system-specific and is dependent upon all the components in the
+system; some systems may be more problematic than other
+systems.

+
Most recent notebook NVIDIA GPUs also support PowerMizer, which
+monitors application work load to adjust system parameters to
+deliver the optimal balance of performance and battery life.
+However, PowerMizer is only enabled by default on some notebooks.
+Please see the known issues below for more details.

+
Hotkey Switching of Display Devices

+
Mobile NVIDIA GPUs also have the capacity to react to a display
+change hotkey event, toggling between each of the connected display
+devices and each possible combination of the connected display
+devices (note that only 2 display devices may be active at a
+time).

+
Hotkey switching dynamically changes the TwinView configuration;
+a given hotkey event will indicate which display devices should be
+in use at that time, and all MetaModes currently configured on the
+X screen will be updated to use the new configuration of display
+devices.

+
Another important aspect of hotkey functionality is that you can
+dynamically connect and remove display devices to/from your
+notebook and use the hotkey to activate and deactivate them without
+restarting X.

+
Note that there are two approaches to implementing this hotkey
+support: ACPI events and polling.

+
Most recent notebooks use ACPI events to deliver hotkeys from
+the System BIOS to the graphics driver. This is the preferred
+method of delivering hotkey events, but is still a new feature
+under most UNIX platforms and may not always function
+correctly.

+
The polling mechanism requires checking during the vertical
+blanking interval for a hotkey status change. It is an older
+mechanism for handling hotkeys, and is therefore not supported on
+all notebooks and is not tested by notebook manufacturers. It also
+does not always report the same combinations of display devices
+that are reported by ACPI hotkey events.

+
The NVIDIA FreeBSD Driver will attempt to use ACPI hotkey
+events, if possible. In the case that ACPI hotkey event support is
+not available, the driver will revert back to trying hotkey
+polling. In the case that the notebook does not support hotkey
+polling, hotkeys will not work. Please see the known issues section
+below for more details.

+
When switching away from X to a virtual terminal, the VGA
+console will always be restored to the display device on which it
+was present when X was started. Similarly, when switching back into
+X, the same display device configuration will be used as when you
+switched away, regardless of what display change hotkey activity
+occurred while the virtual terminal was active.

+
Docking Events

+
All notebook NVIDIA GPUs support docking, however support may be
+limited by the OS or system. There are three types of notebook
+docking (hot, warm, and cold), which refer to the state of the
+system when the docking event occurs. hot refers to a powered on
+system with a live desktop, warm refers to a system that has
+entered a suspended power management state, and cold refers to a
+system that has been powered off. Only warm and cold docking are
+supported by the NVIDIA driver.

+
TwinView

+
All notebook NVIDIA GPUs support TwinView. TwinView on a
+notebook can be configured in the same way as on a desktop computer
+(refer to Chapter 12,
+Configuring TwinView ); note that in a TwinView
+configuration using the notebook's internal flat panel and an
+external CRT, the CRT is the primary display device (specify its
+HorizSync and VertRefresh in the Monitor section of your X config
+file) and the flat panel is the secondary display device (specify
+its HorizSync and VertRefresh through the SecondMonitorHorizSync
+and SecondMonitorVertRefresh options).

+
The "UseEdidFreqs" X config option is enabled by default, so
+normally you should not need to specify the
+"SecondMonitorHorizSync" and "SecondMonitorVertRefresh" options.
+See the description of the UseEdidFreqs option in Appendix B, X
+Config Options for details).

+
Known Notebook Issues

+
There are a few known issues associated with notebooks:

 

 
    
 
  • 
-
    Unified Back Buffer (UBB): UBB is available only on the Quadro
-family of GPUs (Quadro4 NVS excluded) and is enabled by default
-when there is sufficient video memory available. This can be
-disabled with the UBB X config option described in Appendix F, X
-Config Options. When UBB is enabled, all windows share the
-same back, stencil and depth buffers. When there are many windows,
-the back, stencil and depth usage will never exceed the size of
-that used by a full screen window. However, even for a single small
-window, the back, stencil, and depth video memory usage is that of
-a full screen window. In that case video memory may be used less
-efficiently than in the non-UBB case.
    
+
    Display change hotkey switching is not available on all
+notebooks. In some cases, the ACPI infrastructure is not fully
+supported by the NVIDIA FreeBSD Driver. Work is ongoing to increase
+the robustness of NVIDIA's support in this area. Toshiba and Lenovo
+notebooks are known to be problematic.
    
 
    • 
 
  • 
-
    Flipping: When OpenGL flipping is enabled, OpenGL can perform
-buffer swaps by changing which buffer the DAC scans out rather than
-copying the back buffer contents to the front buffer; this is
-generally a much higher performance mechanism and allows tearless
-swapping during the vertical retrace (when __GL_SYNC_TO_VBLANK is
-set). The conditions under which OpenGL can flip are slightly
-complicated, but in general: on GeForce or newer hardware, OpenGL
-can flip when a single full screen unobscured OpenGL application is
-running, and __GL_SYNC_TO_VBLANK is enabled. Additionally, OpenGL
-can flip on Quadro hardware even when an OpenGL window is partially
-obscured or not full screen or __GL_SYNC_TO_VBLANK is not
-enabled.
    
+
    ACPI Display change hotkey switching is not supported by X.Org X
+servers earlier than 1.2.0; see EnableACPIHotkeys in Appendix B, X
+Config Options for details.
    
+
    • 
+
  • 
+
    In many cases, suspending and/or resuming will fail. As
+mentioned above, this functionality is very system-specific. There
+are still many cases that are problematic. Here are some tips that
+may help:
    
+
    
+
      
+
    • 
+
      In some cases, hibernation can have bad interactions with the
+PCI Express bus clocks, which can lead to system hangs when
+entering hibernation. This issue is still being investigated, but a
+known workaround is to leave an OpenGL application running when
+hibernating.
      
+
      • 
+
    
+
    
+
    
+
    • 
+
  • 
+
    On some notebooks, PowerMizer is not enabled by default. This
+issue is being investigated, and there is no known workaround.
    
+
    • 
+
  • 
+
    ACPI is not currently supported on FreeBSD As a result, ACPI
+hotkey events are not supported.
    
+
    • 
+
  • 
+
    The video overlay only works on the first display device on
+which you started X. For example, if you start X on the internal
+LCD, run a video application that uses the video overlay (uses the
+"Video Overlay" adapter advertised through the XV extension), and
+then hotkey switch to add a second display device, the video will
+not appear on the second display device. To work around this, you
+can either configure the video application to use the "Video
+Blitter" adapter advertised through the XV extension (this is
+always available), or hotkey switch to the display device on which
+you want to use the video overlay *before* starting X.
    
 
    • 
 

 

@@ -90,15 +196,15 @@ enabled.
Up  Next
-Chapter 16. Programming Modes  Home - Appendix C. The Sysctl Interface
diff --git a/doc/html/chapter-18.html b/doc/html/chapter-18.html index 417e75f..1db59e9 100644 --- a/doc/html/chapter-18.html +++ b/doc/html/chapter-18.html @@ -5,28 +5,27 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Chapter 18. Using the X Composite -Extension +Chapter 18. Programming Modes - + +"Chapter 19. Configuring Flipping and UBB">
- + +"chapter-17.html">Prev  +"chapter-27.html">Next +Chapter 25. Configuring Frame Lock and Genlock  + Chapter 27. Configuring Depth 30 Displays
Chapter 18. Using the X -Composite ExtensionChapter 18. Programming +Modes
Prev  Part I. Installation and Configuration Instructions  
-

Chapter 18. Using the X -Composite Extension

+

Chapter 18. Programming Modes

-

X.Org X servers, beginning with X11R6.8.0, contain experimental -support for a new X protocol extension called Composite. This -extension allows windows to be drawn into pixmaps instead of -directly onto the screen. In conjunction with the Damage and Render -extensions, this allows a program called a composite manager to -blend windows together to draw the screen.

-

Performance will be degraded significantly if the RenderAccel option is disabled in -xorg.conf. See Appendix F, X -Config Options for more details.

-

When the NVIDIA X driver is used with an X.Org X server -X11R6.9.0 or newer and the Composite extension is enabled, NVIDIA's -OpenGL implementation interacts properly with the Damage and -Composite X extensions. This means that OpenGL rendering is drawn -into offscreen pixmaps and the X server is notified of the Damage -event when OpenGL renders to the pixmap. This allows OpenGL -applications to behave properly in a composited X desktop.

-

If the Composite extension is enabled on an X server older than -X11R6.9.0, then GLX will be disabled. You can force GLX on while -Composite is enabled on pre-X11R6.9.0 X servers with the -AllowGLXWithComposite X -configuration option. However, GLX will not render correctly in -this environment. Upgrading your X server to X11R6.9.0 or newer is -recommended.

-

You can enable the Composite X extension by running -nvidia-xconfig ---composite. Composite can be disabled with -nvidia-xconfig ---no-composite. See the nvidia-xconfig(1) man page -for details.

-

If you are using Composite with GLX, it is recommended that you -also enable the DamageEvents X -option for enhanced performance. If you are using an OpenGL-based -composite manager, you may also need the DisableGLXRootClipping option to obtain -proper output.

-

The Composite extension also causes problems with other driver -components:

+

The NVIDIA Accelerated FreeBSD Graphics Driver supports all +standard VGA and VESA modes, as well as most user-written custom +mode lines; double-scan modes are supported on all hardware. +Interlaced modes are supported on all GeForce FX/Quadro FX and +newer GPUs, and certain older GPUs; the X log file will contain a +message "Interlaced video modes are supported on this GPU" if +interlaced modes are supported.

+

To request one or more standard modes for use in X, you can +simply add a "Modes" line such as:

+
+    Modes "1600x1200" "1024x768" "640x480"
+
+

in the appropriate Display subsection of your X config file (see +the XF86Config(5x) or xorg.conf(5x) man pages for details). Or, the +nvidia-xconfig(1) utility can be used to request additional modes; +for example:

+
+    nvidia-xconfig --mode 1600x1200
+
+

See the nvidia-xconfig(1) man page for details.

+

Depth, Bits per Pixel, and Pitch

+

While not directly a concern when programming modes, the bits +used per pixel is an issue when considering the maximum +programmable resolution; for this reason, it is worthwhile to +address the confusion surrounding the terms "depth" and "bits per +pixel". Depth is how many bits of data are stored per pixel. +Supported depths are 8, 15, 16, and 24. Most video hardware, +however, stores pixel data in sizes of 8, 16, or 32 bits; this is +the amount of memory allocated per pixel. When you specify your +depth, X selects the bits per pixel (bpp) size in which to store +the data. Below is a table of what bpp is used for each possible +depth:

+
+ +++ + + + + + + + + + + + + + + + + + + + + + + + + +
DepthBPP
88
1516
1616
2432
+
+

Lastly, the "pitch" is how many bytes in the linear frame buffer +there are between one pixel's data, and the data of the pixel +immediately below. You can think of this as the horizontal +resolution multiplied by the bytes per pixel (bits per pixel +divided by 8). In practice, the pitch may be more than this product +due to alignment constraints.

+

Maximum Resolutions

+

The NVIDIA Accelerated FreeBSD Graphics Driver and NVIDIA +GPU-based graphics cards support resolutions up to 8192x8192 pixels +for the GeForce 8 series and above, and up to 4096x4096 pixels for +the GeForce 7 series and below, though the maximum resolution your +system can support is also limited by the amount of video memory +(see USEFUL FORMULAS for details) and the maximum supported +resolution of your display device (monitor/flat panel/television). +Also note that while use of a video overlay does not limit the +maximum resolution or refresh rate, video memory bandwidth used by +a programmed mode does affect the overlay quality.

+

Useful Formulas

+

The maximum resolution is a function both of the amount of video +memory and the bits per pixel you elect to use:

+
+
HR * VR * (bpp/8) = Video Memory +Used
+
+

In other words, the amount of video memory used is equal to the +horizontal resolution (HR) multiplied by the vertical resolution +(VR) multiplied by the bytes per pixel (bits per pixel divided by +eight). Technically, the video memory used is actually the pitch +times the vertical resolution, and the pitch may be slightly +greater than (HR * +(bpp/8)) to accommodate the hardware requirement that +the pitch be a multiple of some value.

+

Note that this is just memory usage for the frame buffer; video +memory is also used by other things, such as OpenGL and pixmap +caching.

+

Another important relationship is that between the resolution, +the pixel clock (also known as the dot clock) and the vertical +refresh rate:

+
+
RR = PCLK / (HFL * VFL)
+
+

In other words, the refresh rate (RR) is equal to the pixel +clock (PCLK) divided by the total number of pixels: the horizontal +frame length (HFL) multiplied by the vertical frame length (VFL) +(note that these are the frame lengths, and not just the visible +resolutions). As described in the XFree86 Video Timings HOWTO, the +above formula can be rewritten as:

+
+
PCLK = RR * HFL * VFL
+
+

Given a maximum pixel clock, you can adjust the RR, HFL and VFL +as desired, as long as the product of the three is consistent. The +pixel clock is reported in the log file. Your X log should contain +a line like this:

+
+    (--) NVIDIA(0): ViewSonic VPD150 (DFP-1): 165 MHz maximum pixel clock
+
+

which indicates the maximum pixel clock for that display +device.

+

How Modes Are Validated

+

In traditional XFree86/X.Org mode validation, the X server takes +as a starting point the X server's internal list of VESA standard +modes, plus any modes specified with special ModeLines in the X +configuration file's Monitor section. These modes are validated +against criteria such as the valid HorizSync/VertRefresh frequency +ranges for the user's monitor (as specified in the Monitor section +of the X configuration file), as well as the maximum pixel clock of +the GPU.

+

Once the X server has determined the set of valid modes, it +takes the list of user requested modes (i.e., the set of modes +named in the "Modes" line in the Display subsection of the Screen +section of X configuration file), and finds the "best" validated +mode with the requested name.

+

The NVIDIA X driver uses a variation on the above approach to +perform mode validation. During X server initialization, the NVIDIA +X driver builds a pool of valid modes for each display device. It +gathers all possible modes from several sources:

  • -

    In X servers prior to X.Org 7.1, Xv cannot draw into pixmaps -that have been redirected offscreen and will draw directly onto the -screen instead. For some programs you can work around this issue by -using an alternative video driver. For example, "mplayer -vo x11" -will work correctly, as will "xine -V xshm". If you must use Xv -with an older server, you can also disable the compositing manager -and re-enable it when you are finished.

    -

    On X.Org 7.1 and higher, the driver will properly redirect video -into offscreen pixmaps. Note that the Xv adaptors will ignore the -sync-to-vblank option when drawing into a redirected window.

    +

    The display device's EDID

    +
    • +
  • +

    The X server's built-in list

    +
    • +
  • +

    Any user-specified ModeLines in the X configuration file

  • -

    Workstation overlays, stereo visuals, and the unified back -buffer (UBB) are incompatible with Composite. These features will -be automatically disabled when Composite is detected.

    +

    The VESA standard modes

+

For every possible mode, the mode is run through mode +validation. The core of mode validation is still performed +similarly to traditional XFree86/X.Org mode validation: the mode +timings are checked against things such as the valid HorizSync and +VertRefresh ranges and the maximum pixelclock. Note that each +individual stage of mode validation can be independently controlled +through the "ModeValidation" X configuration option.

+

Note that when validating interlaced mode timings, VertRefresh +specifies the field rate, rather than the frame rate. For example, +the following modeline has a vertical refresh rate of 87 Hz:

+
+ # 1024x768i @ 87Hz (industry standard)
+ ModeLine "1024x768"  44.9  1024 1032 1208 1264  768 768 776 817 +hsync +vsync Interlace
+

-

This NVIDIA FreeBSD supports OpenGL rendering to 32-bit ARGB -windows on X.Org 7.2 and higher or when the AddARGBGLXVisuals X config file option is -enabled. If you are an application developer, you can use these new -visuals in conjunction with a composite manager to create -translucent OpenGL applications:

+

Invalid modes are discarded; valid modes are inserted into the +mode pool. See MODE VALIDATION REPORTING for how to get more +details on mode validation results for each considered mode.

+

Valid modes are given a unique name that is guaranteed to be +unique across the whole mode pool for this display device. This +mode name is constructed approximately like this:

+
+    <width>x<height>_<refreshrate>
+
+

(e.g., "1600x1200_85")

+

The name may also be prepended with another number to ensure the +mode is unique; e.g., "1600x1200_85_0".

+

As validated modes are inserted into the mode pool, duplicate +modes are removed, and the mode pool is sorted, such that the +"best" modes are at the beginning of the mode pool. The sorting is +based roughly on:

+
+
    +
  • +

    Resolution

    +
    • +
  • +

    Source (EDID-provided modes are prioritized higher than +VESA-provided modes, which are prioritized higher than modes that +were in the X server's built-in list)

    +
    • +
  • +

    Refresh rate

    +
    • +
+
+

Once modes from all mode sources are validated and the mode pool +is constructed, all modes with the same resolution are compared; +the best mode with that resolution is added to the mode pool a +second time, using just the resolution as its unique modename +(e.g., "1600x1200"). In this way, when you request a mode using the +traditional names (e.g., "1600x1200"), you still get what you got +before (the 'best' 1600x1200 mode); the added benefit is that all +modes in the mode pool can be addressed by a unique name.

+

When verbose logging is enabled (see the FAQ section on increasing the +amount of data printed in the X log file), the mode pool for each +display device is printed to the X log file.

+

After the mode pool is built for all display devices, the +requested modes (as specified in the X configuration file), are +looked up from the mode pool. Each requested mode that can be +matched against a mode in the mode pool is then advertised to the X +server and is available to the user through the X server's mode +switching hotkeys (ctrl-alt-plus/minus) and the XRandR and +XF86VidMode X extensions.

+

If only one display device is in use by the X screen when the X +server starts, all modes in the mode pool are implicitly made +available to the X server. See the "IncludeImplicitMetaModes" X +configuration option in Appendix B, X +Config Options for details.

+

The NVIDIA-Auto-Select Mode

+

You can request a special mode by name in the X config file, +named "nvidia-auto-select". When the X driver builds the mode pool +for a display device, it selects one of the modes as the +"nvidia-auto-select" mode; a new entry is made in the mode pool, +and "nvidia-auto-select" is used as the unique name for the +mode.

+

The "nvidia-auto-select" mode is intended to be a reasonable +mode for the display device in question. For example, the +"nvidia-auto-select" mode is normally the native resolution for +flatpanels, as reported by the flatpanel's EDID, or one of the +detailed timings from the EDID. The "nvidia-auto-select" mode is +guaranteed to always be present, and to always be defined as +something considered valid by the X driver for this display +device.

+

Note that the "nvidia-auto-select" mode is not necessarily the +largest possible resolution, nor is it necessarily the mode with +the highest refresh rate. Rather, the "nvidia-auto-select" mode is +selected such that it is a reasonable default. The selection +process is roughly:

+
+
    +
  • +

    If the EDID for the display device reported a preferred mode +timing, and that mode timing is considered a valid mode, then that +mode is used as the "nvidia-auto-select" mode. You can check if the +EDID reported a preferred timing by starting X with logverbosity +greater than or equal to 5 (see the FAQ section on increasing the +amount of data printed in the X log file), and looking at the EDID +printout; if the EDID contains a line:

    +
    +    Prefer first detailed timing : Yes
+
    +

    Then the first mode listed under the "Detailed Timings" in the +EDID will be used.

    +
    • +
  • +

    If the EDID did not provide a preferred timing, the best +detailed timing from the EDID is used as the "nvidia-auto-select" +mode.

    +
    • +
  • +

    If the EDID did not provide any detailed timings (or there was +no EDID at all), the best valid mode not larger than 1024x768 is +used as the "nvidia-auto-select" mode. The 1024x768 limit is +imposed here to restrict use of modes that may have been validated, +but may be too large to be considered a reasonable default, such as +2048x1536.

    +
    • +
  • +

    If all else fails, the X driver will use a built-in 800 x 600 +60Hz mode as the "nvidia-auto-select" mode.

    +
    • +
+
+

If no modes are requested in the X configuration file, or none +of the requested modes can be found in the mode pool, then the X +driver falls back to the "nvidia-auto-select" mode, so that X can +always start. Appropriate warning messages will be printed to the X +log file in these fallback scenarios.

+

You can add the "nvidia-auto-select" mode to your X +configuration file by running the command

+
+    nvidia-xconfig --mode nvidia-auto-select
+
+

and restarting your X server.

+

The X driver can generally do a much better job of selecting the +"nvidia-auto-select" mode if the display device's EDID is +available. This is one reason why it is recommended to only use the +"UseEDID" X configuration option sparingly. Note that, rather than +globally disable all uses of the EDID with the "UseEDID" option, +you can individually disable each particular use of the EDID using +the "UseEDIDFreqs", "UseEDIDDpi", and/or the "NoEDIDModes" argument +in the "ModeValidation" X configuration option.

+

Mode Validation Reporting

+

When log verbosity is set to 6 or higher (see FAQ section on increasing the +amount of data printed in the X log file), the X log will record +every mode that is considered for each display device's mode pool, +and report whether the mode passed or failed. For modes that were +considered invalid, the log will report why the mode was considered +invalid.

+

Ensuring Identical Mode Timings

+

Some functionality, such as Active Stereo with TwinView, +requires control over exactly which mode timings are used. For +explicit control over which mode timings are used on each display +device, you can specify the ModeLine you want to use (using one of +the ModeLine generators available), and using a unique name. For +example, if you wanted to use 1024x768 at 120 Hz on each monitor in +TwinView with active stereo, you might add something like this to +the monitor section of your X configuration file:

+
+    # 1024x768 @ 120.00 Hz (GTF) hsync: 98.76 kHz; pclk: 139.05 MHz
+    Modeline "1024x768_120"  139.05  1024 1104 1216 1408  768 769 772 823 -HSync +Vsync
+
+

Then, in the Screen section of your X config file, specify a +MetaMode like this:

-    int attrib[] = {
-        GLX_RENDER_TYPE, GLX_RGBA_BIT,
-        GLX_DRAWABLE_TYPE, GLX_WINDOW_BIT,
-        GLX_RED_SIZE, 1,
-        GLX_GREEN_SIZE, 1,
-        GLX_BLUE_SIZE, 1,
-        GLX_ALPHA_SIZE, 1,
-        GLX_DOUBLEBUFFER, True,
-        GLX_DEPTH_SIZE, 1,
-        None };
-    GLXFBConfig *fbconfigs, fbconfig;
-    int numfbconfigs, render_event_base, render_error_base;
-    XVisualInfo *visinfo;
-    XRenderPictFormat *pictFormat;
-
-    /* Make sure we have the RENDER extension */
-    if(!XRenderQueryExtension(dpy, &render_event_base, &render_error_base)) {
-        fprintf(stderr, "No RENDER extension found\n");
-        exit(EXIT_FAILURE);
-    }
-
-    /* Get the list of FBConfigs that match our criteria */
-    fbconfigs = glXChooseFBConfig(dpy, scrnum, attrib, &numfbconfigs);
-    if (!fbconfigs) {
-        /* None matched */
-        exit(EXIT_FAILURE);
-    }
-
-    /* Find an FBConfig with a visual that has a RENDER picture format that
-     * has alpha */
-    for (i = 0; i < numfbconfigs; i++) {
-        visinfo = glXGetVisualFromFBConfig(dpy, fbconfigs[i]);
-        if (!visinfo) continue;
-        pictFormat = XRenderFindVisualFormat(dpy, visinfo->visual);
-        if (!pictFormat) continue;
-
-        if(pictFormat->direct.alphaMask > 0) {
-            fbconfig = fbconfigs[i];
-            break;
-        }
-
-        XFree(visinfo);
-    }
-
-    if (i == numfbconfigs) {
-        /* None of the FBConfigs have alpha.  Use a normal (opaque)
-         * FBConfig instead */
-        fbconfig = fbconfigs[0];
-        visinfo = glXGetVisualFromFBConfig(dpy, fbconfig);
-        pictFormat = XRenderFindVisualFormat(dpy, visinfo->visual);
-    }
-
-    XFree(fbconfigs);
+    Option "MetaModes" "1024x768_120, 1024x768_120"

-

When rendering to a 32-bit window, keep in mind that the X -RENDER extension, used by most composite managers, expects -"premultiplied alpha" colors. This means that if your color has -components (r,g,b) and alpha value a, then you must render (a*r, -a*g, a*b, a) into the target window.

-

More information about Composite can be found at http://freedesktop.org/Software/CompositeExt

+

Additional Information

+

An XFree86 ModeLine generator, conforming to the GTF Standard is +available at http://gtf.sourceforge.net/. Additional generators can +be found by searching for "modeline" on freshmeat.net.

+"chapter-17.html">Prev  +Chapter 17. Configuring a Notebook  + Chapter 19. Configuring Flipping and UBB
Prev  Up  
-Appendix D. Configuring Low-level Parameters  Home - Chapter 19. Using the nvidia-settings Utility
diff --git a/doc/html/chapter-19.html b/doc/html/chapter-19.html index 42f7d40..97ce873 100644 --- a/doc/html/chapter-19.html +++ b/doc/html/chapter-19.html @@ -5,24 +5,23 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Chapter 19. Using the nvidia-settings -Utility +Chapter 19. Configuring Flipping and UBB +"Chapter 18. Programming Modes"> +"Chapter 20. The Sysctl Interface">
- + +Chapter 18. Programming Modes  + Chapter 20. The Sysctl Interface
Chapter 19. Using the -nvidia-settings UtilityChapter 19. Configuring +Flipping and UBB
-

Chapter 19. Using the -nvidia-settings Utility

+

Chapter 19. Configuring Flipping and +UBB

-

A graphical configuration utility, nvidia-settings, is included with the -NVIDIA FreeBSD graphics driver. After installing the driver and -starting X, you can run this configuration utility by running:

-
-    % nvidia-settings
-
-

in a terminal window.

-

Detailed information about the configuration options available -are documented in the help window in the utility.

-

For more information, see the nvidia-settings man page or the -user guide available here: ftp://download.nvidia.com/XFree86/Linux-x86/nvidia-settings-user-guide.txt

-

The source code to nvidia-settings is released as GPL and is -available here: ftp://download.nvidia.com/XFree86/nvidia-settings/

-

If you have trouble running the nvidia-settings binary shipped -with the NVIDIA FreeBSD Graphics Driver, refer to the -nvidia-settings entry in Chapter 6, Common -Problems.

+

The NVIDIA Accelerated FreeBSD Graphics Driver supports Unified +Back Buffer (UBB) and OpenGL Flipping. These features can provide +performance gains in certain situations.

+
+
    +
  • +

    Unified Back Buffer (UBB): UBB is available only on the Quadro +family of GPUs (Quadro4 NVS excluded) and is enabled by default +when there is sufficient video memory available. This can be +disabled with the UBB X config option described in Appendix B, X +Config Options. When UBB is enabled, all windows share the +same back, stencil and depth buffers. When there are many windows, +the back, stencil and depth usage will never exceed the size of +that used by a full screen window. However, even for a single small +window, the back, stencil, and depth video memory usage is that of +a full screen window. In that case video memory may be used less +efficiently than in the non-UBB case.

    +
    • +
  • +

    Flipping: When OpenGL flipping is enabled, OpenGL can perform +buffer swaps by changing which buffer the DAC scans out rather than +copying the back buffer contents to the front buffer; this is +generally a much higher performance mechanism and allows tearless +swapping during the vertical retrace (when __GL_SYNC_TO_VBLANK is +set). The conditions under which OpenGL can flip are slightly +complicated, but in general: on GeForce or newer hardware, OpenGL +can flip when a single full screen unobscured OpenGL application is +running, and __GL_SYNC_TO_VBLANK is enabled. Additionally, OpenGL +can flip on Quadro hardware even when an OpenGL window is partially +obscured or not full screen or __GL_SYNC_TO_VBLANK is not +enabled.

    +
    • +
+
+

@@ -82,12 +94,11 @@ Problems.

-Chapter 18. Using the X Composite Extension  Home - Chapter 20. Configuring SLI and Multi-GPU -FrameRendering
diff --git a/doc/html/chapter-20.html b/doc/html/chapter-20.html index 1bb5bdf..8d1fdb1 100644 --- a/doc/html/chapter-20.html +++ b/doc/html/chapter-20.html @@ -5,24 +5,23 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Chapter 20. Configuring SLI and Multi-GPU -FrameRendering +Chapter 20. The Sysctl Interface +"Chapter 19. Configuring Flipping and UBB"> +"Chapter 21. Configuring Low-level Parameters">
- + +Chapter 19. Configuring Flipping and UBB  + Chapter 21. Configuring Low-level Parameters
Chapter 20. Configuring -SLI and Multi-GPU FrameRenderingChapter 20. The Sysctl +Interface
-

Chapter 20. Configuring SLI and Multi-GPU -FrameRendering

+

Chapter 20. The Sysctl +Interface

-

The NVIDIA FreeBSD driver contains support for NVIDIA SLI -FrameRendering and NVIDIA Multi-GPU FrameRendering. Both of these -technologies allow an OpenGL application to take advantage of -multiple GPUs to improve visual performance.

-

The distinction between SLI and Multi-GPU is straightforward. -SLI is used to leverage the processing power of GPUs across two or -more graphics cards, while Multi-GPU is used to leverage the -processing power of two GPUs colocated on the same graphics card. -If you want to link together separate graphics cards, you should -use the "SLI" X config option. Likewise, if you want to link -together GPUs on the same graphics card, you should use the -"MultiGPU" X config option. If you have two cards, each with two -GPUs, and you wish to link them all together, you should use the -"SLI" option.

-

In FreeBSD, with two GPUs SLI and Multi-GPU can both operate in -one of three modes: Alternate Frame Rendering (AFR), Split Frame -Rendering (SFR), and Antialiasing (AA). When AFR mode is active, -one GPU draws the next frame while the other one works on the frame -after that. In SFR mode, each frame is split horizontally into two -pieces, with one GPU rendering each piece. The split line is -adjusted to balance the load between the two GPUs. AA mode splits -antialiasing work between the two GPUs. Both GPUs work on the same -scene and the result is blended together to produce the final -frame. This mode is useful for applications that spend most of -their time processing with the CPU and cannot benefit from AFR.

-

With four GPUs, the same options are applicable. AFR mode cycles -through all four GPUs, each GPU rendering a frame in turn. SFR mode -splits the frame horizontally into four pieces. AA mode splits the -work between the four GPUs, allowing antialiasing up to 64x. With -four GPUs SLI can also operate in an additional mode, Alternate -Frame Rendering of Antialiasing. (AFR of AA). With AFR of AA, pairs -of GPUs render alternate frames, each GPU in a pair doing half of -the antialiasing work. Note that these scenarios apply whether you -have four separate cards or you have two cards, each with two -GPUs.

-

Multi-GPU is enabled by setting the "MultiGPU" option in the X -configuration file; see Appendix F, X -Config Options for details about the "MultiGPU" option.

-

The nvidia-xconfig utility can be used to set the "MultiGPU" -option, rather than modifying the X configuration file by hand. For -example:

-
-    % nvidia-xconfig --multigpu=on
-
-

-

SLI is enabled by setting the "SLI" option in the X -configuration file; see Appendix F, X -Config Options for details about the SLI option.

-

The nvidia-xconfig utility can be used to set the SLI option, -rather than modifying the X configuration file by hand. For -example:

-
-    % nvidia-xconfig --sli=on
-
+

The sysctl interface allows you to obtain run-time information +about the driver, any installed NVIDIA graphics cards and the AGP +status. It also allows you to control low-level configuration +options and/or overrides.

+

The various pieces of information are held in a hierarchy under +hw.nvidia and are accessible with the sysctl(8) command.

+
+

NVIDIA sysctl Entries

+
+
hw.nvidia.version
+
+

Prints the installed driver revision

+
+
hw.nvidia.cards.n.*
+
+

These OIDs provide information about NVIDIA device 'n':

+
+ +++ + + + + + + + + + + + + + + + + + + + + + + + + +
IDDescription
modelthe device's product name
irqthe IRQ claimed by this device
vbiosthe device's Video BIOS revision
typethe bus type of this device
+

-

Hardware requirements

-

SLI functionality requires:

-
-
    -
  • -

    Identical PCI-Express graphics cards

    -
    • -
  • -

    A supported motherboard

    -
    • -
  • -

    In most cases, a video bridge connecting the two graphics -cards

    -
    • -
+
+
hw.nvidia.agp.host-bridge.*, +hw.nvidia.agp.card.*,
+
+

These OIDs provide information about the AGP capabilities of the +installed AGP graphics card and host-bridge respectively. These +values are most likely to be correct after system boot and before +the X server is started (and the AGP subsystem initialized).

+
+ +++ + + + + + + + + + + + + + + + + + + + + + + + + +
IDDescription
ratesthe AGP rates supported by this device
fwif the device supports AGP fast-writes
sbaif the device supports AGP side-band-addressing
registersthe device's AGP registers, status:command
-

For the latest in supported SLI and Multi-GPU configurations, -including SLI- and Multi-GPU capable GPUs and SLI-capable -motherboards, see http://www.slizone.com.

-

Other Notes and Requirements

-

The following other requirements apply to SLI and Multi-GPU:

-
-
    -
  • -

    Mobile GPUs are NOT supported

    -
    • -
  • -

    SLI on Quadro-based graphics cards always requires a video -bridge

    -
    • -
  • -

    TwinView is also not supported with SLI or Multi-GPU. Only one -display can be used when SLI or Multi-GPU is enabled.

    -
    • -
  • -

    If X is configured to use multiple screens and screen 0 has SLI -or Multi-GPU enabled, the other screens will be disabled. Note that -if SLI or Multi-GPU is enabled, the GPUs used by that configuration -will be unavailable for single GPU rendering.

    -
    • -
+

+
+
hw.nvidia.agp.status.*
+
+

Prints AGP status information based on the AGP command registers +of the host-bridge and of the AGP card.

+
+ +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
IDDescription
statusif AGP is enabled or disabled
driverwhich driver is being used
ratethe programmed AGP rate
fwif fast-writes are enabled or disabled
sbaif side-band-addressing is enabled or disabled

-
- -+ +
hw.nvidia.registry.*
+
+

Low-level kernel module configuration options. Changing these is +typically not necessary and potentially dangerous. If you do need +to change any of these options, you will need to do so before you start the X server.

+
+
+++ + + + + + + - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + +
IDDescription
-

20.1. -Frequently Asked SLI and Multi-GPU Questions

-
-

Why is glxgears slower when SLI or Multi-GPU is -enabled?

-
-

When SLI or Multi-GPU is enabled, the NVIDIA driver must -coordinate the operations of all GPUs when each new frame is -swapped (made visible). For most applications, this GPU -synchronization overhead is negligible. However, because glxgears -renders so many frames per second, the GPU synchronization overhead -consumes a significant portion of the total time, and the framerate -is reduced.

-
-

Why is Doom 3 slower when SLI or Multi-GPU is -enabled?

-
-

The NVIDIA Accelerated FreeBSD Graphics Driver does not -automatically detect the optimal SLI or Multi-GPU settings for -games such as Doom 3 and Quake 4. To work around this issue, the -environment variable __GL_DOOM3 can be set to tell OpenGL that Doom -3's optimal settings should be used. In Bash, this can be done in -the same command that launches Doom 3 so the environment variable -does not remain set for other OpenGL applications started in the -same session:

-
-    % __GL_DOOM3=1 doom3
-
-

Doom 3's startup script can also be modified to set this -environment variable:

-
-    #!/bin/sh
-    # Needed to make symlinks/shortcuts work.
-    # the binaries must run with correct working directory
-    cd "/usr/local/games/doom3/"
-    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:.
-    export __GL_DOOM3=1
-    exec ./doom.x86 "$@"
-
-

This environment variable is temporary and will be removed in -the future.

-
statusif AGP is enabled or disabled
driverwhich driver is being used
ratethe programmed AGP rate
fwif fast-writes are enabled or disabled
sbaif side-band-addressing is enabled or disabled
+

+
+
+
+

@@ -229,11 +233,11 @@ the future.

-Chapter 19. Using the nvidia-settings Utility  Home - Chapter 21. Configuring Frame Lock and Genlock
diff --git a/doc/html/chapter-21.html b/doc/html/chapter-21.html index 7984dde..4a837d5 100644 --- a/doc/html/chapter-21.html +++ b/doc/html/chapter-21.html @@ -5,24 +5,24 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Chapter 21. Configuring Frame Lock and -Genlock +Chapter 21. Configuring Low-level +Parameters +"Chapter 20. The Sysctl Interface"> +"Chapter 22. Using the X Composite Extension">
+Low-level Parameters - + + Chapter 22. Using the X Composite Extension
Chapter 21. Configuring -Frame Lock and Genlock
-

Chapter 21. Configuring Frame Lock and -Genlock

+

Chapter 21. Configuring Low-level +Parameters

-

NOTE: Frame Lock and Genlock features are supported only on -specific hardware, as noted below.

-

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.

-

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.

-

Definition of Terms

-

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.

-

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.

-

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.

-

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.

-

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.

-

Supported Hardware

-

Frame lock and genlock are supported for the following -hardware:

+

The NVIDIA resource manager recognizes several low-level +configuration parameters that can be set using the sysctl driver +interface before the X +server is started. Normally you should not need to modify any of +these parameters, but it is sometimes necessary or desirable to do +so.

+

To view the current settings of these parameters, you need to +issue this sysctl command (nvidia.ko +needs to be loaded):

+
+    % sysctl -a hw.nvidia.registry
+
+

To change any of the parameters, you need to pass the complete +name of the OID followed by '=' and the new value, e.g.:

+
+    % sysctl hw.nvidia.registry.EnableVia4x=1
+
+

It is possible to automate setting these parameters by adding +them to the /etc/sysctl.conf file. +See man 5 +sysctl.conf for details.

+

The following parameters are recognized by nvidia.ko:

+
+

Resource Manager Parameters

+
+
VideoMemoryTypeOverride
+
+

We normally detect memory type on TNT cards by scanning the +embedded BIOS. Unfortunately, we've seen some cases where a TNT +card has been flashed with the wrong BIOS. For example, an SDRAM +based TNT has been flashed with an SGRAM BIOS, and therefore claims +to be an SGRAM TNT. We've therefore provided an override here. Make +sure to set the value toe the type of memory used on your card.

@@ -95,542 +86,225 @@ hardware:

- - + + - - + + - - + + + +
Card ValueMeaning
Quadro FX 3000G 1SDRAM
Quadro FX G-Sync, used in conjunction with a Quadro FX 4400, -Quadro FX 4500, or Quadro FX 5500 2SGRAM
+
+

Note that we can only do so much here. There are border cases +where even this fails. For example, if 2 TNT cards are in the same +system, one SGRAM, one SDRAM.

+

This option is disabled by default, see below for information on +how to enable it.

+
+
EnableVia4x
+
+

We've had problems with some Via chipsets in 4x mode, we need +force them back down to 2x mode. If you'd like to experiment with +retaining 4x mode, you may try setting this value to 1 If that +hangs the system, you're stuck with 2x mode; there's nothing we can +do about it.

+
+ +++ + - - + + + + + + + + + + + +
Quadro FX G-Sync II, used in conjunction with a Quadro FX 4600, -or Quadro FX 5600 ValueMeaning
0disable AGP 4x on Via chipsets (default)
1enable AGP 4x on Via chipsets

-

Hardware Setup

-

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.

-

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.

-
-
    -
  1. -

    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 -Chapter 20, Configuring SLI and Multi-GPU -FrameRendering) 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.

    -
    2. -
  2. -

    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.

    -
    3. -
  3. -

    Connect the other end of the ribbon cable to the fourteen-pin -connector on the graphics card.

    -
    4. -
-
-

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 FreeBSD -Driver Set. If you have not done so, see Chapter 2, -Installing the NVIDIA Driver.

-

Configuration with nvidia-settings GUI

-

Frame lock and genlock are configured through the -nvidia-settings utility. See the nvidia-settings(1) 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).

-

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.

-

After the system has booted and X Windows has been started, run -nvidia-settings as

-
-    % nvidia-settings
-
-

You may wish to start this utility before continuing, as we -refer to it frequently in the subsequent discussion.

-

The setup of genlock and frame lock are described separately. We -then describe the use of genlock and frame lock together.

-

Genlock Setup

-

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.

-

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 system:m, e.g.:

-
-    mycomputer.domain.com:0
-
-

or

-
-    localhost:0
-
-

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, -"Port 0"/"Port 1" 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 check boxes, -refresh rate, "Timing" LED and "Stereo" LED.

-

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" check box of the -desired display device.

-

If you are using a G-Sync card, you must also click the "Use -House Sync if Present" check box. 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.

-

Modifications to genlock settings (e.g., "Use House Sync if -Present", "Add Devices...") must be done while synchronization is -disabled.

-

-

Frame Lock Setup

-

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 Chapter 16, -Programming Modes for information on mode timings.

-

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). -Do not connect a frame lock port to an -ethernet card or hub. Doing so may permanently damage the -hardware. 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.

-

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.

-

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 "Port 0" and "Port 1" 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.

-

Any X Server can be added to the frame lock group, provided -that

-
-
    -
  1. -

    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.

    -
    2. -
  2. -

    The system driving nvidia-settings can locate and has display -privileges on the X server that is to be included for frame -lock.

    -
    3. -
+
+
EnableALiAGP
+
+

Some ALi chipsets (ALi1541, ALi1647) are known to cause severe +system stability problems with AGP enabled. To avoid lockups, we +disable AGP on systems with these chipsets by default. It appears +that updating the system BIOS and using recent versions of the +kernel AGP Gart driver can make such systems much more stable. If +you own a system with one of the aforementioned chipsets and had it +working reasonably well previously, or if you want to experiment +with BIOS and AGPGART revisions, you can re-enable AGP support by +setting this option to 1.

+
+ +++ + + + + + + + + + + + + + + + + +
ValueMeaning
0disable AGP on Ali1541 and ALi1647 (default)
1enable AGP on Ali1541 and ALi1647
-

A system can gain display privileges on a remote system by -executing

-
-    % xhost +
-
-

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.

-

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 Chapter 16, -Programming Modes for information on mode timings.

-

Modifications to frame lock settings (e.g. "Add/Remove -Devices...") must be done while synchronization is disabled.

-

nvidia-settings will not automatically enable Frame Lock via the -nvidia-settings.rc file. To enable Frame Lock when starting the X -server, a line such as the following can be added to the -~/.xinitrc file:

-
-    # nvidia-settings -a [gpu:0]/FrameLockEnable=1
-

-

Frame Lock + Genlock

-

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 Frame -Lock Setup, 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 check box 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" check box. 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.

-

Configuration with nvidia-settings command line

-

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.)

-

To properly configure Frame Lock, the following steps should be -completed:

-
-
    -
  1. -

    Make sure Frame Lock Sync is disabled on all GPUs.

    -
    2. -
  2. -

    Make sure all display devices that are to be frame locked have -the same refresh rate.

    -
    3. -
  3. -

    Configure which (display/GPU) device should be the master.

    -
    4. -
  4. -

    Configure house sync (if applicable).

    -
    5. -
  5. -

    Configure the slave display devices.

    -
    6. -
  6. -

    Enable frame lock sync on the master GPU.

    -
    7. -
  7. -

    Enable frame lock sync on the slave GPUs.

    -
    8. -
  8. -

    Toggle the test signal on the master GPU (for testing the -hardware connectivity.)

    -
    9. -
+
+
NvAGP
+
+

This options controls which AGP GART driver is used when no +explicit request is made to change the default (X server).

+
+ +++ + + + + + + + + + + + + + + + + + + + + + + + + +
ValueMeaning
0disable AGP support
1use the NVIDIA builtin driver (if possible)
2use the kernel's AGPGART driver (if possible)
3use any available driver (try 2, then 1)
-

-

For a full list of the nvidia-settings Frame Lock attributes, -please see the nvidia-settings(1) man -page. Examples:

-
-
    -
  1. -

    1 System, 1 Frame Lock board, 1 GPU, and 1 display device -syncing to the house signal:

    -
    -  # - 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 frame lock
-  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
-
    -

    -
    2. -
  2. -

    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:

    -
    -  # - 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 frame lock on server
-  nvidia-settings -a myserver:0[gpu:0]/FrameLockEnable=1
-
-  # - Enable frame lock 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
-
    -

    -
    3. -
  3. -

    1 System, 4 GPUs, 2 Frame Lock boards and 2 display devices per -GPU syncing from the first GPU's display device:

    -
    -  # - 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=0
-
-  # - 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 frame lock on master GPU
-  nvidia-settings -a [gpu:0]/FrameLockEnable=1
-
-  # - Enable frame lock 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
-
    -

    -
    4. -
+

Note that the NVIDIA internal AGP GART driver will not be used +if AGPGART was either statically linked into your kernel or built +as a kernel module and loaded before the NVIDIA kernel module.

+
+
ReqAGPRate
+
+

Normally, the driver will compare speed modes of the chipset and +the card, picking the highest common rate. This key forces a +maximum limit, to limit the driver to lower speeds. The driver will +not attempt a speed beyond what the chipset and card claim they are +capable of.

+

Make sure you really know what you're doing before you enable +this override. By default, AGP drivers will enable the fastest AGP +rate your card and motherboard chipset are capable of. Then, in +some cases, our driver will force this rate down to work around +bugs in both our chipsets, and motherboard chipsets. Using this +variable will override our bug fixes. This may be desirable in some +cases, but not most. This is completely +unsupported!

+

This option expects a bitmask (7 = 1|2|3|4, 3=1|2, etc.)

+

This option is disabled by default, see below for information on +how to enable it.

+
+
EnableAGPSBA
+
+

For stability reasons, the driver will not use Side Band +Addressing even if both the host chipset and the AGP card support +it. You may override this behavior with the following registry key. +This is completely +unsupported!

+
+ +++ + + + + + + + + + + + + + + + + +
ValueMeaning
0disable Side Band Addressing (default on x86, see below)
1enable Side Band Addressing (if supported)

-

Leveraging Frame Lock/Genlock in OpenGL

-

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.

-

Frame Lock Restrictions:

-

The following restrictions must be met for enabling frame -lock:

-
-
    -
  1. -

    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.

    -
    2. -
  2. -

    All X Screens (driving the selected client/server display -devices) must have the same stereo setting. See Appendix F, X -Config Options for instructions on how to set the stereo X -option.

    -
    3. -
  3. -

    The frame lock server (master) display device must be on a GPU -on the primary connector to a G-Sync device.

    -
    4. -
  4. -

    If connecting a single GPU to a G-Sync device, the primary -connector must be used.

    -
    5. -
  5. -

    In configurations with more than one display device per GPU, we -recommend enabling frame lock on all display devices on those -GPUs.

    -
    6. -
  6. -

    Virtual terminal switching or mode 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.

    -
    7. -
+
+
EnableAGPFW
+
+

Similar to Side Band Addressing, Fast Writes are disabled by +default. If you wish to enable them on systems that support them, +you can do so with this registry key. Note that this may render +your system unstable with many AGP chipsets. This is completely unsupported!

+
+ +++ + + + + + + + + + + + + + + + + +
ValueMeaning
0disable Fast Writes (default)
1enable Fast Writes

-

Supported Frame Lock Configurations:

-

The following configurations are currently supported:

-
-
    -
  1. -

    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.

    -
    2. -
  2. -

    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.

    -
    3. -
  3. -

    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.

    -
    4. -
  4. -

    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.

    -
    5. -
  5. -

    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.

    -
    6. -
  6. -

    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.

    -
    7. -
+
+

@@ -646,13 +320,12 @@ extension are not supported.

"chapter-22.html">Next
-Chapter 20. Configuring SLI and Multi-GPU -FrameRendering Chapter 20. The +Sysctl Interface  Home - Chapter 22. Configuring SDI Video Output
diff --git a/doc/html/chapter-22.html b/doc/html/chapter-22.html index 96f4d11..8b36ed4 100644 --- a/doc/html/chapter-22.html +++ b/doc/html/chapter-22.html @@ -5,23 +5,24 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Chapter 22. Configuring SDI Video Output +Chapter 22. Using the X Composite +Extension +"Chapter 21. Configuring Low-level Parameters"> +"Chapter 23. Using the nvidia-settings Utility">
- + +Chapter 21. Configuring Low-level Parameters  + Chapter 23. Using the nvidia-settings Utility
Chapter 22. Configuring -SDI Video OutputChapter 22. Using the X +Composite Extension
-

Chapter 22. Configuring SDI Video Output

+

Chapter 22. Using the X +Composite Extension

-

Broadcast, film, and video post production and digital cinema -applications can require Serial Digital (SDI) or High Definition -Serial Digital (HD-SDI) video output. SDI/HD-SDI is a digital video -interface used for the transmission of uncompressed video signals -as well as packetized data. SDI is standardized in ITU-R BT.656 and -SMPTE 259M while HD-SDI is standardized in SMPTE 292M. SMPTE 372M -extends HD-SDI to define a dual-link configuration that uses a pair -of SMPTE 292M links to provide a 2.970 Gbit/second interface. SMPTE -424M extends the interface further to define a single 2.97 -Gbit/second serial data link.

-

SDI and HD-SDI video output is provided through the use of the -NVIDIA driver along with an NVIDIA SDI output daughter board. In -addition to single- and dual-link SDI/HD-SDI digital video output, -frame lock and genlock synchronization are provided in order to -synchronize the outgoing video with an external source signal (see -Chapter 21, -Configuring Frame Lock and Genlock for details on these -technologies). This section describes the setup and use of the SDI -video output.

-

Hardware Setup

-

Before you begin, you should check that your hardware has been -properly installed. If you are using the Quadro FX 4000 SDI, the -SDI/HD-SDI hardware is located on the dual-slot card itself, and -after installing the card, no additional setup is necessary. If you -are using the Quadro FX 4500/5500 SDI or Quadro FX 4600/5600 SDI -II, the following additional setup steps are required in order to -connect the SDI daughter card to the graphics card. These steps -must be performed when the system is off.

-
-
    +

    X.Org X servers, beginning with X11R6.8.0, contain experimental +support for a new X protocol extension called Composite. This +extension allows windows to be drawn into pixmaps instead of +directly onto the screen. In conjunction with the Damage and Render +extensions, this allows a program called a composite manager to +blend windows together to draw the screen.

    +

    Performance will be degraded significantly if the RenderAccel option is disabled in +xorg.conf. See Appendix B, X +Config Options for more details.

    +

    When the NVIDIA X driver is used with an X.Org X server +X11R6.9.0 or newer and the Composite extension is enabled, NVIDIA's +OpenGL implementation interacts properly with the Damage and +Composite X extensions. This means that OpenGL rendering is drawn +into offscreen pixmaps and the X server is notified of the Damage +event when OpenGL renders to the pixmap. This allows OpenGL +applications to behave properly in a composited X desktop.

    +

    If the Composite extension is enabled on an X server older than +X11R6.9.0, then GLX will be disabled. You can force GLX on while +Composite is enabled on pre-X11R6.9.0 X servers with the +AllowGLXWithComposite X +configuration option. However, GLX will not render correctly in +this environment. Upgrading your X server to X11R6.9.0 or newer is +recommended.

    +

    You can enable the Composite X extension by running +nvidia-xconfig +--composite. Composite can be disabled with +nvidia-xconfig +--no-composite. See the nvidia-xconfig(1) man page +for details.

    +

    If you are using Composite with GLX, it is recommended that you +also enable the DamageEvents X +option for enhanced performance. If you are using an OpenGL-based +composite manager, you may also need the DisableGLXRootClipping option to obtain +proper output.

    +

    The Composite extension also causes problems with other driver +components:

    +
    +
    • -

      Insert the NVIDIA SDI Output card into any available expansion -slot within six inches of the NVIDIA Quadro graphics card. Secure -the card's bracket using the method provided by the chassis -manufacturer (usually a thumb screw or an integrated latch).

      +

      In X servers prior to X.Org 7.1, Xv cannot draw into pixmaps +that have been redirected offscreen and will draw directly onto the +screen instead. For some programs you can work around this issue by +using an alternative video driver. For example, "mplayer -vo x11" +will work correctly, as will "xine -V xshm". If you must use Xv +with an older server, you can also disable the compositing manager +and re-enable it when you are finished.

      +

      On X.Org 7.1 and higher, the driver will properly redirect video +into offscreen pixmaps. Note that the Xv adaptors will ignore the +sync-to-vblank option when drawing into a redirected window.

    • -

      Connect one end of the 14-pin ribbon cable to the G-Sync -connector on the NVIDIA Quadro graphics card, and the other end to -the NVIDIA SDI output card.

      +

      Workstation overlays, stereo visuals, and the unified back +buffer (UBB) are incompatible with Composite. These features will +be automatically disabled when Composite is detected.

    • -

      On Quadro FX 4500/5500 SDI, connect the SMA-to-BNC cables by -screwing the male SMA connectors onto the female SMA connectors on -the NVIDIA SDI output card. On Quadro FX 4600/5600 SDI II, this -step is not necessary: the SDI II has BNC connectors rather than -SMA connectors.

      +

      The Composite extension is currently incompatible with Xinerama, +due to limitations in the X.Org X server. Composite will be +automatically disabled when Xinerama is enabled.

      • -
    • -

      Connect the DVI-loopback connector by connecting one end of the -DVI cable to the DVI connector on the NVIDIA SDI output card and -the other end to the "north" DVI connector on the NVIDIA Quadro -graphics card. The "north" DVI connector on the NVIDIA Quadro -graphics card is the DVI connector that is the farthest from the -graphics card PCI-E connection to the motherboard. The SDI output -card will NOT function properly if this cable is connected to the -"south" DVI connector.

      -
      • -
-
-

Once the above installation is complete, you may boot the system -and configure the SDI video output using nvidia-settings. These -instructions assume that you have already successfully installed -the NVIDIA FreeBSD Accelerated Graphics Driver. If you have not -done so, see Chapter 2, -Installing the NVIDIA Driver for details.

-

Clone Mode Configuration with nvidia-settings

-

SDI video output is configured through the nvidia-settings -utility. See the nvidia-settings(1) -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).

-

After the system has booted and X Windows has been started, run -nvidia-settings as

-
-    % nvidia-settings
-
-

When the NVIDIA X Server Settings page appears, follow the steps -below to configure the SDI video output.

-
-
    -
  1. -

    Click on the Graphics to Video -Out tree item on the side menu. This will open the -Graphics to Video Out page.

    -
    2. -
  2. -

    Go to the "Synchronization Options" subpage and choose a -synchronization method. From the Sync -Options drop down click the list arrow to the right and then -click the method that you want to use to synchronize the SDI -output.

    -
    - --- - - - - - - - - - - - - - - - - - - - - -
    Sync MethodDescription
    Free RunningThe SDI output will be synchronized with the timing chosen from -the SDI signal format list.
    GenlockSDI output will be synchronized with the external sync -signal.
    Frame LockThe SDI output will be synchronized with the timing chosen from -the SDI signal format list. In this case, the list of available -timings is limited to those timings that can be synchronized with -the detected external sync signal.
    +

    -

    Note that on Quadro FX 4600/5600 SDI II, you must first choose -the correct Sync Format before an incoming sync signal will be -detected.

    -
    3. -
  3. -

    From the top Graphics to Video Out page, choose the output video -format that will control the video resolution, field rate, and -SMPTE signaling standard for the outgoing video stream. From the -Clone Mode drop down box, click -the Video Format arrow and then -click the signal format that you would like to use. Note that only -those resolutions that are smaller or equal to the desktop -resolution will be available. Also, this list is pruned according -to the sync option selected. If genlock synchronization is chosen, -the output video format is automatically set to match the incoming -video sync format and this drop down list will be grayed out -preventing you from choosing another format. If frame lock -synchronization has been selected, then only those modes that are -compatible with the detected sync signal will be available.

    -
    4. -
  4. -

    Choose the output data format from the Output Data Format drop down list.

    -
    5. -
  5. -

    Click the Enable SDI Output -button to enable video output using the settings above. The status -of the SDI output can be verified by examining the LED indicators -in the Graphics to SDI property -page banner.

    -
    6. -
  6. -

    To subsequently stop SDI output, simply click on the button that -now says Disable SDI -Output.

    -
    7. -
  7. -

    In order to change any of the SDI output parameters such as the -Output Video Format, Output Data Format as well as the -Synchronization Delay, it is necessary to first disable the SDI -output.

    -
    8. -
-
-

-

Configuration for TwinView or as a Separate X Screen

-

SDI video output can be configured through the nvidia-settings X -Server Display Configuration page, for use in TwinView or as a -separate X screen. The SDI video output can be configured as if it -were a digital flat panel, choosing the resolution, refresh rate, -and position within the desktop.

-

Similarly, the SDI video output can be configured for use in -TwinView or as a separate X screen through the X configuration -file. The supported SDI video output modes can be requested by name -anywhere a mode name can be used in the X configuration file -(either in the "Modes" line, or in the "MetaModes" option). -E.g.,

+

This NVIDIA FreeBSD supports OpenGL rendering to 32-bit ARGB +windows on X.Org 7.2 and higher or when the AddARGBGLXVisuals X config file option is +enabled. If you are an application developer, you can use these new +visuals in conjunction with a composite manager to create +translucent OpenGL applications:

- Option "MetaModes" "CRT-0:nvidia-auto-select, DFP-1:1280x720_60.00_smpte296"
-    
+    int attrib[] = {
+        GLX_RENDER_TYPE, GLX_RGBA_BIT,
+        GLX_DRAWABLE_TYPE, GLX_WINDOW_BIT,
+        GLX_RED_SIZE, 1,
+        GLX_GREEN_SIZE, 1,
+        GLX_BLUE_SIZE, 1,
+        GLX_ALPHA_SIZE, 1,
+        GLX_DOUBLEBUFFER, True,
+        GLX_DEPTH_SIZE, 1,
+        None };
+    GLXFBConfig *fbconfigs, fbconfig;
+    int numfbconfigs, render_event_base, render_error_base;
+    XVisualInfo *visinfo;
+    XRenderPictFormat *pictFormat;
+
+    /* Make sure we have the RENDER extension */
+    if(!XRenderQueryExtension(dpy, &render_event_base, &render_error_base)) {
+        fprintf(stderr, "No RENDER extension found\n");
+        exit(EXIT_FAILURE);
+    }
+
+    /* Get the list of FBConfigs that match our criteria */
+    fbconfigs = glXChooseFBConfig(dpy, scrnum, attrib, &numfbconfigs);
+    if (!fbconfigs) {
+        /* None matched */
+        exit(EXIT_FAILURE);
+    }
+
+    /* Find an FBConfig with a visual that has a RENDER picture format that
+     * has alpha */
+    for (i = 0; i < numfbconfigs; i++) {
+        visinfo = glXGetVisualFromFBConfig(dpy, fbconfigs[i]);
+        if (!visinfo) continue;
+        pictFormat = XRenderFindVisualFormat(dpy, visinfo->visual);
+        if (!pictFormat) continue;
+
+        if(pictFormat->direct.alphaMask > 0) {
+            fbconfig = fbconfigs[i];
+            break;
+        }
+
+        XFree(visinfo);
+    }
+
+    if (i == numfbconfigs) {
+        /* None of the FBConfigs have alpha.  Use a normal (opaque)
+         * FBConfig instead */
+        fbconfig = fbconfigs[0];
+        visinfo = glXGetVisualFromFBConfig(dpy, fbconfig);
+        pictFormat = XRenderFindVisualFormat(dpy, visinfo->visual);
+    }
+
+    XFree(fbconfigs);
-

The mode names are reported in the nvidia-settings Display -Configuration page when in advanced mode.

-

Note that SDI "Clone Mode" as configured through the Graphics to -Video Out page in nvidia-settings is mutually exclusive with using -the SDI video output in TwinView or as a separate X screen.

+

+

When rendering to a 32-bit window, keep in mind that the X +RENDER extension, used by most composite managers, expects +"premultiplied alpha" colors. This means that if your color has +components (r,g,b) and alpha value a, then you must render (a*r, +a*g, a*b, a) into the target window.

+

More information about Composite can be found at http://freedesktop.org/Software/CompositeExt

@@ -250,11 +194,11 @@ the SDI video output in TwinView or as a separate X screen.

-Chapter 21. Configuring Frame Lock and Genlock  Home - Chapter 23. Configuring Depth 30 Displays
diff --git a/doc/html/chapter-23.html b/doc/html/chapter-23.html index 4f10ea8..3e90714 100644 --- a/doc/html/chapter-23.html +++ b/doc/html/chapter-23.html @@ -5,23 +5,24 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Chapter 23. Configuring Depth 30 Displays +Chapter 23. Using the nvidia-settings +Utility +"Chapter 22. Using the X Composite Extension"> +"Chapter 24. Configuring SLI and Multi-GPU FrameRendering">
- + +Chapter 22. Using the X Composite Extension  + Chapter 24. Configuring SLI and Multi-GPU +FrameRendering
Chapter 23. Configuring -Depth 30 DisplaysChapter 23. Using the +nvidia-settings Utility
-

Chapter 23. Configuring Depth 30 -Displays

+

Chapter 23. Using the +nvidia-settings Utility

-

This driver release supports X screens with screen depths of 30 -bits per pixel (10 bits per color component) on NVIDIA Quadro GPUs -based on G80 and higher chip architectures. This provides about 1 -billion possible colors, allowing for higher color precision and -smoother gradients.

-

When displaying a depth 30 image on a digital flat panel, the -color data will be dithered to 8 or 6 bits per pixel, depending on -the capabilities of the flat panel. VGA outputs can display the -full 10 bit range of colors.

-

To work reliably, depth 30 requires X.Org 7.3 or higher and -pixman 0.11.6 or higher.

-

In addition to the above software requirements, many X -applications and toolkits do not understand depth 30 visuals as of -this writing. Some programs may work correctly, some may work but -display incorrect colors, and some may simply fail to run. In -particular, many OpenGL applications request 8 bits of alpha when -searching for FBConfigs. Since depth 30 visuals have only 2 bits of -alpha, no suitable FBConfigs will be found and such applications -will fail to start.

+

A graphical configuration utility, nvidia-settings, is included with the +NVIDIA FreeBSD graphics driver. After installing the driver and +starting X, you can run this configuration utility by running:

+
+    % nvidia-settings
+
+

in a terminal window.

+

Detailed information about the configuration options available +are documented in the help window in the utility.

+

For more information, see the nvidia-settings man page.

+

The source code to nvidia-settings is released as GPL and is +available here: ftp://download.nvidia.com/XFree86/nvidia-settings/

+

If you have trouble running the nvidia-settings binary shipped +with the NVIDIA FreeBSD Graphics Driver, refer to the +nvidia-settings entry in Chapter 8, Common +Problems.

@@ -76,12 +78,12 @@ will fail to start.

-Chapter 22. Configuring SDI Video Output  Home - Chapter 24. NVIDIA Contact Info and Additional -Resources
diff --git a/doc/html/chapter-24.html b/doc/html/chapter-24.html index d6849e0..6b09706 100644 --- a/doc/html/chapter-24.html +++ b/doc/html/chapter-24.html @@ -5,24 +5,24 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Chapter 24. NVIDIA Contact Info and Additional -Resources +Chapter 24. Configuring SLI and Multi-GPU +FrameRendering +"Chapter 23. Using the nvidia-settings Utility"> +"Chapter 25. Configuring Frame Lock and Genlock">
- + +Chapter 23. Using the nvidia-settings Utility  + Chapter 25. Configuring Frame Lock and Genlock
Chapter 24. NVIDIA Contact -Info and Additional ResourcesChapter 24. Configuring +SLI and Multi-GPU FrameRendering
-

Chapter 24. NVIDIA Contact Info and -Additional Resources

+

Chapter 24. Configuring SLI and Multi-GPU +FrameRendering

-

If you believe that you have found a bug or have a problem that -you need assistance with and cannot find the solution elsewhere, or -if you have found inaccuracies in this document, send email to -

+

The NVIDIA FreeBSD driver contains support for NVIDIA SLI +FrameRendering and NVIDIA Multi-GPU FrameRendering. Both of these +technologies allow an OpenGL application to take advantage of +multiple GPUs to improve visual performance.

+

The distinction between SLI and Multi-GPU is straightforward. +SLI is used to leverage the processing power of GPUs across two or +more graphics cards, while Multi-GPU is used to leverage the +processing power of two GPUs colocated on the same graphics card. +If you want to link together separate graphics cards, you should +use the "SLI" X config option. Likewise, if you want to link +together GPUs on the same graphics card, you should use the +"MultiGPU" X config option. If you have two cards, each with two +GPUs, and you wish to link them all together, you should use the +"SLI" option.

+

Rendering Modes

+

In FreeBSD, with two GPUs SLI and Multi-GPU can both operate in +one of three modes: Alternate Frame Rendering (AFR), Split Frame +Rendering (SFR), and Antialiasing (AA). When AFR mode is active, +one GPU draws the next frame while the other one works on the frame +after that. In SFR mode, each frame is split horizontally into two +pieces, with one GPU rendering each piece. The split line is +adjusted to balance the load between the two GPUs. AA mode splits +antialiasing work between the two GPUs. Both GPUs work on the same +scene and the result is blended together to produce the final +frame. This mode is useful for applications that spend most of +their time processing with the CPU and cannot benefit from AFR.

+

With four GPUs, the same options are applicable. AFR mode cycles +through all four GPUs, each GPU rendering a frame in turn. SFR mode +splits the frame horizontally into four pieces. AA mode splits the +work between the four GPUs, allowing antialiasing up to 64x. With +four GPUs SLI can also operate in an additional mode, Alternate +Frame Rendering of Antialiasing. (AFR of AA). With AFR of AA, pairs +of GPUs render alternate frames, each GPU in a pair doing half of +the antialiasing work. Note that these scenarios apply whether you +have four separate cards or you have two cards, each with two +GPUs.

+

With a Quadro Plex Visual Computing System (VCS), the same +options as above are available, if your Quadro Plex VCS has two or +four GPUs. In addition, there is a special SLI Mosaic Mode to +extend a single X screen transparently across all of the available +display outputs on the Quadro Plex VCS.

+

Enabling Multi-GPU

+

Multi-GPU is enabled by setting the "MultiGPU" option in the X +configuration file; see Appendix B, X +Config Options for details about the "MultiGPU" option.

+

The nvidia-xconfig utility can be used to set the "MultiGPU" +option, rather than modifying the X configuration file by hand. For +example:

+
+    % nvidia-xconfig --multigpu=on
+

-
-

Additional Resources

-
-
XFree86 Video Timings HOWTO
-
-

http://www.tldp.org/HOWTO/XFree86-Video-Timings-HOWTO/index.html

-
-
The X.Org Foundation
-
-

http://www.x.org

-
-
OpenGL
-
-

http://www.opengl.org

-
-
+

Enabling SLI

+

SLI is enabled by setting the "SLI" option in the X +configuration file; see Appendix B, X +Config Options for details about the SLI option.

+

The nvidia-xconfig utility can be used to set the SLI option, +rather than modifying the X configuration file by hand. For +example:

+
+    % nvidia-xconfig --sli=on
+
+

+

Enabling SLI Mosaic Mode

+

The simplest way to configure Mosaic Mode using a grid of +monitors is to use nvidia-settings (see Chapter 23, +Using the nvidia-settings Utility). The steps to perform +this configuration are as follows:

+
+
    +
  1. +

    Install your Quadro Plex VCS into the system, following the +steps provided in the Quadro Plex Installation Guide.

    +
    2. +
  2. +

    Connect all of the monitors you would like to use to the Quadro +Plex VCS. If you are going to use fewer monitors than there are +connectors, connect one monitor to each GPU before adding a second +monitor to any GPUs.

    +
    3. +
  3. +

    Install the NVIDIA display driver set.

    +
    4. +
  4. +

    Configure an X screen to use the "nvidia" driver on at least one +of the GPUs in your Quadro Plex VCS (see Chapter 6, +Configuring X for the NVIDIA Driver for more +information).

    +
    5. +
  5. +

    Start X.

    +
    6. +
  6. +

    Run nvidia-settings. You should see a tab in +the left pane of nvidia-settings labeled "SLI Mosaic Mode +Settings". Note that you may need to expand the entry for the X +screen you configured earlier.

    +
    7. +
  7. +

    Check the "Use SLI Mosaic Mode" check box.

    +
    8. +
  8. +

    Select the monitor grid configuration you'd like to use from the +"display configuration" dropdown.

    +
    9. +
  9. +

    Choose the resolution and refresh rate at which you would like +to drive each individual monitor.

    +
    10. +
  10. +

    Set any overlap you would like between the displays.

    +
    11. +
  11. +

    Click the "Save to X Configuration File" button. NOTE: If you +don't have permissions to write to your system's X configuration +file, you will be prompted to choose a location to save the file. +After doing so, you must +copy the X configuration file into a location the X server will +consider upon startup (usually /etc/X11/xorg.conf for X.Org servers or +/etc/X11/XF86Config for XFree86 +servers).

    +
    12. +
  12. +

    Exit nvidia-settings and restart your X server.

    +
    13. +
+
+

Hardware requirements

+

SLI functionality requires:

+
+
    +
  • +

    Identical PCI-Express graphics cards

    +
    • +
  • +

    A supported motherboard

    +
    • +
  • +

    In most cases, a video bridge connecting the two graphics +cards

    +
    • +
  • +

    A Quadro Plex VCS to use Mosaic Mode

    +
    • +
+
+

For the latest in supported SLI and Multi-GPU configurations, +including SLI- and Multi-GPU capable GPUs and SLI-capable +motherboards, see http://www.slizone.com.

+

Other Notes and Requirements

+

The following other requirements apply to SLI and Multi-GPU:

+
+
    +
  • +

    Mobile GPUs are NOT supported

    +
    • +
  • +

    SLI on Quadro-based graphics cards always requires a video +bridge

    +
    • +
  • +

    TwinView is also not supported with SLI or Multi-GPU. Only one +display can be used when SLI or Multi-GPU is enabled, with the +exception of Mosaic.

    +
    • +
  • +

    If X is configured to use multiple screens and screen 0 has SLI +or Multi-GPU enabled, the other screens configured to use the +nvidia driver will be disabled. Note that if SLI or Multi-GPU is +enabled, the GPUs used by that configuration will be unavailable +for single GPU rendering.

    +
    • +

+
+ ++ + + + + + + + + + + + + + + + + + + + + +
+

24.1. +Frequently Asked SLI and Multi-GPU Questions

+
+

Why is glxgears slower when SLI or Multi-GPU is +enabled?

+
+

When SLI or Multi-GPU is enabled, the NVIDIA driver must +coordinate the operations of all GPUs when each new frame is +swapped (made visible). For most applications, this GPU +synchronization overhead is negligible. However, because glxgears +renders so many frames per second, the GPU synchronization overhead +consumes a significant portion of the total time, and the framerate +is reduced.

+
+

Why is Doom 3 slower when SLI or Multi-GPU is +enabled?

+
+

The NVIDIA Accelerated FreeBSD Graphics Driver does not +automatically detect the optimal SLI or Multi-GPU settings for +games such as Doom 3 and Quake 4. To work around this issue, the +environment variable __GL_DOOM3 can be set to tell OpenGL that Doom +3's optimal settings should be used. In Bash, this can be done in +the same command that launches Doom 3 so the environment variable +does not remain set for other OpenGL applications started in the +same session:

+
+    % __GL_DOOM3=1 doom3
+
+

Doom 3's startup script can also be modified to set this +environment variable:

+
+    #!/bin/sh
+    # Needed to make symlinks/shortcuts work.
+    # the binaries must run with correct working directory
+    cd "/usr/local/games/doom3/"
+    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:.
+    export __GL_DOOM3=1
+    exec ./doom.x86 "$@"
+
+

This environment variable is temporary and will be removed in +the future.

+
+
@@ -87,11 +313,11 @@ target=
-Chapter 23. Configuring Depth 30 Displays  Home - Chapter 25. Credits
diff --git a/doc/html/chapter-25.html b/doc/html/chapter-25.html index ebe17b3..6a2b0e7 100644 --- a/doc/html/chapter-25.html +++ b/doc/html/chapter-25.html @@ -5,22 +5,24 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Chapter 25. Credits +Chapter 25. Configuring Frame Lock and +Genlock +"Chapter 24. Configuring SLI and Multi-GPU FrameRendering"> +"Chapter 26. Configuring SDI Video Output">
- + +Chapter 24. Configuring SLI and Multi-GPU +FrameRendering  + Chapter 26. Configuring SDI Video Output
Chapter 25. CreditsChapter 25. Configuring +Frame Lock and Genlock
-

Chapter 25. Credits

+

Chapter 25. Configuring Frame Lock and +Genlock

-

The port of the NVIDIA driver to FreeBSD is due in no small part -to the many contributions of Christian Zander <zander 'at' -mail.minion.de> and Matthew N. Dodd <mdodd 'at' -freebsd.org>.

+

NOTE: Frame Lock and Genlock features are supported only on +specific hardware, as noted below.

+

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.

+

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.

+

Definition of Terms

+

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.

+

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.

+

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.

+

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.

+

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.

+

Supported Hardware

+

Frame lock and genlock are supported for the following +hardware:

+
+ +++ + + + + + + + + + + + + + + + + + + + + +
Card 
Quadro FX 3000G 
Quadro FX G-Sync, used in conjunction with a Quadro FX 4400, +Quadro FX 4500, or Quadro FX 5500 
Quadro FX G-Sync II, used in conjunction with a Quadro FX 4600, +or Quadro FX 5600 
+
+

+

Hardware Setup

+

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.

+

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.

+
+
    +
  1. +

    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 +Chapter 24, Configuring SLI and Multi-GPU +FrameRendering) 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.

    +
    2. +
  2. +

    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.

    +
    3. +
  3. +

    Connect the other end of the ribbon cable to the fourteen-pin +connector on the graphics card.

    +
    4. +
+
+

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 FreeBSD +Driver Set. If you have not done so, see Chapter 3, +Installing the NVIDIA Driver.

+

Configuration with nvidia-settings GUI

+

Frame lock and genlock are configured through the +nvidia-settings utility. See the nvidia-settings(1) 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).

+

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.

+

After the system has booted and X Windows has been started, run +nvidia-settings as

+
+    % nvidia-settings
+
+

You may wish to start this utility before continuing, as we +refer to it frequently in the subsequent discussion.

+

The setup of genlock and frame lock are described separately. We +then describe the use of genlock and frame lock together.

+

Genlock Setup

+

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.

+

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 system:m, e.g.:

+
+    mycomputer.domain.com:0
+
+

or

+
+    localhost:0
+
+

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, +"Port 0"/"Port 1" 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 check boxes, +refresh rate, "Timing" LED and "Stereo" LED.

+

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" check box of the +desired display device.

+

If you are using a G-Sync card, you must also click the "Use +House Sync if Present" check box. 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.

+

Modifications to genlock settings (e.g., "Use House Sync if +Present", "Add Devices...") must be done while synchronization is +disabled.

+

+

Frame Lock Setup

+

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 Chapter 18, +Programming Modes for information on mode timings.

+

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). +Do not connect a frame lock port to an +ethernet card or hub. Doing so may permanently damage the +hardware. 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.

+

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.

+

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 "Port 0" and "Port 1" 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.

+

Any X Server can be added to the frame lock group, provided +that

+
+
    +
  1. +

    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.

    +
    2. +
  2. +

    The system driving nvidia-settings can locate and has display +privileges on the X server that is to be included for frame +lock.

    +
    3. +
+
+

A system can gain display privileges on a remote system by +executing

+
+    % xhost +
+
+

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.

+

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 Chapter 18, +Programming Modes for information on mode timings.

+

Modifications to frame lock settings (e.g. "Add/Remove +Devices...") must be done while synchronization is disabled.

+

nvidia-settings will not automatically enable Frame Lock via the +nvidia-settings.rc file. To enable Frame Lock when starting the X +server, a line such as the following can be added to the +~/.xinitrc file:

+
+    # nvidia-settings -a [gpu:0]/FrameLockEnable=1
+
+

+

Frame Lock + Genlock

+

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 Frame +Lock Setup, 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 check box 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" check box. 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.

+

Configuration with nvidia-settings command line

+

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.)

+

To properly configure Frame Lock, the following steps should be +completed:

+
+
    +
  1. +

    Make sure Frame Lock Sync is disabled on all GPUs.

    +
    2. +
  2. +

    Make sure all display devices that are to be frame locked have +the same refresh rate.

    +
    3. +
  3. +

    Configure which (display/GPU) device should be the master.

    +
    4. +
  4. +

    Configure house sync (if applicable).

    +
    5. +
  5. +

    Configure the slave display devices.

    +
    6. +
  6. +

    Enable frame lock sync on the master GPU.

    +
    7. +
  7. +

    Enable frame lock sync on the slave GPUs.

    +
    8. +
  8. +

    Toggle the test signal on the master GPU (for testing the +hardware connectivity.)

    +
    9. +
+
+

+

For a full list of the nvidia-settings Frame Lock attributes, +please see the nvidia-settings(1) man +page. Examples:

+
+
    +
  1. +

    1 System, 1 Frame Lock board, 1 GPU, and 1 display device +syncing to the house signal:

    +
    +  # - 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 frame lock
+  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
+
    +

    +
    2. +
  2. +

    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:

    +
    +  # - 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 frame lock on server
+  nvidia-settings -a myserver:0[gpu:0]/FrameLockEnable=1
+
+  # - Enable frame lock 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
+
    +

    +
    3. +
  3. +

    1 System, 4 GPUs, 2 Frame Lock boards and 2 display devices per +GPU syncing from the first GPU's display device:

    +
    +  # - 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=0
+
+  # - 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 frame lock on master GPU
+  nvidia-settings -a [gpu:0]/FrameLockEnable=1
+
+  # - Enable frame lock 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
+
    +

    +
    4. +
+
+

+

Leveraging Frame Lock/Genlock in OpenGL

+

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.

+

Frame Lock Restrictions:

+

The following restrictions must be met for enabling frame +lock:

+
+
    +
  1. +

    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.

    +
    2. +
  2. +

    All X Screens (driving the selected client/server display +devices) must have the same stereo setting. See Appendix B, X +Config Options for instructions on how to set the stereo X +option.

    +
    3. +
  3. +

    The frame lock server (master) display device must be on a GPU +on the primary connector to a G-Sync device.

    +
    4. +
  4. +

    If connecting a single GPU to a G-Sync device, the primary +connector must be used.

    +
    5. +
  5. +

    In configurations with more than one display device per GPU, we +recommend enabling frame lock on all display devices on those +GPUs.

    +
    6. +
  6. +

    Virtual terminal switching or mode 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.

    +
    7. +
+
+

+

Supported Frame Lock Configurations:

+

The following configurations are currently supported:

+
+
    +
  1. +

    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.

    +
    2. +
  2. +

    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.

    +
    3. +
  3. +

    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.

    +
    4. +
  4. +

    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.

    +
    5. +
  5. +

    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.

    +
    6. +
  6. +

    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.

    +
    7. +
+
+

@@ -59,12 +647,12 @@ freebsd.org>.

-Chapter 24. NVIDIA Contact Info and Additional -Resources  Home - Chapter 26. Acknowledgements
diff --git a/doc/html/chapter-26.html b/doc/html/chapter-26.html index 63af61c..20fcd80 100644 --- a/doc/html/chapter-26.html +++ b/doc/html/chapter-26.html @@ -5,23 +5,23 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Chapter 26. Acknowledgements +Chapter 26. Configuring SDI Video Output - +"Chapter 25. Configuring Frame Lock and Genlock"> +
- + +"chapter-27.html">Next
-Chapter 26. AcknowledgementsChapter 26. Configuring +SDI Video Output
Part I. Installation and Configuration Instructions  Next
@@ -37,21 +37,205 @@ Configuration Instructions
-

Chapter 26. Acknowledgements

+

Chapter 26. Configuring SDI Video Output

-

The driver splash screen is decoded using libpng: http://libpng.org/pub/png/libpng.html

-

This NVIDIA FreeBSD driver contains code from the int10 module -of the X.Org project.

-

The BSD implementations of the following compiler intrinsics are -used for better portability: __udivdi3, __umoddi3, __divdi3, -__moddi3, __ucmpdi2, __cmpdi2, __fixunssfdi, __fixunsdfdi, -__ashldi3 and __lshrdi3.

+

Broadcast, film, and video post production and digital cinema +applications can require Serial Digital (SDI) or High Definition +Serial Digital (HD-SDI) video output. SDI/HD-SDI is a digital video +interface used for the transmission of uncompressed video signals +as well as packetized data. SDI is standardized in ITU-R BT.656 and +SMPTE 259M while HD-SDI is standardized in SMPTE 292M. SMPTE 372M +extends HD-SDI to define a dual-link configuration that uses a pair +of SMPTE 292M links to provide a 2.970 Gbit/second interface. SMPTE +424M extends the interface further to define a single 2.97 +Gbit/second serial data link.

+

SDI and HD-SDI video output is provided through the use of the +NVIDIA driver along with an NVIDIA SDI output daughter board. In +addition to single- and dual-link SDI/HD-SDI digital video output, +frame lock and genlock synchronization are provided in order to +synchronize the outgoing video with an external source signal (see +Chapter 25, +Configuring Frame Lock and Genlock for details on these +technologies). This section describes the setup and use of the SDI +video output.

+

Hardware Setup

+

Before you begin, you should check that your hardware has been +properly installed. If you are using the Quadro FX 4000 SDI, the +SDI/HD-SDI hardware is located on the dual-slot card itself, and +after installing the card, no additional setup is necessary. If you +are using the Quadro FX 4500/5500 SDI or Quadro FX 4600/5600 SDI +II, the following additional setup steps are required in order to +connect the SDI daughter card to the graphics card. These steps +must be performed when the system is off.

+
+
    +
  1. +

    Insert the NVIDIA SDI Output card into any available expansion +slot within six inches of the NVIDIA Quadro graphics card. Secure +the card's bracket using the method provided by the chassis +manufacturer (usually a thumb screw or an integrated latch).

    +
    2. +
  2. +

    Connect one end of the 14-pin ribbon cable to the G-Sync +connector on the NVIDIA Quadro graphics card, and the other end to +the NVIDIA SDI output card.

    +
    3. +
  3. +

    On Quadro FX 4500/5500 SDI, connect the SMA-to-BNC cables by +screwing the male SMA connectors onto the female SMA connectors on +the NVIDIA SDI output card. On Quadro FX 4600/5600 SDI II, this +step is not necessary: the SDI II has BNC connectors rather than +SMA connectors.

    +
    4. +
  4. +

    Connect the DVI-loopback connector by connecting one end of the +DVI cable to the DVI connector on the NVIDIA SDI output card and +the other end to the "north" DVI connector on the NVIDIA Quadro +graphics card. The "north" DVI connector on the NVIDIA Quadro +graphics card is the DVI connector that is the farthest from the +graphics card PCI-E connection to the motherboard. The SDI output +card will NOT function properly if this cable is connected to the +"south" DVI connector.

    +
    5. +
+
+

Once the above installation is complete, you may boot the system +and configure the SDI video output using nvidia-settings. These +instructions assume that you have already successfully installed +the NVIDIA FreeBSD Accelerated Graphics Driver. If you have not +done so, see Chapter 3, +Installing the NVIDIA Driver for details.

+

Clone Mode Configuration with nvidia-settings

+

SDI video output is configured through the nvidia-settings +utility. See the nvidia-settings(1) +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).

+

After the system has booted and X Windows has been started, run +nvidia-settings as

+
+    % nvidia-settings
+
+

When the NVIDIA X Server Settings page appears, follow the steps +below to configure the SDI video output.

+
+
    +
  1. +

    Click on the Graphics to Video +Out tree item on the side menu. This will open the +Graphics to Video Out page.

    +
    2. +
  2. +

    Go to the "Synchronization Options" subpage and choose a +synchronization method. From the Sync +Options drop down click the list arrow to the right and then +click the method that you want to use to synchronize the SDI +output.

    +
    + +++ + + + + + + + + + + + + + + + + + + + + +
    Sync MethodDescription
    Free RunningThe SDI output will be synchronized with the timing chosen from +the SDI signal format list.
    GenlockSDI output will be synchronized with the external sync +signal.
    Frame LockThe SDI output will be synchronized with the timing chosen from +the SDI signal format list. In this case, the list of available +timings is limited to those timings that can be synchronized with +the detected external sync signal.
    +
    +

    +

    Note that on Quadro FX 4600/5600 SDI II, you must first choose +the correct Sync Format before an incoming sync signal will be +detected.

    +
    3. +
  3. +

    From the top Graphics to Video Out page, choose the output video +format that will control the video resolution, field rate, and +SMPTE signaling standard for the outgoing video stream. From the +Clone Mode drop down box, click +the Video Format arrow and then +click the signal format that you would like to use. Note that only +those resolutions that are smaller or equal to the desktop +resolution will be available. Also, this list is pruned according +to the sync option selected. If genlock synchronization is chosen, +the output video format is automatically set to match the incoming +video sync format and this drop down list will be grayed out +preventing you from choosing another format. If frame lock +synchronization has been selected, then only those modes that are +compatible with the detected sync signal will be available.

    +
    4. +
  4. +

    Choose the output data format from the Output Data Format drop down list.

    +
    5. +
  5. +

    Click the Enable SDI Output +button to enable video output using the settings above. The status +of the SDI output can be verified by examining the LED indicators +in the Graphics to SDI property +page banner.

    +
    6. +
  6. +

    To subsequently stop SDI output, simply click on the button that +now says Disable SDI +Output.

    +
    7. +
  7. +

    In order to change any of the SDI output parameters such as the +Output Video Format, Output Data Format as well as the +Synchronization Delay, it is necessary to first disable the SDI +output.

    +
    8. +
+
+

+

Configuration for TwinView or as a Separate X Screen

+

SDI video output can be configured through the nvidia-settings X +Server Display Configuration page, for use in TwinView or as a +separate X screen. The SDI video output can be configured as if it +were a digital flat panel, choosing the resolution, refresh rate, +and position within the desktop.

+

Similarly, the SDI video output can be configured for use in +TwinView or as a separate X screen through the X configuration +file. The supported SDI video output modes can be requested by name +anywhere a mode name can be used in the X configuration file +(either in the "Modes" line, or in the "MetaModes" option). +E.g.,

+
+ Option "MetaModes" "CRT-0:nvidia-auto-select, DFP-1:1280x720_60.00_smpte296"
+    
+
+

The mode names are reported in the nvidia-settings Display +Configuration page when in advanced mode.

+

Note that SDI "Clone Mode" as configured through the Graphics to +Video Out page in nvidia-settings is mutually exclusive with using +the SDI video output in TwinView or as a separate X screen.

@@ -62,15 +246,15 @@ __ashldi3 and __lshrdi3.

Up  Next
-Chapter 25. Credits  Home - Part II. Appendices
diff --git a/doc/html/chapter-23.html b/doc/html/chapter-27.html similarity index 69% copy from doc/html/chapter-23.html copy to doc/html/chapter-27.html index 4f10ea8..a36c88d 100644 --- a/doc/html/chapter-23.html +++ b/doc/html/chapter-27.html @@ -5,31 +5,31 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Chapter 23. Configuring Depth 30 Displays +Chapter 27. Configuring Depth 30 Displays - - + +
- +"chapter-26.html">Prev  +"chapter-28.html">Next
Chapter 23. Configuring +Chapter 27. Configuring Depth 30 Displays
Prev  Part I. Installation and Configuration Instructions  Next
@@ -38,7 +38,7 @@ Configuration Instructions

Chapter 23. Configuring Depth 30 +"depth30">Chapter 27. Configuring Depth 30 Displays

@@ -48,10 +48,13 @@ bits per pixel (10 bits per color component) on NVIDIA Quadro GPUs based on G80 and higher chip architectures. This provides about 1 billion possible colors, allowing for higher color precision and smoother gradients.

-

When displaying a depth 30 image on a digital flat panel, the -color data will be dithered to 8 or 6 bits per pixel, depending on -the capabilities of the flat panel. VGA outputs can display the -full 10 bit range of colors.

+

When displaying a depth 30 image, the color data may be dithered +to lower bit depths, depending on the capabilities of the display +device and how it is connected to the GPU. Some devices connected +via analog VGA, DisplayPort, and HDMI can display the full 10 bit +range of colors. Devices connected via DVI, as well as laptop +internal panels connected via LVDS, will be dithered to 8 or 6 bits +per pixel.

To work reliably, depth 30 requires X.Org 7.3 or higher and pixman 0.11.6 or higher.

In addition to the above software requirements, many X @@ -68,19 +71,19 @@ will fail to start.

+"chapter-26.html">Prev  +"chapter-28.html">Next +Chapter 26. Configuring SDI Video Output 
Prev  Up  Next
-Chapter 22. Configuring SDI Video Output  Home - Chapter 24. NVIDIA Contact Info and Additional + Chapter 28. NVIDIA Contact Info and Additional Resources
diff --git a/doc/html/chapter-24.html b/doc/html/chapter-28.html similarity index 80% copy from doc/html/chapter-24.html copy to doc/html/chapter-28.html index d6849e0..204fe5a 100644 --- a/doc/html/chapter-24.html +++ b/doc/html/chapter-28.html @@ -5,32 +5,32 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Chapter 24. NVIDIA Contact Info and Additional +<title>Chapter 28. NVIDIA Contact Info and Additional Resources - - + +
- +"chapter-27.html">Prev  +"chapter-29.html">Next
Chapter 24. NVIDIA Contact +Chapter 28. NVIDIA Contact Info and Additional Resources
Prev  Part I. Installation and Configuration Instructions  Next
@@ -39,7 +39,7 @@ Configuration Instructions

Chapter 24. NVIDIA Contact Info and +"addtlresources">Chapter 28. NVIDIA Contact Info and Additional Resources

@@ -79,19 +79,19 @@ target= +"chapter-27.html">Prev  +"chapter-29.html">Next +Chapter 27. Configuring Depth 30 Displays  + Chapter 29. Credits
Prev  Up  Next
-Chapter 23. Configuring Depth 30 Displays  Home - Chapter 25. Credits
diff --git a/doc/html/chapter-25.html b/doc/html/chapter-29.html similarity index 74% copy from doc/html/chapter-25.html copy to doc/html/chapter-29.html index ebe17b3..0da8060 100644 --- a/doc/html/chapter-25.html +++ b/doc/html/chapter-29.html @@ -5,30 +5,30 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Chapter 25. Credits +Chapter 29. Credits - - + +
- + +"chapter-28.html">Prev  +"chapter-30.html">Next
Chapter 25. CreditsChapter 29. Credits
Prev  Part I. Installation and Configuration Instructions  Next
@@ -37,7 +37,7 @@ Configuration Instructions

Chapter 25. Credits

+"credits">Chapter 29. Credits
@@ -51,20 +51,20 @@ freebsd.org>.

+"chapter-28.html">Prev  +"chapter-30.html">Next + Chapter 30. Acknowledgements
Prev  Up  Next
-Chapter 24. NVIDIA Contact Info and Additional +Chapter 28. NVIDIA Contact Info and Additional Resources  Home - Chapter 26. Acknowledgements
diff --git a/doc/html/chapter-26.html b/doc/html/chapter-30.html similarity index 86% copy from doc/html/chapter-26.html copy to doc/html/chapter-30.html index 63af61c..1438466 100644 --- a/doc/html/chapter-26.html +++ b/doc/html/chapter-30.html @@ -5,14 +5,14 @@ "HTML Tidy for FreeBSD (vers 1 September 2005), see www.w3.org"> -Chapter 26. Acknowledgements +Chapter 30. Acknowledgements - + @@ -21,11 +21,11 @@ +Chapter 30. Acknowledgements +"chapter-29.html">Prev 
-Chapter 26. Acknowledgements
Prev  Part I. Installation and Configuration Instructions  

Chapter 26. Acknowledgements

+"acknowledgements">Chapter 30. Acknowledgements
@@ -58,7 +58,7 @@ __ashldi3 and __lshrdi3.

+"chapter-29.html">Prev  +Chapter 29. Credits  +"chapter-30.html">Prev  +"appendix-a.html">Next
Prev  Up  
-Chapter 25. Credits  Home diff --git a/doc/html/index.html b/doc/html/index.html index 7c6d0d2..2c28354 100644 --- a/doc/html/index.html +++ b/doc/html/index.html @@ -43,7 +43,7 @@ Guide
-

Copyright © 2006 - 2008 NVIDIA +

Copyright © 2006 - 2009 NVIDIA Corporation

@@ -93,72 +93,72 @@ Configuration Instructions
1. Introduction
-
A. Minimum +
2. Minimum Software Requirements
-
2. Installing +
3. Installing the NVIDIA Driver
-
B. Installed +
4. Installed Components
-
3. Using Linux +
5. Using Linux Compatibility Support
-
4. Configuring +
6. Configuring X for the NVIDIA Driver
-
Using +
Using nvidia-xconfig to configure the X server
Manually Editing the Configuration +"chapter-06-section-02.html">Manually Editing the Configuration File
-
5. Frequently +
7. Frequently Asked Questions
-
6. Common +
8. Common Problems
-
7. Known +
9. Known Issues
-
8. Specifying +
10. Specifying OpenGL Environment Variable Settings
-
9. Configuring +
11. Configuring AGP
-
10. Configuring +
12. Configuring TwinView
-
11. Configuring +
13. Configuring GLX in Xinerama
-
12. Configuring +
14. Configuring Multiple X Screens on One Card
-
13. Configuring +
15. Configuring TV-Out
-
14. Using the +
16. Using the XRandR Extension
-
15. Configuring +
17. Configuring a Notebook
-
16. Programming +
18. Programming Modes
-
17. Configuring +
19. Configuring Flipping and UBB
-
C. The Sysctl +
20. The Sysctl Interface
-
D. Configuring +
21. Configuring Low-level Parameters
-
18. Using the X +
22. Using the X Composite Extension
-
19. Using the +
23. Using the nvidia-settings Utility
-
20. Configuring +
24. Configuring SLI and Multi-GPU FrameRendering
-
21. Configuring +
25. Configuring Frame Lock and Genlock
-
22. Configuring +
26. Configuring SDI Video Output
-
23. Configuring +
27. Configuring Depth 30 Displays
-
24. NVIDIA +
28. NVIDIA Contact Info and Additional Resources
-
25. +
29. Credits
-
26. +
30. Acknowledgements
@@ -166,52 +166,52 @@ Acknowledgements Appendices
-
E. Supported +
A. Supported NVIDIA GPU Products
-
F. X Config +
B. X Config Options
-
G. Display +
C. Display Device Names
-
H. GLX +
D. GLX Support
-
I. Dots Per +
E. Dots Per Inch
-
J. XvMC +
F. XvMC Support
-
K. VDPAU +
G. VDPAU Support
Implementation Limits
+"appendix-g.html#id2653783">Implementation Limits
VdpVideoSurface
+"appendix-g.html#id2653790">VdpVideoSurface
VdpBitmapSurface
+"appendix-g.html#id2653883">VdpBitmapSurface
VdpOutputSurface
+"appendix-g.html#id2653925">VdpOutputSurface
VdpDecoder
+"appendix-g.html#id2653989">VdpDecoder
VdpVideoMixer
+"appendix-g.html#id2655625">VdpVideoMixer
VdpPresentationQueue
+"appendix-g.html#id2655763">VdpPresentationQueue
Performance Levels
+"appendix-g-section-02.html">Performance Levels
Getting the Best Performance from the +"appendix-g-section-03.html">Getting the Best Performance from the API
Additional Notes
+"appendix-g-section-04.html">Additional Notes
Debugging and Tracing
+"appendix-g-section-05.html">Debugging and Tracing
-
L. Tips for +
H. Tips for New FreeBSD Users
diff --git a/doc/html/part-01.html b/doc/html/part-01.html index 7aa4419..3b5a20c 100644 --- a/doc/html/part-01.html +++ b/doc/html/part-01.html @@ -48,72 +48,72 @@ Instructions
1. Introduction
-
A. Minimum +
2. Minimum Software Requirements
-
2. Installing +
3. Installing the NVIDIA Driver
-
B. Installed +
4. Installed Components
-
3. Using Linux +
5. Using Linux Compatibility Support
-
4. Configuring +
6. Configuring X for the NVIDIA Driver
-
Using +
Using nvidia-xconfig to configure the X server
Manually Editing the Configuration +"chapter-06-section-02.html">Manually Editing the Configuration File
-
5. Frequently +
7. Frequently Asked Questions
-
6. Common +
8. Common Problems
-
7. Known +
9. Known Issues
-
8. Specifying +
10. Specifying OpenGL Environment Variable Settings
-
9. Configuring +
11. Configuring AGP
-
10. Configuring +
12. Configuring TwinView
-
11. Configuring +
13. Configuring GLX in Xinerama
-
12. Configuring +
14. Configuring Multiple X Screens on One Card
-
13. Configuring +
15. Configuring TV-Out
-
14. Using the +
16. Using the XRandR Extension
-
15. Configuring +
17. Configuring a Notebook
-
16. Programming +
18. Programming Modes
-
17. Configuring +
19. Configuring Flipping and UBB
-
C. The Sysctl +
20. The Sysctl Interface
-
D. Configuring +
21. Configuring Low-level Parameters
-
18. Using the X +
22. Using the X Composite Extension
-
19. Using the +
23. Using the nvidia-settings Utility
-
20. Configuring +
24. Configuring SLI and Multi-GPU FrameRendering
-
21. Configuring +
25. Configuring Frame Lock and Genlock
-
22. Configuring +
26. Configuring SDI Video Output
-
23. Configuring +
27. Configuring Depth 30 Displays
-
24. NVIDIA +
28. NVIDIA Contact Info and Additional Resources
-
25. +
29. Credits
-
26. +
30. Acknowledgements
diff --git a/doc/html/part-02.html b/doc/html/part-02.html index b3be7bf..14a1abf 100644 --- a/doc/html/part-02.html +++ b/doc/html/part-02.html @@ -11,10 +11,10 @@ "NVIDIA Accelerated FreeBSD Graphics Driver README and Installation Guide"> - - + +
@@ -24,10 +24,10 @@
Prev     Next
@@ -43,52 +43,52 @@

Table of Contents

-
E. Supported +
A. Supported NVIDIA GPU Products
-
F. X Config +
B. X Config Options
-
G. Display +
C. Display Device Names
-
H. GLX +
D. GLX Support
-
I. Dots Per +
E. Dots Per Inch
-
J. XvMC +
F. XvMC Support
-
K. VDPAU +
G. VDPAU Support
Implementation Limits
+"appendix-g.html#id2653783">Implementation Limits
VdpVideoSurface
+"appendix-g.html#id2653790">VdpVideoSurface
VdpBitmapSurface
+"appendix-g.html#id2653883">VdpBitmapSurface
VdpOutputSurface
+"appendix-g.html#id2653925">VdpOutputSurface
VdpDecoder
+"appendix-g.html#id2653989">VdpDecoder
VdpVideoMixer
+"appendix-g.html#id2655625">VdpVideoMixer
VdpPresentationQueue
+"appendix-g.html#id2655763">VdpPresentationQueue
Performance Levels
+"appendix-g-section-02.html">Performance Levels
Getting the Best Performance from the +"appendix-g-section-03.html">Getting the Best Performance from the API
Additional Notes
+"appendix-g-section-04.html">Additional Notes
Debugging and Tracing
+"appendix-g-section-05.html">Debugging and Tracing
-
L. Tips for +
H. Tips for New FreeBSD Users
@@ -98,18 +98,18 @@ New FreeBSD Users +"chapter-30.html">Prev  +"appendix-a.html">Next +Chapter 30. Acknowledgements  + Appendix A. Supported NVIDIA GPU Products
Prev     Next
-Chapter 26. Acknowledgements  Home - Appendix E. Supported NVIDIA GPU Products
diff --git a/doc/vdpau.h b/doc/vdpau.h index a14e8d2..110b3af 100755 --- a/doc/vdpau.h +++ b/doc/vdpau.h @@ -7,7 +7,7 @@ * This copyright notice applies to this header file: * * Copyright (c) 2008 NVIDIA Corporation - * + * * Permission is hereby granted, free of charge, to any person * obtaining a copy of this software and associated documentation * files (the "Software"), to deal in the Software without @@ -32,7 +32,7 @@ /** * \mainpage Video Decode and Presentation API for Unix - * + * * \section intro Introduction * * The Video Decode and Presentation API for Unix (VDPAU) provides @@ -83,7 +83,7 @@ * A surface stores pixel information. Various types of surfaces * existing for different purposes: * - * - \ref VdpVideoSurface "VdpVideoSurface"s store decompressed + * - \ref VdpVideoSurface "VdpVideoSurface"s store decompressed * YCbCr video frames in an implementation-defined internal * format. * - \ref VdpOutputSurface "VdpOutputSurface"s store RGB 4:4:4 @@ -165,7 +165,7 @@ * * VDPAU is designed so that multiple implementations can be * used without application changes. For example, VDPAU could be - * hosted on X11, or via direct GPU access. + * hosted on X11, or via direct GPU access. * * The key technology behind this is the use of function * pointers and a "get proc address" style API for all entry @@ -189,8 +189,8 @@ * library would handle loading the appropriate back-end, and * implementing a similar "get proc address" scheme internally. * - * However, the above scheme does not work well in the context - * of separated \ref api_core and \ref api_winsys. In this + * However, the above scheme does not work well in the context + * of separated \ref api_core and \ref api_winsys. In this * scenario, one would require a separate wrapper library per * Window System, since each Window System would have a * different function name and prototype for the main factory @@ -208,67 +208,67 @@ * * \section threading Multi-threading * - * All VDPAU functionality is fully thread-safe; any number of + * All VDPAU functionality is fully thread-safe; any number of * threads may call into any VDPAU functions at any time. VDPAU * may not be called from signal-handlers. - * - * Note, however, that this simply guarantees that internal - * VDPAU state will not be corrupted by thread usage, and that + * + * Note, however, that this simply guarantees that internal + * VDPAU state will not be corrupted by thread usage, and that * crashes and deadlocks will not occur. Completely arbitrary * thread usage may not generate the results that an application * desires. In particular, care must be taken when multiple * threads are performing operations on the same VDPAU objects. - * - * VDPAU implementations guarantee correct flow of surface - * content through the rendering pipeline, but only when + * + * VDPAU implementations guarantee correct flow of surface + * content through the rendering pipeline, but only when * function calls that read from or write to a surface return to * the caller prior to any thread calling any other function(s) * that read from or write to the surface. Invoking multiple * reads from a surface in parallel is OK. - * - * Note that this restriction is placed upon VDPAU function - * invocations, and specifically not upon any back-end - * hardware's physical rendering operations. VDPAU - * implementations are expected to internally synchronize such - * hardware operations. - * - * In a single-threaded application, the above restriction comes - * naturally; each function call completes before it is possible - * to begin a new function call. - * - * In a multi-threaded application, threads may need to be + * + * Note that this restriction is placed upon VDPAU function + * invocations, and specifically not upon any back-end + * hardware's physical rendering operations. VDPAU + * implementations are expected to internally synchronize such + * hardware operations. + * + * In a single-threaded application, the above restriction comes + * naturally; each function call completes before it is possible + * to begin a new function call. + * + * In a multi-threaded application, threads may need to be * synchronized. For example, consider the situation where: - * - * - Thread 1 is parsing compressed video data, passing them + * + * - Thread 1 is parsing compressed video data, passing them * through a \ref VdpDecoder "VdpDecoder" object, and filling a * ring-buffer of \ref VdpVideoSurface "VdpVideoSurface"s - * - Thread 2 is consuming those \ref VdpVideoSurface + * - Thread 2 is consuming those \ref VdpVideoSurface * "VdpVideoSurface"s, and using a \ref VdpVideoMixer * "VdpVideoMixer" to process them and composite them with UI. - * - * In this case, the threads must synchronize to ensure that - * thread 1's call to \ref VdpDecoderRender has returned prior to - * thread 2's call(s) to \ref VdpVideoMixerRender that use that - * specific surface. This could be achieved using the following - * pseudo-code: - * + * + * In this case, the threads must synchronize to ensure that + * thread 1's call to \ref VdpDecoderRender has returned prior to + * thread 2's call(s) to \ref VdpVideoMixerRender that use that + * specific surface. This could be achieved using the following + * pseudo-code: + * * \code - * Queue q_full_surfaces; - * Queue q_empty_surfaces; - * - * thread_1() { + * Queue q_full_surfaces; + * Queue q_empty_surfaces; + * + * thread_1() { * for (;;) { * VdpVideoSurface s = q_empty_surfaces.get(); * // Parse compressed stream here * VdpDecoderRender(s, ...); * q_full_surfaces.put(s); * } - * } - * + * } + * * // This would need to be more complex if * // VdpVideoMixerRender were to be provided with more * // than one field/frame at a time. - * thread_1() { + * thread_2() { * for (;;) { * // Possibly, other rendering operations to mixer * // layer surfaces here. @@ -282,26 +282,26 @@ * } * } * \endcode - * + * * Finally, note that VDPAU makes no guarantees regarding any * level of parallelism in any given implementation. Put another * way, use of multi-threading is not guaranteed to yield any * performance gain, and in theory could even slightly reduce * performance due to threading/synchronization overhead. - * + * * However, the intent of the threading requirements is to allow - * for e.g. video decoding and video mixer operations to proceed - * in parallel in hardware. Given a (presumably multi-threaded) - * application that kept each portion of the hardware busy, this - * would yield a performance increase. - * + * for e.g. video decoding and video mixer operations to proceed + * in parallel in hardware. Given a (presumably multi-threaded) + * application that kept each portion of the hardware busy, this + * would yield a performance increase. + * * \section endianness Surface Endianness * - * When dealing with surface content, i.e. the input/output of - * Put/GetBits functions, applications must take care to access - * memory in the correct fashion, so as to avoid endianness - * issues. - * + * When dealing with surface content, i.e. the input/output of + * Put/GetBits functions, applications must take care to access + * memory in the correct fashion, so as to avoid endianness + * issues. + * * By established convention in the 3D graphics world, RGBA data * is defined to be an array of 32-bit pixels containing packed * RGBA components, not as an array of bytes or interleaved RGBA @@ -311,161 +311,394 @@ * as interleaved arrays of 8-bit components (i.e. using an * 8-bit pointer.) Deviation from this convention will lead to * endianness issues, unless appropriate care is taken. - * + * * The same convention is followed for some packed YCbCr formats * such as \ref VDP_YCBCR_FORMAT_Y8U8V8A8; i.e. they are * considered arrays of 32-bit pixels, and hence should be * accessed as such. - * + * * For YCbCr formats with chroma decimation and/or planar - * formats, however, this convention is awkward. Therefore, + * formats, however, this convention is awkward. Therefore, * formats such as \ref VDP_YCBCR_FORMAT_NV12 are defined as * arrays of (potentially interleaved) byte-sized components. * Hence, applications should manipulate such data 8-bits at a * time, using 8-bit pointers. - * + * * Note that one common usage for the input/output of * Put/GetBits APIs is file I/O. Typical file I/O APIs treat all * memory as a simple array of 8-bit values. This violates the * rule requiring surface data to be accessed in its true native * format. As such, applications may be required to solve * endianness issues. Possible solutions include: - * + * * - Authoring static UI data files according to the endianness * of the target execution platform. * - Conditionally byte-swapping Put/GetBits data buffers at * run-time based on execution platform. - * - * Note: Complete details regarding each surface format's - * precise pixel layout is included with the documentation of - * each surface type. For example, see \ref - * VDP_RGBA_FORMAT_B8G8R8A8. - * + * + * Note: Complete details regarding each surface format's + * precise pixel layout is included with the documentation of + * each surface type. For example, see \ref + * VDP_RGBA_FORMAT_B8G8R8A8. + * + * \section video_decoder_usage Video Decoder Usage + * + * VDPAU is a slice-level API. Put another way, VDPAU implementations accept + * "slice" data from the bitstream, and perform all required processing of + * those slices (e.g VLD decoding, IDCT, motion compensation, in-loop + * deblocking, etc.). + * + * The client application is responsible for: + * + * - Extracting the slices from the bitstream (e.g. parsing/demultiplexing + * container formats, scanning the data to determine slice start positions + * and slice sizes). + * - Parsing various bitstream headers/structures (e.g. sequence header, + * sequence parameter set, picture parameter set, entry point structures, + * etc.) Various fields from the parsed header structures needs to be + * provided to VDPAU alongside the slice bitstream in a "picture info" + * structure. + * - Surface management (e.g. H.264 DPB processing, display re-ordering) + * + * It is recommended that applications pass solely the slice data to VDPAU; + * specifically that any header data structures be excluded from the portion + * of the bitstream passed to VDPAU. VDPAU implementations must operate + * correctly if non-slice data is included, at least for formats employing + * start codes to delimit slice data. However, any extra data may need + * to be uploaded to hardware for parsing thus lowering performance, and/or, + * in the worst case, may even overflow internal buffers that are sized solely + * for slice data. + * + * The exact data that should be passed to VDPAU is detailed below for each + * supported format: + * + * \subsection MPEG-1 and MPEG-2 + * + * Include all slices beginning with start codes 0x00000101 through + * 0x000001AF. The slice start code must be included for all slices. + * + * \subsection H.264 + * + * Include all NALs with nal_unit_type of 1 or 5 (coded slice of non-IDR/IDR + * picture respectively). The complete slice start code (including 0x000001 + * prefix) must be included for all slices, even when the prefix is not + * included in the bitstream. + * + * Note that if desired: + * + * - The slice start code prefix may be included in a separate bitstream + * buffer array entry to the actual slice data extracted from the bitstream. + * - Multiple bitstream buffer array entries (e.g. one per slice) may point at + * the same physical data storage for the slice start code prefix. + * + * \subsection VC-1 Simple and Main Profile + * + * VC-1 simple/main profile bitstreams always consist of a single slice per + * picture, and do not use start codes to delimit pictures. Instead, the + * container format must indicate where each picture begins/ends. + * + * As such, no slice start codes should be included in the data passed to + * VDPAU; simply pass in the exact data from the bitstream. + * + * Header information contained in the bitstream should be parsed by the + * application and passed to VDPAU using the "picture info" data structure; + * this header information explicitly must not be included in the bitstream + * data passed to VDPAU for this encoding format. + * + * \subsection VC-1 Advanced Profile + * + * Include all slices beginning with start codes 0x0000010D (frame), + * 0x0000010C (field) or 0x0000010B (slice). The slice start code should be + * included in all cases. + * + * Some VC-1 advanced profile streams do not contain slice start codes; again, + * the container format must indicate where picture data begins and ends. In + * this case, pictures are assumed to be progressive and to contain a single + * slice. It is highly recommended that applications detect this condition, + * and add the missing start codes to the bitstream passed to VDPAU. However, + * VDPAU implementations must allow bitstreams with missing start codes, and + * act as if a 0x0000010D (frame) start code had been present. + * + * Note that pictures containing multiple slices, or interlace streams, must + * contain a complete set of slice start codes in the original bitstream; + * without them, it is not possible to correctly parse and decode the stream. + * + * The bitstream passed to VDPAU should contain all original emulation + * prevention bytes present in the original bitstream; do not remove these + * from the bitstream. + * * \section video_mixer_usage Video Mixer Usage - * - * \subsection video_surface_content VdpVideoSurface Content - * - * Each \ref VdpVideoSurface "VdpVideoSurface" is expected to - * contain an entire frame's-worth of data, irrespective of - * whether an interlaced of progressive sequence is being - * decoded. - * - * Depending on the exact encoding structure of the compressed - * video stream, the application may need to call \ref - * VdpDecoderRender twice to fill a single \ref VdpVideoSurface - * "VdpVideoSurface". When the stream contains an encoded - * progressive frame, or a "frame coded" interlaced field-pair, - * a single \ref VdpDecoderRender call will fill the entire - * surface. When the stream contains separately encoded - * interlaced fields, two \ref VdpDecoderRender calls will be - * required; one for the top field, and one for the bottom - * field. - * - * Implementation note: When \ref VdpDecoderRender renders an - * interlaced field, this operation must not disturb the content - * of the other field in the surface. - * - * \subsection vm_render_surfaces VdpVideoMixerRender surface list - * - * The \ref VdpVideoMixerRender API receives \ref VdpVideoSurface - * "VdpVideoSurface" IDs for any number of fields/frames. The - * application should strive to provide as many fields/frames as - * practical, to enable advanced video processing - * algorithms. At a minimum, the current field/frame must be - * provided. It is recommended that at least 2 past and 1 future - * frame be provided in all cases. - * - * Note that it is entirely possible, in general, for any of the - * \ref VdpVideoMixer "VdpVideoMixer" post-processing steps to - * require access to multiple input fields/frames. - * - * It is legal for an application not to provide some or all of - * the surfaces other than the "current" surface. Note that this - * may cause degraded operation of the \ref VdpVideoMixer - * "VdpVideoMixer" algorithms. However, this may be required in - * the case of temporary file or network read errors, decode - * errors, etc. - * - * When an application chooses not to provide a particular - * surface to \ref VdpVideoMixerRender, then this "slot" in the - * surface list must be filled with the special value \ref - * VDP_INVALID_HANDLE, to explicitly indicate that the picture - * is missing; do not simply shuffle other surfaces together to - * fill in the gap. - * - * The \ref VdpVideoMixerRender parameter \b - * current_picture_structure applies to \b - * video_surface_current. The picture structure for the other - * surfaces will be automatically derived from that for the - * current picture as detailed below. - * - * If \b current_picture_structure is \ref - * VDP_VIDEO_MIXER_PICTURE_STRUCTURE_FRAME, then all surfaces are - * assumed to be frames. Otherwise, the picture structure is - * assumed to alternate between top and bottom field, anchored - * against \b current_picture_structure and \b - * video_surface_current. - * - * \subsection deinterlacing Applying de-interlacing - * - * Note that \ref VdpVideoMixerRender disables de-interlacing - * when \b current_picture_structure is \ref - * VDP_VIDEO_MIXER_PICTURE_STRUCTURE_FRAME; frames by definition - * need no de-interlacing. - * - * Weave de-interlacing may be obtained by giving the video - * mixer a surface containing two interlaced fields, but - * informing the \ref VdpVideoMixer "VdpVideoMixer" that the - * surface has \ref VDP_VIDEO_MIXER_PICTURE_STRUCTURE_FRAME. - * - * Bob de-interlacing is the default for interlaced content. - * More advanced de-interlacing techniques may be available, - * depending on the implementation. Such features need to be - * requested when creating the \ref VdpVideoMixer "VdpVideoMixer", - * and subsequently enabled. - * - * If the source material is marked progressive, two options are - * available for \ref VdpVideoMixerRender usage: - * - * -# Simply pass the allegedly progressive frames through the - * mixer, marking them as progressive. This equates to a - * so-called "flag following" mode. - * -# Apply any pulldown flags in the stream, yielding a higher - * rate stream of interlaced fields. These should then be - * passed through the mixer, marked as fields, with - * de-interlacing enabled, and inverse telecine optionally - * enabled. This should allow for so-called "bad edit" - * detection. However, it requires more processing power from - * the hardware. - * - * If the source material is marked interlaced, the decoded - * interlaced fields should always be marked as fields when - * processing them with the mixer. Some de-interlacing - * algorithm is then always applied. Inverse telecine may be - * useful in cases where some portions, or all of, the - * interlaced stream is telecined film. - * - * \section extending Extending the API - * + * + * \subsection video_surface_content VdpVideoSurface Content + * + * Each \ref VdpVideoSurface "VdpVideoSurface" is expected to contain an + * entire frame's-worth of data, irrespective of whether an interlaced of + * progressive sequence is being decoded. + * + * Depending on the exact encoding structure of the compressed video stream, + * the application may need to call \ref VdpDecoderRender twice to fill a + * single \ref VdpVideoSurface "VdpVideoSurface". When the stream contains an + * encoded progressive frame, or a "frame coded" interlaced field-pair, a + * single \ref VdpDecoderRender call will fill the entire surface. When the + * stream contains separately encoded interlaced fields, two + * \ref VdpDecoderRender calls will be required; one for the top field, and + * one for the bottom field. + * + * Implementation note: When \ref VdpDecoderRender renders an interlaced + * field, this operation must not disturb the content of the other field in + * the surface. + * + * \subsection vm_surf_list VdpVideoMixer Surface List + * + * An video stream is logically composed of a sequence of fields. An + * example is shown below, in display order, assuming top field first: + * + * 
t0 b0 t1 b1 t2 b2 t3 b3 t4 b4 t5 b5 t6 b6 t7 b7 t8 b8 t9 b9
+ * + * The canonical usage is to call \ref VdpVideoMixerRender once for decoded + * field, in display order, to yield one post-processed frame for display. + * + * For each call to \ref VdpVideoMixerRender, the field to be processed should + * be provided as the \b video_surface_current parameter. + * + * To enable operation of advanced de-interlacing algorithms and/or + * post-processing algorithms, some past and/or future surfaces should be + * provided as context. These are provided in the \b video_surface_past and + * \b video_surface_future lists. In general, these lists may contain any + * number of surfaces. Specific implementations may have specific requirements + * determining the minimum required number of surfaces for optimal operation, + * and the maximum number of useful surfaces, beyond which surfaces are not + * used. It is recommended that in all cases other than plain bob/weave, at + * least 2 past and 1 future frame be provided. + * + * Note that it is entirely possible, in general, for any of the + * \ref VdpVideoMixer "VdpVideoMixer" post-processing steps other than + * de-interlacing to require access to multiple input fields/frames. For + * example, an motion-sensitive noise-reduction algorithm. + * + * For example, when processing field t4, the \ref VdpVideoMixerRender + * parameters may contain the following values, if the application chose to + * provide 3 fields of context for both the past and future: + * + * 
+ * current_picture_structure: VDP_VIDEO_MIXER_PICTURE_STRUCTURE_TOP_FIELD
+ * past:    [b3, t3, b2]
+ * current: t4
+ * future:  [b4, t5, b5]
+ *
+ * + * Note that for both the past/future lists, array index 0 represents the + * field temporally closest to current, in display order. + * + * The \ref VdpVideoMixerRender parameter \b current_picture_structure applies + * to \b video_surface_current. The picture structure for the other surfaces + * will be automatically derived from that for the current picture. The + * derivation algorithm is extremely simple; the concatenated list + * past/current/future is simply assumed to have an alternating top/bottom + * pattern throughout. + * + * Continuing the example above, subsequent calls to \ref VdpVideoMixerRender + * would provide the following sets of parameters: + * + * 
+ * current_picture_structure: VDP_VIDEO_MIXER_PICTURE_STRUCTURE_BOTTOM_FIELD
+ * past:    [t4, b3, t3]
+ * current: b4
+ * future:  [t5, b5, t6]
+ *
+ * + * then: + * + * 
+ * current_picture_structure: VDP_VIDEO_MIXER_PICTURE_STRUCTURE_TOP_FIELD
+ * past:    [b4, t4, b3]
+ * current: t5
+ * future:  [b5, t6, b7]
+ *
+ * + * In other words, the concatenated list of past/current/future frames simply + * forms a window that slides through the sequence of decoded fields. + * + * It is syntactically legal for an application to choose not to provide a + * particular entry in the past or future lists. In this case, the "slot" in + * the surface list must be filled with the special value + * \ref VDP_INVALID_HANDLE, to explicitly indicate that the picture is + * missing; do not simply shuffle other surfaces together to fill in the gap. + * Note that entries should only be omitted under special circumstances, such + * as failed decode due to bitstream error during picture header parsing, + * since missing entries will typically cause advanced de-interlacing + * algorithms to experience significantly degraded operation. + * + * Specific examples for different de-interlacing types are presented below. + * + * \subsection deint_weave Weave De-interlacing + * + * Weave de-interlacing is the act of interleaving the lines of two temporally + * adjacent fields to form a frame for display. + * + * To disable de-interlacing for progressive streams, simply specify + * \b current_picture_structure as \ref VDP_VIDEO_MIXER_PICTURE_STRUCTURE_FRAME; + * no de-interlacing will be applied. + * + * Weave de-interlacing for interlaced streams is identical to disabling + * de-interlacing, as describe immediately above, because each + * \ref VdpVideoSurface already contains an entire frame's worth (i.e. two + * fields) of picture data. + * + * Inverse telecine is disabled when using weave de-interlacing. + * + * Weave de-interlacing produces one output frame for each input frame. The + * application should make one \ref VdpVideoMixerRender call per pair of + * decoded fields, or per decoded frame. + * + * Weave de-interlacing requires no entries in the past/future lists. + * + * All implementations must support weave de-interlacing. + * + * \subsection deint_bob Bob De-interlacing + * + * Bob de-interlacing is the act of vertically scaling a single field to the + * size of a single frame. + * + * To achieve bob de-interlacing, simply provide a single field as + * \b video_surface_current, and set \b current_picture_structure + * appropriately, to indicate whether a top or bottom field was provided. + * + * Inverse telecine is disabled when using bob de-interlacing. + * + * Bob de-interlacing produces one output frame for each input field. The + * application should make one \ref VdpVideoMixerRender call per decoded + * field. + * + * Bob de-interlacing requires no entries in the past/future lists. + * + * Bob de-interlacing is the default when no advanced method is requested and + * enabled. Advanced de-interlacing algorithms may fall back to bob e.g. when + * required past/future fields are missing. + * + * All implementations must support bob de-interlacing. + * + * \subsection deint_adv Advanced De-interlacing + * + * Operation of both temporal and temporal-spatial de-interlacing is + * identical; the only difference is the internal processing the algorithm + * performs in generating the output frame. + * + * These algorithms use various advanced processing on the pixels of both the + * current and various past/future fields in order to determine how best to + * de-interlacing individual portions of the image. + * + * Inverse telecine may be enabled when using advanced de-interlacing. + * + * Advanced de-interlacing produces one output frame for each input field. The + * application should make one \ref VdpVideoMixerRender call per decoded + * field. + * + * Advanced de-interlacing requires entries in the past/future lists. + * + * Availability of advanced de-interlacing algorithms is implementation + * dependent. + * + * \subsection deint_rate De-interlacing Rate + * + * For all de-interlacing algorithms except weave, a choice may be made to + * call \ref VdpVideoMixerRender for either each decoded field, or every + * second decoded field. + * + * If \ref VdpVideoMixerRender is called for every decoded field, the + * generated post-processed frame rate is equal to the decoded field rate. + * Put another way, the generated post-processed nominal field rate is equal + * to 2x the decoded field rate. This is standard practice. + * + * If \ref VdpVideoMixerRender is called for every second decoded field (say + * every top field), the generated post-processed frame rate is half to the + * decoded field rate. This mode of operation is thus referred to as + * "half-rate". + * + * Implementations may choose whether to support half-rate de-interlacing mode + * or not. Regular de-interlacing mode should be supported to any supported + * advanced de-interlacing algorithm. + * + * The descriptions of de-interlacing algorithms above assume that regular + * (not half-rate) operation is being performed, when detailing the number of + "half-rate" de-interlacing is used.deoMixerRender calls. + * + * Recall that the concatenation of past/current/future surface lists simply + * forms a window into the stream of decoded fields. To achieve standard + * de-interlacing, the window is slid through the list of decoded fields one + * field at a time, and a call is made to \ref VdpVideoMixerRender for each + * movement of the window. To achieve half-rate de-interlacing, the window is + * slid through the* list of decoded fields two fields at a time, and a + * call is made to \ref VdpVideoMixerRender for each movement of the window. + * + * \subsection invtc Inverse Telecine + * + * Assuming the implementation supports it, inverse telecine may be enabled + * alongside any advanced de-interlacing algorithm. Inverse telecine is never + * active for bob or weave. + * + * Operation of \ref VdpVideoMixerRender with inverse telecine active is + * identical to the basic operation mechanisms describe above in every way; + * all inverse telecine processing is performed internally to the + * \ref VdpVideoMixer "VdpVideoMixer". + * + * In particular, there is no provision way for \ref VdpVideoMixerRender to + * indicate when identical input fields have been observed, and consequently + * identical output frames may have been produced. + * + * De-interlacing (and inverse telecine) may be applied to streams that are + * marked as being progressive. This will allow detection of, and correct + * de-interlacing of, mixed interlace/progressive streams, bad edits, etc. + * To implement de-interlacing/inverse-telecine on progressive material, + * simply treat the stream of decoded frames as a stream of decoded fields, + * apply any telecine flags (see the next section), and then apply + * de-interlacing to those fields as described above. + * + * Implementations are free to determine whether inverse telecine operates + * in conjunction with half-rate de-interlacing or not. It should always + * operate with regular de-interlacing, when advertized. + * + * \subsection tcflags Telecine (Pull-Down) Flags + * + * Some media delivery formats, e.g. DVD-Video, include flags that are + * intended to modify the decoded field sequence before display. This allows + * e.g. 24p content to be encoded at 48i, which saves space relative to a 60i + * encoded stream, but still displayed at 60i, to match target consumer + * display equipment. + * + * If the inverse telecine option is not activated in the + * \ref VdpVideoMixer "VdpVideoMixer", these flags should be ignored, and the + * decoded fields passed directly to \ref VdpVideoMixerRender as detailed + * above. + * + * However, to make full use of the inverse telecine feature, these flags + * should be applied to the field stream, yielding another field stream with + * some repeated fields, before passing the field stream to + * \ref VdpVideoMixerRender. In this scenario, the sliding window mentioned + * in the descriptions above applies to the field stream after application of + * flags. + * + * \section extending Extending the API + * * \subsection extend_enums Enumerations and Other Constants - * + * * VDPAU defines a number of enumeration types. - * + * * When modifying VDPAU, existing enumeration constants must * continue to exist (although they may be deprecated), and do * so in the existing order. - * - * The above discussion naturally applies to "manually" defined - * enumerations, using pre-processor macros, too. - * + * + * The above discussion naturally applies to "manually" defined + * enumerations, using pre-processor macros, too. + * * \subsection extend_structs Structures - * + * * In most case, VDPAU includes no provision for modifying existing * structure definitions, although they may be deprecated. - * + * * New structures may be created, together with new API entry - * points or feature/attribute/parameter values, to expose new - * functionality. + * points or feature/attribute/parameter values, to expose new + * functionality. * * A few structures are considered plausible candidates for future extension. * Such structures include a version number as the first field, indicating the @@ -473,21 +706,21 @@ * modified by adding new fields to the end of the structure, so that the * original structure definition is completely compatible with a leading * subset of fields of the extended structure. - * + * * \subsection extend_functions Functions - * + * * Existing functions may not be modified, although they may be * deprecated. - * + * * New functions may be added at will. Note the enumeration * requirements when modifying the enumeration that defines the * list of entry points. - * - * \section preemption_note Display Preemption - * - * Please note that the display may be preempted away from - * VDPAU at any time. See \ref display_preemption for more - * details. + * + * \section preemption_note Display Preemption + * + * Please note that the display may be preempted away from + * VDPAU at any time. See \ref display_preemption for more + * details. * * \subsection trademarks Trademarks * @@ -523,7 +756,7 @@ extern "C" { /** * \defgroup base_types Basic Types - * + * * VDPAU primarily uses ISO C99 types from \c stdint.h. * * @{ @@ -533,8 +766,8 @@ extern "C" { #define VDP_TRUE 1 /** \brief A false \ref VdpBool value */ #define VDP_FALSE 0 -/** - * \brief A boolean value, holding \ref VDP_TRUE or \ref +/** + * \brief A boolean value, holding \ref VDP_TRUE or \ref * VDP_FALSE. */ typedef int VdpBool; @@ -548,14 +781,14 @@ typedef int VdpBool; */ /** - * \brief An invalid object handle value. - * - * This value may be used to represent an invalid, or - * non-existent, object (\ref VdpDevice "VdpDevice", - * \ref VdpVideoSurface "VdpVideoSurface", etc.) - * - * Note that most APIs require valid object handles in all - * cases, and will fail when presented with this value. + * \brief An invalid object handle value. + * + * This value may be used to represent an invalid, or + * non-existent, object (\ref VdpDevice "VdpDevice", + * \ref VdpVideoSurface "VdpVideoSurface", etc.) + * + * Note that most APIs require valid object handles in all + * cases, and will fail when presented with this value. */ #define VDP_INVALID_HANDLE 0xffffffffU @@ -577,85 +810,85 @@ typedef uint32_t VdpChromaType; */ typedef uint32_t VdpYCbCrFormat; -/** - * \hideinitializer - * \brief The "NV12" YCbCr surface format. - * - * This format has a two planes, a Y plane and a UV plane. - * - * The Y plane is an array of byte-sized Y components. - * Applications should access this data via a uint8_t pointer. - * - * The UV plane is an array of interleaved byte-sized U and V - * components, in the order U, V, U, V. Applications should - * access this data via a uint8_t pointer. - */ +/** + * \hideinitializer + * \brief The "NV12" YCbCr surface format. + * + * This format has a two planes, a Y plane and a UV plane. + * + * The Y plane is an array of byte-sized Y components. + * Applications should access this data via a uint8_t pointer. + * + * The UV plane is an array of interleaved byte-sized U and V + * components, in the order U, V, U, V. Applications should + * access this data via a uint8_t pointer. + */ #define VDP_YCBCR_FORMAT_NV12 (VdpYCbCrFormat)0 -/** - * \hideinitializer - * \brief The "YV12" YCbCr surface format. - * +/** + * \hideinitializer + * \brief The "YV12" YCbCr surface format. + * * This format has a three planes, a Y plane, a U plane, and a V - * plane. - * - * Each of the planes is an array of byte-sized components. - * - * Applications should access this data via a uint8_t pointer. - */ + * plane. + * + * Each of the planes is an array of byte-sized components. + * + * Applications should access this data via a uint8_t pointer. + */ #define VDP_YCBCR_FORMAT_YV12 (VdpYCbCrFormat)1 -/** - * \hideinitializer - * \brief The "UYVY" YCbCr surface format. - * - * This format may also be known as Y422, UYNV, HDYC. - * - * This format has a single plane. - * - * This plane is an array of interleaved byte-sized Y, U, and V - * components, in the order U, Y, V, Y, U, Y, V, Y. - * +/** + * \hideinitializer + * \brief The "UYVY" YCbCr surface format. + * + * This format may also be known as Y422, UYNV, HDYC. + * + * This format has a single plane. + * + * This plane is an array of interleaved byte-sized Y, U, and V + * components, in the order U, Y, V, Y, U, Y, V, Y. + * * Applications should access this data via a uint8_t pointer. - */ + */ #define VDP_YCBCR_FORMAT_UYVY (VdpYCbCrFormat)2 -/** - * \hideinitializer - * \brief The "YUYV" YCbCr surface format. - * +/** + * \hideinitializer + * \brief The "YUYV" YCbCr surface format. + * * This format may also be known as YUY2, YUNV, V422. - * - * This format has a single plane. - * - * This plane is an array of interleaved byte-sized Y, U, and V - * components, in the order Y, U, Y, V, Y, U, Y, V. - * + * + * This format has a single plane. + * + * This plane is an array of interleaved byte-sized Y, U, and V + * components, in the order Y, U, Y, V, Y, U, Y, V. + * * Applications should access this data via a uint8_t pointer. - */ + */ #define VDP_YCBCR_FORMAT_YUYV (VdpYCbCrFormat)3 -/** - * \hideinitializer +/** + * \hideinitializer * \brief A packed YCbCr format. - * - * This format has a single plane. - * - * This plane is an array packed 32-bit pixel data. Within each - * 32-bit pixel, bits [31:24] contain A, bits [23:16] contain V, - * bits [15:8] contain U, and bits [7:0] contain Y. - * + * + * This format has a single plane. + * + * This plane is an array packed 32-bit pixel data. Within each + * 32-bit pixel, bits [31:24] contain A, bits [23:16] contain V, + * bits [15:8] contain U, and bits [7:0] contain Y. + * * Applications should access this data via a uint32_t pointer. - */ + */ #define VDP_YCBCR_FORMAT_Y8U8V8A8 (VdpYCbCrFormat)4 -/** - * \hideinitializer +/** + * \hideinitializer * \brief A packed YCbCr format. - * - * This format has a single plane. - * - * This plane is an array packed 32-bit pixel data. Within each + * + * This format has a single plane. + * + * This plane is an array packed 32-bit pixel data. Within each * 32-bit pixel, bits [31:24] contain A, bits [23:16] contain Y, - * bits [15:8] contain U, and bits [7:0] contain V. - * + * bits [15:8] contain U, and bits [7:0] contain V. + * * Applications should access this data via a uint32_t pointer. - */ + */ #define VDP_YCBCR_FORMAT_V8U8Y8A8 (VdpYCbCrFormat)5 /** @@ -663,68 +896,68 @@ typedef uint32_t VdpYCbCrFormat; */ typedef uint32_t VdpRGBAFormat; -/** - * \hideinitializer +/** + * \hideinitializer * \brief A packed RGB format. - * - * This format has a single plane. - * - * This plane is an array packed 32-bit pixel data. Within each + * + * This format has a single plane. + * + * This plane is an array packed 32-bit pixel data. Within each * 32-bit pixel, bits [31:24] contain A, bits [23:16] contain R, - * bits [15:8] contain G, and bits [7:0] contain B. - * + * bits [15:8] contain G, and bits [7:0] contain B. + * * Applications should access this data via a uint32_t pointer. - */ + */ #define VDP_RGBA_FORMAT_B8G8R8A8 (VdpRGBAFormat)0 -/** - * \hideinitializer +/** + * \hideinitializer * \brief A packed RGB format. - * - * This format has a single plane. - * - * This plane is an array packed 32-bit pixel data. Within each + * + * This format has a single plane. + * + * This plane is an array packed 32-bit pixel data. Within each * 32-bit pixel, bits [31:24] contain A, bits [23:16] contain B, - * bits [15:8] contain G, and bits [7:0] contain R. - * + * bits [15:8] contain G, and bits [7:0] contain R. + * * Applications should access this data via a uint32_t pointer. - */ + */ #define VDP_RGBA_FORMAT_R8G8B8A8 (VdpRGBAFormat)1 -/** - * \hideinitializer +/** + * \hideinitializer * \brief A packed RGB format. - * - * This format has a single plane. - * - * This plane is an array packed 32-bit pixel data. Within each + * + * This format has a single plane. + * + * This plane is an array packed 32-bit pixel data. Within each * 32-bit pixel, bits [31:30] contain A, bits [29:20] contain B, - * bits [19:10] contain G, and bits [9:0] contain R. - * - * Applications should access this data via a uint32_t pointer. - */ + * bits [19:10] contain G, and bits [9:0] contain R. + * + * Applications should access this data via a uint32_t pointer. + */ #define VDP_RGBA_FORMAT_R10G10B10A2 (VdpRGBAFormat)2 -/** - * \hideinitializer +/** + * \hideinitializer * \brief A packed RGB format. - * - * This format has a single plane. - * - * This plane is an array packed 32-bit pixel data. Within each + * + * This format has a single plane. + * + * This plane is an array packed 32-bit pixel data. Within each * 32-bit pixel, bits [31:30] contain A, bits [29:20] contain R, - * bits [19:10] contain G, and bits [9:0] contain B. - * - * Applications should access this data via a uint32_t pointer. - */ + * bits [19:10] contain G, and bits [9:0] contain B. + * + * Applications should access this data via a uint32_t pointer. + */ #define VDP_RGBA_FORMAT_B10G10R10A2 (VdpRGBAFormat)3 -/** - * \hideinitializer - * \brief An alpha-only surface format. - * - * This format has a single plane. - * +/** + * \hideinitializer + * \brief An alpha-only surface format. + * + * This format has a single plane. + * * This plane is an array of byte-sized components. - * - * Applications should access this data via a uint8_t pointer. - */ + * + * Applications should access this data via a uint8_t pointer. + */ #define VDP_RGBA_FORMAT_A8 (VdpRGBAFormat)4 /** @@ -732,53 +965,53 @@ typedef uint32_t VdpRGBAFormat; */ typedef uint32_t VdpIndexedFormat; -/** - * \hideinitializer - * \brief A 4-bit indexed format, with alpha. - * - * This format has a single plane. - * - * This plane is an array of byte-sized components. Within each +/** + * \hideinitializer + * \brief A 4-bit indexed format, with alpha. + * + * This format has a single plane. + * + * This plane is an array of byte-sized components. Within each * byte, bits [7:4] contain I (index), and bits [3:0] contain A. - * - * Applications should access this data via a uint8_t pointer. - */ + * + * Applications should access this data via a uint8_t pointer. + */ #define VDP_INDEXED_FORMAT_A4I4 (VdpIndexedFormat)0 -/** - * \hideinitializer - * \brief A 4-bit indexed format, with alpha. - * - * This format has a single plane. - * - * This plane is an array of byte-sized components. Within each - * byte, bits [7:4] contain A, and bits [3:0] contain I (index). - * - * Applications should access this data via a uint8_t pointer. - */ +/** + * \hideinitializer + * \brief A 4-bit indexed format, with alpha. + * + * This format has a single plane. + * + * This plane is an array of byte-sized components. Within each + * byte, bits [7:4] contain A, and bits [3:0] contain I (index). + * + * Applications should access this data via a uint8_t pointer. + */ #define VDP_INDEXED_FORMAT_I4A4 (VdpIndexedFormat)1 -/** - * \hideinitializer - * \brief A 8-bit indexed format, with alpha. - * - * This format has a single plane. - * - * This plane is an array of interleaved byte-sized A and I - * (index) components, in the order A, I, A, I. - * +/** + * \hideinitializer + * \brief A 8-bit indexed format, with alpha. + * + * This format has a single plane. + * + * This plane is an array of interleaved byte-sized A and I + * (index) components, in the order A, I, A, I. + * * Applications should access this data via a uint8_t pointer. - */ + */ #define VDP_INDEXED_FORMAT_A8I8 (VdpIndexedFormat)2 -/** - * \hideinitializer - * \brief A 8-bit indexed format, with alpha. - * - * This format has a single plane. - * - * This plane is an array of interleaved byte-sized A and I - * (index) components, in the order I, A, I, A. - * +/** + * \hideinitializer + * \brief A 8-bit indexed format, with alpha. + * + * This format has a single plane. + * + * This plane is an array of interleaved byte-sized A and I + * (index) components, in the order I, A, I, A. + * * Applications should access this data via a uint8_t pointer. - */ + */ #define VDP_INDEXED_FORMAT_I8A8 (VdpIndexedFormat)3 /** @@ -840,7 +1073,7 @@ typedef struct { */ /** - * \hideinitializer + * \hideinitializer * \brief The set of all possible error codes. */ typedef enum { @@ -850,10 +1083,10 @@ typedef enum { * No backend implementation could be loaded. */ VDP_STATUS_NO_IMPLEMENTATION, - /** + /** * The display was preempted, or a fatal error occurred. * - * The application must re-initialize VDPAU. + * The application must re-initialize VDPAU. */ VDP_STATUS_DISPLAY_PREEMPTED, /** @@ -980,7 +1213,7 @@ typedef enum { /** * \brief Retrieve a string describing an error code. * \param[in] status The error code. - * \return A pointer to the string. Note that this is a + * \return A pointer to the string. Note that this is a * statically allocated read-only string. As such, the * application must not free the returned pointer. The * pointer is valid as long as the VDPAU implementation is @@ -992,24 +1225,24 @@ typedef char const * VdpGetErrorString( /*@}*/ -/** - * \defgroup versioning Versioning - * - * - * @{ - */ +/** + * \defgroup versioning Versioning + * + * + * @{ + */ -/** - * \brief The VDPAU version described by this header file. - * - * Note that VDPAU version numbers are simple integers that - * increase monotonically (typically by value 1) with each VDPAU - * header revision. +/** + * \brief The VDPAU version described by this header file. + * + * Note that VDPAU version numbers are simple integers that + * increase monotonically (typically by value 1) with each VDPAU + * header revision. */ #define VDPAU_VERSION 0 /** - * \brief Retrieve the VDPAU version implemented by the backend. + * \brief Retrieve the VDPAU version implemented by the backend. * \param[out] api_version The API version. * \return VdpStatus The completion status of the operation. */ @@ -1019,7 +1252,7 @@ typedef VdpStatus VdpGetApiVersion( ); /** - * \brief Retrieve an implementation-specific string description + * \brief Retrieve an implementation-specific string description * of the implementation. This typically includes detailed version * information. * \param[out] information_string A pointer to the information @@ -1028,12 +1261,12 @@ typedef VdpStatus VdpGetApiVersion( * free the returned pointer. The pointer is valid as long * as the implementation is present within the * application's address space. - * \return VdpStatus The completion status of the operation. - * - * Note that the returned string is useful for information - * reporting. It is not intended that the application should - * parse this string in order to determine any information about - * the implementation. + * \return VdpStatus The completion status of the operation. + * + * Note that the returned string is useful for information + * reporting. It is not intended that the application should + * parse this string in order to determine any information about + * the implementation. */ typedef VdpStatus VdpGetInformationString( /* output parameters follow */ @@ -1076,8 +1309,8 @@ typedef VdpStatus VdpDeviceDestroy( * \defgroup VdpCSCMatrix VdpCSCMatrix; CSC Matrix Manipulation * * When converting from YCbCr to RGB data formats, a color space - * conversion operation must be performed. This operation is - * parameterized using a "color space conversion matrix". The + * conversion operation must be performed. This operation is + * parameterized using a "color space conversion matrix". The * VdpCSCMatrix is a data structure representing this * information. * @@ -1137,7 +1370,7 @@ typedef struct { float contrast; /** * Saturation adjustment amount. A value clamped between 0.0 and - * 10.0. 1.0 represents no modification. + * 10.0. 1.0 represents no modification. */ float saturation; /** @@ -1183,7 +1416,7 @@ typedef VdpStatus VdpGenerateCSCMatrix( * \defgroup VdpVideoSurface VdpVideoSurface; Video Surface object * * A VdpVideoSurface stores YCbCr data in an internal format, - * with a variety of possible chroma sub-sampling options. + * with a variety of possible chroma sub-sampling options. * * A VdpVideoSurface may be filled with: * - Data provided by the CPU via \ref @@ -1262,12 +1495,12 @@ typedef uint32_t VdpVideoSurface; * \param[in] width The width of the new surface. * \param[in] height The height of the new surface. * \param[out] surface The new surface's handle. - * \return VdpStatus The completion status of the operation. - * + * \return VdpStatus The completion status of the operation. + * * The memory backing the surface may not be initialized during - * creation. Applications are expected to initialize any region - * that they use, via \ref VdpDecoderRender or \ref - * VdpVideoSurfacePutBitsYCbCr. + * creation. Applications are expected to initialize any region + * that they use, via \ref VdpDecoderRender or \ref + * VdpVideoSurfacePutBitsYCbCr. */ typedef VdpStatus VdpVideoSurfaceCreate( VdpDevice device, @@ -1360,7 +1593,7 @@ typedef VdpStatus VdpVideoSurfacePutBitsYCbCr( * \defgroup VdpOutputSurface VdpOutputSurface; Output Surface \ * object * - * A VdpOutputSurface stores RGBA data in a defined format. + * A VdpOutputSurface stores RGBA data in a defined format. * * A VdpOutputSurface may be filled with: * - Data provided by the CPU via the various @@ -1386,22 +1619,22 @@ typedef VdpStatus VdpVideoSurfacePutBitsYCbCr( */ /** - * \brief The set of all known color table formats, for use with + * \brief The set of all known color table formats, for use with * \ref VdpOutputSurfacePutBitsIndexed. */ typedef uint32_t VdpColorTableFormat; -/** - * \hideinitializer - * \brief 8-bit per component packed into 32-bits - * - * This format is an array of packed 32-bit RGB color values. - * Bits [31:24] are unused, bits [23:16] contain R, bits [15:8] - * contain G, and bits [7:0] contain B. Note: The format is - * physically an array of uint32_t values, and should be accessed - * as such by the application in order to avoid endianness - * issues. - */ +/** + * \hideinitializer + * \brief 8-bit per component packed into 32-bits + * + * This format is an array of packed 32-bit RGB color values. + * Bits [31:24] are unused, bits [23:16] contain R, bits [15:8] + * contain G, and bits [7:0] contain B. Note: The format is + * physically an array of uint32_t values, and should be accessed + * as such by the application in order to avoid endianness + * issues. + */ #define VDP_COLOR_TABLE_FORMAT_B8G8R8X8 (VdpColorTableFormat)0 /** @@ -1452,7 +1685,7 @@ typedef VdpStatus VdpOutputSurfaceQueryGetPutBitsNativeCapabilities( * which information is requested. * \param[in] bits_indexed_format The format of the application * data buffer. - * \param[in] color_table_format The format of the color lookup + * \param[in] color_table_format The format of the color lookup * table. * \param[out] is_supported Is this surface format supported? * \return VdpStatus The completion status of the operation. @@ -1499,8 +1732,8 @@ typedef uint32_t VdpOutputSurface; * \param[in] width The width of the new surface. * \param[in] height The height of the new surface. * \param[out] surface The new surface's handle. - * \return VdpStatus The completion status of the operation. - * + * \return VdpStatus The completion status of the operation. + * * The memory backing the surface will be initialized to 0 color * and 0 alpha (i.e. black.) */ @@ -1610,10 +1843,10 @@ typedef VdpStatus VdpOutputSurfacePutBitsNative( * \param[in] destination_rect The sub-rectangle of the surface * to fill with application data. If NULL, the entire * surface will be updated. - * \param[in] color_table_format The format of the color_table. + * \param[in] color_table_format The format of the color_table. * \param[in] color_table A table that maps between source index * and target color data. See \ref VdpColorTableFormat for - * details regarding the memory layout. + * details regarding the memory layout. * \return VdpStatus The completion status of the operation. */ typedef VdpStatus VdpOutputSurfacePutBitsIndexed( @@ -1737,10 +1970,10 @@ typedef uint32_t VdpBitmapSurface; * Implementations may use this as a hint to determine how * to allocate the underlying storage for the surface. * \param[out] surface The new surface's handle. - * \return VdpStatus The completion status of the operation. - * - * The memory backing the surface may not be initialized - * during creation. Applications are expected initialize any + * \return VdpStatus The completion status of the operation. + * + * The memory backing the surface may not be initialized + * during creation. Applications are expected initialize any * region that they use, via \ref VdpBitmapSurfacePutBitsNative. */ typedef VdpStatus VdpBitmapSurfaceCreate( @@ -1821,10 +2054,10 @@ typedef VdpStatus VdpBitmapSurfacePutBitsNative( * @{ */ -/** - * \hideinitializer +/** + * \hideinitializer * \brief The blending equation factors. - */ + */ typedef enum { VDP_OUTPUT_SURFACE_RENDER_BLEND_FACTOR_ZERO = 0, VDP_OUTPUT_SURFACE_RENDER_BLEND_FACTOR_ONE = 1, @@ -1843,10 +2076,10 @@ typedef enum { VDP_OUTPUT_SURFACE_RENDER_BLEND_FACTOR_ONE_MINUS_CONSTANT_ALPHA = 14, } VdpOutputSurfaceRenderBlendFactor; -/** - * \hideinitializer +/** + * \hideinitializer * \brief The blending equations. - */ + */ typedef enum { VDP_OUTPUT_SURFACE_RENDER_BLEND_EQUATION_SUBTRACT = 0, VDP_OUTPUT_SURFACE_RENDER_BLEND_EQUATION_REVERSE_SUBTRACT = 1, @@ -1874,35 +2107,35 @@ typedef struct { VdpColor blend_constant; } VdpOutputSurfaceRenderBlendState; -/** - * \hideinitializer +/** + * \hideinitializer * \brief Do not rotate source_surface prior to compositing. */ #define VDP_OUTPUT_SURFACE_RENDER_ROTATE_0 0 /** - * \hideinitializer + * \hideinitializer * \brief Rotate source_surface 90 degrees clockwise prior to * compositing. */ #define VDP_OUTPUT_SURFACE_RENDER_ROTATE_90 1 /** - * \hideinitializer + * \hideinitializer * \brief Rotate source_surface 180 degrees prior to * compositing. */ #define VDP_OUTPUT_SURFACE_RENDER_ROTATE_180 2 /** - * \hideinitializer + * \hideinitializer * \brief Rotate source_surface 270 degrees clockwise prior to * compositing. */ #define VDP_OUTPUT_SURFACE_RENDER_ROTATE_270 3 /** - * \hideinitializer + * \hideinitializer * \brief A separate color is used for each vertex of the * smooth-shaded quad. Hence, colors array contains 4 * elements rather than 1. See description of colors @@ -2301,14 +2534,14 @@ typedef struct { } VdpBitstreamBuffer; /** - * \brief A generic "picture information" pointer type. - * - * This type serves solely to document the expected usage of a - * generic (void *) function parameter. In actual usage, the - * application is expected to physically provide a pointer to an - * instance of one of the "real" VdpPictureInfo* structures, - * picking the type appropriate for the decoder object in - * question. + * \brief A generic "picture information" pointer type. + * + * This type serves solely to document the expected usage of a + * generic (void *) function parameter. In actual usage, the + * application is expected to physically provide a pointer to an + * instance of one of the "real" VdpPictureInfo* structures, + * picking the type appropriate for the decoder object in + * question. */ typedef void * VdpPictureInfo; @@ -2564,8 +2797,10 @@ typedef struct { */ uint8_t syncmarker; /** - * Copy of the VC-1 bitstream field. See VC-1 J.1.17. + * VC-1 SP/MP range reduction control. * Only used by simple and main profiles. + * Bit 0: Copy of rangered VC-1 bitstream field; See VC-1 J.1.17. + * Bit 1: Copy of rangeredfrm VC-1 bitstream fiels; See VC-1 7.1.13. */ uint8_t rangered; /** @@ -2619,7 +2854,7 @@ typedef VdpStatus VdpDecoderRender( /** * \defgroup VdpVideoMixer VdpVideoMixer; Video Post-processing \ * and Compositing object - * + * * VdpVideoMixer can perform some subset of the following * post-processing steps on video: * - De-interlacing @@ -2634,9 +2869,9 @@ typedef VdpStatus VdpDecoderRender( * processing steps on it (potentially using information from * past or future video surfaces). It scales the video and * converts it to RGB, then optionally composites it with - * multiple auxiliary \ref VdpOutputSurface "VdpOutputSurface"s - * before writing the result to the destination \ref - * VdpOutputSurface "VdpOutputSurface". + * multiple auxiliary \ref VdpOutputSurface "VdpOutputSurface"s + * before writing the result to the destination \ref + * VdpOutputSurface "VdpOutputSurface". * * The video mixer compositing model is as follows: * @@ -2647,7 +2882,7 @@ typedef VdpStatus VdpDecoderRender( * * - The first layer is the background color. The background * color will fill the entire rectangle. - * + * * - The second layer is the processed video which has been * converted to RGB. These pixels will overwrite the * background color of the first layer except where the second @@ -2657,7 +2892,7 @@ typedef VdpStatus VdpDecoderRender( * output rectangle is outside of the output rectangle, those * portions will be clipped. * - * - The third layer contains some number of auxiliary layers + * - The third layer contains some number of auxiliary layers * (in the form of \ref VdpOutputSurface "VdpOutputSurface"s) * which will be composited using the alpha value from the * those surfaces. The compositing operations are equivalent @@ -2670,28 +2905,28 @@ typedef VdpStatus VdpDecoderRender( */ /** - * \brief A VdpVideoMixer feature that must be requested at + * \brief A VdpVideoMixer feature that must be requested at * creation time to be used. - * - * Certain advanced VdpVideoMixer features are optional, and the - * ability to use those features at all must be requested when - * the VdpVideoMixer object is created. Each feature is named via + * + * Certain advanced VdpVideoMixer features are optional, and the + * ability to use those features at all must be requested when + * the VdpVideoMixer object is created. Each feature is named via * a specific VdpVideoMixerFeature value. - * - * Once requested, these features are permanently available - * within that specific VdpVideoMixer object. All features that - * are not explicitly requested at creation time default to - * being permanently unavailable. - * - * Even when requested, all features default to being initially - * disabled. However, applications can subsequently enable and - * disable features at any time. See \ref - * VdpVideoMixerSetFeatureEnables. - * - * Some features allow configuration of their operation. Each - * configurable item is an \ref VdpVideoMixerAttribute. These - * attributes may be manipulated at any time using \ref - * VdpVideoMixerSetAttributeValues. + * + * Once requested, these features are permanently available + * within that specific VdpVideoMixer object. All features that + * are not explicitly requested at creation time default to + * being permanently unavailable. + * + * Even when requested, all features default to being initially + * disabled. However, applications can subsequently enable and + * disable features at any time. See \ref + * VdpVideoMixerSetFeatureEnables. + * + * Some features allow configuration of their operation. Each + * configurable item is an \ref VdpVideoMixerAttribute. These + * attributes may be manipulated at any time using \ref + * VdpVideoMixerSetAttributeValues. */ typedef uint32_t VdpVideoMixerFeature; @@ -2699,25 +2934,25 @@ typedef uint32_t VdpVideoMixerFeature; * \hideinitializer * \brief A VdpVideoMixerFeature. * - * When requested and enabled, motion adaptive temporal - * deinterlacing will be used on interlaced content. - * - * When multiple de-interlacing options are requested and - * enabled, the back-end implementation chooses the best - * algorithm to apply. + * When requested and enabled, motion adaptive temporal + * deinterlacing will be used on interlaced content. + * + * When multiple de-interlacing options are requested and + * enabled, the back-end implementation chooses the best + * algorithm to apply. */ #define VDP_VIDEO_MIXER_FEATURE_DEINTERLACE_TEMPORAL (VdpVideoMixerFeature)0 /** * \hideinitializer * \brief A VdpVideoMixerFeature. * - * When requested and enabled, this enables a more advanced - * version of temporal de-interlacing, that additionally uses - * edge-guided spatial interpolation. - * - * When multiple de-interlacing options are requested and - * enabled, the back-end implementation chooses the best - * algorithm to apply. + * When requested and enabled, this enables a more advanced + * version of temporal de-interlacing, that additionally uses + * edge-guided spatial interpolation. + * + * When multiple de-interlacing options are requested and + * enabled, the back-end implementation chooses the best + * algorithm to apply. */ #define VDP_VIDEO_MIXER_FEATURE_DEINTERLACE_TEMPORAL_SPATIAL (VdpVideoMixerFeature)1 /** @@ -2725,148 +2960,148 @@ typedef uint32_t VdpVideoMixerFeature; * \brief A VdpVideoMixerFeature. * * When requested and enabled, cadence detection will be enabled - * on interlaced content and the video mixer will try to extract - * progressive frames from pull-down material. + * on interlaced content and the video mixer will try to extract + * progressive frames from pull-down material. */ #define VDP_VIDEO_MIXER_FEATURE_INVERSE_TELECINE (VdpVideoMixerFeature)2 /** * \hideinitializer * \brief A VdpVideoMixerFeature. * - * When requested and enabled, a noise reduction algorithm will - * be applied to the video. + * When requested and enabled, a noise reduction algorithm will + * be applied to the video. */ #define VDP_VIDEO_MIXER_FEATURE_NOISE_REDUCTION (VdpVideoMixerFeature)3 /** * \hideinitializer * \brief A VdpVideoMixerFeature. * - * When requested and enabled, a sharpening algorithm will be - * applied to the video. + * When requested and enabled, a sharpening algorithm will be + * applied to the video. */ #define VDP_VIDEO_MIXER_FEATURE_SHARPNESS (VdpVideoMixerFeature)4 /** * \hideinitializer * \brief A VdpVideoMixerFeature. * - * When requested and enabled, the alpha of the rendered - * surface, which is normally set to the alpha of the background - * color, will be forced to 0.0 on pixels corresponding to - * source video surface luminance values in the range specified + * When requested and enabled, the alpha of the rendered + * surface, which is normally set to the alpha of the background + * color, will be forced to 0.0 on pixels corresponding to + * source video surface luminance values in the range specified * by attributes \ref VDP_VIDEO_MIXER_ATTRIBUTE_LUMA_KEY_MIN_LUMA - * to \ref VDP_VIDEO_MIXER_ATTRIBUTE_LUMA_KEY_MAX_LUMA. This - * keying is performed after scaling and de-interlacing. + * to \ref VDP_VIDEO_MIXER_ATTRIBUTE_LUMA_KEY_MAX_LUMA. This + * keying is performed after scaling and de-interlacing. */ #define VDP_VIDEO_MIXER_FEATURE_LUMA_KEY (VdpVideoMixerFeature)5 /** * \brief A VdpVideoMixer creation parameter. - * + * * When a VdpVideoMixer is created, certain parameters may be * supplied. Each parameter is named via a specific - * VdpVideoMixerParameter value. - * - * Each parameter has a specific type, and specific default - * value if not specified at VdpVideoMixer creation time. The - * application may query the legal supported range for some - * parameters. + * VdpVideoMixerParameter value. + * + * Each parameter has a specific type, and specific default + * value if not specified at VdpVideoMixer creation time. The + * application may query the legal supported range for some + * parameters. */ typedef uint32_t VdpVideoMixerParameter; -/** - * \hideinitializer - * \brief The exact width of input video surfaces. - * - * This attribute's type is uint32_t. - * - * This parameter defaults to 0 if not specified, which entails - * that it must be specified. - * - * The application may query this parameter's supported - * range. +/** + * \hideinitializer + * \brief The exact width of input video surfaces. + * + * This parameter's type is uint32_t. + * + * This parameter defaults to 0 if not specified, which entails + * that it must be specified. + * + * The application may query this parameter's supported + * range. */ #define VDP_VIDEO_MIXER_PARAMETER_VIDEO_SURFACE_WIDTH (VdpVideoMixerParameter)0 -/** - * \hideinitializer - * \brief The exact height of input video surfaces. - * - * This attribute's type is uint32_t. - * - * This parameter defaults to 0 if not specified, which entails - * that it must be specified. - * - * The application may query this parameter's supported +/** + * \hideinitializer + * \brief The exact height of input video surfaces. + * + * This parameter's type is uint32_t. + * + * This parameter defaults to 0 if not specified, which entails + * that it must be specified. + * + * The application may query this parameter's supported * range. - */ + */ #define VDP_VIDEO_MIXER_PARAMETER_VIDEO_SURFACE_HEIGHT (VdpVideoMixerParameter)1 -/** - * \hideinitializer - * \brief The chroma type of the input video surfaces the will +/** + * \hideinitializer + * \brief The chroma type of the input video surfaces the will * process. - * - * This attribute's type is VdpChromaType. - * + * + * This parameter's type is VdpChromaType. + * * If not specified, this parameter defaults to - * VDP_CHROMA_TYPE_420. - * - * The application may not query this application's supported + * VDP_CHROMA_TYPE_420. + * + * The application may not query this application's supported * range, since it is a potentially disjoint enumeration. - */ + */ #define VDP_VIDEO_MIXER_PARAMETER_CHROMA_TYPE (VdpVideoMixerParameter)2 -/** - * \hideinitializer - * \brief The number of auxiliary layers in the mixer's +/** + * \hideinitializer + * \brief The number of auxiliary layers in the mixer's * compositing model. - * - * Note that this indicates the maximum number of layers that - * may be processed by a given \ref VdpVideoMixer "VdpVideoMixer" - * object. Each individual \ref VdpVideoMixerRender invocation - * may choose to use a different number of actual layers, from 0 + * + * Note that this indicates the maximum number of layers that + * may be processed by a given \ref VdpVideoMixer "VdpVideoMixer" + * object. Each individual \ref VdpVideoMixerRender invocation + * may choose to use a different number of actual layers, from 0 * up to this limit. - * - * This attribute's type is uint32_t. - * + * + * This attribute's type is uint32_t. + * * If not specified, this parameter defaults to 0. - * - * The application may query this parameter's supported + * + * The application may query this parameter's supported * range. - */ + */ #define VDP_VIDEO_MIXER_PARAMETER_LAYERS (VdpVideoMixerParameter)3 /** - * \brief An adjustable attribute of VdpVideoMixer operation. - * - * Various attributes of VdpVideoMixer operation may be adjusted + * \brief An adjustable attribute of VdpVideoMixer operation. + * + * Various attributes of VdpVideoMixer operation may be adjusted * at any time. Each attribute is named via a specific - * VdpVideoMixerAttribute value. - * - * Each attribute has a specific type, and specific default - * value if not specified at VdpVideoMixer creation time. The - * application may query the legal supported range for some - * attributes. + * VdpVideoMixerAttribute value. + * + * Each attribute has a specific type, and specific default + * value if not specified at VdpVideoMixer creation time. The + * application may query the legal supported range for some + * attributes. */ typedef uint32_t VdpVideoMixerAttribute; -/** - * \hideinitializer - * \brief The background color in the VdpVideoMixer's compositing +/** + * \hideinitializer + * \brief The background color in the VdpVideoMixer's compositing * model. - * - * This attribute's type is VdpColor. - * - * This parameter defaults to black (all color components 0.0 + * + * This attribute's type is VdpColor. + * + * This parameter defaults to black (all color components 0.0 * and alpha 1.0). - * - * The application may not query this parameter's supported + * + * The application may not query this parameter's supported * range, since the type is not scalar. - */ + */ #define VDP_VIDEO_MIXER_ATTRIBUTE_BACKGROUND_COLOR (VdpVideoMixerAttribute)0 -/** - * \hideinitializer - * \brief The color-space conversion matrix used by the +/** + * \hideinitializer + * \brief The color-space conversion matrix used by the * VdpVideoMixer. - * - * This attribute's type is \ref VdpCSCMatrix. + * + * This attribute's type is \ref VdpCSCMatrix. * * Note: When using \ref VdpVideoMixerGetAttributeValues to retrieve the * current CSC matrix, the attribute_values array must contain a pointer to @@ -2874,7 +3109,7 @@ typedef uint32_t VdpVideoMixerAttribute; * either initialize the referenced CSC matrix to the current value, *or* * clear the supplied pointer to NULL, if the previous set call supplied a * value of NULL in parameter_values, to request the default matrix. - * + * * \code * VdpCSCMatrix matrix; * VdpCSCMatrix * matrix_ptr; @@ -2883,68 +3118,83 @@ typedef uint32_t VdpVideoMixerAttribute; * \endcode * * This parameter defaults to a matrix suitable for ITU-R BT.601 - * input surfaces, with no procamp adjustments. - * - * The application may not query this parameter's supported + * input surfaces, with no procamp adjustments. + * + * The application may not query this parameter's supported * range, since the type is not scalar. - */ + */ #define VDP_VIDEO_MIXER_ATTRIBUTE_CSC_MATRIX (VdpVideoMixerAttribute)1 -/** - * \hideinitializer +/** + * \hideinitializer * \brief The amount of noise reduction algorithm to apply. - * - * This attribute's type is float. - * - * This parameter defaults to 0.0, which equates to no noise + * + * This attribute's type is float. + * + * This parameter defaults to 0.0, which equates to no noise * reduction. - * - * The application may query this parameter's supported range. - * However, the range is fixed as 0.0...1.0. - */ + * + * The application may query this parameter's supported range. + * However, the range is fixed as 0.0...1.0. + */ #define VDP_VIDEO_MIXER_ATTRIBUTE_NOISE_REDUCTION_LEVEL (VdpVideoMixerAttribute)2 -/** - * \hideinitializer +/** + * \hideinitializer * \brief The amount of sharpening, or blurring, to apply. - * + * * This attribute's type is float. - * - * This parameter defaults to 0.0, which equates to no - * sharpening. - * - * Positive values request sharpening. Negative values request - * blurring. - * - * The application may query this parameter's supported range. - * However, the range is fixed as -1.0...1.0. - */ + * + * This parameter defaults to 0.0, which equates to no + * sharpening. + * + * Positive values request sharpening. Negative values request + * blurring. + * + * The application may query this parameter's supported range. + * However, the range is fixed as -1.0...1.0. + */ #define VDP_VIDEO_MIXER_ATTRIBUTE_SHARPNESS_LEVEL (VdpVideoMixerAttribute)3 -/** - * \hideinitializer +/** + * \hideinitializer * \brief The minimum luma value for the luma key algorithm. - * - * This attribute's type is float. - * + * + * This attribute's type is float. + * * This parameter defaults to 0.0. - * - * The application may query this parameter's supported range. - * However, the range is fixed as 0.0...1.0. - */ + * + * The application may query this parameter's supported range. + * However, the range is fixed as 0.0...1.0. + */ #define VDP_VIDEO_MIXER_ATTRIBUTE_LUMA_KEY_MIN_LUMA (VdpVideoMixerAttribute)4 -/** - * \hideinitializer +/** + * \hideinitializer * \brief The maximum luma value for the luma key algorithm. - * - * This attribute's type is float. - * + * + * This attribute's type is float. + * * This parameter defaults to 1.0. - * - * The application may query this parameter's supported range. - * However, the range is fixed as 0.0...1.0. - */ + * + * The application may query this parameter's supported range. + * However, the range is fixed as 0.0...1.0. + */ #define VDP_VIDEO_MIXER_ATTRIBUTE_LUMA_KEY_MAX_LUMA (VdpVideoMixerAttribute)5 +/** + * \hideinitializer + * \brief Whether de-interlacers should operate solely on luma, and bob chroma. + * + * Note: This attribute only affects advanced de-interlacing algorithms, not + * bob or weave. + * + * This attribute's type is uint8_t. + * + * This parameter defaults to 0. + * + * The application may query this parameter's supported range. + * However, the range is fixed as 0 (no/off) ... 1 (yes/on). + */ +#define VDP_VIDEO_MIXER_ATTRIBUTE_SKIP_CHROMA_DEINTERLACE (VdpVideoMixerAttribute)6 /** - * \brief Query the implementation's support for a specific + * \brief Query the implementation's support for a specific * feature. * \param[in] device The device to query. * \param[in] feature The feature for which support is to be @@ -2960,12 +3210,12 @@ typedef VdpStatus VdpVideoMixerQueryFeatureSupport( ); /** - * \brief Query the implementation's support for a specific + * \brief Query the implementation's support for a specific * parameter. * \param[in] device The device to query. * \param[in] parameter The parameter for which support is to be * queried. - * \param[out] is_supported Is the specified parameter + * \param[out] is_supported Is the specified parameter * supported? * \return VdpStatus The completion status of the operation. */ @@ -2977,7 +3227,7 @@ typedef VdpStatus VdpVideoMixerQueryParameterSupport( ); /** - * \brief Query the implementation's support for a specific + * \brief Query the implementation's support for a specific * attribute. * \param[in] device The device to query. * \param[in] feature The feature for which support is to be @@ -2993,7 +3243,7 @@ typedef VdpStatus VdpVideoMixerQueryAttributeSupport( ); /** - * \brief Query the implementation's supported for a specific + * \brief Query the implementation's supported for a specific * parameter. * \param[in] device The device to query. * \param[in] parameter The parameter for which support is to be @@ -3011,7 +3261,7 @@ typedef VdpStatus VdpVideoMixerQueryParameterValueRange( ); /** - * \brief Query the implementation's supported for a specific + * \brief Query the implementation's supported for a specific * attribute. * \param[in] device The device to query. * \param[in] attribute The attribute for which support is to be @@ -3035,22 +3285,22 @@ typedef uint32_t VdpVideoMixer; /** * \brief Create a VdpVideoMixer. - * \param[in] device The device that will contain the mixer. + * \param[in] device The device that will contain the mixer. * \param[in] feature_count The number of features to request. * \param[in] features The list of features to request. * \param[in] parameter_count The number of parameters to set. * \param[in] parameters The list of parameters to set. * \param[in] parameter_values The values for the parameters. Note that each * entry in the value array is a pointer to the actual value. In other - * words, the values themselves are not cast to "void *" and passed + * words, the values themselves are not cast to "void *" and passed * "inside" the array. * \param[out] mixer The new mixer's handle. - * \return VdpStatus The completion status of the operation. - * - * Initially, all requested features will be disabled. They can - * be enabled using \ref VdpVideoMixerSetFeatureEnables. - * - * Initially, all attributes will have default values. Values + * \return VdpStatus The completion status of the operation. + * + * Initially, all requested features will be disabled. They can + * be enabled using \ref VdpVideoMixerSetFeatureEnables. + * + * Initially, all attributes will have default values. Values * can be changed using \ref VdpVideoMixerSetAttributeValues. */ typedef VdpStatus VdpVideoMixerCreate( @@ -3069,10 +3319,10 @@ typedef VdpStatus VdpVideoMixerCreate( /** * \brief Enable or disable features. * \param[in] mixer The mixer to manipulate. - * \param[in] feature_count The number of features to + * \param[in] feature_count The number of features to * enable/disable. * \param[in] features The list of features to enable/disable. - * \param[in] feature_enables The list of new feature enable + * \param[in] feature_enables The list of new feature enable * values. * \return VdpStatus The completion status of the operation. */ @@ -3090,7 +3340,7 @@ typedef VdpStatus VdpVideoMixerSetFeatureEnables( * \param[in] attributes The list of attributes to set. * \param[in] attribute_values The values for the attributes. Note that each * entry in the value array is a pointer to the actual value. In other - * words, the values themselves are not cast to "void *" and passed + * words, the values themselves are not cast to "void *" and passed * "inside" the array. A NULL pointer requests that the default value be * set for that attribute. * \return VdpStatus The completion status of the operation. @@ -3103,12 +3353,12 @@ typedef VdpStatus VdpVideoMixerSetAttributeValues( ); /** - * \brief Retrieve whether features were requested at creation + * \brief Retrieve whether features were requested at creation * time. * \param[in] mixer The mixer to query. * \param[in] feature_count The number of features to query. * \param[in] features The list of features to query. - * \param[out] feature_supported A list of values indicating + * \param[out] feature_supported A list of values indicating * whether the feature was requested, and hence is * available. * \return VdpStatus The completion status of the operation. @@ -3126,7 +3376,7 @@ typedef VdpStatus VdpVideoMixerGetFeatureSupport( * \param[in] mixer The mixer to manipulate. * \param[in] feature_count The number of features to query. * \param[in] features The list of features to query. - * \param[out] feature_enabled A list of values indicating + * \param[out] feature_enabled A list of values indicating * whether the feature is enabled. * \return VdpStatus The completion status of the operation. */ @@ -3143,7 +3393,7 @@ typedef VdpStatus VdpVideoMixerGetFeatureEnables( * \param[in] mixer The mixer to manipulate. * \param[in] parameter_count The number of parameters to query. * \param[in] parameters The list of parameters to query. - * \param[out] parameter_values The list of current values for + * \param[out] parameter_values The list of current values for * the parameters. Note that each entry in the value array is a pointer to * storage that will receive the actual value. If the attribute's type is * a pointer itself, please closely read the documentation for that @@ -3163,7 +3413,7 @@ typedef VdpStatus VdpVideoMixerGetParameterValues( * \param[in] mixer The mixer to manipulate. * \param[in] attribute_count The number of attributes to query. * \param[in] attributes The list of attributes to query. - * \param[out] attribute_values The list of current values for + * \param[out] attribute_values The list of current values for * the attributes. Note that each entry in the value array is a pointer to * storage that will receive the actual value. If the attribute's type is * a pointer itself, please closely read the documentation for that @@ -3187,62 +3437,62 @@ typedef VdpStatus VdpVideoMixerDestroy( VdpVideoMixer mixer ); -/** - * \hideinitializer +/** + * \hideinitializer * \brief The structure of the picture present in a \ref * VdpVideoSurface "VdpVideoSurface". - */ + */ typedef enum { - /** - * The picture is a field, and is the top field of the surface. - */ + /** + * The picture is a field, and is the top field of the surface. + */ VDP_VIDEO_MIXER_PICTURE_STRUCTURE_TOP_FIELD, - /** + /** * The picture is a field, and is the bottom field of the * surface. */ VDP_VIDEO_MIXER_PICTURE_STRUCTURE_BOTTOM_FIELD, - /** - * The picture is a frame, and hence is the entire surface. - */ + /** + * The picture is a frame, and hence is the entire surface. + */ VDP_VIDEO_MIXER_PICTURE_STRUCTURE_FRAME, } VdpVideoMixerPictureStructure; #define VDP_LAYER_VERSION 0 -/** - * \brief Definition of an additional \ref VdpOutputSurface +/** + * \brief Definition of an additional \ref VdpOutputSurface * "VdpOutputSurface" layer in the composting model. - */ + */ typedef struct { /** * This field must be filled with VDP_LAYER_VERSION */ uint32_t struct_version; - /** - * The surface to composite from. - */ + /** + * The surface to composite from. + */ VdpOutputSurface source_surface; - /** - * The sub-rectangle of the source surface to use. If NULL, the - * entire source surface will be used. - */ + /** + * The sub-rectangle of the source surface to use. If NULL, the + * entire source surface will be used. + */ VdpRect const * source_rect; - /** - * The sub-rectangle of the destination surface to map - * this layer into. This rectangle is relative to the entire - * destination surface. This rectangle will be clipped by \ref - * VdpVideoMixerRender's \b destination_rect. If NULL, the - * destination rectangle will be sized to match the source - * rectangle, and will be located at the origin. - */ + /** + * The sub-rectangle of the destination surface to map + * this layer into. This rectangle is relative to the entire + * destination surface. This rectangle will be clipped by \ref + * VdpVideoMixerRender's \b destination_rect. If NULL, the + * destination rectangle will be sized to match the source + * rectangle, and will be located at the origin. + */ VdpRect const * destination_rect; } VdpLayer; /** - * \brief Perform a video post-processing and compositing + * \brief Perform a video post-processing and compositing * operation. - * \param[in] mixer The mixer object that will perform the + * \param[in] mixer The mixer object that will perform the * mixing/rendering operation. * \param[in] background_surface A background image. If set to any value other * than VDP_INVALID_HANDLE, the specific surface will be used instead of @@ -3253,7 +3503,7 @@ typedef struct { * be used as the background layer. The specified region will be * extracted and scaled to match the size of destination_rect. If NULL, * the entire background_surface will be used. - * \param[in] current_picture_structure The picture structure of + * \param[in] current_picture_structure The picture structure of * the field/frame to be processed. This field/frame is * presented in the \b video_surface_current parameter. If * frame, then all \b video_surface_* parameters are @@ -3261,7 +3511,7 @@ typedef struct { * video_surface_* parameters are assumed to be fields, * with alternating top/bottom-ness derived from * video_surface_current. - * \param[in] video_surfaces_past_count The number of provided + * \param[in] video_surfaces_past_count The number of provided * fields/frames prior to the current picture. * \param[in] video_surfaces_past The fields/frames prior to the * current field/frame. Note that array index 0 is the @@ -3269,24 +3519,24 @@ typedef struct { * field/frame, with increasing array indices used for * older frames. Unavailable entries may be set to * \ref VDP_INVALID_HANDLE. - * \param[in] video_surface_current The field/frame to be + * \param[in] video_surface_current The field/frame to be * processed. * \param[in] video_surfaces_future_count The number of provided * fields/frames following the current picture. - * \param[in] video_surfaces_future The fields/frames that + * \param[in] video_surfaces_future The fields/frames that * follow the current field/frame. Note that array index 0 * is the field/frame temporally nearest to the current * field/frame, with increasing array indices used for * newer frames. Unavailable entries may be set to \ref * VDP_INVALID_HANDLE. - * \param[in] video_source_rect The sub-rectangle of the source + * \param[in] video_source_rect The sub-rectangle of the source * video surface to extract and process. If NULL, the * entire surface will be used. * \param[in] destination_surface - * \param[in] destination_rect The sub-rectangle of the + * \param[in] destination_rect The sub-rectangle of the * destination surface to modify. Note that rectangle clips * all other actions. - * \param[in] destination_video_rect The sub-rectangle of the + * \param[in] destination_video_rect The sub-rectangle of the * destination surface that will contain the processed * video. This rectangle is relative to the entire * destination surface. This rectangle is clipped by \b @@ -3297,10 +3547,10 @@ typedef struct { * composite above the video. * \param[in] layers The array of additional layers to composite * above the video. - * \return VdpStatus The completion status of the operation. - * - * For a complete discussion of how to use this API, please see - * \ref video_mixer_usage. + * \return VdpStatus The completion status of the operation. + * + * For a complete discussion of how to use this API, please see + * \ref video_mixer_usage. */ typedef VdpStatus VdpVideoMixerRender( VdpVideoMixer mixer, @@ -3331,42 +3581,42 @@ typedef VdpStatus VdpVideoMixerRender( * the associated timestamp is reached, the surface is displayed * to the user. This timestamp-based approach yields high * quality video delivery. - * - * The exact location of the displayed content is Window System - * specific. For this reason, the \ref api_winsys provides an - * API to create a \ref VdpPresentationQueueTarget object (e.g. - * via \ref VdpPresentationQueueTargetCreateX11) which - * encapsulates this information. - * - * Note that the presentation queue performs no scaling of - * surfaces to match the display target's size, aspect ratio, - * etc. - * - * Surfaces that are too large to fit into the display target - * will be clipped. Surfaces that are too small to fill the - * display target will be aligned to the top-left corner of the - * display target, with the balance of the display target being + * + * The exact location of the displayed content is Window System + * specific. For this reason, the \ref api_winsys provides an + * API to create a \ref VdpPresentationQueueTarget object (e.g. + * via \ref VdpPresentationQueueTargetCreateX11) which + * encapsulates this information. + * + * Note that the presentation queue performs no scaling of + * surfaces to match the display target's size, aspect ratio, + * etc. + * + * Surfaces that are too large to fit into the display target + * will be clipped. Surfaces that are too small to fill the + * display target will be aligned to the top-left corner of the + * display target, with the balance of the display target being * filled with a constant configurable "background" color. - * - * Note that the presentation queue operates in a manner that is - * semantically equivalent to an overlay surface, with any - * required color key painting hidden internally. However, - * implementations are free to use whatever semantically + * + * Note that the presentation queue operates in a manner that is + * semantically equivalent to an overlay surface, with any + * required color key painting hidden internally. However, + * implementations are free to use whatever semantically * equivalent technique they wish. Note that implementations * that actually use color-keyed overlays will typically use * the "background" color as the overlay color key value, so * this color should be chosen with care. - * - * @{ + * + * @{ */ -/** +/** * \brief The representation of a point in time. - * + * * VdpTime timestamps are intended to be a high-precision timing * system, potentially independent from any other time domain in * the system. - * + * * Time is represented in units of nanoseconds. The origin * (i.e. the time represented by a value of 0) is implementation * dependent. @@ -3374,12 +3624,12 @@ typedef VdpStatus VdpVideoMixerRender( typedef uint64_t VdpTime; /** - * \brief An opaque handle representing the location where + * \brief An opaque handle representing the location where * video will be presented. - * + * * VdpPresentationQueueTarget are created using a \ref api_winsys - * specific API, such as \ref - * VdpPresentationQueueTargetCreateX11. + * specific API, such as \ref + * VdpPresentationQueueTargetCreateX11. */ typedef uint32_t VdpPresentationQueueTarget; @@ -3393,18 +3643,18 @@ typedef VdpStatus VdpPresentationQueueTargetDestroy( ); /** - * \brief An opaque handle representing a presentation queue + * \brief An opaque handle representing a presentation queue * object. */ typedef uint32_t VdpPresentationQueue; /** * \brief Create a VdpPresentationQueue. - * \param[in] device The device that will contain the queue. - * \param[in] presentation_queue_target The location to display + * \param[in] device The device that will contain the queue. + * \param[in] presentation_queue_target The location to display * the content. * \param[out] presentation_queue The new queue's handle. - * \return VdpStatus The completion status of the operation. + * \return VdpStatus The completion status of the operation. * * Note: The initial value for the background color will be set to * an implementation-defined value. @@ -3427,9 +3677,9 @@ typedef VdpStatus VdpPresentationQueueDestroy( /** * \brief Configure the background color setting. - * \param[in] presentation_queue The queue to manipulate. - * \param[in] background_color The new background color. - * + * \param[in] presentation_queue The queue to manipulate. + * \param[in] background_color The new background color. + * * Note: Implementations may choose whether to apply the * new background color value immediately, or defer it until * the next surface is presented. @@ -3441,7 +3691,7 @@ typedef VdpStatus VdpPresentationQueueSetBackgroundColor( /** * \brief Retrieve the current background color setting. - * \param[in] presentation_queue The queue to query. + * \param[in] presentation_queue The queue to query. * \param[out] background_color The current background color. */ typedef VdpStatus VdpPresentationQueueGetBackgroundColor( @@ -3450,11 +3700,11 @@ typedef VdpStatus VdpPresentationQueueGetBackgroundColor( ); /** - * \brief Retrieve the presentation queue's "current" time. - * \param[in] presentation_queue The queue to query. - * \param[out] current_time The current time, which may + * \brief Retrieve the presentation queue's "current" time. + * \param[in] presentation_queue The queue to query. + * \param[out] current_time The current time, which may * represent a point between display VSYNC events. - * \return VdpStatus The completion status of the operation. + * \return VdpStatus The completion status of the operation. */ typedef VdpStatus VdpPresentationQueueGetTime( VdpPresentationQueue presentation_queue, @@ -3472,11 +3722,11 @@ typedef VdpStatus VdpPresentationQueueGetTime( * \param[in] clip_height If set to a non-zero value, the presentation queue * will display only clip_height lines of the surface (anchored to the * top-left corner of the surface. - * \param[in] earliest_presentation_time The timestamp + * \param[in] earliest_presentation_time The timestamp * associated with the surface. The presentation queue * will not display the surface until the presentation * queue's current time is at least this value. - * \return VdpStatus The completion status of the operation. + * \return VdpStatus The completion status of the operation. * * Applications may choose to allow resizing of the presentation queue target * (which may be e.g. a regular Window when using an X11-based @@ -3493,7 +3743,7 @@ typedef VdpStatus VdpPresentationQueueGetTime( * Using this technique, an application's response to window resizing may * simply be to render to, and display, a different region of the surface, * rather than de-/re-allocation of surfaces to match the updated window size. - */ + */ typedef VdpStatus VdpPresentationQueueDisplay( VdpPresentationQueue presentation_queue, VdpOutputSurface surface, @@ -3505,15 +3755,15 @@ typedef VdpStatus VdpPresentationQueueDisplay( /** * \brief Wait for a surface to finish being displayed. * \param[in] presentation_queue The queue to query. - * \param[in] surface The surface to wait for. - * \param[out] first_presentation_time The timestamp of the + * \param[in] surface The surface to wait for. + * \param[out] first_presentation_time The timestamp of the * VSYNC at which this surface was first displayed. Note * that 0 means the surface was never displayed. - * \return VdpStatus The completion status of the operation. - * - * Note that this API will block indefinitely if queried about - * the surface most recently added to a presentation queue, - * since there is no other surface that could possibly replace + * \return VdpStatus The completion status of the operation. + * + * Note that this API will block indefinitely if queried about + * the surface most recently added to a presentation queue, + * since there is no other surface that could possibly replace * the queried surface. */ typedef VdpStatus VdpPresentationQueueBlockUntilSurfaceIdle( @@ -3523,8 +3773,8 @@ typedef VdpStatus VdpPresentationQueueBlockUntilSurfaceIdle( VdpTime * first_presentation_time ); -/** - * \hideinitializer +/** + * \hideinitializer * \brief The status of a surface within a presentation queue. */ typedef enum { @@ -3539,13 +3789,13 @@ typedef enum { /** * \brief Poll the current queue status of a surface. * \param[in] presentation_queue The queue to query. - * \param[in] surface The surface to query. - * \param[out] status The current status of the surface within + * \param[in] surface The surface to query. + * \param[out] status The current status of the surface within * the queue. - * \param[out] first_presentation_time The timestamp of the + * \param[out] first_presentation_time The timestamp of the * VSYNC at which this surface was first displayed. Note * that 0 means the surface was never displayed. - * \return VdpStatus The completion status of the operation. + * \return VdpStatus The completion status of the operation. */ typedef VdpStatus VdpPresentationQueueQuerySurfaceStatus( VdpPresentationQueue presentation_queue, @@ -3558,56 +3808,56 @@ typedef VdpStatus VdpPresentationQueueQuerySurfaceStatus( /*@}*/ /** - * \defgroup display_preemption Display Preemption - * - * The Window System may operate within a frame-work (such as - * Linux's VT switching) where the display is shared between the - * Window System (e.g. X) and some other output mechanism (e.g. - * the VT.) Given this scenario, the Window System's control of - * the display could be preempted, and restored, at any time. - * - * VDPAU does not mandate that implementations hide such - * preemptions from VDPAU client applications; doing so may - * impose extreme burdens upon VDPAU implementations. Equally, - * however, implementations are free to hide such preemptions - * from client applications. - * + * \defgroup display_preemption Display Preemption + * + * The Window System may operate within a frame-work (such as + * Linux's VT switching) where the display is shared between the + * Window System (e.g. X) and some other output mechanism (e.g. + * the VT.) Given this scenario, the Window System's control of + * the display could be preempted, and restored, at any time. + * + * VDPAU does not mandate that implementations hide such + * preemptions from VDPAU client applications; doing so may + * impose extreme burdens upon VDPAU implementations. Equally, + * however, implementations are free to hide such preemptions + * from client applications. + * * VDPAU allows implementations to inform the client application - * when such a preemption has occurred, and then refuse to - * continue further operation. - * + * when such a preemption has occurred, and then refuse to + * continue further operation. + * * Similarly, some form of fatal hardware error could prevent further * operation of the VDPAU implementation, without a complete * re-initialization. * - * The following discusses the behavior of implementations that - * choose not to hide preemption from client applications. - * - * When preemption occurs, VDPAU internally destroys all - * objects; the client application need not do this. However, if - * the client application wishes to continue operation, it must - * recreate all objects that it uses. It is probable that this - * recreation will not succeed until the display ownership is - * restored to the Window System. - * - * Once preemption has occurred, all VDPAU entry points will - * return the specific error code \ref - * VDP_STATUS_DISPLAY_PREEMPTED. - * - * VDPAU client applications may also be notified of such - * preemptions and fatal errors via a callback. See \ref - * VdpPreemptionCallbackRegister for more details. - * + * The following discusses the behavior of implementations that + * choose not to hide preemption from client applications. + * + * When preemption occurs, VDPAU internally destroys all + * objects; the client application need not do this. However, if + * the client application wishes to continue operation, it must + * recreate all objects that it uses. It is probable that this + * recreation will not succeed until the display ownership is + * restored to the Window System. + * + * Once preemption has occurred, all VDPAU entry points will + * return the specific error code \ref + * VDP_STATUS_DISPLAY_PREEMPTED. + * + * VDPAU client applications may also be notified of such + * preemptions and fatal errors via a callback. See \ref + * VdpPreemptionCallbackRegister for more details. + * * @{ */ /** - * \brief A callback to notify the client application that a + * \brief A callback to notify the client application that a * device's display has been preempted. * \param[in] device The device that had its display preempted. - * \param[in] context The client-supplied callback context + * \param[in] context The client-supplied callback context * information. - * \return void No return value + * \return void No return value */ typedef void VdpPreemptionCallback( VdpDevice device, @@ -3616,13 +3866,13 @@ typedef void VdpPreemptionCallback( /** * \brief Configure the display preemption callback. - * \param[in] device The device to be monitored for preemption. - * \param[in] callback The client application's callback + * \param[in] device The device to be monitored for preemption. + * \param[in] callback The client application's callback * function. If NULL, the callback is unregistered. - * \param[in] context The client-supplied callback context + * \param[in] context The client-supplied callback context * information. This information will be passed to the * callback function if/when invoked. - * \return VdpStatus The completion status of the operation. + * \return VdpStatus The completion status of the operation. */ typedef VdpStatus VdpPreemptionCallbackRegister( VdpDevice device, @@ -3634,19 +3884,19 @@ typedef VdpStatus VdpPreemptionCallbackRegister( /** * \defgroup get_proc_address Entry Point Retrieval - * + * * In order to facilitate multiple implementations of VDPAU * co-existing within a single process, all functionality is * available via function pointers. The mechanism to retrieve * those function pointers is described below. - * - * @{ + * + * @{ */ -/** - * \brief A type suitable for \ref VdpGetProcAddress +/** + * \brief A type suitable for \ref VdpGetProcAddress * "VdpGetProcAddress"'s \b function_id parameter. - */ + */ typedef uint32_t VdpFuncId; /** \hideinitializer */ @@ -3774,14 +4024,14 @@ typedef uint32_t VdpFuncId; #define VDP_FUNC_ID_BASE_WINSYS 0x1000 -/** +/** * \brief Retrieve a VDPAU function pointer. * \param[in] device The device that the function will operate * against. - * \param[in] function_id The specific function to retrieve. + * \param[in] function_id The specific function to retrieve. * \param[out] function_pointer The actual pointer for the * application to call. - * \return VdpStatus The completion status of the operation. + * \return VdpStatus The completion status of the operation. */ typedef VdpStatus VdpGetProcAddress( VdpDevice device, diff --git a/doc/vdpau_x11.h b/doc/vdpau_x11.h index d56ae1c..e8445f1 100755 --- a/doc/vdpau_x11.h +++ b/doc/vdpau_x11.h @@ -7,7 +7,7 @@ * This copyright notice applies to this header file: * * Copyright (c) 2008 NVIDIA Corporation - * + * * Permission is hereby granted, free of charge, to any person * obtaining a copy of this software and associated documentation * files (the "Software"), to deal in the Software without @@ -33,11 +33,11 @@ /** * \file vdpau_x11.h * \brief X11 Window System Integration Layer - * - * This file contains the \ref api_winsys_x11 "X11 Window System - * Integration Layer". - */ - + * + * This file contains the \ref api_winsys_x11 "X11 Window System + * Integration Layer". + */ + #ifndef _VDPAU_X11_H #define _VDPAU_X11_H @@ -49,74 +49,74 @@ extern "C" { #endif /** - * \ingroup api_winsys - * @{ + * \ingroup api_winsys + * @{ */ /** * \defgroup api_winsys_x11 X11 Window System Integration Layer - * - * The set of VDPAU functionality specific to usage with the X + * + * The set of VDPAU functionality specific to usage with the X * Window System. - * - * \section Driver Library Layout - * - * An X11-oriented VDPAU installation consists of the following - * components: - * - * - Header files. These files are located in the standard + * + * \section Driver Library Layout + * + * An X11-oriented VDPAU installation consists of the following + * components: + * + * - Header files. These files are located in the standard * system header file path. * - \c vdpau/vdpau.h * - \c vdpau/vdpau_x11.h - * - The VDPAU wrapper library. These files are located in the + * - The VDPAU wrapper library. These files are located in the * standard system (possibly X11-specific) library path. * - \c libvdpau.so.1 (runtime) * - \c libvdpau.so (development) - * - Back-end driver files. These files are located in the + * - Back-end driver files. These files are located in the * standard system (possibly X11-specific) library path. * - \c libvdpau_\%s.so * For example: * - \c libvdpau_nvidia.so * - \c libvdpau_intel.so * - \c libvdpau_ati.so - * - * The VDPAU wrapper library implements just one function; \ref - * vdp_device_create_x11. The wrapper will implement this function - * by dynamically loading the appropriate back-end driver file + * + * The VDPAU wrapper library implements just one function; \ref + * vdp_device_create_x11. The wrapper will implement this function + * by dynamically loading the appropriate back-end driver file * mentioned above. Long-term, the wrapper will use a * VDPAU-specific X extension to determine which back-end driver * to load. Currently, the wrapper library hard-codes the driver - * name as "nvidia", although this can be overridden using the + * name as "nvidia", although this can be overridden using the * environment variable VDPAU_DRIVER. * - * The back-end driver is expected to implement a function named + * The back-end driver is expected to implement a function named * \b vdp_imp_device_create_x11. The wrapper will call this function to - * actually implement the \ref vdp_device_create_x11 application call. - * - * Note that it is theoretically possible for an application to - * create multiple \ref VdpDevice "VdpDevice" objects. In this - * case, the wrapper library may load multiple back-end drivers - * into the same application, and/or invoke a specific back-end - * driver's \b VdpImpDeviceCreateX11 multiple times. The wrapper - * libray imposes no policy regarding whether the application + * actually implement the \ref vdp_device_create_x11 application call. + * + * Note that it is theoretically possible for an application to + * create multiple \ref VdpDevice "VdpDevice" objects. In this + * case, the wrapper library may load multiple back-end drivers + * into the same application, and/or invoke a specific back-end + * driver's \b VdpImpDeviceCreateX11 multiple times. The wrapper + * libray imposes no policy regarding whether the application * may instantiate multiple \ref VdpDevice "VdpDevice" objects for - * the same display and/or screen. However, back-end drivers are - * free to limit the number of \ref VdpDevice "VdpDevice" objects - * as required by their implementation. - * - * @{ + * the same display and/or screen. However, back-end drivers are + * free to limit the number of \ref VdpDevice "VdpDevice" objects + * as required by their implementation. + * + * @{ */ -/** - * \brief Create a VdpDevice object for use with X11. +/** + * \brief Create a VdpDevice object for use with X11. * \param[in] display The X Display that the VdpDevice VdpDevice * will operate against. - * \param[in] screen The X screen that the VdpDevice will operate + * \param[in] screen The X screen that the VdpDevice will operate * against. - * \param[out] device The new device's handle. - * \param[out] get_proc_address The get_proc_address entry point + * \param[out] device The new device's handle. + * \param[out] get_proc_address The get_proc_address entry point * to use with this device. - * \return VdpStatus The completion status of the operation. + * \return VdpStatus The completion status of the operation. */ typedef VdpStatus VdpDeviceCreateX11( Display * display, @@ -126,21 +126,21 @@ typedef VdpStatus VdpDeviceCreateX11( VdpGetProcAddress * * get_proc_address ); -/** - * \brief Create a VdpDevice object for use with X11. +/** + * \brief Create a VdpDevice object for use with X11. * This is an actual symbol of type \ref VdpDeviceCreateX11 - * + * */ VdpDeviceCreateX11 vdp_device_create_x11; -/** +/** * \brief Create a VdpPresentationQueueTarget for use with X11. - * \param[in] device The device that will contain the queue + * \param[in] device The device that will contain the queue * target. - * \param[in] drawable The X11 Drawable that the presentation + * \param[in] drawable The X11 Drawable that the presentation * queue will present into. - * \param[out] target The new queue target's handle. - * \return VdpStatus The completion status of the operation. + * \param[out] target The new queue target's handle. + * \return VdpStatus The completion status of the operation. * * Note: VDPAU expects to own the entire drawable for the duration of time * that the presentation queue target exists. In particular, diff --git a/lib/compat/Makefile b/lib/compat/Makefile index 5101c5a..7b0a111 100644 --- a/lib/compat/Makefile +++ b/lib/compat/Makefile @@ -3,6 +3,7 @@ SUBDIR= libGL \ libGLcore \ libvdpau \ libvdpau_trace \ - libvdpau_nvidia + libvdpau_nvidia \ + libcuda .include diff --git a/lib/compat/libGL/Makefile b/lib/compat/libGL/Makefile index c8be9ae..20ff647 100644 --- a/lib/compat/libGL/Makefile +++ b/lib/compat/libGL/Makefile @@ -1,7 +1,7 @@ NVIDIA_ROOT= ${.CURDIR}/../../.. LIB= GL -SHLIB_VERSION= 180.29 +SHLIB_VERSION= 185.18.36 SHLIB_NAME= lib${LIB}.so.${SHLIB_VERSION} SHLIB_LINK= lib${LIB}.so.1 LIBDIR= /compat/linux/usr/lib diff --git a/lib/compat/libGLcore/Makefile b/lib/compat/libGLcore/Makefile index 1e19888..a30dcb4 100644 --- a/lib/compat/libGLcore/Makefile +++ b/lib/compat/libGLcore/Makefile @@ -1,7 +1,7 @@ NVIDIA_ROOT= ${.CURDIR}/../../.. LIB= GLcore -SHLIB_VERSION= 180.29 +SHLIB_VERSION= 185.18.36 SHLIB_NAME= lib${LIB}.so.${SHLIB_VERSION} SHLIB_LINK= lib${LIB}.so.1 LIBDIR= /compat/linux/usr/lib diff --git a/lib/compat/libGLcore/Makefile b/lib/compat/libcuda/Makefile similarity index 84% copy from lib/compat/libGLcore/Makefile copy to lib/compat/libcuda/Makefile index 1e19888..b173481 100644 --- a/lib/compat/libGLcore/Makefile +++ b/lib/compat/libcuda/Makefile @@ -1,7 +1,7 @@ NVIDIA_ROOT= ${.CURDIR}/../../.. -LIB= GLcore -SHLIB_VERSION= 180.29 +LIB= cuda +SHLIB_VERSION= 185.18.36 SHLIB_NAME= lib${LIB}.so.${SHLIB_VERSION} SHLIB_LINK= lib${LIB}.so.1 LIBDIR= /compat/linux/usr/lib diff --git a/lib/compat/libnvidia-tls/Makefile b/lib/compat/libnvidia-tls/Makefile index 0ba9ca0..3a51eb9 100644 --- a/lib/compat/libnvidia-tls/Makefile +++ b/lib/compat/libnvidia-tls/Makefile @@ -1,10 +1,16 @@ NVIDIA_ROOT= ${.CURDIR}/../../.. LIB= nvidia-tls -SHLIB_VERSION= 180.29 +SHLIB_VERSION= 185.18.36 SHLIB_NAME= lib${LIB}.so.${SHLIB_VERSION} SHLIB_LINK= lib${LIB}.so.1 LIBDIR= /compat/linux/usr/lib -OBJDIR= obj/linux +OBJDIR!= if [ -x ${NVIDIA_ROOT}/obj/linux/tls/tls_test ] && \ + ${NVIDIA_ROOT}/obj/linux/tls/tls_test \ + ${NVIDIA_ROOT}/obj/linux/tls/tls_test_dso.so ; then \ + echo obj/linux/tls ; \ + else \ + echo obj/linux ; \ + fi .include <${NVIDIA_ROOT}/mk/nvidia.lib.mk> diff --git a/lib/compat/libvdpau/Makefile b/lib/compat/libvdpau/Makefile index 09139e6..84c6809 100644 --- a/lib/compat/libvdpau/Makefile +++ b/lib/compat/libvdpau/Makefile @@ -1,7 +1,7 @@ NVIDIA_ROOT= ${.CURDIR}/../../.. LIB= vdpau -SHLIB_VERSION= 180.29 +SHLIB_VERSION= 185.18.36 SHLIB_NAME= lib${LIB}.so.${SHLIB_VERSION} SHLIB_LINK= lib${LIB}.so.1 LIBDIR= /compat/linux/usr/lib diff --git a/lib/compat/libvdpau_nvidia/Makefile b/lib/compat/libvdpau_nvidia/Makefile index 40c1bb3..ffb3805 100644 --- a/lib/compat/libvdpau_nvidia/Makefile +++ b/lib/compat/libvdpau_nvidia/Makefile @@ -1,7 +1,7 @@ NVIDIA_ROOT= ${.CURDIR}/../../.. LIB= vdpau_nvidia -SHLIB_VERSION= 180.29 +SHLIB_VERSION= 185.18.36 SHLIB_NAME= lib${LIB}.so.${SHLIB_VERSION} SHLIB_LINK= lib${LIB}.so LIBDIR= /compat/linux/usr/lib diff --git a/lib/compat/libvdpau_trace/Makefile b/lib/compat/libvdpau_trace/Makefile index 189319b..3e0f901 100644 --- a/lib/compat/libvdpau_trace/Makefile +++ b/lib/compat/libvdpau_trace/Makefile @@ -1,7 +1,7 @@ NVIDIA_ROOT= ${.CURDIR}/../../.. LIB= vdpau_trace -SHLIB_VERSION= 180.29 +SHLIB_VERSION= 185.18.36 SHLIB_NAME= lib${LIB}.so.${SHLIB_VERSION} SHLIB_LINK= lib${LIB}.so LIBDIR= /compat/linux/usr/lib diff --git a/obj/libGL.so.1 b/obj/libGL.so.1 index 4e42ecf..1c9c0a5 100644 Binary files a/obj/libGL.so.1 and b/obj/libGL.so.1 differ diff --git a/obj/libGLcore.so.1 b/obj/libGLcore.so.1 index 6cd08cf..a1249c0 100755 Binary files a/obj/libGLcore.so.1 and b/obj/libGLcore.so.1 differ diff --git a/obj/libXvMCNVIDIA.a b/obj/libXvMCNVIDIA.a index 945400c..eb29a04 100755 Binary files a/obj/libXvMCNVIDIA.a and b/obj/libXvMCNVIDIA.a differ diff --git a/obj/libXvMCNVIDIA.so.1 b/obj/libXvMCNVIDIA.so.1 index 966f625..ca5e7ee 100755 Binary files a/obj/libXvMCNVIDIA.so.1 and b/obj/libXvMCNVIDIA.so.1 differ diff --git a/obj/libglx.so.1 b/obj/libglx.so.1 index 3edaf5c..f36ee14 100644 Binary files a/obj/libglx.so.1 and b/obj/libglx.so.1 differ diff --git a/obj/libnvidia-cfg.so.1 b/obj/libnvidia-cfg.so.1 index 350ab6e..a95cd1e 100644 Binary files a/obj/libnvidia-cfg.so.1 and b/obj/libnvidia-cfg.so.1 differ diff --git a/obj/libnvidia-tls.so.1 b/obj/libnvidia-tls.so.1 index c1fdb0c..846f9c0 100644 Binary files a/obj/libnvidia-tls.so.1 and b/obj/libnvidia-tls.so.1 differ diff --git a/obj/libvdpau.so.1 b/obj/libvdpau.so.1 index dbf0cbc..d01be3f 100755 Binary files a/obj/libvdpau.so.1 and b/obj/libvdpau.so.1 differ diff --git a/obj/libvdpau_nvidia.so.1 b/obj/libvdpau_nvidia.so.1 index 3837a13..c30bddc 100755 Binary files a/obj/libvdpau_nvidia.so.1 and b/obj/libvdpau_nvidia.so.1 differ diff --git a/obj/libvdpau_trace.so.1 b/obj/libvdpau_trace.so.1 index da0e6bc..077013c 100755 Binary files a/obj/libvdpau_trace.so.1 and b/obj/libvdpau_trace.so.1 differ diff --git a/obj/linux/libGL.so.180.29 b/obj/linux/libGL.so.180.29 deleted file mode 100755 index 1e73f46..0000000 Binary files a/obj/linux/libGL.so.180.29 and /dev/null differ diff --git a/obj/linux/libGL.so.185.18.36 b/obj/linux/libGL.so.185.18.36 new file mode 100755 index 0000000..6255a44 Binary files /dev/null and b/obj/linux/libGL.so.185.18.36 differ diff --git a/obj/linux/libGLcore.so.180.29 b/obj/linux/libGLcore.so.185.18.36 similarity index 63% rename from obj/linux/libGLcore.so.180.29 rename to obj/linux/libGLcore.so.185.18.36 index 5e3866d..4e01de8 100755 Binary files a/obj/linux/libGLcore.so.180.29 and b/obj/linux/libGLcore.so.185.18.36 differ diff --git a/obj/linux/libcuda.so.180.29 b/obj/linux/libcuda.so.180.29 deleted file mode 100755 index 80d78b1..0000000 Binary files a/obj/linux/libcuda.so.180.29 and /dev/null differ diff --git a/obj/linux/libcuda.so.185.18.36 b/obj/linux/libcuda.so.185.18.36 new file mode 100755 index 0000000..332e6f9 Binary files /dev/null and b/obj/linux/libcuda.so.185.18.36 differ diff --git a/obj/linux/libnvidia-cfg.so.180.29 b/obj/linux/libnvidia-cfg.so.180.29 deleted file mode 100755 index 635ba22..0000000 Binary files a/obj/linux/libnvidia-cfg.so.180.29 and /dev/null differ diff --git a/obj/linux/libnvidia-cfg.so.185.18.36 b/obj/linux/libnvidia-cfg.so.185.18.36 new file mode 100755 index 0000000..71ade1e Binary files /dev/null and b/obj/linux/libnvidia-cfg.so.185.18.36 differ diff --git a/obj/linux/libnvidia-tls.so.180.29 b/obj/linux/libnvidia-tls.so.180.29 deleted file mode 100755 index 73bd51d..0000000 Binary files a/obj/linux/libnvidia-tls.so.180.29 and /dev/null differ diff --git a/obj/linux/libnvidia-tls.so.185.18.36 b/obj/linux/libnvidia-tls.so.185.18.36 new file mode 100755 index 0000000..2105ff6 Binary files /dev/null and b/obj/linux/libnvidia-tls.so.185.18.36 differ diff --git a/obj/linux/libvdpau.so.180.29 b/obj/linux/libvdpau.so.180.29 deleted file mode 100755 index 6078718..0000000 Binary files a/obj/linux/libvdpau.so.180.29 and /dev/null differ diff --git a/obj/linux/libvdpau.so.185.18.36 b/obj/linux/libvdpau.so.185.18.36 new file mode 100755 index 0000000..c120f3e Binary files /dev/null and b/obj/linux/libvdpau.so.185.18.36 differ diff --git a/obj/linux/libvdpau_nvidia.so.180.29 b/obj/linux/libvdpau_nvidia.so.180.29 deleted file mode 100755 index f0e370b..0000000 Binary files a/obj/linux/libvdpau_nvidia.so.180.29 and /dev/null differ diff --git a/obj/linux/libvdpau_nvidia.so.185.18.36 b/obj/linux/libvdpau_nvidia.so.185.18.36 new file mode 100755 index 0000000..59d8bd8 Binary files /dev/null and b/obj/linux/libvdpau_nvidia.so.185.18.36 differ diff --git a/obj/linux/libvdpau_trace.so.180.29 b/obj/linux/libvdpau_trace.so.180.29 deleted file mode 100755 index 66a8a8e..0000000 Binary files a/obj/linux/libvdpau_trace.so.180.29 and /dev/null differ diff --git a/obj/linux/libvdpau_trace.so.185.18.36 b/obj/linux/libvdpau_trace.so.185.18.36 new file mode 100755 index 0000000..439cbfa Binary files /dev/null and b/obj/linux/libvdpau_trace.so.185.18.36 differ diff --git a/obj/linux/tls/libnvidia-tls.so.185.18.36 b/obj/linux/tls/libnvidia-tls.so.185.18.36 new file mode 100755 index 0000000..6b353b0 Binary files /dev/null and b/obj/linux/tls/libnvidia-tls.so.185.18.36 differ diff --git a/obj/linux/tls/tls_test b/obj/linux/tls/tls_test new file mode 100755 index 0000000..9622f7c Binary files /dev/null and b/obj/linux/tls/tls_test differ diff --git a/obj/linux/tls/tls_test_dso.so b/obj/linux/tls/tls_test_dso.so new file mode 100755 index 0000000..2418309 Binary files /dev/null and b/obj/linux/tls/tls_test_dso.so differ diff --git a/obj/nvidia-bug-report.sh b/obj/nvidia-bug-report.sh index c688198..caed47a 100755 --- a/obj/nvidia-bug-report.sh +++ b/obj/nvidia-bug-report.sh @@ -1,15 +1,24 @@ #!/bin/sh # NVIDIA Graphics Driver bug reporting shell script. This shell -# script will generate a log file named "nvidia-bug-report.log", which +# script will generate a log file named "nvidia-bug-report.log.gz", which # should be attached when emailing bug reports to NVIDIA. +PATH="/sbin:/usr/sbin:$PATH" +BASE_LOG_FILENAME="nvidia-bug-report.log" -LOG_FILENAME=nvidia-bug-report.log - - -PATH="/sbin:/usr/sbin:$PATH" +# check if gzip is present +GZIP_CMD=`which gzip 2> /dev/null | head -n 1` +if [ $? -eq 0 -a "$GZIP_CMD" ]; then + GZIP_CMD="gzip -c" + LOG_FILENAME="$BASE_LOG_FILENAME.gz" + OLD_LOG_FILENAME="$BASE_LOG_FILENAME.old.gz" +else + GZIP_CMD="cat" + LOG_FILENAME=$BASE_LOG_FILENAME + OLD_LOG_FILENAME="$BASE_LOG_FILENAME.old" +fi NVIDIA_BUG_REPORT_CHANGE="$Change: 1833133 $" @@ -20,18 +29,20 @@ NVIDIA_BUG_REPORT_VERSION=`echo $NVIDIA_BUG_REPORT_CHANGE | tr -c -d [:digit:]` # append() { - echo "____________________________________________" >> $LOG_FILENAME - echo "" >> $LOG_FILENAME - - if [ ! -f "$1" ]; then - echo "$1 does not exist" >> $LOG_FILENAME - elif [ ! -r "$1" ]; then - echo "$1 is not readable" >> $LOG_FILENAME - else - echo "$1" >> $LOG_FILENAME - cat "$1" >> $LOG_FILENAME - fi - echo "" >> $LOG_FILENAME + ( + echo "____________________________________________" + echo "" + + if [ ! -f "$1" ]; then + echo "$1 does not exist" + elif [ ! -r "$1" ]; then + echo "$1 is not readable" + else + echo "$1" + cat "$1" + fi + echo "" + ) | $GZIP_CMD >> $LOG_FILENAME } # @@ -40,13 +51,15 @@ append() { # append_silent() { - if [ -f "$1" -a -r "$1" ]; then - echo "____________________________________________" >> $LOG_FILENAME - echo "" >> $LOG_FILENAME - echo "$1" >> $LOG_FILENAME - cat "$1" >> $LOG_FILENAME - echo "" >> $LOG_FILENAME - fi + ( + if [ -f "$1" -a -r "$1" ]; then + echo "____________________________________________" + echo "" + echo "$1" + cat "$1" + echo "" + fi + ) | $GZIP_CMD >> $LOG_FILENAME } # @@ -66,20 +79,22 @@ append_glob() { # append_sysctl() { - echo "____________________________________________" >> $LOG_FILENAME - echo "" >> $LOG_FILENAME - - sysctl=`which sysctl 2> /dev/null | head -n 1` - if [ $? -eq 0 -a "$sysctl" ]; then - value=`$sysctl $1 2> /dev/null` - if [ $? -eq 0 -a "$value" ]; then - echo "$value" >> $LOG_FILENAME + ( + echo "____________________________________________" + echo "" + + sysctl=`which sysctl 2> /dev/null | head -n 1` + if [ $? -eq 0 -a "$sysctl" ]; then + value=`$sysctl $1 2> /dev/null` + if [ $? -eq 0 -a "$value" ]; then + echo "$value" + else + echo "$1 does not exist" + fi else - echo "$1 does not exist" >> $LOG_FILENAME + echo "sysctl not found" fi - else - echo "sysctl not found" >> $LOG_FILENAME - fi + ) | $GZIP_CMD >> $LOG_FILENAME } @@ -97,10 +112,10 @@ if [ `id -u` -ne 0 ]; then fi -# move any old log file out of the way +# move any old log file (zipped) out of the way if [ -f $LOG_FILENAME ]; then - mv $LOG_FILENAME ${LOG_FILENAME}.old + mv $LOG_FILENAME $OLD_LOG_FILENAME fi @@ -126,17 +141,19 @@ echo -n "Running $(basename $0)..."; # print prologue to the log file -echo "____________________________________________" >> $LOG_FILENAME -echo "" >> $LOG_FILENAME -echo "Start of NVIDIA bug report log file. Please send this" >> $LOG_FILENAME -echo "report along with a description of your bug, to" >> $LOG_FILENAME -echo "freebsd-gfx-bugs@nvidia.com." >> $LOG_FILENAME -echo "" >> $LOG_FILENAME -echo "nvidia-bug-report.sh Version: $NVIDIA_BUG_REPORT_VERSION" >> $LOG_FILENAME -echo "" >> $LOG_FILENAME -echo "Date: `date`" >> $LOG_FILENAME -echo "uname: `uname -a`" >> $LOG_FILENAME -echo "" >> $LOG_FILENAME +( + echo "____________________________________________" + echo "" + echo "Start of NVIDIA bug report log file. Please send this" + echo "report along with a description of your bug, to" + echo "freebsd-gfx-bugs@nvidia.com." + echo "" + echo "nvidia-bug-report.sh Version: $NVIDIA_BUG_REPORT_VERSION" + echo "" + echo "Date: `date`" + echo "uname: `uname -a`" + echo "" +) | $GZIP_CMD >> $LOG_FILENAME # append useful sysctl keys @@ -168,145 +185,178 @@ done # append vmstat info -vmstat=`which vmstat 2> /dev/null | head -n 1` - -echo "____________________________________________" >> $LOG_FILENAME -echo "" >> $LOG_FILENAME - -if [ $? -eq 0 -a "$vmstat" ]; then - echo "$vmstat" >> $LOG_FILENAME - echo "" >> $LOG_FILENAME - ( $vmstat >> $LOG_FILENAME ; exit 0 ) > /dev/null 2>&1 - echo "" >> $LOG_FILENAME - echo "____________________________________________" >> $LOG_FILENAME - echo "" >> $LOG_FILENAME - echo "$vmstat -a -i" >> $LOG_FILENAME - echo "" >> $LOG_FILENAME - ( $vmstat -a -i >> $LOG_FILENAME ; exit 0 ) > /dev/null 2>&1 - echo "" >> $LOG_FILENAME -else - echo "Skipping vmstat output (vmstat not found)" >> $LOG_FILENAME - echo "" >> $LOG_FILENAME -fi +( + echo "____________________________________________" + echo "" + + vmstat=`which vmstat 2> /dev/null | head -n 1` + + if [ $? -eq 0 -a -x "$vmstat" ]; then + echo "$vmstat" + echo "" + $vmstat 2> /dev/null + echo "" + echo "____________________________________________" + echo "" + echo "$vmstat -a -i" + echo "" + $vmstat -a -i 2> /dev/null + echo "" + else + echo "Skipping vmstat output (vmstat not found)" + echo "" + fi +) | $GZIP_CMD >> $LOG_FILENAME # append kldstat info -kldstat=`which kldstat 2> /dev/null | head -n 1` +( + echo "____________________________________________" + echo "" -echo "____________________________________________" >> $LOG_FILENAME -echo "" >> $LOG_FILENAME + kldstat=`which kldstat 2> /dev/null | head -n 1` -if [ $? -eq 0 -a "$kldstat" ]; then - echo "$kldstat -v" >> $LOG_FILENAME - echo "" >> $LOG_FILENAME - ( $kldstat -v >> $LOG_FILENAME ; exit 0 ) > /dev/null 2>&1 - echo "" >> $LOG_FILENAME -else - echo "Skipping kldstat output (kldstat not found)" >> $LOG_FILENAME - echo "" >> $LOG_FILENAME -fi + if [ $? -eq 0 -a -x "$kldstat" ]; then + echo "$kldstat -v" + echo "" + $kldstat -v 2> /dev/null + echo "" + else + echo "Skipping kldstat output (kldstat not found)" + echo "" + fi +) | $GZIP_CMD >> $LOG_FILENAME # append ldd info -glxinfo=`which glxinfo 2> /dev/null | head -n 1` +( + echo "____________________________________________" + echo "" -echo "____________________________________________" >> $LOG_FILENAME -echo "" >> $LOG_FILENAME + glxinfo=`which glxinfo 2> /dev/null | head -n 1` -if [ $? -eq 0 -a "$glxinfo" ]; then - echo "ldd $glxinfo" >> $LOG_FILENAME - echo "" >> $LOG_FILENAME - ( ldd $glxinfo >> $LOG_FILENAME ; exit 0 ) > /dev/null 2>&1 - echo "" >> $LOG_FILENAME -else - echo "Skipping ldd output (glxinfo not found)" >> $LOG_FILENAME - echo "" >> $LOG_FILENAME -fi + if [ $? -eq 0 -a -x "$glxinfo" ]; then + echo "ldd $glxinfo" + echo "" + ldd $glxinfo 2> /dev/null + echo "" + else + echo "Skipping ldd output (glxinfo not found)" + echo "" + fi +) | $GZIP_CMD >> $LOG_FILENAME # pciconf information -pciconf=`which pciconf 2> /dev/null | head -n 1` +( + echo "____________________________________________" + echo "" -echo "____________________________________________" >> $LOG_FILENAME -echo "" >> $LOG_FILENAME + pciconf=`which pciconf 2> /dev/null | head -n 1` -if [ $? -eq 0 -a "$pciconf" ]; then - echo "$pciconf -l -v" >> $LOG_FILENAME - echo "" >> $LOG_FILENAME - ( $pciconf -l -v >> $LOG_FILENAME ; exit 0 ) > /dev/null 2>&1 - echo "" >> $LOG_FILENAME -else - echo "Skipping pciconf output (pciconf not found)" >> $LOG_FILENAME - echo "" >> $LOG_FILENAME -fi + if [ $? -eq 0 -a -x "$pciconf" ]; then + echo "$pciconf -l -v" + echo "" + $pciconf -l -v 2> /dev/null + echo "" + else + echo "Skipping pciconf output (pciconf not found)" + echo "" + fi +) | $GZIP_CMD >> $LOG_FILENAME # get any relevant kernel messages -echo "____________________________________________" >> $LOG_FILENAME -echo "" >> $LOG_FILENAME -echo "Scanning kernel log files for NVRM messages:" >> $LOG_FILENAME -echo "" >> $LOG_FILENAME +( + echo "____________________________________________" + echo "" + echo "Scanning kernel log files for NVRM messages:" + echo "" -for i in /var/log/messages /var/log/kernel.log ; do - if [ -f $i ]; then - echo " $i:" >> $LOG_FILENAME - ( cat $i | grep NVRM >> $LOG_FILENAME ; exit 0 ) > /dev/null 2>&1 - fi -done + for i in /var/log/messages /var/log/kernel.log ; do + if [ -f $i -a -r $i ]; then + echo " $i:" + ( cat $i | grep NVRM ) 2> /dev/null + else + echo "$i is not readable" + fi + done +) | $GZIP_CMD >> $LOG_FILENAME # append dmesg output -echo "" >> $LOG_FILENAME -echo "____________________________________________" >> $LOG_FILENAME -echo "" >> $LOG_FILENAME -echo "dmesg:" >> $LOG_FILENAME -echo "" >> $LOG_FILENAME -( dmesg >> $LOG_FILENAME ; exit 0 ) > /dev/null 2>&1 - -which gcc >/dev/null 2>&1 -if [ $? -eq 0 ]; then - echo "____________________________________________" >> $LOG_FILENAME - echo "" >> $LOG_FILENAME - ( gcc -v 2>> $LOG_FILENAME ; exit 0 ) > /dev/null 2>&1 -fi +( + echo "" + echo "____________________________________________" + echo "" + echo "dmesg:" + echo "" + dmesg 2> /dev/null +) | $GZIP_CMD >> $LOG_FILENAME + +# print the gcc & g++ version info + +( + which gcc >/dev/null 2>&1 + if [ $? -eq 0 ]; then + echo "____________________________________________" + echo "" + gcc -v 2>&1 + fi -which g++ >/dev/null 2>&1 -if [ $? -eq 0 ]; then - echo "____________________________________________" >> $LOG_FILENAME - echo "" >> $LOG_FILENAME - ( g++ -v 2>> $LOG_FILENAME ; exit 0 ) > /dev/null 2>&1 -fi + which g++ >/dev/null 2>&1 + if [ $? -eq 0 ]; then + echo "____________________________________________" + echo "" + g++ -v 2>&1 + fi +) | $GZIP_CMD >> $LOG_FILENAME -echo "____________________________________________" >> $LOG_FILENAME -echo "" >> $LOG_FILENAME -echo "xset -q:" >> $LOG_FILENAME -echo "" >> $LOG_FILENAME +# In case of failure, if xset returns with delay, we print the +# message from check "$?" & if it returns error immediately before kill, +# we directly write the error to the log file. -( xset -q >> $LOG_FILENAME & sleep 1 ; kill -9 $! ) > /dev/null 2>&1 +( + echo "____________________________________________" + echo "" + echo "xset -q:" + echo "" -if [ $? -eq 0 ]; then - # The xset process is still there. - echo "xset could not connect to an X server" >> $LOG_FILENAME -fi + xset -q 2>&1 & sleep 1 ; kill -9 $! > /dev/null 2>&1 -echo "____________________________________________" >> $LOG_FILENAME -echo "" >> $LOG_FILENAME -echo "nvidia-settings -q all:" >> $LOG_FILENAME -echo "" >> $LOG_FILENAME + if [ $? -eq 0 ]; then + # The xset process is still there. + echo "xset could not connect to an X server" + fi +) | $GZIP_CMD >> $LOG_FILENAME -( nvidia-settings -q all >> $LOG_FILENAME & sleep 1 ; kill -9 $! ) > /dev/null 2>&1 +# In case of failure, if nvidia-settings returns with delay, we print the +# message from check "$?" & if it returns error immediately before kill, +# we directly write the error to the log file. -if [ $? -eq 0 ]; then - # The nvidia-settings process is still there. - echo "nvidia-settings could not connect to an X server" >> $LOG_FILENAME -fi -echo "____________________________________________" >> $LOG_FILENAME +( + echo "____________________________________________" + echo "" + echo "nvidia-settings -q all:" + echo "" + + nvidia-settings -q all 2>&1 & sleep 1 ; kill -9 $! > /dev/null 2>&1 + + if [ $? -eq 0 ]; then + # The nvidia-settings process is still there. + echo "nvidia-settings could not connect to an X server" + fi +) | $GZIP_CMD >> $LOG_FILENAME + +( + echo "____________________________________________" -# print epilogue to log file + # print epilogue to log file -echo "" >> $LOG_FILENAME -echo "End of NVIDIA bug report log file." >> $LOG_FILENAME + echo "" + echo "End of NVIDIA bug report log file." +) | $GZIP_CMD >> $LOG_FILENAME # Done diff --git a/obj/nvidia-settings b/obj/nvidia-settings index 21e9fd9..0c843c4 100755 Binary files a/obj/nvidia-settings and b/obj/nvidia-settings differ diff --git a/obj/nvidia-xconfig b/obj/nvidia-xconfig index c1ef619..7ccb9d2 100755 Binary files a/obj/nvidia-xconfig and b/obj/nvidia-xconfig differ diff --git a/obj/nvidia_drv.so b/obj/nvidia_drv.so index 539719a..e6fe41c 100755 Binary files a/obj/nvidia_drv.so and b/obj/nvidia_drv.so differ diff --git a/src/Makefile b/src/Makefile index 3bb7d3a..f351daa 100644 --- a/src/Makefile +++ b/src/Makefile @@ -1,5 +1,5 @@ # This Makefile is automatically generated -# Generated on 'builder59' on Tue Feb 3 10:07:12 PST 2009 +# Generated on 'builder65' on Fri Aug 14 16:36:46 PDT 2009 OSOBJ= nv-freebsd.o KMOD= nvidia @@ -12,8 +12,8 @@ KMODDIR?= /boot/modules SRCS= nvidia_ctl.c nvidia_dev.c nvidia_linux.c nvidia_os.c nvidia_os_pci.c nvidia_os_registry.c nvidia_pci.c nvidia_subr.c nvidia_sysctl.c nvidia_i2c.c SRCS+= device_if.h bus_if.h pci_if.h vnode_if.h -CFLAGS+= -I${NVIDIA_ROOT}/src -DNV_VERSION_STRING=\"180.29\" -CFLAGS+= -D__KERNEL__ -DNVRM -UDEBUG -U_DEBUG -DNDEBUG -O +CFLAGS+= -I${NVIDIA_ROOT}/src -DNV_VERSION_STRING=\"185.18.36\" +CFLAGS+= -D__KERNEL__ -DNVRM -UDEBUG -U_DEBUG -DNDEBUG -O -fno-defer-pop OBJS+= ${RMOBJ} .if ${BSDVER} >= 600000 diff --git a/src/nv-freebsd.h b/src/nv-freebsd.h index 6f26ea3..d357f9b 100644 --- a/src/nv-freebsd.h +++ b/src/nv-freebsd.h @@ -80,7 +80,11 @@ #include #include +#if __FreeBSD_version < 800004 #include +#else +#include +#endif #include #if defined(NVCPU_X86_64) @@ -112,6 +116,10 @@ #define CURTHREAD curthread +#if __FreeBSD_version >= 800049 +#define suser(_td) priv_check((_td), PRIV_DRIVER) +#endif + /* * The resource manager client tracking needs an identifier that uniquely * represents a client connection across threads. It needs to be specific diff --git a/src/nv-kernel.o b/src/nv-kernel.o index 0bb1634..fcc164e 100644 Binary files a/src/nv-kernel.o and b/src/nv-kernel.o differ diff --git a/src/nv-reg.h b/src/nv-reg.h index 24e3378..a58c451 100644 --- a/src/nv-reg.h +++ b/src/nv-reg.h @@ -539,6 +539,9 @@ #define __NV_MAP_REGISTERS_EARLY MapRegistersEarly #define NV_REG_MAP_REGISTERS_EARLY NV_REG_STRING(__NV_MAP_REGISTERS_EARLY) +#define __NV_RM_NVCLK_IDLE_GR RmNvclkIdleGraphics +#define NV_REG_RM_NVCLK_IDLE_GR NV_REG_STRING(__NV_RM_NVCLK_IDLE_GR) + #if defined(NV_DEFINE_REGISTRY_KEY_TABLE) /* @@ -564,6 +567,7 @@ NV_DEFINE_REG_ENTRY(__NV_RM_EDGE_INTR_CHECK, 1); NV_DEFINE_REG_ENTRY(__NV_USE_PAGE_ATTRIBUTE_TABLE, ~0); NV_DEFINE_REG_ENTRY(__NV_ENABLE_MSI, 0); NV_DEFINE_REG_ENTRY(__NV_MAP_REGISTERS_EARLY, 0); +NV_DEFINE_REG_ENTRY(__NV_RM_NVCLK_IDLE_GR, 0); #if defined(NV_LINUX) NV_DEFINE_REG_STRING_ENTRY(__NV_REGISTRY_DWORDS, NULL); @@ -612,6 +616,7 @@ nv_parm_t nv_parms[] = { NV_DEFINE_PARAMS_TABLE_ENTRY(__NV_USE_PAGE_ATTRIBUTE_TABLE), NV_DEFINE_PARAMS_TABLE_ENTRY(__NV_ENABLE_MSI), NV_DEFINE_PARAMS_TABLE_ENTRY(__NV_MAP_REGISTERS_EARLY), + NV_DEFINE_PARAMS_TABLE_ENTRY(__NV_RM_NVCLK_IDLE_GR), {NULL, NULL, NULL} }; diff --git a/src/nv.h b/src/nv.h index d255f6e..a5e2ff6 100644 --- a/src/nv.h +++ b/src/nv.h @@ -25,7 +25,7 @@ #define NV_MAJOR_DEVICE_NUMBER 195 /* most cards in a single system */ -#define NV_MAX_DEVICES 16 +#define NV_MAX_DEVICES 32 /* NOTE: using an ioctl() number > 55 will overflow! */ #define NV_IOCTL_MAGIC 'F' @@ -86,10 +86,10 @@ typedef struct nv_ioctl_card_info NvU16 vendor_id; /* PCI vendor id */ NvU16 device_id; NvU16 interrupt_line; - NvU32 reg_address; /* register aperture */ - NvU32 reg_size; - NvU32 fb_address; /* framebuffer aperture */ - NvU32 fb_size; + NvU64 reg_address NV_ALIGN_BYTES(8); + NvU64 reg_size NV_ALIGN_BYTES(8); + NvU64 fb_address NV_ALIGN_BYTES(8); + NvU64 fb_size NV_ALIGN_BYTES(8); } nv_ioctl_card_info_t; #define NV_IOCTL_CARD_INFO_BUS_TYPE_PCI 0x0001 @@ -210,8 +210,8 @@ typedef union typedef struct { - NvU32 address; - NvU32 size; + NvU64 address; + NvU64 size; NvU32 offset; NvU32 *map; nv_phwreg_t map_u; @@ -257,7 +257,7 @@ typedef struct nv_event_s typedef struct nv_kern_mapping_s { void *addr; - NvU32 size; + NvU64 size; struct nv_kern_mapping_s *next; } nv_kern_mapping_t; @@ -379,10 +379,14 @@ typedef struct #define NV_ACPI_NVIF_HANDLE_PRESENT 0x01 #define NV_ACPI_DSM_HANDLE_PRESENT 0x02 #define NV_ACPI_WMMX_HANDLE_PRESENT 0x04 +#define NV_ACPI_MXMI_HANDLE_PRESENT 0x08 +#define NV_ACPI_MXMS_HANDLE_PRESENT 0x10 #define NV_ACPI_METHOD_NVIF 0x01 #define NV_ACPI_METHOD_DSM_NBSI 0x02 #define NV_ACPI_METHOD_WMMX 0x03 +#define NV_ACPI_METHOD_MXMI 0x04 +#define NV_ACPI_METHOD_MXMS 0x05 #define NV_NBSI_REVISION_ID 0x00000101 @@ -583,7 +587,6 @@ RM_STATUS NV_API_CALL rm_write_registry_binary (nv_stack_t *, nv_state_t *, U0 RM_STATUS NV_API_CALL rm_run_rc_callback (nv_stack_t *, nv_state_t *); RM_STATUS NV_API_CALL rm_get_device_name (nv_stack_t *, nv_state_t *, U032, U032, U008*); -RM_STATUS NV_API_CALL rm_validate_pfn_range (nv_stack_t *, nv_state_t *, void *, U032, U032, BOOL); NvU64 NV_API_CALL nv_rdtsc (void); void NV_API_CALL rm_register_compatible_ioctls (nv_stack_t *); diff --git a/src/nvidia_dev.c b/src/nvidia_dev.c index e7248da..0e2eb64 100644 --- a/src/nvidia_dev.c +++ b/src/nvidia_dev.c @@ -40,7 +40,7 @@ int nvidia_dev_open( int status; struct nvidia_softc *sc; nv_state_t *nv; - int unit = minor(dev); + int unit = dev2unit(dev); sc = devclass_get_softc(nvidia_devclass, unit); if (!sc) @@ -65,7 +65,7 @@ int nvidia_dev_close( int status; struct nvidia_softc *sc; nv_state_t *nv; - int unit = minor(dev); + int unit = dev2unit(dev); sc = devclass_get_softc(nvidia_devclass, unit); nv = sc->nv_state; @@ -88,7 +88,7 @@ int nvidia_dev_ioctl( int status; struct nvidia_softc *sc; nv_state_t *nv; - int unit = minor(dev); + int unit = dev2unit(dev); if (__NV_IOC_TYPE(cmd) != NV_IOCTL_MAGIC) return ENOTTY; @@ -112,7 +112,7 @@ int nvidia_dev_poll( struct nvidia_softc *sc; nv_state_t *nv; struct nvidia_event *et; - int unit = minor(dev); + int unit = dev2unit(dev); sc = devclass_get_softc(nvidia_devclass, unit); nv = sc->nv_state; @@ -146,7 +146,7 @@ int nvidia_dev_mmap( struct nvidia_softc *sc; vm_offset_t physical; nv_state_t *nv; - int unit = minor(dev); + int unit = dev2unit(dev); sc = devclass_get_softc(nvidia_devclass, unit); nv = sc->nv_state; diff --git a/src/nvidia_os.c b/src/nvidia_os.c index 5cd495a..77a7c1d 100644 --- a/src/nvidia_os.c +++ b/src/nvidia_os.c @@ -252,31 +252,9 @@ void NV_API_CALL os_unmap_kernel_space( pmap_unmapdev_attr((vm_offset_t)address, size); } -void* NV_API_CALL os_map_kernel_space_high( - U032 pfn, - U032 size -) -{ - U032 start; - if (!(pfn & ~0xfffff)) { - start = pfn << PAGE_SHIFT; - return os_map_kernel_space(start, size, NV_MEMORY_CACHED); - } - return NULL; -} - -void NV_API_CALL os_unmap_kernel_space_high( - void *addr, - U032 pfn, - U032 size -) -{ - os_unmap_kernel_space(addr, size); -} - RM_STATUS NV_API_CALL os_set_mem_range( - U032 start, - U032 size, + NvU64 start, + NvU64 size, U032 mode ) { @@ -297,8 +275,8 @@ RM_STATUS NV_API_CALL os_set_mem_range( } RM_STATUS NV_API_CALL os_unset_mem_range( - U032 start, - U032 size + NvU64 start, + NvU64 size ) { int arg; @@ -667,34 +645,6 @@ BOOL NV_API_CALL os_pat_supported(void) return FALSE; } -RM_STATUS NV_API_CALL os_set_mlock_capability() -{ - return (RM_ERROR); -} - -S032 NV_API_CALL os_mlock_user_memory( - void *address, - U032 length -) -{ - return -1; -} - -S032 NV_API_CALL os_munlock_user_memory( - void *address, - U032 length -) -{ - return -1; -} - -RM_STATUS NV_API_CALL os_check_process_map_limit( - NvU64 proc_max_map_count -) -{ - return (RM_ERROR); -} - void NV_API_CALL os_register_compatible_ioctl( U032 cmd, U032 size @@ -718,3 +668,21 @@ RM_STATUS NV_API_CALL os_enable_console_access(void) { return RM_OK; } + +NvU64 NV_API_CALL os_acquire_spinlock(void *pSema) +{ + struct os_mutex *mtx = pSema; + + mtx_lock(&mtx->mutex_mtx); + + return 0; +} + +void NV_API_CALL os_release_spinlock(void *pSema, NvU64 oldIrql) +{ + struct os_mutex *mtx = pSema; + + mtx_unlock(&mtx->mutex_mtx); +} + + diff --git a/src/nvidia_subr.c b/src/nvidia_subr.c index a1ad6a4..1140861 100644 --- a/src/nvidia_subr.c +++ b/src/nvidia_subr.c @@ -315,7 +315,7 @@ int nvidia_handle_ioctl( { struct nvidia_softc *sc; nv_state_t *nv; - int unit = minor(dev); + int unit = dev2unit(dev); nv_stack_t *sp; void *args; nv_ioctl_xfer_t *xfer = NULL; diff --git a/src/os-interface.h b/src/os-interface.h index e767638..752c753 100644 --- a/src/os-interface.h +++ b/src/os-interface.h @@ -88,8 +88,8 @@ void* NV_API_CALL os_map_kernel_space (NvU64, NvU64, U032); void NV_API_CALL os_unmap_kernel_space (void *, NvU64); RM_STATUS NV_API_CALL os_flush_cpu_cache (void); void NV_API_CALL os_flush_cpu_write_combine_buffer(void); -RM_STATUS NV_API_CALL os_set_mem_range (U032, U032, U032); -RM_STATUS NV_API_CALL os_unset_mem_range (U032, U032); +RM_STATUS NV_API_CALL os_set_mem_range (NvU64, NvU64, U032); +RM_STATUS NV_API_CALL os_unset_mem_range (NvU64, NvU64); BOOL NV_API_CALL os_pci_device_present (U016, U016); U008 NV_API_CALL os_io_read_byte (PHWINFO, U032); U016 NV_API_CALL os_io_read_word (PHWINFO, U032); @@ -107,14 +107,6 @@ RM_STATUS NV_API_CALL os_clear_smp_barrier (void); RM_STATUS NV_API_CALL os_disable_console_access (void); RM_STATUS NV_API_CALL os_enable_console_access (void); RM_STATUS NV_API_CALL os_registry_init (void); - -void* NV_API_CALL os_map_kernel_space_high (U032, U032); -void NV_API_CALL os_unmap_kernel_space_high (void *, U032, U032); -RM_STATUS NV_API_CALL os_set_mlock_capability (void); -RM_STATUS NV_API_CALL os_check_process_map_limit (NvU64); -S032 NV_API_CALL os_mlock_user_memory (void *, U032); -S032 NV_API_CALL os_munlock_user_memory (void *, U032); - RM_STATUS NV_API_CALL os_alloc_sema (void **); RM_STATUS NV_API_CALL os_free_sema (void *); RM_STATUS NV_API_CALL os_acquire_sema (void *); @@ -122,6 +114,9 @@ BOOL NV_API_CALL os_cond_acquire_sema (void *); RM_STATUS NV_API_CALL os_release_sema (void *); BOOL NV_API_CALL os_is_acquired_sema (void *); RM_STATUS NV_API_CALL os_schedule (void); +NvU64 NV_API_CALL os_acquire_spinlock (void *); +void NV_API_CALL os_release_spinlock (void *, NvU64); + void NV_API_CALL os_register_compatible_ioctl (U032, U032); void NV_API_CALL os_unregister_compatible_ioctl (U032, U032); diff --git a/src/rmretval.h b/src/rmretval.h index 8f86754..3a67d19 100644 --- a/src/rmretval.h +++ b/src/rmretval.h @@ -86,8 +86,14 @@ typedef NvU32 RM_STATUS; #define RM_ERR_NO_SUCH_DOMAIN 0x0000003A #define RM_ERR_I2C_ERROR 0x0000003B #define RM_ERR_FREQ_NOT_SUPPORTED 0x0000003C -#define RM_ERR_INVALID_REQUEST 0x0000003C -#define RM_ERR_MORE_PROCESSING_REQUIRED 0x0000003D +#define RM_ERR_INVALID_REQUEST 0x0000003D +#define RM_ERR_MORE_PROCESSING_REQUIRED 0x0000003E +#define RM_ERR_NO_INTR_PENDING 0x0000003F +#define RM_ERR_INSUFFICIENT_PERMISSIONS 0x00000041 +#define RM_ERR_NOT_READY 0x00000042 + +// Warnings: #define RM_WARN_NULL_OBJECT 0x00000100 +#define RM_WARN_INCORRECT_PERFMON_DATA 0x00000101 #endif /* _RMRETVAL_H_ */ diff --git a/x11/man/nvidia-xconfig.1 b/x11/man/nvidia-xconfig.1 index 7aa94dc..c1010f3 100644 --- a/x11/man/nvidia-xconfig.1 +++ b/x11/man/nvidia-xconfig.1 @@ -92,9 +92,6 @@ Set this option to specify an alternate path to the Linux ACPI daemon (acpid)'s .BI "\-\-add-argb-glx-visuals, \-\-no\-add-argb-glx-visuals" Enables or disables support for OpenGL rendering into 32\-bit ARGB windows and pixmaps. .TP -.BI "\-\-allow-dfp-stereo, \-\-no\-allow-dfp-stereo" -Enable or disable the "AllowDFPStereo" X configuration option. -.TP .BI "\-\-allow-glx-with-composite, \-\-no\-allow-glx-with-composite" Enable or disable the "AllowGLXWithComposite" X configuration option. .TP @@ -189,9 +186,6 @@ The nvidia\-xconfig utility operates on a Server Layout within the X configurati .I LAYOUT in the X configuration file will be used. If this option is not specified, the first Server Layout in the X configuration file is used. .TP -.BI "\-\-load-kernel-module, \-\-no\-load-kernel-module" -Allow or disallow NVIDIA Linux X driver module to load the NVIDIA Linux kernel module automatically. -.TP .BI "\-\-logo, \-\-no\-logo" Disable or enable the "NoLogo" X configuration option. .TP @@ -235,7 +229,7 @@ Set the NvAGP X config option value. Possible values are 0 (no AGP), 1 (NVIDIA' The nvidia\-cfg library is used to communicate with the NVIDIA kernel module to query basic properties of every GPU in the system. This library is typically only used by nvidia\-xconfig when configuring multiple X screens. This option tells nvidia\-xconfig where to look for this library (in case it cannot find it on its own). This option should normally not be needed. .TP .BI "\-\-only-one-x-screen" - +Disable all but one X screen. .TP .BI "\-\-overlay, \-\-no\-overlay" Enable or disable the "Overlay" X configuration option. @@ -293,7 +287,7 @@ are 'Off', 'On', 'Auto', 'AFR', 'SFR', 'AA', 'AFRofAA'. .BI "\-\-stereo=" "STEREO" ", \-\-no\-stereo" Enable or disable the stereo mode. Valid values for .I STEREO -are: 1 (DCC glasses), 2 (Blueline glasses), 3 (Onboard stereo), 4 (TwinView clone mode stereo), 5 (SeeReal digital flat panel), 6 (Sharp3D digital flat panel). +are: 0 (Disabled), 1 (DCC glasses), 2 (Blueline glasses), 3 (Onboard stereo), 4 (TwinView clone mode stereo), 5 (SeeReal digital flat panel), 6 (Sharp3D digital flat panel), 7 (Arisawa/Hyundai/Zalman/Pavione/Miracube), 8 (3D DLP), 9 (3D DLP INV). .TP .BI "\-\-tv-standard=" "TV-STANDARD" ", \-\-no\-tv-standard" Enable or disable the "TVStandard" X configuration option. Valid values for "TVStandard" are: "PAL\-B", "PAL\-D", "PAL\-G", "PAL\-H", "PAL\-I", "PAL\-K1", "PAL\-M", "PAL\-N", "PAL\-NC", "NTSC\-J", "NTSC\-M", "HD480i", "HD480p", "HD720p", "HD1080i", "HD1080p", "HD576i", "HD576p".