comparison DOCS/VIDEOCARDS @ 749:550e3ff06099

big review ! (translators curse me:)
author gabucino
date Thu, 10 May 2001 09:48:03 +0000
parents b93cc18c3596
children 6d49b76acf04
comparison
equal deleted inserted replaced
748:717e4677d9ce 749:550e3ff06099
76 II. OpenGL drivers with *working* *fast* glTexSubImage() support. 76 II. OpenGL drivers with *working* *fast* glTexSubImage() support.
77 77
78 Currently only the old Utah-GLX drivers (for X 3.3.6) have it. 78 Currently only the old Utah-GLX drivers (for X 3.3.6) have it.
79 See http://utah-glx.sourceforge.net for details about how to install it. 79 See http://utah-glx.sourceforge.net for details about how to install it.
80 80
81 The new X4/DRI and nVidia's binary drivers has no usable glTexSubImage :( 81 The new X4/DRI and nVidia's binary drivers have no usable glTexSubImage :(
82 82
83 III. Native card-specific drivers 83 III. Native card-specific drivers
84 84
85 There is 3 native drivers for Linux: 85 There is 3 native drivers for Linux:
86 1. Matrox G200/G400/G450 BES (Back-End Scaler) support -> mga_vid kernel drv. 86 1. Matrox G200/G400/G450 BES (Back-End Scaler) support -> mga_vid kernel drv.
87 It's active developed by me (A'rpi), and it has hardware VSYNC support 87 It's active developed by me (A'rpi), and it has hardware VSYNC support
88 with triple buffering. It works on both framebuffer console and under X. 88 with triple buffering. It works on both framebuffer console and under X.
89 89
90 To use, simply compile the mga_vid.o in the drivers/ subdir (type: make) 90 To use, simply compile the mga_vid.o in the drivers/ subdir (type: make)
91 and load it with insmod mga_vid.o. You should verify the memory size 91 create /dev/mga_vid device :
92 mknod /dev/mga_vid c 178 0
93 and load the driver with insmod mga_vid.o. You should verify the memory size
92 detection using the 'dmesg' command. If it's bad, use the mga_ram_size 94 detection using the 'dmesg' command. If it's bad, use the mga_ram_size
93 option (rmmod mga_vid first), specify card's memory size in MB: 95 option (rmmod mga_vid first), specify card's memory size in MB:
94 insmod mga_vid.o mga_ram_size=16 96 insmod mga_vid.o mga_ram_size=16
97 To make it load/unload automatically when needed, insert the following line
98 at the end of /etc/modules.conf :
99 alias char-major-178 mga_vid
95 100
96 Using it from MPlayer: (you should re-compile it with mga_vid support...) 101 Using it from MPlayer: (you should re-compile it with mga_vid support...)
97 102
98 Use the 'mga' vo driver on framebuffer console (matroxfb): -vo mga 103 Use the 'mga' vo driver on framebuffer console (matroxfb): -vo mga
99 and use the xmga driver for X 3.3.x: -vo xmga 104 and use the xmga driver for X 3.3.x: -vo xmga
156 Of course you'll have to install svgalib and its development package in 161 Of course you'll have to install svgalib and its development package in
157 order for MPlayer build its SVGAlib driver (autodetected, but can be 162 order for MPlayer build its SVGAlib driver (autodetected, but can be
158 forced), and don't forget to edit /etc/vga/libvga.config to suit your 163 forced), and don't forget to edit /etc/vga/libvga.config to suit your
159 card & monitor. 164 card & monitor.
160 165
166 Try the aalib target ('-vo sdl -sdl aalib'), it's great! :)
161 167
162 b, You want to use framebuffer... 168 b, You want to use framebuffer...
163 ... Whether to build the FBdev target is autodetected during ./configure . 169 ... Whether to build the FBdev target is autodetected during ./configure .
164 Read the framebuffer documentation in the kernel sources 170 Read the framebuffer documentation in the kernel sources
165 (Documentation/fb/*) for info on how to enable it, etc.. ! 171 (Documentation/fb/*) for info on how to enable it, etc.. !
166 172
167 ... but your card doesn't support VBE 2.0 standard (older ISA/PCI 173 ... but your card doesn't support VBE 2.0 standard (older ISA/PCI
168 cards, such as S3 Trio64) : 174 cards, such as S3 Trio64), only VBE 1.2 (or older?) :
169 Well, VESAfb is still available, but you'll have to load SciTech Display 175 Well, VESAfb is still available, but you'll have to load SciTech Display
170 Doctor (formerly UniVBE) before booting Linux. Use a DOS boot disk or 176 Doctor (formerly UniVBE) before booting Linux. Use a DOS boot disk or
171 whatever. And don't forget to register your UniVBE ;)) 177 whatever. And don't forget to register your UniVBE ;))
172 178
173 NOTE : FBdev video mode changing _does not work_ with the VESA framebuffer, 179 NOTE : FBdev video mode changing _does not work_ with the VESA framebuffer,