1XGI(4) Kernel Interfaces Manual XGI(4)
2
3
4
6 xgi - XGI video driver
7
9 Section "Device"
10 Identifier "devname"
11 Driver "xgi"
12 ...
13 EndSection
14
16 xgi is an XFree86 driver for XGI video chips. The driver is acceler‐
17 ated, and provides support for colordepths of 8, 16 and 24 bpp.
18 XVideo, Render and other extensions are supported as well.
19
21 The xgi driver supports PCI and AGP video cards based on the following
22 chipsets:
23
24 XGI5597/5598 XGI530/620 XGI6326/AGP/DVD XGI300/305 XGI540 XGI630/730
25 XGI315/H/PRO XGI550/551/552 XGI650/651/M650/661FX/M661FX/M661MX/740/741
26 XGI330 (Xabre) XGI760
27
28 In the following text, the following terms are used:
29
30 old series for XGI5597/5598, 530/620 and 6326/AGP/DVD
31
32 300 series for XGI300/305, 540 and 630/730
33
34 315/330 series for XGI315/H/PRO, 55x and (M)65x/(M)661xX/74x, 330, 760
35
36 Note: Support for 661FX, M661FX, M661MX, 741 and 760 is untested.
37
39 Please refer to XF86Config(5) for general configuration details. This
40 section only covers configuration details specific to this driver.
41
42 Detailed information on all supported options can be obtained at
43 http://www.winischhofer.net/linuxxgivga.shtml
44
45 This manpage only covers a subset of the supported options.
46
47 1. For all supported chipsets
48
49 The following driver Options are supported on all chipsets:
50
51 Option "NoAccel" "boolean"
52 Disable or enable 2D acceleration. Default: acceleration is
53 enabled.
54
55 Option "HWCursor" "boolean"
56 Enable or disable the HW cursor. Default: HWCursor is on.
57
58 Option "SWCursor" "boolean"
59 The opposite of HWCursor. Default: SWCursor is off.
60
61 Option "Rotate" "CW"
62 Rotate the display clockwise. This mode is unaccelerated, and
63 uses the Shadow Frame Buffer layer. Using this option disables
64 the Resize and Rotate extension (RandR). Default: no rotation.
65
66 Option "Rotate" "CCW"
67 Rotate the display counterclockwise. This mode is unaccelerated,
68 and uses the Shadow Frame Buffer layer. Using this option dis‐
69 ables the Resize and Rotate extension (RandR). Default: no
70 rotation.
71
72 Option "ShadowFB" "boolean"
73 Enable or disable use of the shadow framebuffer layer. Default:
74 Shadow framebuffer is off.
75
76 Option "CRT1Gamma" "boolean"
77 Enable or disable gamma correction. Default: Gamma correction
78 is on.
79
80 2. Old series specific information
81
82 The driver will auto-detect the amount of video memory present for all
83 these chips, but in the case of the 6326, it will limit the memory size
84 to 4MB. This is because the 6326's 2D engine can only address 4MB. The
85 remaining memory seems to be intended for 3D texture data, since only
86 the 3D engine can address RAM above 4MB. However, you can override this
87 limitation using the "VideoRAM" option in the Device section if your
88 board has more than 4MB and you need to use it. However, 2D accelera‐
89 tion, Xvideo and the HWCursor will be disabled in this case.
90
91 The driver will also auto-detect the maximum dotclock and DAC speed.
92 If you have problems getting high resolutions because of dot clock lim‐
93 itations, try using the "DacSpeed" option, also in the Device section.
94 However, this is not recommended for the 6326. For this chip, the
95 driver has two built-in modes for high resolutions which you should use
96 instead. These are named "XGI1280x1024-75" and "XGI1600x1200-60" and
97 they will be added to the list of default modes. To use these modes,
98 just place them in your Screen section. Example:
99
100 Modes "XGI1600x1200-60" "XGI1280x1024x75" "1024x768" ...
101
102 Of these modes, 1280x1024 is only available at 8, 15 and 16bpp.
103 1600x1200 is available at 8bpp only.
104
105 TV support for the 6326
106
107 TV output is supported for the 6326. The driver will auto detect a TV
108 connected and in this case add the following modes to the list of
109 default modes: "PAL800x600", "PAL800x600U", "PAL720x540", "PAL640x480",
110 "NTSC640x480", "NTSC640x480U" and "NTSC640x400". Use these modes like
111 the hi-res modes described above.
112
113 The following driver Options are supported on the old series:
114
115 Option "TurboQueue" "boolean"
116 Enable or disable TurboQueue mode. Default: off for 530/620, on
117 for the others
118
119 Option "FastVram" "boolean"
120 Enable or disable FastVram mode. Enabling this sets the video
121 RAM timing to one cycle per read operation instead of two
122 cycles. Disabling this will set two cycles for read and write
123 operations. Leaving this option out uses the default, which
124 varies depending on the chipset.
125
126 Option "NoHostBus" "boolean"
127 (XGI5597/5598 only). Disable CPU-to-VGA host bus support. This
128 speeds up CPU to video RAM transfers. Default: Host bus is
129 enabled.
130
131 Option "NoXVideo" "boolean"
132 Disable XV (XVideo) extension support. Default: XVideo is on.
133
134 Option "NoYV12" "boolean"
135 Disable YV12 Xv support. This might me required due to hardware
136 bugs in some chipsets. Disabling YV12 support forces Xv-aware
137 applications to use YUV2 or XShm for video output. Default:
138 YV12 support is on.
139
140 Option "TVStandard" "string"
141 (6326 only) Valid parameters are PAL or NTSC. The default is
142 set by a jumper on the card.
143
144 Option "TVXPosOffset" "integer"
145 (6326 only) This option allows tuning the horizontal position of
146 the image for TV output. The range is from -16 to 16. Default: 0
147
148 Option "TVYPosOffset" "integer"
149 (6326 only) This option allows tuning the vertical position of
150 the image for TV output. The range is from -16 to 16. Default: 0
151
152 Option "XGI6326TVEnableYFilter" "boolean"
153 (6326 only) This option allows enabling/disabling the Y (chroma)
154 filter for TV output.
155
156 Option "XGI6326TVAntiFlicker" "string"
157 (6326 only) This option allow enabling/disabling the anti
158 flicker facility for TV output. Possible parameters are OFF,
159 LOW, MED, HIGH or ADAPTIVE. By experience, ADAPTIVE yields the
160 best results, hence it is the default.
161
162 2. 300 and 315/330 series specific information
163
164 The 300 and 315/330 series feature two CRT controllers and very often
165 come with a video bridge for controlling LCD and TV output. Here‐
166 inafter, the term CRT1 refers to the VGA output of the chip, and CRT2
167 refers to either LCD, TV or secondary VGA. Due to timing reasons, only
168 one CRT2 output can be active at the same time. But this limitation
169 does not apply to using CRT1 and CRT2 at the same time which makes it
170 possible to run the driver in dual head mode.
171
172 The driver supports the following video bridges:
173
174 XGI301 XGI301B(-DH) XGI301C XGI301LV(X) XGI302LV
175
176 Instead of a video bridge, some machines have a LVDS transmitter to
177 control LCD panels, and a Chrontel 7005 or 7019 for TV output. All
178 these are supported as well.
179
180 About TV output
181
182 On the XGI301 and the Chrontel 7005, only resolutions up to 800x600 are
183 supported. On all others, resolutions up to 1024x768 are supported.
184 However, due to a hardware bug, Xvideo might be distorted on XGI video
185 bridges if running NTSC or PAL-M at 1024x768.
186
187 About XVideo support
188
189 XVideo is supported on all chipsets of both families. However, there
190 are some differences in hardware features which cause limitations. The
191 300 series as well as the XGI55x, M650, 651, 661FX, M661FX, and 741
192 support two video overlays. The XGI315/H/PRO, 650/740 and 330 support
193 only one such overlay. On chips with two overlays, one overlay is used
194 for CRT1, the other for CRT2. On the other chipsets, the option "XvOn‐
195 CRT2" can be used to select the desired output channel.
196
197 About Merged Framebuffer support
198
199 This mode is strongly recommended over Xinerama. Please see
200 http://www.winischhofer.net/linuxxgivga.shtml for detailed information.
201
202 About dual-head support
203
204 Dual head mode has some limitations as regards color depth and resolu‐
205 tion. Due to memory bandwidth limits, CRT1 might have a reduced maximum
206 refresh rate if running on higher resolutions than 1280x1024.
207
208 Colordepth 8 is not supported when running in dual head mode.
209
210 The following driver Options are supported on the 300 and 315/330
211 series:
212
213 Option "NoXVideo" "boolean"
214 Disable XV (XVideo) extension support. Default: XVideo is on.
215
216 Option "XvOnCRT2" "boolean"
217 On chipsets with only one video overlay, this option can used to
218 bind the overlay to CRT1 ( if a monitor is detected and if this
219 option is either unset or set to false ) or CRT2 ( if a CRT2
220 device is detected or forced, and if this option is set to true
221 ). If either only CRT1 or CRT2 is detected, the driver decides
222 automatically. In Merged Framebuffer mode, this option is
223 ignored. Default: overlay is used on CRT1
224
225 Option "ForceCRT1" "boolean"
226 Force CRT1 to be on of off. If a monitor is connected, it will
227 be detected during server start. However, some old monitors are
228 not detected correctly. In such cases, you may set this option
229 to on in order to make the driver initialize CRT1 anyway. If
230 this option is set to off , the driver will switch off CRT1.
231 Default: auto-detect
232
233 Option "ForceCRT2Type" "string"
234 Force display type to one of: NONE , TV , SVIDEO , COMPOSITE ,
235 SVIDEO+COMPOSITE , SCART , LCD , VGA ; NONE will disable CRT2.
236 The SVIDEO, COMPOSITE, SVIDEO+COMPOSITE and SCART parameters are
237 for XGI video bridges only and can be used to force the driver
238 to use a specific TV output connector (if present). Default:
239 auto detect.
240
241 Option "CRT2Gamma" "boolean"
242 Enable or disable gamma correction for CRT2. Only supported for
243 XGI video bridges. Default: Gamma correction for CRT2 is on.
244
245 Option "TVStandard" "string"
246 Force the TV standard to either PAL or NTSC. On some machines
247 with 630, 730 and the 315/330 series, PALM , PALN and NTSCJ are
248 supported as well. Default: BIOS setting.
249
250 Option "TVXPosOffset" "integer"
251 This option allows tuning the horizontal position of the image
252 for TV output. The range is from -32 to 32. Not supported on the
253 Chrontel 7019. Default: 0
254
255 Option "TVYPosOffset" "integer"
256 This option allows tuning the vertical position of the image for
257 TV output. The range is from -32 to 32. Not supported on the
258 Chrontel 7019. Default: 0
259
260 Option "XGITVXScale" "integer"
261 This option selects the horizontal zooming level for TV output.
262 The range is from -16 to 16. Only supported on XGI video
263 bridges. Default: 0
264
265 Option "XGITVYScale" "integer"
266 This option selects the vertical zooming level for TV output in
267 the following modes: 640x480, 800x600. On the 315/330 series,
268 also 720x480, 720x576 and 768x576. The range is from -4 to 3.
269 Only supported on XGI video bridges. Default: 0
270
271 Option "CHTVOverscan" "boolean"
272 On machines with a Chrontel TV encoder, this can be used to
273 force the TV mode to overscan or underscan. on means overscan,
274 off means underscan. Default: BIOS setting.
275
276 Option "CHTVSuperOverscan" "boolean"
277 On machines with a Chrontel 7005 TV encoder, this option enables
278 a super-overscan mode. This is only supported if the TV standard
279 is PAL. Super overscan will produce an image on the TV which is
280 larger than the viewable area.
281
282 The driver supports many more options. Please see http://www.winis‐
283 chhofer.net/linuxxgivga.shtml for more information.
284
285 3. 300 series specific information
286
287 DRI is supported on the 300 series only. On Linux, DRI requires the
288 kernel's XGI framebuffer driver ( xgifb ) and some other modules which
289 come with either the kernel or XFree86.
290
291 Xgifb takes care of memory management for texture data. In order to
292 prevent the X Server and xgifb from overwriting each other's data,
293 xgifb reserves an amount of video memory for the X driver. This amount
294 can either be selected using xgifb's mem parameter, or auto-selected
295 depending on the amount of total video RAM available.
296
297 Xgifb can be used for memory management only, or as a complete frame‐
298 buffer driver. If you start xgifb with a valid mode (ie you gain a
299 graphical console), the X driver can communicate with xgifb and doesn't
300 require any manual configuration for finding out about the video memory
301 it is allowed to use. However, if you are running a 2.4 series Linux
302 kernel and use xgifb for video memory management only, ie you started
303 xgifb with mode=none and still have a text mode console, there is no
304 communication between xgifb and the X driver. For this purpose, the
305
306 Option "MaxXFBMem" "integer"
307
308 exists. This option must be set to the same value as given to xgifb
309 through its "mem" parameter, ie the amount of memory to use for X in
310 kilobytes.
311
312 If you started xgifb without the mem argument, xgifb will reserve
313
314 12288KB if more than 16MB of total video RAM is available,
315
316 8192KB if between 12 and 16MB of video RAM is available,
317
318 4096KB in all other cases.
319
320 If you intend to use DRI, I recommend setting the total video memory in
321 the BIOS to 64MB in order to at least overcome the lack of memory swap
322 functions.
323
324 Option "DRI" "boolean"
325 This option allows enabling or disabling DRI. By default, DRI is
326 on.
327
328 Option "AGPSize" "integer"
329 This option allows selecting the amount of AGP memory to be used
330 for DRI. The amount is to be specified in megabyte, the default
331 is 8.
332
334 none.
335
337 XFree86(1), XF86Config(5), xf86config(1), Xserver(1), X(7)
338
339 http://www.winischhofer.net/linuxxgivga.shtml for more information and
340 updates
341
343 Authors include: Alan Hourihane, Mike Chapman, Juanjo Santamarta,
344 Mitani Hiroshi, David Thomas, Sung-Ching Lin, Ademar Reis, Thomas
345 Winischhofer
346
347
348
349X Version 11 xf86-video-xgi 1.6.1 XGI(4)