view drivers/README.Matrox @ 23572:a00685941686

demux_mkv very long seek fix The seek code searching for the closest position in the index used "int64_t min_diff=0xFFFFFFFL" as the initial "further from the goal than any real alternative" value. The unit is milliseconds so seeks more than about 75 hours past the end of the file would fail to recognize the last index position as the best match. This was triggered in practice by chapter seek code which apparently uses a seek of 1000000000 seconds forward to mean "seek to the end". The practical effect was that trying to seek to the next chapter in a file without chapters made MPlayer block until it finished reading the file from the current position to the end. Fixed by increasing the initial value from FFFFFFF to FFFFFFFFFFFFFFF.
author uau
date Wed, 20 Jun 2007 18:19:03 +0000
parents 544914dadb52
children 0ad2da052b2e
line wrap: on
line source

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.