summaryrefslogtreecommitdiffstats
path: root/DOCS
diff options
context:
space:
mode:
authorranma <ranma@b3059339-0415-0410-9bf9-f77b7e298cf2>2002-11-02 00:27:57 +0000
committerranma <ranma@b3059339-0415-0410-9bf9-f77b7e298cf2>2002-11-02 00:27:57 +0000
commit9ac9c08a9f41048ed29e418af8d6083a44207986 (patch)
tree795cc987fe505cb137abb2b6ee8ca2a7a7a710ee /DOCS
parent81a28c52c1a3ef2b4a36abc5256300c0477b6919 (diff)
downloadmpv-9ac9c08a9f41048ed29e418af8d6083a44207986.tar.bz2
mpv-9ac9c08a9f41048ed29e418af8d6083a44207986.tar.xz
Document xvidix pixmap corruption issue and known workarounds.
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@8030 b3059339-0415-0410-9bf9-f77b7e298cf2
Diffstat (limited to 'DOCS')
-rw-r--r--DOCS/video.html9
1 files changed, 8 insertions, 1 deletions
diff --git a/DOCS/video.html b/DOCS/video.html
index 42343c3f4c..d0b23c78a2 100644
--- a/DOCS/video.html
+++ b/DOCS/video.html
@@ -851,7 +851,14 @@
<UL>
<LI>You can use standalone video output driver: <CODE>-vo xvidix</CODE><BR>
This driver was developed as X11's front end to VIDIX technology. It
- requires X server and can work only under X server.</LI>
+ requires X server and can work only under X server. Note that, as it
+ directly accesses the hardware and circumvents the X driver, pixmaps
+ cached in the graphics card's memory may be corrupted. You can prevent
+ this by limiting the amount of video memory used by X with the XF86Config
+ option "VideoRam" in the device section. You should set this to the amount
+ of memory installed on your card minus 4MB. If you have less than 8MB of
+ video ram, you can use the option "XaaNoPixmapCache" in the screen section
+ instead.</LI>
<LI>You can use VIDIX subdevice which was applied to several video output
drivers, such as:<BR>
<CODE>-vo vesa:vidix</CODE> (<B>Linux only</B>) and <CODE>-vo fbdev:vidix</CODE></LI>