From 7d5ae10689c3a12e37251c541d7d5a6373bf4b8c Mon Sep 17 00:00:00 2001 From: arpi Date: Mon, 7 Oct 2002 11:27:20 +0000 Subject: [PATCH] documenting vesa 3 / GTF config patch by Rudolf Marek git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@7652 b3059339-0415-0410-9bf9-f77b7e298cf2 --- DOCS/video.html | 10 +++++++++- etc/example.conf | 14 ++++++++------ 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 @@

2.3.1.11 VESA - output to VESA BIOS

This driver was designed and introduced as a generic driver 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.
VESA BIOS EXTENSION (VBE) Version 3.0 Date: September 16, 1998 (Page 70) says:

@@ -752,6 +752,10 @@ in vm86 mode).
  • You can use Vidix with it, thus getting accelerated video display AND TV output at the same time! (recommended for ATI cards)
    • +
  • 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 ALL monitor's options.

    • Disadvantages:

    @@ -774,6 +778,10 @@
    -double
    enables double buffering mode. (Available only in DGA mode). Should be slower of single buffering, but has no flickering effects.
    +
    -monitor_hfreq
    +
    -monitor_vfreq
    +
    -monitor_dotclock
    +
    Important values, see example.conf

    Known problems and workaround:

    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