|
翻译原文:
http://www.linuxsir.cn/forum.php?mod=viewthread&tid=4642
已经校对过的
编号001-015:
http://www.linuxsir.cn/forum.php?mod=viewthread&tid=5738
http://www.linuxsir.cn/forum.php?mod=viewthread&tid=6466
http://www.linuxsir.cn/forum.php?mod=viewthread&tid=6526
http://www.linuxsir.cn/forum.php?mod=viewthread&tid=6842
http://www.linuxsir.cn/forum.php?mod=viewthread&tid=6973
http://www.linuxsir.cn/forum.php?mod=viewthread&tid=7451
http://www.linuxsir.cn/forum.php?mod=viewthread&tid=8154
http://www.linuxsir.cn/forum.php?mod=viewthread&tid=8214
http://www.linuxsir.cn/forum.php?mod=viewthread&tid=8615
http://www.linuxsir.cn/forum.php?mod=viewthread&tid=9380
http://www.linuxsir.cn/forum.php?mod=viewthread&tid=10873
http://www.linuxsir.cn/forum.php?mod=viewthread&tid=11740
http://www.linuxsir.cn/forum.php?mod=viewthread&tid=12309
http://www.linuxsir.cn/forum.php?mod=viewthread&tid=13464
http://www.linuxsir.cn/forum.php?mod=viewthread&tid=18557
有新意见的朋友还可以继续跟贴,谢谢!
今天开始翻译校对编号016,希望大家热情参与:
******************************
本文档已由dragonnapalm兄弟领译,多谢dragonnapalm兄弟。
弟兄们向您致意!
============================================
============================================
编号016
———————————————————————————————————
(app-m)附录 M:画面交换模式、窗口交换模式、以及UBB(统一反向缓冲器)
———————————————————————————————————
从发行版1.0-2313开始,NVIDIA Linux加速驱动包开始支持统一反向缓冲器(UBB
)、画面交换模式以及窗口交换模式。这些特性在某些场合可以提供更高的性能
提升。下面是对它们分别的描述:
·画面交换模式:所有的GeForce系列显示卡或者更新的硬件设备已经包含此种特
性(注:不包括TNT/TNT2系列产品),它可以在进行同步垂直刷新的时候激活,
使OpenGL应用程序在单一全屏幕显示的时候更加清晰。缓冲交换将通过改变DAC所
扫描出的缓存来完成,而不是通过将后置缓存的内容复制到前置缓存来实现;此
种机制可以普遍地使性能得到进一步的提升,并且在场景折回的过程中可以实现
无损交换(当__GL_SYNC_TO_VBLANK 已被设置)。该特性可以 在XF86Config中使
用“PageFlip”选项来禁用
·统一反向缓冲器(UBB):UBB在所有的Quadro系列芯片中已经得到支持(Quadr
o4 200/400NVS 除外),并且当显存足够时,它已经被默认设置为打开。它可以
使用在附录D中所描述的 XF86Config “UBB”选项来禁用。当UBB被打开时,所有
的窗口将使用统一的背景、模板及深度缓冲。在出现很多窗口的情况下,背景、
模板和深度所占用的显存将不会超过全屏幕状态下所使用的大小。但是,即使是
对单一的小型窗口,背景、模板及深度的对显存的占用将和全屏幕窗口所占用的
大小相同,这样的话,显存的使用效率可能要低于采用非UBB显示的模式。
·窗口交换模式:该特性需要UBB的支持,并且只在Quadro芯片上可用。当单一的
OpenGL窗口出现时,该窗口的缓存可以通过DAC扫描出的缓存来改变,而不是将后
置缓存的内容移动到前置缓存中去。这和画面交换模式类似,但是它取消了该窗
口必须为清晰显示状态以及为全屏模式的限制。该特性只能工作在单一的OpenGL
窗口模式下,并且默认情况下为禁用。要启用,请使用附录D中所描述的XF86Conf
ig “WindowFlip”选项
______________________________________________________________________
(app-n) 附录N: 已知的问题
______________________________________________________________________
以下的问题在此发行版中仍然存在,并且有待于解决:
·OpenGL + Xinerama:在Xinerama环境下,除了在单头显示模式下,OpenGL将不
会被起用
·OpenGL及dlopen()函数
在使用了dlopen()函数的程序中,存在着一系列问题有待商讨。这些问题存在于
较老版本的glibc动态装载程序(如:随RedHat7.2所附带的版本)以及像雷神之
锤3、辐射这样的应用程序。欲了解详细信息,请参阅常见问题解答章节
·DPMS及双头显示
当使用双头显示的时候,DPMS中的“延缓”及“等待”模式在第二台CRT显示器上
不会正确工作。该显示器的屏幕会变为空白,而不是调整为被要求的DPMS状态。
·DPMS及平板显示器
DPMS中的“延缓”及“等待”模式在平板显示器上不会正确工作。显示器的屏幕
将变为空白,而不是调整为被要求的DPMS状态
·多显示卡以及多显示器
在某些情况下,从显示卡不会被NVdriver内核模块正确初始化,要解决该问题,
可以激活XFree86
Int10模块来软起动所有的从显示卡。请参阅“附录D:XF86CONFIG配置”章节获
取详细信息。
·膝上型电脑
如果你使用的是膝上型电脑,请在附录D中参阅“已知的膝上型电脑问题”部分
·FSAA(全屏幕抗锯齿)
当FSAA被激活时(__GL_FSAA_MODE变量环境已经被赋上激活FSAA的值,同时多次
取样视觉效果已经被选择)。当调整窗口大小的时候,该渲染可能会被破坏
硬件问题
该部分描述了不会被修复的问题。通常这些问题已经超出了NVIDIA的控制范围。
下面是这些问题的列表:
·技嘉GA-6BX主板
该主板所使用的LinFinity校整器安装在了额定电流被调整为5A的3.3V电压轨上—
—这少于AGP规格所要求的6A。当诊断或应用程序运行时,校整器温度升高,将会
引起NVIDIA芯片的电压降低到2.2V。在此情况下,校整器将不能在3.3V电压轨上
供给NVIDIA芯片所需要的足够电流。
如果显示卡有一个可变式校整器,或者外部电源供应连接在了3.3V电压轨上,该
问题则不会发生。
·带AGP2X的VIA KX133及694X芯片组
在使用VIA KX133或694X 芯片组的Athlon主板上,例如华硕K7V主板,NVIDIA驱动
将会在某一种信号的影响下被默认设置为AGP2X模式,以不足的驱动强度来工作。
·带AGP1X的Irongate芯片组
在使用Irongate芯片组的Athlon主板上,AGP1X传输模式将会在该芯片组中出现信
号完整性的问题
·ALi 芯片组,ALi1541及ALi1647
在ALi1541及ALi1647芯片组中,由于时间性问题及信号完整性问题,NVIDIA驱动
将禁用AGP工作模式。请参阅“附录G:ALI特别问题”获得ALi芯片组的更多信息。
-----------------------
英文原文:
__________________________________________________________________________
(app-m) APPENDIX M: PAGE FLIPPING, WINDOW FLIPPING, AND UBB
__________________________________________________________________________
Starting with the 1.0-2313 driver release, the NVIDIA Accelerated
Linux Driver Set supports Unified Back Buffer (UBB), Page Flipping,
and Window Flipping. These features can provide performance gains in
certain situtations. Here is a discription of each:
o Page Flipping: This feature is available on all GeForce or newer
hardware (ie: not TNT/TNT2 products), and is enabled in the
case of a single full screen unobscured OpenGL application when
syncing to vblank. Buffer swapping is done 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
retrace (when __GL_SYNC_TO_VBLANK is set). This feature can be
disabled with the PageFlip XF86Config option.
o Unified Back Buffer (UBB): UBB is available only on the Quadro family
of GPUs (Quadro4 200/400NVS excluded) and is enabled by default
when there is sufficient video memory available. This can be
disabled with the UBB XF86Config option described in Appendix D.
When UBB is enabled, all windows share the same back, stencil
and depth buffer. 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 usage are that of a full screen
window so in that case video ram may be used less efficiently
than in the non-UBB case.
o Window Flipping: This feature requires UBB, and thus is only available
on Quadro parts. When there is a single OpenGL window this
window's buffers can be swapped by changing which buffer the DAC
scans out rather than blitting the back buffer contents to the
front buffer. This is similar to Page Flipping but removes the
restriction that the window be unobscured and be full screen.
This only works when there is a single OpenGL window. Window
Flipping is disabled by default and can be enabled with the
"WindowFlip" XF86Config option described in Appendix D.
__________________________________________________________________________
(app-n) APPENDIX N: KNOWN ISSUES
__________________________________________________________________________
The following problems still exist in this release and are in the process
of being resolved.
o OpenGL + Xinerama
Currently, OpenGL will not display to anything other than the
first head in a Xinerama environment.
o OpenGL and dlopen()
There are some issues with older versions of the glibc dynamic
loader (e.g., the version that shipped with RedHat 7.2) and
applications such as Quake3 and Radiant, that use dlopen().
See the FREQUENTLY ASKED QUESTIONS section for more details.
o DPMS and TwinView
DPMS Modes "suspend" and "standby" do not work correctly on
a second CRT when using TwinView. The screen becomes blank
instead of the monitor being set to the requested DPMS state.
o DPMS and Flat Panel
DPMS modes "suspend" and "standby" do not work correctly on a
flat panel display. The screen becomes blank instead of the
flat panel being set to the requested DPMS state.
o Multicard, Multimonitor
In some cases, the secondary card is not initialized correctly
by the NVdriver kernel module. You can work around this by enabling
the XFree86 Int10 module to soft-boot all secondary cards. See
"APPENDIX D: XF86CONFIG OPTIONS" for details.
o Laptop
If you are using a laptop please see the "Known Laptop Issues" in
APPENDIX D.
o 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.
HARDWARE ISSUES
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:
o Gigabyte GA-6BX Motherboard
This motherboard uses a LinFinity regulator on the 3.3-V rail
that is rated to only 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 chip 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 chip requires.
This problem does not occur when the graphics board has a
switching regulator or when an external power supply is connected
to the 3.3-V rail.
o 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.
o Irongate Chip sets with AGP 1x
AGP 1x transfers are used on Athlon motherboards with the Irongate
chip set to work around a problem with the signal integrity of
the chip set.
o ALi chipsets, ALi1541 and ALi1647
On ALi1541 and ALi1647 chipsets, NVIDIA drivers disable AGP to work
around timing issues and signal integrity issues. See "APPENDIX G:
ALI SPECIFIC ISSUES" for more information on ALi chipsets. |
|