mostly fixes, some updates

git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@3028 b3059339-0415-0410-9bf9-f77b7e298cf2

5 files changed, 138 insertions, 85 deletions

diff --git a/DOCS/codecs.html b/DOCS/codecs.html
index eae011670b..0d08b47e7b 100644
--- a/DOCS/codecs.html
+++ b/DOCS/codecs.html
@@ -155,11 +155,13 @@ option to tell <B>MPlayer</B> to use them if possible.</P>
 <P><B><A NAME=2.2.1.4>2.2.1.4.  VIVO video</A></B></P>
 
 <P><B>MPlayer</B> can play Vivo (1.0 and 2.0) videos. The most suitable codec
-for this task is XAnim's H263 decoder codec (it supports fast YV12 output), you
-can call it with the <CODE>-vc h263xa</CODE> option. Of course you have to
-compile XAnim codecs support it, for details see the <A HREF=#2.2.1.3>XAnim
-video codecs</A>. If this doesn't work, get the <CODE>ivvideo.dll</CODE> DLL
-file (from <A HREF="http://www.mplayerhq.hu/MPlayer/samples/drivers32/ivvideo.dll">here</A>),
+for 1.0 files is FFmpeg's H263 decoder, you can use it with the <CODE>-vc
+ffh263</CODE> option (you'll need the newest libavcodec !). For 2.0 files, use
+XAnim's H263 decoder codec (it supports fast YV12 output). You can call it with
+the <CODE>-vc h263xa</CODE> option. Of course you have to compile XAnim codecs
+support in, for details see the <A HREF=#2.2.1.3>XAnim video codecs</A>. If
+this doesn't work, get the <CODE>ivvideo.dll</CODE> DLL file (from <A
+HREF="http://www.mplayerhq.hu/MPlayer/samples/drivers32/ivvideo.dll">here</A>),
 and install it under <CODE>/usr/lib/win32</CODE> or wherever you store the
 Win32 codecs. This latter codec doesn't support YV12 nor YUY2 only BGR modes,
 thus usable only with the X11 and OpenGL outputs. Discouraged.</P>
diff --git a/DOCS/documentation.html b/DOCS/documentation.html
index 35abd51f53..3d506491be 100644
--- a/DOCS/documentation.html
+++ b/DOCS/documentation.html
@@ -144,6 +144,7 @@
       <LI><A HREF="#6.3">6.3 Solaris</A></LI>
       <LI><A HREF="#6.4">6.4 StrongARM</A></LI>
       <LI><A HREF="#6.5">6.5 SGI/Irix</A></LI>
+      <LI><A HREF="#6.6">6.6 QNX</A></LI>
     </UL>
   <LI><A HREF="#A">A. Authors</A></LI>
   <UL>
@@ -269,16 +270,13 @@ experience any problems:<BR>
 <LI>If you have <B>gcc 2.96</B> on your system, <A HREF="users_against_developers.html"><B><I>READ
 THIS!!!</I></B></A></LI>
 
-<LI>If you plan to use <B>MPlayer</B> on x86 architecture, you possibly want to use
-Win32 codecs. If you only want to play DVDs and DivXes, you probably don't
-want these, since the <B>libavcodec</B>'s DivX decoder (see below) is the
-fastest decoder available, and DVD is decoded with the <B>libmpeg2</B>
-library.<BR>
-If you want to play or encode for example movies recorded with digital cameras (example:
-DV), you must install them. Download and unzip w32codecs.zip to /usr/lib/win32 .
-Note: the avifile project has similar codecs package, but it differs
-from ours, so if you want to use all supported codecs, then use
-our package! However, you can use our codecs package with avifile.</LI>
+<LI>If you plan to use <B>MPlayer</B> on x86 architecture, you possibly want to
+use Win32 codecs. If you want to play or encode for example movies recorded
+with digital cameras (example: DV), you must install them. Download and unzip
+w32codecs.zip to /usr/lib/win32 . Note: the avifile project has similar codecs
+package, but it differs from ours, so if you want to use all supported codecs,
+then use our package! However, you can use our codecs package with
+avifile.</LI>
 
 <LI>If you own a Matrox G200/G400/G450/G550 card, then please see the <A HREF="video.html#2.3.1.7">mga_vid</A>
 section in order to gain big speedup. It is important to do these steps
@@ -293,9 +291,10 @@ otherwise no 3Dfx support will be built. Also see the <A HREF="video.html#2.3.1.
 TV out section</A>.</LI>
 
 <LI>If you own an ATI card, see the <A HREF="video.html#2.3.1.A.2">ATI cards
-section</A> of the TV-out documentation, to know what features of your card is supported under Linux/MPlayer.
-If you have a <B>Radeon</B> card, we have a <B>radeon_vid</B> driver for you !
-Check <A HREF="video.html#2.3.1.14">this</A> section !</LI>
+section</A> of the TV-out documentation, to know what features of your card is
+supported under Linux/MPlayer. If you have a <B>Radeon</B> card, we have a
+<B>radeon_vid</B> driver for you, with TV out ! Check <A
+HREF="video.html#2.3.1.14">this</A> section !</LI>
 
 <LI>If you plan to use the ProjectMayo's <B>DivX4</B> codec, check the
 <A HREF="codecs.html#2.2.1.1">2.2.1.1</A> section before compiling.
@@ -334,9 +333,9 @@ encode movies with <B>MPlayer</B>, read the <A HREF=#2.5>TV input</A> section.</
     make
     make install</PRE>
 
-<P><B><I>ALWAYS browse the output of ./configure</I></B> , it contains info
-about what will be built, and what won't. You may also want to view
-config.h and config.mak files.</P>
+<P><B><I>ALWAYS browse the output of ./configure</I></B>, and the
+<CODE>configure.log</CODE> file, they contain info about what will be built,
+and what won't. You may also want to view config.h and config.mak files.</P>
 
 <P>Though not mandatory, the fonts should be installed in order to gain
 OSD, and subtitle functionality. Download mp-arial-iso-8859-*.zip and/or optional
@@ -570,13 +569,6 @@ TV tuner</B>.</P>
 </TR>
 <TR>
   <TD>&nbsp;&nbsp;</TD>
-  <TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2><I>freq</I></TD>
-  <TD>&nbsp;&nbsp;</TD>
-  <TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>
-  set the tuner to the given frequency (like 511.250)</TD>
-</TR>
-<TR>
-  <TD>&nbsp;&nbsp;</TD>
   <TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2><I>channel</I></TD>
   <TD>&nbsp;&nbsp;</TD>
   <TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>
@@ -684,7 +676,7 @@ support using  ./configure --enable-lirc</P>
 
 <P>If everything went fine, <B>MPlayer</B> will print a message like
 LIRC init was successful.
-on startup. If an error occurs it will tell you. If it doens't tell you
+on startup. If an error occurs it will tell you. If it doesn't tell you
 anything about LIRC there's no support compiled in. That's it :-)</P>
 
 <P>The application name for <B>MPlayer</B> is - oh wonder - mplayer_lirc.
@@ -886,6 +878,13 @@ all data is accessed modulo 4GB
 Anyone has closer info?</P>
 
 
+<P><B><A NAME=6.6>6.6. QNX</A></B></P>
+
+<P>Works. Only has <CODE>-vo x11</CODE> output which is even much slower
+than on Linux, since QNX has only X <I>emulation</I> which is VERY slow.
+No closer info yet.</P>
+
+
 <P><B><A NAME=A>Appendix A - Authors</A></B></P>
 
 <P>NOTE: Do *NOT* send bugreports, help &amp; feature requests directly to the authors!</P>
diff --git a/DOCS/encoding.html b/DOCS/encoding.html
index 119c8b0e9f..a0c41ba614 100644
--- a/DOCS/encoding.html
+++ b/DOCS/encoding.html
@@ -17,23 +17,23 @@ other interesting stuff.</P>
 <P><B><I>Compiling</I></B>
   <UL>
     <LI>read <B>MPlayer</B>'s compilation instructions, it contains info about
-    how to install <I>libdvdread</I> for <B>DVD</B> support, etc.</LI>
+      how to install <I>libdvdread</I> for <B>DVD</B> support, etc.</LI>
     <LI>download the newest <B>DivX4linux</B> libs
-    from <A HREF="http://avifile.sourceforge.net/download.htm">avifile.sourceforge.net</A>,
-    and have them PROPERLY installed. This is needed for DivX4 (1/2 pass)
-    encoding.</LI>
+      from <A HREF="http://avifile.sourceforge.net/download.htm">avifile.sourceforge.net</A>,
+      and have them PROPERLY installed. This is needed for DivX4 (1/2 pass)
+      encoding. And since this is mandatory (now), MEncoder is Linux-only.</LI>
     <LI>download and install <B>libmp3lame</B> (from lame 3.89beta or lame CVS). This
-    is needed for CBR/VBR MP3 audio encoding ability. Note that a single
-    <CODE>lame</CODE> binary isn't sufficient. BTW: the less optimization
-    you use for lame, the better the quality will be. You can test
-    quality by running <CODE>make test</CODE> after lame's compiling process
-    is over. The resulting number should be less than <B>30</B>. Don't
-    panic if it's <B>400</B> or so, you shouldn't heard any audible
-    quality decrease. Oh, and if your compiler doesn't even run <CODE>make test</CODE> ...
-    Well, delete that <B>GCC 2.96</B>.</LI>
+      is needed for CBR/VBR MP3 audio encoding ability. Note that a single
+      <CODE>lame</CODE> binary isn't sufficient. BTW: the less optimization
+      you use for lame, the better the quality will be. You can test
+      quality by running <CODE>make test</CODE> after lame's compiling process
+      is over. The resulting number should be less than <B>30</B>. Don't
+      panic if it's <B>400</B> or so, you shouldn't heard any audible
+      quality decrease. Oh, and if your compiler doesn't even run <CODE>make test</CODE> ...
+      Well, delete that <B>GCC 2.96</B>.</LI>
     <LI>use <CODE>./configure</CODE> with optional parameters as usual
-    (use <CODE>--enable-tv</CODE> to include V4L tuner grabbing code), and
-    type : <CODE>make mencoder</CODE> , then <CODE>make install</CODE> .
+      (use <CODE>--enable-tv</CODE> to include V4L tuner grabbing code), and
+      type : <CODE>make mencoder</CODE> , then <CODE>make install</CODE>.</LI>
   </UL>
 </P>
 
@@ -67,11 +67,11 @@ other interesting stuff.</P>
 <P><B><I>Encoding 2-pass DivX4</I></B></P>
 
 <P>The name comes from the fact that this method encodes the file <I>twice</I>.
-The first encoding (dubbed <I>pass</I>) creates a temporary file with a size
-of few megabytes. In the second pass, the output file is created, using the
-bitrate data from the temporary file. The resulting file will have much
-better image quality. If this is the first time you heard about this, you
-should consult some guides available on the Net.</P>
+The first encoding (dubbed <I>pass</I>) creates some temporary files with a
+size of few megabytes (do not delete them yet). In the second pass, the output
+file is created, using the bitrate data from the temporary file. The resulting
+file will have much better image quality. If this is the first time you heard
+about this, you should consult some guides available on the Net.</P>
 
 <P>This example shows how to encode a DVD to a 2-pass DivX4 AVI. Just two
 commands are needed :<BR>
diff --git a/DOCS/formats.html b/DOCS/formats.html
index d1e2fa6bed..42d1cf4b2a 100644
--- a/DOCS/formats.html
+++ b/DOCS/formats.html
@@ -113,7 +113,7 @@ playable, the other is neither.</P>
 supported by most of the players. The file format makes it possible to use VBR
 audio, but most players expect CBR audio, thus they fail with VBR. VBR is
 unusual, and Microsoft's AVI specs only describe CBR audio. I also note, that
-most AVI encoders/multiplexers create bad files if using VBR audio. only 2
+most AVI encoders/multiplexers create bad files if using VBR audio. Only 2
 exception (known by me): NaNDub and <A HREF="encoding.html">MEncoder</A>.</P>
 
 
@@ -132,7 +132,9 @@ v2.0 files :) . Note, that .ASF files nowdays come with the extension .WMA or
 
 <P>These are from Macintosh. Usually have extensions of .QT or .MOV . Note
 that since the MPEG4 Group chose QuickTime as the recommended file format
-for MPEG4, their .MOV files come with .MPG or .MP4 extension.</P>
+for MPEG4, their .MOV files come with .MPG or .MP4 extension (interesting
+that in these files the video stream is a real .MPG file. With the
+<CODE>-dumpvideo</CODE> option you can even extract it.).</P>
 
 <P><B>Codecs</B>: any codecs allowed, both CBR and VBR. Note: most new mov files use
 <B>Sorenson</B> video and QDesign Music audio. These formats are completely
diff --git a/DOCS/video.html b/DOCS/video.html
index 9ad970064b..83d6a37b49 100644
--- a/DOCS/video.html
+++ b/DOCS/video.html
@@ -9,39 +9,86 @@
 
 <TD COLSPAN=4><P><B><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>General:</B></P></TD><TR>
 
-<TD>&nbsp;&nbsp;</TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2><A HREF=#2.3.1.13>x11</A></TD><TD>&nbsp;&nbsp;</TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>X11 with optional SHM extension</TD><TR>
-<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2><A HREF=#2.3.1.2>xv</A></TD><TD></TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>X11 using overlays with the Xvideo extension (hardware YUV & scaling)</TD><TR>
-<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2><A HREF=#2.3.1.10</A></TD><TD></TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>OpenGL renderer, so far works only with:
+<TD>&nbsp;&nbsp;</TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica,
+  sans-serif" size=2><A HREF=#2.3.1.13>x11</A></TD><TD>&nbsp;&nbsp;</TD><TD><FONT
+  face="Verdana, Arial, Helvetica, sans-serif" size=2>X11 with optional SHM
+  extension</TD><TR>
+<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2><A HREF=#2.3.1.2>xv</A></TD><TD></TD><TD><FONT face="Verdana, Arial,
+  Helvetica, sans-serif" size=2>X11 using overlays with the Xvideo extension
+  (hardware YUV & scaling)</TD><TR>
+<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2><A HREF=#2.3.1.10>gl</A></TD><TD></TD><TD><FONT face="Verdana, Arial,
+  Helvetica, sans-serif" size=2>OpenGL renderer, so far works only with:
 <UL><LI>all cards with Utah-GLX
 <LI>Matrox cards with X/DRI >=4.0.3
 <LI>Radeon with X/DRI CVS</UL></TD><TR>
-<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2><A HREF=#2.3.1.3>dga</A></TD><TD></TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>X11 DGA extension</TD><TR>
-<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2><A HREF=#2.3.1.6>fbdev</A></TD><TD></TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Output to general framebuffers</TD><TR>
-<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2><A HREF=#2.3.1.5>svga</A></TD><TD></TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Output to SVGAlib</TD><TR>
-<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2><A HREF=#2.3.1.4>sdl</A></TD><TD></TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>
+<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2><A HREF=#2.3.1.3>dga</A></TD><TD></TD><TD><FONT face="Verdana, Arial,
+  Helvetica, sans-serif" size=2>X11 DGA extension</TD><TR>
+<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2><A HREF=#2.3.1.6>fbdev</A></TD><TD></TD><TD><FONT face="Verdana, Arial,
+  Helvetica, sans-serif" size=2>Output to general framebuffers</TD><TR>
+<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2><A HREF=#2.3.1.5>svga</A></TD><TD></TD><TD><FONT face="Verdana, Arial,
+  Helvetica, sans-serif" size=2>Output to SVGAlib</TD><TR>
+<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2><A HREF=#2.3.1.4>sdl</A></TD><TD></TD><TD><FONT face="Verdana, Arial,
+  Helvetica, sans-serif" size=2>
 &nbsp;&nbsp;<CODE>1.1.7:</CODE> supports software scaling<BR>
 &nbsp;&nbsp;<CODE>1.1.8:</CODE> supports Xvideo (hardware scaling/fullscreen)<BR>
 &nbsp;&nbsp;<CODE>1.2.0:</CODE> supports AAlib (-vo aa is very recommended, see below!)</TD><TR>
-<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2><A HREF=#2.3.1.14-TODO>ggi</A></TD><TD></TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>similar to SDL</TD><TR>
-<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2><A HREF=#2.3.1.11>aa</A></TD><TD></TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>textmode rendering with AAlib</TD><TR>
-<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2><a href=#2.3.1.12>vesa</a></TD><TD></TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Output to VESA BIOS.</TD><TR>
-
-<TD COLSPAN=4><P><B><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Card specific:</B></P></TD><TR>
-
-<TD>&nbsp;&nbsp;</TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2><A HREF=#2.3.1.7>mga</A></TD><TD>&nbsp;&nbsp;</TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Matrox G200/G400 hardware YUV overlay via the mga_vid device</TD><TR>
-<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2><A HREF=#2.3.1.7>xmga</A></TD><TD></TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Matrox G200/G400 overlay (mga_vid) in X11 window<BR>
+<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2><A HREF=#2.3.1.14-TODO>ggi</A></TD><TD></TD><TD><FONT face="Verdana,
+  Arial, Helvetica, sans-serif" size=2>similar to SDL</TD><TR>
+<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2><A HREF=#2.3.1.11>aa</A></TD><TD></TD><TD><FONT face="Verdana, Arial,
+  Helvetica, sans-serif" size=2>textmode rendering with AAlib</TD><TR>
+<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2><a href=#2.3.1.12>vesa</a></TD><TD></TD><TD><FONT face="Verdana, Arial,
+  Helvetica, sans-serif" size=2>Output to VESA BIOS.</TD><TR>
+
+<TD COLSPAN=4><P><B><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2>Card specific:</B></P></TD><TR>
+
+<TD>&nbsp;&nbsp;</TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica,
+  sans-serif" size=2><A HREF=#2.3.1.7>mga</A></TD><TD>&nbsp;&nbsp;</TD><TD><FONT
+  face="Verdana, Arial, Helvetica, sans-serif" size=2>Matrox G200/G400 hardware
+  YUV overlay via the mga_vid device</TD><TR>
+<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2><A HREF=#2.3.1.7>xmga</A></TD><TD></TD><TD><FONT face="Verdana, Arial,
+  Helvetica, sans-serif" size=2>Matrox G200/G400 overlay (mga_vid) in X11
+  window<BR>
 (<I>Xv emulation on X 3.3.x!</I>)</TD><TR>
-<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>syncfb</TD><TD></TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Matrox G400 YUV support on framebuffer (obsoleted, use mga/xmga)</TD><TR>
-<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>3dfx</TD><TD></TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Voodoo3/Banshee hardware YUV (/dev/3dfx) support (not yet tested, maybe
-broken)</TD><TR>
-<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2><A HREF=#2.3.1.9>tdfxfb</A></TD><TD></TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Voodoo3/Banshee hardware YUV support on tdfx framebuffer (works!)</TD><TR>
-
-<TD COLSPAN=4><P><B><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Special:</B></P></TD><TR>
-
-<TD>&nbsp;&nbsp;</TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>png</TD><TD>&nbsp;&nbsp;</TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>PNG files output (use -z switch to set compression)</TD><TR>
-<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>pgm</TD><TD></TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>PGM files output (for testing purposes or ffmpeg encoding)</TD><TR>
-<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>md5</TD><TD></TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>MD5sum output (for MPEG conformance tests)</TD><TR>
-<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>null</TD><TD></TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Null output (for speed tests/benchmarking)</TD><TR>
+<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2>syncfb</TD><TD></TD><TD><FONT face="Verdana, Arial, Helvetica,
+  sans-serif" size=2>Matrox G400 YUV support on framebuffer (obsoleted, use
+  mga/xmga)</TD><TR>
+<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2>3dfx</TD><TD></TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2>Voodoo3/Banshee hardware YUV (/dev/3dfx) support (not yet tested, maybe
+  broken)</TD><TR>
+<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2><A HREF=#2.3.1.9>tdfxfb</A></TD><TD></TD><TD><FONT face="Verdana, Arial,
+  Helvetica, sans-serif" size=2>Voodoo3/Banshee hardware YUV support on tdfx
+  framebuffer (works!)</TD><TR>
+
+<TD COLSPAN=4><P><B><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2>Special:</B></P></TD><TR>
+
+<TD>&nbsp;&nbsp;</TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica,
+  sans-serif" size=2>png</TD><TD>&nbsp;&nbsp;</TD><TD><FONT face="Verdana, Arial,
+  Helvetica, sans-serif" size=2>PNG files output (use -z switch to set
+  compression)</TD><TR>
+<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2>pgm</TD><TD></TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2>PGM files output (for testing purposes or ffmpeg encoding)</TD><TR>
+<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2>md5</TD><TD></TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2>MD5sum output (for MPEG conformance tests)</TD><TR>
+<TD></TD><TD VALIGN=top><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2>null</TD><TD></TD><TD><FONT face="Verdana, Arial, Helvetica, sans-serif"
+  size=2>Null output (for speed tests/benchmarking)</TD><TR>
 </TABLE>
 
 <P>NOTE: <I>check the following subsections for details and requirements!</I></P>
@@ -176,10 +223,10 @@ section!</P>
 <P>S3 Savage3D's should work fine, but for Savage4, use XFree86 version 4.0.3
 or greater (in case of image problems, try 16bpp). As for S3 Virge.. sell it.</P>
 
-<P><B>NOTE</B>: Savage4 has a slow YV12 image displaying capability (it needs
+<P><B>NOTE</B>: Savage cards have a slow YV12 image displaying capability (it needs
 to do YV12->YUY2 conversion, because the Savage hardware can't display YV12).
 So when this documentation says at some point "this has YV12 output use this,
-it's faster", you shouldn't. Stick to YUY2.</P>
+it's faster", it's not sure. Try.</P>
 
 
 <P><B><A NAME=2.3.1.2.3>2.3.1.2.3. nVidia cards</A></B></P>
@@ -201,11 +248,10 @@ Complain to NVidia.</UL></P>
 disabling VSYNC somehow, or set refresh rate to n*(fps of the movie) Hz.</LI>
 
 <LI>Radeon VE - currently only XFree86 CVS has driver for this card, version
-4.1.0 doesn't. Of course with <B>MPlayer</B> you can happily get
-<B>accelerated</B> display, with or without <B>TV output</B>, and no libraries
-or X are needed. Read <a href=#2.3.1.12>VESA driver</a> and <A
-HREF=#2.3.1.14>Radeon acceleration</A> sections).</LI>
-</P>
+4.1.0 doesn't. And no TV out support. Of course with <B>MPlayer</B> you can
+happily get <B>accelerated</B> display, with or without <B>TV output</B>, and
+no libraries or X are needed. Read <a href=#2.3.1.12>VESA driver</a> and <A
+HREF=#2.3.1.14>Radeon acceleration</A> sections).</LI> </P>
 
 
 <P><B><A NAME=2.3.1.2.5>2.3.1.2.5. NeoMagic cards</A></B></P>
@@ -890,7 +936,11 @@ we have no chance to get working TV-out on ATI.</P>
 <P>What's status of ATI's tv-out chips under Linux:
 <LI><b>ATI Mach64</b> has <i>ImpacTV</i> which is supported by gatos.
 <LI><b>ASIC Radeon VIVO</b> has <i>Rage Theatre</i> which is supported by gatos.
-<LI><b>Radeon VE</b> and <b>Rage PRO LT</b> have <i>ImpacTV2+</i> which is not supported under Linux.</P>
+<LI><b>Radeon VE</b> and <b>Rage PRO LT</b> have <i>ImpacTV2+</i> which is not supported under Linux.
+But with <B>MPlayer</B> you get <B>full hardware acceleration</B> and <B>TV out</B>
+for Radeons !
+Check <a href=#2.3.1.12>VESA driver</a> and <A HREF=#2.3.1.14>Radeon
+acceleration</A> sections.</P>
 
 <P>
 Fortunately, owners of fast enough CPUs (Duron, Celeron2 and better) <b>can watch
@@ -923,7 +973,7 @@ documentation.
 </P>
 
 
-<P><B><A NAME=2.3.1.A.4>2.3.1.A.4. Voodoo 3</A></B></P>
+<P><B><A NAME=2.3.1.A.3>2.3.1.A.3. Voodoo 3</A></B></P>
 
 <P>
 Check <A HREF="http://www.iki.fi/too/tvout-voodoo3-3000-xfree">this URL</A>.