summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorarpi <arpi@b3059339-0415-0410-9bf9-f77b7e298cf2>2002-10-07 11:27:20 +0000
committerarpi <arpi@b3059339-0415-0410-9bf9-f77b7e298cf2>2002-10-07 11:27:20 +0000
commit7d5ae10689c3a12e37251c541d7d5a6373bf4b8c (patch)
tree5e3db14d3ad4a63c035336fd2f072998a2129696
parent7147ea6aa62f6b03a157500d38751332e47d3f55 (diff)
downloadmpv-7d5ae10689c3a12e37251c541d7d5a6373bf4b8c.tar.bz2
mpv-7d5ae10689c3a12e37251c541d7d5a6373bf4b8c.tar.xz
documenting vesa 3 / GTF config
patch by Rudolf Marek <MAREKR2@cs.felk.cvut.cz> git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@7652 b3059339-0415-0410-9bf9-f77b7e298cf2
-rw-r--r--DOCS/video.html10
-rw-r--r--etc/example.conf14
2 files changed, 17 insertions, 7 deletions
diff --git a/DOCS/video.html b/DOCS/video.html
index d28195d9ce..432688eda5 100644
--- a/DOCS/video.html
+++ b/DOCS/video.html
@@ -713,7 +713,7 @@
<H4><A NAME="vesa">2.3.1.11 VESA - output to VESA BIOS</A></H4>
<P>This driver was designed and introduced as a <B>generic driver</B> for any
- video card which has VESA VBE 2.0 compatible BIOS. Another advantage of this
+ video card which has VESA VBE 2.0+ compatible BIOS. Another advantage of this
driver is that it tries to force TV output on.<BR>
<B>VESA BIOS EXTENSION (VBE) Version 3.0 Date: September 16, 1998</B> (Page
70) says:</P>
@@ -752,6 +752,10 @@
in vm86 mode).</LI>
<LI>You can use Vidix with it, thus getting accelerated video display
<B>AND</B> TV output at the same time! (recommended for ATI cards)</LI>
+ <LI>If you have VESA VBE 3.0+, and you had specified monitor_hfreq, monitor_vfreq,
+ monitor_dotclock somewhere (config file, or commandline) you will get highest
+ possible refresh rate. (Using General Timing Formula). To enable this
+ feature you have to specify <B>ALL</B> monitor's options.</LI>
</UL>
<H4>Disadvantages:</H4>
@@ -774,6 +778,10 @@
<DT><CODE>-double</CODE></DT>
<DD>enables double buffering mode. (Available only in DGA mode). Should be
slower of single buffering, but has no flickering effects.</DD>
+ <DT><CODE>-monitor_hfreq</CODE></DT>
+ <DT><CODE>-monitor_vfreq</CODE></DT>
+ <DT><CODE>-monitor_dotclock</CODE></DT>
+ <DD><STRONG>Important</STRONG> values, see <CODE>example.conf</CODE></DD>
</DL>
<H4>Known problems and workaround:</H4>
diff --git a/etc/example.conf b/etc/example.conf
index d9c7efa29a..65a0cae2d7 100644
--- a/etc/example.conf
+++ b/etc/example.conf
@@ -75,8 +75,14 @@ fs=yes # Enlarges movie window to your desktop's size.
# ffactor = 0.75
##
-## FBdev driver: specify your monitor's timings, so resolutions
-## can be autodetected.
+## FBdev driver:
+
+# fb = /dev/fb0 # framebuffer device to use
+# fbmode = 640x480-120 # use this mode (read from fb.modes!)
+# fbmodeconfig = /etc/fb.modes # the fb.modes file
+
+## VESA and FBdev driver: specify your monitor's timings
+##
## (see for example /etc/X11/XF86Config for timings!)
## ** CAUTION! IF YOUR DISPLAY DOESN'T SUPPORT AUTOMATICALLY TURNING OFF WHEN
## OVERDRIVED (AND EVEN IF IT DOES), THIS MAY CAUSE DAMAGE TO YOUR DISPLAY!
@@ -85,10 +91,6 @@ fs=yes # Enlarges movie window to your desktop's size.
## k, K : means multiply by 1000
## m, M : means multiply by 1.000.000
##
-
-# fb = /dev/fb0 # framebuffer device to use
-# fbmode = 640x480-120 # use this mode (read from fb.modes!)
-# fbmodeconfig = /etc/fb.modes # the fb.modes file
# monitor_hfreq = 31.5k-50k,70k # horizontal frequency range
# monitor_vfreq = 50-90 # vertical frequency range
# monitor_dotclock = 30M-300M # dotclock (or pixelclock) range