Mercurial > mplayer.hg

view drivers/README.Matrox @ 32434:acb796d7ca50

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Make mencoder account for encoder delay when considering the current time position of a muxer stream. To mencoder core, delayed frames should be considered as "dealt with", since they'll get to the muxer eventually. Without this compensation, mencoder will sometimes make different frame skip/duplicate decisions on the first of a two-pass x264 encode (since x264 buffers many more frames on the first pass), leading to a segfault in x264 when it gets fed more frames on the second pass.
author corey
date Thu, 21 Oct 2010 07:05:30 +0000
parents 0ad2da052b2e
children
line wrap: on
line source

The code in this directory is the old mga_vid driver for Linux kernels
prior to 2.6. It does _not_ compile for version 2.6.x.

For Linux kernel 2.6.x please get the newest version of the 2.6 port from
http://attila.kinali.ch/mga/


mga_vid  -  MGA G200/G400 YUV Overlay kernel module

        Author:
                Aaron Holtzman <aholtzma@ess.engr.uvic.ca>, Oct 1999

        Contributions by:
                Fredrik Vraalsen <vraalsen@cs.uiuc.edu>
                Alan Cox <alan@lxorguk.ukuu.org.uk>

                       WARNING  -----  WARNING

This code messes with your video card and your X server. It will probably
lock up your box, format your hard drive, and cause your brand new G400
MAX to spout 6 inch flames. You have been warned.

                       WARNING  -----  WARNING

What does this code do?

         mga_vid is a kernel module that utilitizes the Matrox G200/G400/G550
         video scaler/overlay unit to perform YUV->RGB colorspace conversion
         and arbitrary video scaling.

         mga_vid is also a monster hack.

How does mga_vid work?

        This kernel module sets up the BES (backend scaler) with appropriate
        values based on parameters supplied via ioctl. It also maps a chunk of
        video memory into userspace via mmap. This memory is stolen from X
        (which may decide to write to it later). The application can then write
        image data directly to the framebuffer (if it knows the right padding,
        etc).


How do I know if mga_vid works on my system?

        There is a test application called mga_vid_test. This test code should
        draw some nice 256x256 images for you if all is working well.