comparison DOCS/xml/en/video.xml @ 11359:496ff2403aac

buglets and consistency improvements
author diego
date Sun, 02 Nov 2003 13:03:27 +0000
parents 7d120a00fcf7
children 853ef483a4c0
comparison
equal deleted inserted replaced
11358:7d120a00fcf7 11359:496ff2403aac
10 It is VERY recommended to check if the MTRR registers 10 It is VERY recommended to check if the MTRR registers
11 are set up properly, because they can give a big performance boost. 11 are set up properly, because they can give a big performance boost.
12 </para> 12 </para>
13 13
14 <para> 14 <para>
15 Do a <command>/proc/mtrr</command>: 15 Do a <command>cat /proc/mtrr</command>:
16 <screen> 16 <screen>
17 <prompt>--($:~)--</prompt> cat /proc/mtrr 17 <prompt>--($:~)--</prompt> cat /proc/mtrr
18 reg00: base=0xe4000000 (3648MB), size= 16MB: write-combining, count=9 18 reg00: base=0xe4000000 (3648MB), size= 16MB: write-combining, count=9
19 reg01: base=0xd8000000 (3456MB), size= 128MB: write-combining, count=1<!-- 19 reg01: base=0xd8000000 (3456MB), size= 128MB: write-combining, count=1<!--
20 --></screen> 20 --></screen>
78 </screen> 78 </screen>
79 </para> 79 </para>
80 80
81 <para> 81 <para>
82 Not all CPUs support MTRRs. For example older K6-2's (around 266MHz, 82 Not all CPUs support MTRRs. For example older K6-2's (around 266MHz,
83 stepping 0) doesn't support MTRR, but stepping 12's do (<command>cat /proc/cpuinfo 83 stepping 0) doesn't support MTRR, but stepping 12's do
84 </command> to check it). 84 (<command>cat /proc/cpuinfo</command> to check it).
85 </para> 85 </para>
86 </sect3> 86 </sect3>
87 87
88 <sect3 id="output-trad"> 88 <sect3 id="output-trad">
89 <title>Video outputs for traditional video cards</title> 89 <title>Video outputs for traditional video cards</title>
90 <sect4 id="xv"> 90 <sect4 id="xv">
91 <title>Xv</title> 91 <title>Xv</title>
92 92
93 <para> 93 <para>
94 Under XFree86 4.0.2 or newer, you can use your card's hardware YUV routines 94 Under XFree86 4.0.2 or newer, you can use your card's hardware YUV routines
95 using the XVideo extension. This is what the option '<option>-vo 95 using the XVideo extension. This is what the option
96 xv</option>' uses. Also, this is driver supports adjusting 96 '<option>-vo xv</option>' uses. Also, this driver supports adjusting
97 brightness/contrast/hue/etc (unless you use the old, slow DirectShow DivX 97 brightness/contrast/hue/etc (unless you use the old, slow DirectShow DivX
98 codec, which supports it everywhere), see the man page. 98 codec, which supports it everywhere), see the man page.
99 </para> 99 </para>
100 100
101 <para> 101 <para>
2025 2025
2026 <para> 2026 <para>
2027 Extra occurrences of <option>-zrcrop</option> invoke <emphasis>cinerama</emphasis> 2027 Extra occurrences of <option>-zrcrop</option> invoke <emphasis>cinerama</emphasis>
2028 mode, i.e. you can distribute the movie over several TV's or beamers to create a 2028 mode, i.e. you can distribute the movie over several TV's or beamers to create a
2029 larger screen. Suppose you have two beamers. The left one is connected to your 2029 larger screen. Suppose you have two beamers. The left one is connected to your
2030 Buz at <systemitem>/dev/video1</systemitem> and the right one is connected to 2030 Buz at <filename>/dev/video1</filename> and the right one is connected to
2031 your DC10+ at <systemitem>/dev/video0</systemitem>. The movie has a resolution 2031 your DC10+ at <filename>/dev/video0</filename>. The movie has a resolution
2032 of 704x288. Suppose also that you want the right beamer in black and white and 2032 of 704x288. Suppose also that you want the right beamer in black and white and
2033 that the left beamer should have JPEG frames at quality 10, then you would 2033 that the left beamer should have JPEG frames at quality 10, then you would
2034 issue the following command 2034 issue the following command
2035 <screen> 2035 <screen>
2036 mplayer -vo zr -zrdev /dev/video0 -zrcrop 352x288+352+0 -zrxdoff 0 -zrbw \ 2036 mplayer -vo zr -zrdev /dev/video0 -zrcrop 352x288+352+0 -zrxdoff 0 -zrbw \