summaryrefslogtreecommitdiffstats
path: root/drivers/README.Matrox
diff options
context:
space:
mode:
authordiego <diego@b3059339-0415-0410-9bf9-f77b7e298cf2>2007-03-17 21:27:42 +0000
committerdiego <diego@b3059339-0415-0410-9bf9-f77b7e298cf2>2007-03-17 21:27:42 +0000
commitf20d1b16a895f5949851aacd70f24da046164670 (patch)
tree946781a9c942f05e338ac821eb974cd791f83cb5 /drivers/README.Matrox
parenta261d54b0188fd00a620e0ab78520393a67b3a09 (diff)
downloadmpv-f20d1b16a895f5949851aacd70f24da046164670.tar.bz2
mpv-f20d1b16a895f5949851aacd70f24da046164670.tar.xz
Move files from radeon/ subdirectory here.
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@22709 b3059339-0415-0410-9bf9-f77b7e298cf2
Diffstat (limited to 'drivers/README.Matrox')
-rw-r--r--drivers/README.Matrox46
1 files changed, 46 insertions, 0 deletions
diff --git a/drivers/README.Matrox b/drivers/README.Matrox
new file mode 100644
index 0000000000..ae641ab452
--- /dev/null
+++ b/drivers/README.Matrox
@@ -0,0 +1,46 @@
+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.