diff options
author | Chris Wilson <chris@chris-wilson.co.uk> | 2014-06-06 11:39:57 +0100 |
---|---|---|
committer | Chris Wilson <chris@chris-wilson.co.uk> | 2014-06-06 11:40:51 +0100 |
commit | 0ebcef4f2ebe82e9b90589aa4266a9228e2b5fdb (patch) | |
tree | f9b20cc220abc1a2dee05758094e872a0321f8fe | |
parent | 1f943a7d92d0e3a8895ba7d539cfc5e726bcc8b7 (diff) |
man: Update notes about TearFree
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
-rw-r--r-- | man/intel.man | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/man/intel.man b/man/intel.man index 27206e37..9deac418 100644 --- a/man/intel.man +++ b/man/intel.man @@ -150,9 +150,11 @@ 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. +compositing manager should be doing, however TearFree will redirect the +compositor updates (and those of fullscreen games) directly on to the scanout +thus incurring no additional overhead in the composited case. Also note that +not all compositing managers prevent tearing, and if the outputs are +rotated, there will still be tearing without TearFree enabled. .IP Default: TearFree is disabled. .TP |