summaryrefslogtreecommitdiffstats
path: root/DOCS/video.html
diff options
context:
space:
mode:
Diffstat (limited to 'DOCS/video.html')
-rw-r--r--DOCS/video.html10
1 files changed, 9 insertions, 1 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>