view drivers/README @ 14337:d4a00d0614fb

1.814: sstep is usually inaccurate. 1.815: use a configurable-size ringbuffer instead of a pipe for buffering key events. 1.816: better explain -nodouble. 1.817: Add a file= suboption to set output file. (md5sum) 1.818: keyframes are more like 10 - 20 seconds apart, not 120 (was already corrected) 1.819: Some fixes and better wording, remove alsa9 and alsa1x audio output drivers and make some numeric options line up properly. 1.820: better mention -vo yuv4mpeg can change output filename

mga_vid  -  MGA G200/G400 YUV Overlay kernel module

	Author:
		Aaron Holtzman <[e-mail]>, Oct 1999

	Contributions by:
		Fredrik Vraalsen <[e-mail]>
		Alan Cox <[e-mail]>

                       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.