comparison DOCS/video.html @ 9260:ea27d0f2d90d

Small fixes and modelines moved to a more sensible place.
author diego
date Mon, 03 Feb 2003 22:08:32 +0000
parents c82e31b31194
children 513e02e2e553
comparison
equal deleted inserted replaced
9259:1a21ce1da8d8 9260:ea27d0f2d90d
218 218
219 219
220 <H4><A NAME="dga">2.3.1.2.2 DGA</A></H4> 220 <H4><A NAME="dga">2.3.1.2.2 DGA</A></H4>
221 221
222 222
223 <H5>PREAMBLE</H4> 223 <H5>PREAMBLE</H5>
224 224
225 <P>This section tries to explain in some words what DGA is in general and what 225 <P>This section tries to explain in some words what DGA is in general and what
226 the DGA video output driver for MPlayer can do (and what it can't).</P> 226 the DGA video output driver for MPlayer can do (and what it can't).</P>
227 227
228 228
303 config file on startup and disables the modelines not suitable for your 303 config file on startup and disables the modelines not suitable for your
304 hardware. You can find out which modes survive with the X11 log file. It can 304 hardware. You can find out which modes survive with the X11 log file. It can
305 be found at: 305 be found at:
306 <CODE>/var/log/XFree86.0.log</CODE>.</P> 306 <CODE>/var/log/XFree86.0.log</CODE>.</P>
307 307
308 <P>See some working modeline definitions <A HREF="#dga_modelines">here</A>.</P> 308 <P>These entries are known to work fine with a Riva128 chip, using the
309 <CODE>nv.o</CODE> X server driver module.</P>
310
311 <PRE>
312 Section "Modes"
313 Identifier "Modes[0]"
314 Modeline "800x600" 40 800 840 968 1056 600 601 605 628
315 Modeline "712x600" 35.0 712 740 850 900 400 410 412 425
316 Modeline "640x480" 25.175 640 664 760 800 480 491 493 525
317 Modeline "400x300" 20 400 416 480 528 300 301 303 314 Doublescan
318 Modeline "352x288" 25.10 352 368 416 432 288 296 290 310
319 Modeline "352x240" 15.750 352 368 416 432 240 244 246 262 Doublescan
320 Modeline "320x240" 12.588 320 336 384 400 240 245 246 262 Doublescan
321 EndSection
322 </PRE>
309 323
310 324
311 <H5>DGA &amp; MPLAYER</H5> 325 <H5>DGA &amp; MPLAYER</H5>
312 326
313 <P>DGA is used in two places with MPlayer: The SDL driver can be made to 327 <P>DGA is used in two places with MPlayer: The SDL driver can be made to
396 <LI>Some drivers simply display strange colors.</LI> 410 <LI>Some drivers simply display strange colors.</LI>
397 <LI>Some drivers lie about the amount of memory they map into the process's 411 <LI>Some drivers lie about the amount of memory they map into the process's
398 address space, thus vo_dga won't use doublebuffering (SIS?).</LI> 412 address space, thus vo_dga won't use doublebuffering (SIS?).</LI>
399 <LI>Some drivers seem to fail to report even a single valid mode. In this 413 <LI>Some drivers seem to fail to report even a single valid mode. In this
400 case the DGA driver will crash telling you about a nonsense mode of 414 case the DGA driver will crash telling you about a nonsense mode of
401 100000x100000 or someathing like that.</LI> 415 100000x100000 or something like that.</LI>
402 <LI>OSD only works with doublebuffering enabled (else it flickers).</LI> 416 <LI>OSD only works with doublebuffering enabled (else it flickers).</LI>
403 </UL> 417 </UL>
404
405
406 <H5><A NAME="dga_modelines">SOME MODELINES</A></H5>
407
408 <PRE>
409 Section "Modes"
410 Identifier "Modes[0]"
411 Modeline "800x600" 40 800 840 968 1056 600 601 605 628
412 Modeline "712x600" 35.0 712 740 850 900 400 410 412 425
413 Modeline "640x480" 25.175 640 664 760 800 480 491 493 525
414 Modeline "400x300" 20 400 416 480 528 300 301 303 314 Doublescan
415 Modeline "352x288" 25.10 352 368 416 432 288 296 290 310
416 Modeline "352x240" 15.750 352 368 416 432 240 244 246 262 Doublescan
417 Modeline "320x240" 12.588 320 336 384 400 240 245 246 262 Doublescan
418 EndSection
419 </PRE>
420
421 <P>These entries work fine with authors (Acki) Riva128 chip, using nv.o X server driver
422 module.</P>
423 418
424 419
425 <H4><A NAME="sdl">2.3.1.2.3 SDL</A></H4> 420 <H4><A NAME="sdl">2.3.1.2.3 SDL</A></H4>
426 421
427 <P>SDL (Simple Directmedia Layer) is basically a unified video/audio 422 <P>SDL (Simple Directmedia Layer) is basically a unified video/audio
572 567
573 568
574 <H4><A NAME="mga_vid">2.3.1.2.6 Matrox framebuffer (mga_vid)</A></H4> 569 <H4><A NAME="mga_vid">2.3.1.2.6 Matrox framebuffer (mga_vid)</A></H4>
575 570
576 <P>This section is about the Matrox G200/G400/G450/G550 BES (Back-End Scaler) 571 <P>This section is about the Matrox G200/G400/G450/G550 BES (Back-End Scaler)
577 support, the mga_vid kernel driver. It's active developed by A'rpi, and 572 support, the mga_vid kernel driver. It's actively developed by A'rpi, and
578 it has hardware VSYNC support with triple buffering. It works on both 573 it has hardware VSYNC support with triple buffering. It works on both
579 framebuffer console and under X.</P> 574 framebuffer console and under X.</P>
580 575
581 <P><B>NOTE</B>: This is Linux only! On non-Linux (tested on FreeBSD) systems, 576 <P><B>NOTE</B>: This is Linux only! On non-Linux (tested on FreeBSD) systems,
582 you can use <A HREF="#vidix">VIDIX</A> instead!</P> 577 you can use <A HREF="#vidix">VIDIX</A> instead!</P>
898 and MPlayer doesn't do it automatically. Please tell about it to the 893 and MPlayer doesn't do it automatically. Please tell about it to the
899 developers. The Right Way is to use VIDIX without arguments to enable driver 894 developers. The Right Way is to use VIDIX without arguments to enable driver
900 autodetection.</P> 895 autodetection.</P>
901 896
902 <P>VIDIX is a new technology and it's extremely possible that on your system 897 <P>VIDIX is a new technology and it's extremely possible that on your system
903 it won't work. In this case the only solution for you is porting (mainly 898 it won't work. In this case the only solution for you is porting it (mainly
904 libdha) it. But there is a hope, that it will work on those systems where X11 899 libdha). But there is hope that it will work on systems where X11 does.</P>
905 does.</P>
906 900
907 <P>Since VIDIX requires direct hardware access you can either run it as root or 901 <P>Since VIDIX requires direct hardware access you can either run it as root or
908 set the SUID bit on the MPlayer binary (<B>Warning: This is a security 902 set the SUID bit on the MPlayer binary (<B>Warning: This is a security
909 risk!</B>). Alternatively, you can use a special kernel module, like this:</P> 903 risk!</B>). Alternatively, you can use a special kernel module, like this:</P>
910 904
919 <LI>Compile the module in the <CODE>svgalib_helper</CODE> directory (it can 913 <LI>Compile the module in the <CODE>svgalib_helper</CODE> directory (it can
920 be found inside the <CODE>svgalib-1.9.17/kernel/</CODE> directory if you've 914 be found inside the <CODE>svgalib-1.9.17/kernel/</CODE> directory if you've
921 downloaded the source from the svgalib site) and insmod it.</LI> 915 downloaded the source from the svgalib site) and insmod it.</LI>
922 <LI>Move the <CODE>svgalib_helper</CODE> directory to 916 <LI>Move the <CODE>svgalib_helper</CODE> directory to
923 <CODE>mplayer/main/libdha/svgalib_helper</CODE>.</LI> 917 <CODE>mplayer/main/libdha/svgalib_helper</CODE>.</LI>
924 <LI>Required if you download the source from the svgalib site: remove the 918 <LI>Required if you download the source from the svgalib site: Remove the
925 comment before the CFLAGS line containing "svgalib_helper" string from the 919 comment before the CFLAGS line containing "svgalib_helper" string from the
926 <CODE>libdha/Makefile</CODE>.</LI> 920 <CODE>libdha/Makefile</CODE>.</LI>
927 <LI>Recompile and install libdha.</LI> 921 <LI>Recompile and install libdha.</LI>
928 </OL> 922 </OL>
929 923