DOCS/xml: updates

Drop one pointless subsectioning level from radio input chapter.

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

Remove subsection that describes how to tweak CD/DVD drives.
It is getting outdated and outside the scope of MPlayer documentation.

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

Remove pointless and non-informative SDL section from video output chapter.

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

Drop one level of pointless subsectioning.

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

Split TV chapter in two.
This avoids a chapter without content apart from the (sub)sections.

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

Remove MTRR section from video output chapter.
The information it contains should be irrelevant in 2010.

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

Remove graphics cards subsections from Xv section in video output chapter.
The information contained is very outdated.

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

5 files changed, 22 insertions, 433 deletions

diff --git a/DOCS/xml/en/cd-dvd.xml b/DOCS/xml/en/cd-dvd.xml
index 535f62fe08..fb198da5e3 100644
--- a/DOCS/xml/en/cd-dvd.xml
+++ b/DOCS/xml/en/cd-dvd.xml
@@ -3,109 +3,6 @@
 <chapter id="cd-dvd">
 <title>CD/DVD usage</title>
 
-<sect1 id="drives">
-<title>CD/DVD drives</title>
-
-<para>
-Modern CD-ROM drives can attain very high head speeds, yet some CD-ROM drives
-are capable of running at reduced speeds. There are several reasons that might
-make you consider changing the speed of a CD-ROM drive:
-</para>
-
-<itemizedlist>
-<listitem><para>
-  There have been reports of read errors at high speeds, especially
-  with badly pressed CD-ROMs. Reducing the speed can prevent data loss under
-  these circumstances.
-</para></listitem>
-
-<listitem><para>
-  Many CD-ROM drives are annoyingly loud, a lower speed may reduce the noise.
-</para></listitem>
-</itemizedlist>
-
-<!-- ********** -->
-
-<sect2 id="drives_linux">
-<title>Linux</title>
-
-<para>
-You can reduce the speed of IDE CD-ROM drives with <command>hdparm</command>,
-<command>setcd</command> or <command>cdctl</command>. It works like this:
-<screen>hdparm -E <replaceable>[speed]</replaceable> <replaceable>[cdrom device]</replaceable></screen>
-<screen>setcd -x <replaceable>[speed]</replaceable> <replaceable>[cdrom device]</replaceable></screen>
-<screen>cdctl -bS <replaceable>[speed]</replaceable></screen>
-</para>
-
-<para>
-If you are using SCSI emulation, you might have to apply the settings to the
-real IDE device, not the emulated SCSI device.
-</para>
-
-<para>
-If you have root privileges the following command may also help:
-<screen>echo file_readahead:2000000 &gt; /proc/ide/<replaceable>[cdrom device]</replaceable>/settings</screen>
-</para>
-
-<para>
-This sets prefetched file reading to 2MB, which helps with scratched CD-ROMs.
-If you set it to too high, the drive will continuously spin up and down, and
-will dramatically decrease the performance.
-It is recommended that you also tune your CD-ROM drive
-with <command>hdparm</command>:
-<screen>hdparm -d1 -a256 -u1 <replaceable>[cdrom device]</replaceable></screen>
-</para>
-
-<para>
-This enables DMA access, read-ahead, and IRQ unmasking (read the
-<command>hdparm</command> man page for a detailed explanation).
-</para>
-
-<para>
-Please refer to
-"<filename>/proc/ide/<replaceable>[cdrom device]</replaceable>/settings</filename>"
-for fine-tuning your CD-ROM.
-</para>
-
-<para>
-You may tweak the speed of SCSI CD-ROM drives with
-<command>sdparm</command>, you need version 1.03 or higher:
-<screen>sdparm --command=speed=<replaceable>[speed in kB/s]</replaceable> <replaceable>[cdrom device]</replaceable></screen>
-Speed must be specified in kilobytes per second, the drive will
-round it as appropriate. Please refer to the sdparm man page for
-details.
-</para>
-
-<para>
-There is also a dedicated tool that works for
-<ulink url="http://das.ist.org/~georg/">Plextor SCSI drives</ulink>.
-</para>
-</sect2>
-
-<!-- ********** -->
-
-<sect2 id="drives_freebsd">
-<title>FreeBSD</title>
-
-<para>speed:
-<screen>
-cdcontrol [-f <replaceable>device</replaceable>] speed <replaceable>[speed]</replaceable>
-</screen>
-</para>
-
-<para>DMA:
-<screen>
-sysctl hw.ata.atapi_dma=1
-</screen>
-</para>
-
-</sect2>
-
-</sect1>
-
-
-<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
-
 
 <sect1 id="dvd">
 <title>DVD playback</title>
diff --git a/DOCS/xml/en/faq.xml b/DOCS/xml/en/faq.xml
index 164843589d..ea54989b8c 100644
--- a/DOCS/xml/en/faq.xml
+++ b/DOCS/xml/en/faq.xml
@@ -848,8 +848,7 @@ My DVD playback is sluggish!
 </para></question>
 <answer><para>
 Use the <option>-cache</option> option (described in the man page) and try
-enabling DMA for the DVD drive with the <command>hdparm</command> tool
-(described in the <link linkend="drives">CD chapter</link>).
+enabling DMA for the DVD drive with the <command>hdparm</command> tool.
 </para></answer>
 </qandaentry>
 
diff --git a/DOCS/xml/en/radio.xml b/DOCS/xml/en/radio.xml
index 5d3e69eba6..75dd481311 100644
--- a/DOCS/xml/en/radio.xml
+++ b/DOCS/xml/en/radio.xml
@@ -3,9 +3,6 @@
 <chapter id="radio">
 <title>Radio</title>
 
-<sect1 id="radio-input" xreflabel="Radio input">
-<title>Radio input</title>
-
 <para>
 This section is about how to enable listening to radio from
 a V4L-compatible radio tuner. See the man page for a
@@ -14,7 +11,7 @@ description of radio options and keyboard controls.
 
 <!-- ********** -->
 
-<sect2 id="radio-compilation">
+<sect1 id="radio-compilation">
 <title>Compilation</title>
 
 <procedure>
@@ -28,11 +25,11 @@ description of radio options and keyboard controls.
   example <application>XawTV</application>.
 </para></step>
 </procedure>
-</sect2>
+</sect1>
 
 <!-- ********** -->
 
-<sect2 id="radio-tips">
+<sect1 id="radio-tips">
 <title>Usage tips</title>
 
 <para>
@@ -65,11 +62,11 @@ Here are just a few tips:
 </para></listitem>
 </itemizedlist>
 </para>
-</sect2>
+</sect1>
 
 <!-- ********** -->
 
-<sect2 id="radio-examples">
+<sect1 id="radio-examples">
 <title>Examples</title>
 
 <informalexample><para>
@@ -105,7 +102,6 @@ by equal signs, commas by periods.
 </para></note>
 </para>
 </informalexample>
-</sect2>
 </sect1>
 
 </chapter>
diff --git a/DOCS/xml/en/tvinput.xml b/DOCS/xml/en/tvinput.xml
index c89b7acf00..8e3853bedf 100644
--- a/DOCS/xml/en/tvinput.xml
+++ b/DOCS/xml/en/tvinput.xml
@@ -1,9 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <!-- $Revision$ -->
-<chapter id="tv">
-<title>TV</title>
-
-<sect1 id="tv-input" xreflabel="TV input">
+<chapter id="tv-input" xreflabel="TV input">
 <title>TV input</title>
 
 <para>
@@ -14,7 +11,7 @@ of TV options and keyboard controls.
 
 <!-- ********** -->
 
-<sect2 id="tv-compilation">
+<sect1 id="tv-compilation">
 <title>Compilation</title>
 
 <procedure>
@@ -29,11 +26,11 @@ of TV options and keyboard controls.
   example <application>XawTV</application>.
 </para></step>
 </procedure>
-</sect2>
+</sect1>
 
 <!-- ********** -->
 
-<sect2 id="tv-tips">
+<sect1 id="tv-tips">
 <title>Usage tips</title>
 
 <para>
@@ -128,11 +125,11 @@ Here are just a few tips:
 </para></listitem>
 </itemizedlist>
 </para>
-</sect2>
+</sect1>
 
 <!-- ********** -->
 
-<sect2 id="tv-examples">
+<sect1 id="tv-examples">
 <title>Examples</title>
 
 <informalexample><para>
@@ -177,14 +174,14 @@ uses the maximum available information and is a little more resistant to noise.
 The bt8x8 chips can do the pixel averaging only in the horizontal direction due
 to a hardware limitation.
 </para></informalexample>
-</sect2>
 </sect1>
+</chapter>
 
 
 <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
 
 
-<sect1 id="tv-teletext">
+<chapter id="tv-teletext">
 <title>Teletext</title>
 
 <para>
@@ -192,7 +189,7 @@ to a hardware limitation.
   for v4l and v4l2 drivers.
 </para>
 
-<sect2 id="tv-teletext-implementation-notes">
+<sect1 id="tv-teletext-implementation-notes">
 <title>Implementation notes</title>
 
 <para>
@@ -209,9 +206,9 @@ starting to receive TV input, so you do not need to wait until the requested pag
 <para>
 Note: Using teletext with <option>-vo xv</option> causes strange colors.
 </para>
-</sect2>
+</sect1>
 
-<sect2 id="tv-teletext-usage">
+<sect1 id="tv-teletext-usage">
 <title>Using teletext</title>
 
 <para>
@@ -231,9 +228,9 @@ Here is an example for Russian:
 
 <para>
 </para>
-</sect2>
+</sect1>
 
-<sect2 id="tv-teletext-hotkeys">
+<sect1 id="tv-teletext-hotkeys">
 <title>Teletext hot keys</title>
 
 <informaltable frame="all">
@@ -269,7 +266,6 @@ Here is an example for Russian:
 </tbody>
 </tgroup>
 </informaltable>
-</sect2>
 </sect1>
 
 </chapter>
diff --git a/DOCS/xml/en/video.xml b/DOCS/xml/en/video.xml
index 249e0adcc9..72c7559408 100644
--- a/DOCS/xml/en/video.xml
+++ b/DOCS/xml/en/video.xml
@@ -3,92 +3,6 @@
 <chapter id="video">
 <title>Video output devices</title>
 
-<sect1 id="mtrr">
-<title>Setting up MTRR</title>
-
-<para>
-It is VERY recommended to check if the MTRR registers
-are set up properly, because they can give a big performance boost.
-</para>
-
-<para>
-Do a <command>cat /proc/mtrr</command>:
-<screen>
-<prompt>--($:~)--</prompt> cat /proc/mtrr
-reg00: base=0xe4000000 (3648MB), size=  16MB: write-combining, count=9
-reg01: base=0xd8000000 (3456MB), size= 128MB: write-combining, count=1<!--
---></screen>
-</para>
-
-<para>
-It's right, shows my Matrox G400 with 16MB memory. I did this from
-XFree 4.x.x, which sets up MTRR registers automatically.
-</para>
-
-<para>
-If nothing worked, you have to do it manually. First, you have to find the
-base address. You have 3 ways to find it:
-
-<orderedlist>
-<listitem><para>
-  from X11 startup messages, for example:
-  <screen>
-(--) SVGA: PCI: Matrox MGA G400 AGP rev 4, Memory @ 0xd8000000, 0xd4000000
-(--) SVGA: Linear framebuffer at 0xD8000000<!--
-  --></screen>
-</para></listitem>
-<listitem><para>
-  from <filename>/proc/pci</filename> (use <command>lspci -v</command>
-  command):
-  <screen>
-01:00.0 VGA compatible controller: Matrox Graphics, Inc.: Unknown device 0525
-Memory at d8000000 (32-bit, prefetchable)<!--
-  --></screen>
-</para></listitem>
-<listitem><para>
-  from mga_vid kernel driver messages (use <command>dmesg</command>):
-  <screen>mga_mem_base = d8000000</screen>
-</para></listitem>
-</orderedlist>
-</para>
-
-<para>
-Then let's find the memory size. This is very easy, just convert video RAM
-size to hexadecimal, or use this table:
-<informaltable frame="none">
-<tgroup cols="2">
-<tbody>
-  <row><entry>1 MB</entry><entry>0x100000</entry></row>
-  <row><entry>2 MB</entry><entry>0x200000</entry></row>
-  <row><entry>4 MB</entry><entry>0x400000</entry></row>
-  <row><entry>8 MB</entry><entry>0x800000</entry></row>
-  <row><entry>16 MB</entry><entry>0x1000000</entry></row>
-  <row><entry>32 MB</entry><entry>0x2000000</entry></row>
-</tbody>
-</tgroup>
-</informaltable>
-</para>
-
-<para>
-You know base address and memory size, let's setup MTRR registers!
-For example, for the Matrox card above (<literal>base=0xd8000000</literal>)
-with 32MB ram (<literal>size=0x2000000</literal>) just execute:
-<screen>
-echo "base=0xd8000000 size=0x2000000 type=write-combining" &gt; /proc/mtrr
-</screen>
-</para>
-
-<para>
-Not all CPUs have MTRRs. For example older K6-2 (around 266MHz,
-stepping 0) CPUs don't have MTRRs, but stepping 12 does
-(execute <command>cat /proc/cpuinfo</command> to check it).
-</para>
-</sect1>
-
-
-<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
-
-
 <sect1 id="xv">
 <title>Xv</title>
 
@@ -160,182 +74,6 @@ screen #0
 </para></listitem>
 </orderedlist>
 </para>
-
-
-<sect2 id="tdfx">
-<title>3dfx cards</title>
-
-<para>
-Older 3dfx drivers were known to have problems with XVideo acceleration, it
-didn't support YUY2 or YV12 colorspaces. Verify that you have XFree86
-version 4.2.0 or later, it can handle YV12 and YUY2 while previous
-versions, including 4.1.0, <emphasis role="bold">crash with YV12</emphasis>.
-If you experience strange effects using <option>-vo xv</option>, try SDL
-(it has XVideo, too) and see if it helps. Check the
-<link linkend="sdl">SDL</link> section for details.
-</para>
-
-<para>
-<emphasis role="bold">OR</emphasis>, try the NEW
-<option>-vo tdfxfb</option> driver! See the <link linkend="tdfxfb">tdfxfb</link>
-section.
-</para>
-</sect2>
-
-
-<sect2 id="s3">
-<title>S3 cards</title>
-
-<para>
-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: there is
-xv support, but the card itself is very slow, so you better sell it.
-</para>
-
-<para>
-There is now a native framebuffer driver for S3 Virge cards similar to
-tdfxfb. Set up your framebuffer (e.g. append
-"<option>vga=792 video=vesa:mtrr</option>" to your kernel command line) and use
-<option>-vo s3fb</option> (<option>-vf yuy2</option> and <option>-dr</option>
-will also help).
-</para>
-
-<note><para>
-It's currently unclear which Savage models lack YV12 support, and convert by
-driver (slow). If you suspect your card, get a newer driver, or ask politely
-on the MPlayer-users mailing list for an MMX/3DNow! enabled driver.
-</para></note>
-</sect2>
-
-
-<sect2 id="nvidia">
-<title>nVidia cards</title>
-
-<para>
-nVidia isn't always a very good choice under Linux ... XFree86's
-open-source driver supports most of these cards, but for some cases, you'll
-have to use the binary closed-source nVidia driver, available at
-<ulink url="http://www.nvidia.com/object/linux.html">nVidia's web site</ulink>.
-You'll always need this driver if you want 3D acceleration, too.
-</para>
-
-<para>
-Riva128 cards don't have XVideo support with XFree86's nVidia driver :(
-Complain to nVidia.
-</para>
-
-<para>
-However, <application>MPlayer</application> contains a
-<link linkend="vidix">VIDIX</link> driver for most nVidia cards. Currently it
-is in beta stage, and has some drawbacks. For more information, see
-<link linkend="vidix-nvidia">nVidia VIDIX</link> section.
-</para>
-</sect2>
-
-
-<sect2 id="ati">
-<title>ATI cards</title>
-
-<para>
-The <ulink url="http://gatos.sf.net">GATOS driver</ulink>
-(which you should use, unless you have Rage128 or Radeon) has VSYNC enabled
-by default. It means that decoding speed (!) is synced to the monitor's
-refresh rate. If playing seems to be slow, try disabling VSYNC somehow, or
-set refresh rate to a n*(fps of the movie) Hz.
-</para>
-
-<para>
-Radeon VE - if you need X, use XFree86 4.2.0 or greater for this card.
-No TV out support. Of course with <application>MPlayer</application> you can
-happily get <emphasis role="bold">accelerated</emphasis> display, with or
-without <emphasis role="bold">TV output</emphasis>, and no libraries or X are
-needed.
-Read the <link linkend="vidix">VIDIX</link> section.
-</para>
-</sect2>
-
-
-<sect2 id="neomagic">
-<title>NeoMagic cards</title>
-
-<para>
-These cards can be found in many laptops. You must use XFree86 4.3.0 or
-above, or else use Stefan Seyfried's
-<ulink url="http://www.mplayerhq.hu/MPlayer/contrib/NeoMagic-driver/">Xv-capable drivers</ulink>.
-Just choose the one that applies to your version of XFree86.
-</para>
-
-<para>
-XFree86 4.3.0 includes Xv support, yet Bohdan Horst sent a small
-<ulink url="http://www.mplayerhq.hu/MPlayer/contrib/NeoMagic-driver/neo_driver.patch">patch</ulink>
-against the XFree86 sources that speeds up framebuffer operations (so XVideo)
-up to four times. The patch has been included in XFree86 CVS and should be in
-the next release after 4.3.0.
-</para>
-
-<para>
-To allow playback of DVD sized content change your XF86Config like this:
-<programlisting>
-Section "Device"
-    [...]
-    Driver "neomagic"
-    <emphasis>Option "OverlayMem" "829440"</emphasis>
-    [...]
-EndSection<!--
---></programlisting>
-</para>
-</sect2>
-
-
-<sect2 id="trident">
-<title>Trident cards</title>
-
-<para>
-If you want to use Xv with a Trident card, provided that it doesn't work
-with 4.1.0, install XFree 4.2.0. 4.2.0 adds support for fullscreen Xv
-support with the Cyberblade XP card.
-</para>
-
-<para>
-Alternatively, <application>MPlayer</application> contains a
-<link linkend="vidix">VIDIX</link> driver for the Cyberblade/i1 card.
-</para>
-</sect2>
-
-
-<sect2 id="kyro">
-<title>Kyro/PowerVR cards</title>
-
-<para>
-If you want to use Xv with a Kyro based card (for example Hercules
-Prophet 4000XT), you should download the drivers from the
-<ulink url="http://www.powervr.com/">PowerVR site</ulink>.
-</para>
-</sect2>
-
-
-<sect2 id="intel">
-<title>Intel cards</title>
-
-<para>
-These cards can be found in many laptops. Recent Xorg is recommended.
-</para>
-
-<para>
-To allow playback of DVD sized (and larger) content change your XF86Config/xorg.conf like this:
-<programlisting>
-Section "Device"
-    [...]
-    Driver "intel"
-    <emphasis>Option "LinearAlloc" "6144"</emphasis>
-    [...]
-EndSection
-</programlisting>
-Lack of this option usually results in an error like
-<screen>X11 error: BadAlloc (insufficient resources for operation)</screen>
-when attempting to use <option>-vo xv</option>.
-</para>
-</sect2>
 </sect1>
 
 <!-- ********** -->
@@ -628,39 +366,6 @@ with every chipset driver for XFree out there.
 
 <!-- ********** -->
 
-<sect1 id="sdl">
-<title>SDL</title>
-
-<para>
-<acronym>SDL</acronym> (Simple Directmedia Layer) is basically a unified
-video/audio interface. Programs that use it know only about SDL, and not
-about what video or audio driver does SDL actually use. For example a Doom
-port using SDL can run on svgalib, aalib, X, fbdev, and others, you only
-have to specify the (for example) video driver to use with the
-<envar>SDL_VIDEODRIVER</envar> environment variable. Well, in theory.
-</para>
-
-<para>
-With <application>MPlayer</application>, we used its X11 driver's software
-scaler ability for cards/drivers that doesn't support XVideo, until we made
-our own (faster, nicer) software scaler. Also we used its aalib output, but
-now we have ours which is more comfortable. Its DGA mode was better than
-ours, until recently. Get it now? :)
-</para>
-
-<para>
-It also helps with some buggy drivers/cards if the video is jerky (not slow
-system problem), or audio is lagging.
-</para>
-
-<para>
-SDL video output supports displaying subtitles under the movie, on the (if
-present) black bar.
-</para>
-</sect1>
-
-<!-- ********** -->
-
 <sect1 id="svgalib">
 <title>SVGAlib</title>
 
@@ -2175,10 +1880,7 @@ problems, or DVD subtitle problems, give <option>:sync</option> a try.
 <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
 
 
-<sect1 id="other">
-<title>Other visualization hardware</title>
-
-<sect2 id="zr">
+<sect1 id="zr">
 <title>Zr</title>
 
 <para>
@@ -2275,11 +1977,11 @@ during playback, it will crash your computer. It is, however, fine to
 wait for <application>MPlayer</application>
 to finish and <emphasis role="bold">THEN</emphasis> stop XawTV.
 </para>
-</sect2>
+</sect1>
 
 <!-- ********** -->
 
-<sect2 id="blinkenlights">
+<sect1 id="blinkenlights">
 <title>Blinkenlights</title>
 
 <para>
@@ -2294,7 +1996,6 @@ has to offer. Just watch some of the
 On the Arcade video you can see the Blinkenlights output driver in
 action at 00:07:50.
 </para>
-</sect2>
 </sect1>