github/mpv
1
Fork 0
mirror of https://github.com/mpv-player/mpv synced 2024-11-14 22:48:35 +01:00
Code Releases Activity
e3bce499be
mpv/drivers
History
arpi c912f043de obsolete, no one seems to be interested to fix/update/finish this 
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@7277 b3059339-0415-0410-9bf9-f77b7e298cf2
2002-09-04 23:53:12 +00:00
..
radeon removed -W -Wall -g and other gcc-specific warning/debug options 2002-08-22 23:29:46 +00:00
.cvsignore FFmpeg libavcodec directory is unknown to CVS, as is mga_vid_test. 2002-07-13 15:10:33 +00:00
3dfx.h Fixed some breakages of single-buffer rendering of tdfx 2002-08-29 12:04:21 +00:00
Makefile removed -W -Wall -g and other gcc-specific warning/debug options 2002-08-22 23:29:46 +00:00
mga_vid_test.c When compiling mga_vid_test.c, memcpy() is subject to an implicit 2002-05-31 21:42:15 +00:00
mga_vid.c - fixed overflow by +-0x80 2002-07-25 21:34:24 +00:00
mga_vid.h min() moved out of #if, applied brightness/contrast patch by Brian J. Murrell 2002-03-10 03:36:16 +00:00
README Initial revision 2001-02-24 20:28:24 +00:00

README 

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.