Aurelien
/
xf86-video-intel
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

man: State the negative aspects of TearFree 

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
This commit is contained in:
Chris Wilson 2013-10-24 19:38:53 +01:00
parent 2b6cb1cf45
commit 0d87113080
1 changed files with 12 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
man/intel.man
View File

@ -136,11 +136,18 @@ Default: use UXA (render acceleration)
.TP
.BI "Option \*qTearFree\*q \*q" boolean \*q
Disable or enable TearFree updates. This option forces X to perform all
rendering to a backbuffer prior to updating the actual display. That update
is then performed synchronously with the vertical refresh of the display so
that the entire update is complete before the display starts its refresh.
That is only one frame is ever visible, preventing an unsightly tear between
two visible differing frames.
rendering to a backbuffer prior to updating the actual display. It requires
an extra memory allocation the same size as a framebuffer, the occasional extra
copy, and requires Damage tracking update. Thus enabling TearFree requires more
memory and is slower (reduced throughput) and introduces a small amount of
output latency, but it should not impact input latency. However, the update to
the screen is then performed synchronously with the vertical refresh of the
display so that the entire update is completed before the display starts its
refresh. That is only one frame is ever visible, preventing an unsightly tear
between two visible and differing frames. Note that this replicates what the
compositing manager should be doing, so it is not advisable to enable both.
However, some compositing managers do cause tearing, and if the outputs are
rotated, there may will still be tearing without TearFree enabled.
.IP
Default: TearFree is disabled.
.TP