view drivers/README @ 19422:718624aec009

r19361: Reintroduce an ugly variant of the -gui/-nogui options. r19348: Add matroska chapter seeking capability. r19286: clarification on -mpegopts :vaspect r19285: New sentences should start on a new line. r19281: don't use vaspect on mpeg1 video streams r19274: Move the section describing the per movie config files up, so it doesn't get seperated from the rest of the config file doc by the config file example r19241: missed some escaping r19240: use DOCS writing standards for default values (asked by diego) r19233: english manpage for pvr:// input r19231: updated en/fr manpages for ao_ivtv r19228: removed default outfile for -ao mpegpes r19206: Improve ao_mpegpes description. r19191: description of the arnd scale video filter parameter r19190: new -ao mpegpes options r19181: - Add missing "00" in -af pan usage line. - Change -af pan usage and description to use a capital 'L' to make the letter easily distinguishable from a '1'. r19161: cosmetics/punctuation/spelling r19149: updated english man page with vo_ivtv description
author kraymer
date Thu, 17 Aug 2006 21:57:01 +0000
parents 3b5f5d1c5041
children 6d257bd87fce
line wrap: on
line source


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 xserver. 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 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 approriate 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 frame buffer (if it knows the right padding, etc).


How do I know if mga_vid works on my system?

	There are test applications called mga_vid_test_g400 and mga_vid_test_g200.
	Use the appropriate one for your card. This test code should draw some
	nice 256x256 images for you if all is working well.