view drivers/README.Matrox @ 36892:f50427ad9ff6

Internally map item 'potmeter' onto 'hpotmeter'. Former version of the GUI treated a potmeter very similar to a hpotmeter (the Win32 GUI still does so) and lots of skins are solely using potmeters instead of hpotmeters, although this doesn't make sense at all. The current version of the GUI is treating a potmeter differently, but in order to not break old skins, restore the old behaviour. For the X11/GTK GUI, a potmeter is now simply a hpotmeter with button=NULL and (button)width=(button)height=0. For the Win32 GUI (where skins unfortunately are handled a bit differently and things are more complicated) a potmeter is now a hpotmeter without button but (button)width=(widget)width and (button)height=(widget)height. Additionally, print a legacy information, because the item 'potmeter' is obsolete now and oughtn't be used any longer.
author ib
date Mon, 10 Mar 2014 17:32:29 +0000
parents 0ad2da052b2e
children
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.