mpv/drivers
diego 9c3c0cb83a warning fixes:
mga_vid_test.c: In function ‘main’:
mga_vid_test.c:157: warning: unused parameter ‘argc’
mga_vid_test.c:157: warning: unused parameter ‘argv’
tdfx_vid_test.c: In function ‘main’:
tdfx_vid_test.c:26: warning: unused parameter ‘argc’
tdfx_vid_test.c:26: warning: unused parameter ‘argv’


git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@24307 b3059339-0415-0410-9bf9-f77b7e298cf2
2007-08-31 11:57:57 +00:00
..
3dfx.h
Makefile Build test programs with standard CFLAGS and use implicit rules. 2007-08-29 09:19:07 +00:00
README.Ati
README.Matrox
generic_math.h
hacking.ati
mga_vid.c ISO8859-1 --> UTF-8 2007-07-09 19:50:36 +00:00
mga_vid.h sync mga_vid.h to the one in the mga_vid repo. 2007-03-18 10:52:41 +00:00
mga_vid_test.c warning fixes: 2007-08-31 11:57:57 +00:00
radeon.h
radeon_vid.c
radeon_vid.h
tdfx_vid.c warning fix: 2007-08-29 09:21:06 +00:00
tdfx_vid.h
tdfx_vid_test.c warning fixes: 2007-08-31 11:57:57 +00:00

README.Matrox

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.