Mercurial > mplayer.hg
view drivers/README.Matrox @ 25157:cf3b6015735d
Set protocol for the vo proxy used in shared-buffer mode.
NOTE: You have to update your mplayerosx to svn r148 or newer to work with it.
This change will speed up vo proxy and fix all these warnings:
vo_macosx.m: In function 'config':
vo_macosx.m:165: warning: 'NSProxy' may not respond to '-startWithWidth:withHeight:withBytes:withAspect:'
vo_macosx.m:165: warning: (Messages without a matching method signature
vo_macosx.m:165: warning: will be assumed to return 'id' and accept
vo_macosx.m:165: warning: '...' as arguments.)
vo_macosx.m: In function 'flip_page':
vo_macosx.m:183: warning: 'NSProxy' may not respond to '-render'
vo_macosx.m: In function 'uninit':
vo_macosx.m:235: warning: 'NSProxy' may not respond to '-stop'
vo_macosx.m: In function 'control':
vo_macosx.m:334: warning: 'NSProxy' may not respond to '-ontop'
vo_macosx.m:336: warning: 'NSProxy' may not respond to '-toggleFullscreen'
author | ulion |
---|---|
date | Wed, 28 Nov 2007 00:01:35 +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.