aboutsummaryrefslogtreecommitdiffhomepage
path: root/drivers/README.Matrox
diff options
context:
space:
mode:
authorGravatar wm4 <wm4@mplayer2.org>2012-07-28 17:37:45 +0200
committerGravatar wm4 <wm4@mplayer2.org>2012-07-28 20:44:25 +0200
commitcf9587fc048be4e7d8dabb6644eac24e2d736ea3 (patch)
tree2cbe5a538e54fe56f53a585967b82625349c362b /drivers/README.Matrox
parentf53dcf163da2d94b7fd2b1257ede8cf91e6ce301 (diff)
Remove ancient kernel device drivers
These were device driver kernel modules for certain prehistoric graphic cards. The source code indicates these are written against early 2.4 kernels.
Diffstat (limited to 'drivers/README.Matrox')
-rw-r--r--drivers/README.Matrox46
1 files changed, 0 insertions, 46 deletions
diff --git a/drivers/README.Matrox b/drivers/README.Matrox
deleted file mode 100644
index 48a37ed057..0000000000
--- a/drivers/README.Matrox
+++ /dev/null
@@ -1,46 +0,0 @@
-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.