1s3virge(4)                 Kernel Interfaces Manual                 s3virge(4)
2
3
4

NAME

6       s3virge - S3 ViRGE video driver
7

SYNOPSIS

9       Section "Device"
10         Identifier "devname"
11         Driver "s3virge"
12         ...
13         [ Option "optionname" ["optionvalue"]]
14       EndSection
15

DESCRIPTION

17       s3virge  is  an  Xorg  driver  for S3 based video cards.  The driver is
18       fully accelerated, and provides support for the  following  framebuffer
19       depths: 8, 15, 16, and 24.  All visual types are supported for depth 8,
20       and TrueColor visuals are supported for the other depths.  XVideo hard‐
21       ware up scaling is supported in depth 16 and 24 on the DX, GX, GX2, MX,
22       MX+, and Trio3D/2X.  Doublescan modes are supported and tested in depth
23       8 and 16 on DX, but disable XVideo.  Doublescan modes on other chipsets
24       are untested.
25

SUPPORTED HARDWARE

27       The s3virge driver supports PCI and AGP video cards based on  the  fol‐
28       lowing S3 chips:
29
30       ViRGE       86C325
31
32       ViRGE VX    86C988
33
34       ViRGE DX    86C375
35
36       ViRGE GX    86C385
37
38       ViRGE GX2   86C357
39
40       ViRGE MX    86C260
41
42       ViRGE MX+   86C280
43
44       Trio 3D     86C365
45
46       Trio 3D/2X  86C362, 86C368
47

CONFIGURATION DETAILS

49       Please  refer to xorg.conf(5x) for general configuration details.  This
50       section only covers configuration details specific to this driver.  All
51       options  names  are case and white space insensitive when parsed by the
52       server, for example,  "virge vx" and "VIRGEvx" are equivalent.
53
54       The driver auto-detects the chipset type,  but  the  following  ChipSet
55       names  may  optionally  be specified in the config file ""Device"" sec‐
56       tion, and will override the auto-detection:
57
58           "virge", "86c325", "virge  vx",  "86c988",  "virge  dx",  "86c375",
59           "virge  gx", "86c385", "virge gx2", "86c357", "virge mx", "86c260",
60           "virge mx+", "86c280", "trio 3d", "86c365", "trio 3d/2x", "86c362",
61           "86c368".
62
63
64       The following Cursor Options are supported:
65
66       Option "HWCursor" ["boolean"]
67              Enable or disable the HW cursor.  Default: on.
68
69       Option "SWCursor" ["boolean"]
70              Inverse of "HWCursor".  Default: off.
71
72
73       The following display Options are supported:
74
75       Option "ShadowFB" ["boolean"]
76              Use  shadow  framebuffer.   Disables  HW acceleration.  Default:
77              off.
78
79       Option "Rotate" "cw | ccw"
80              Rotate the screen CW - clockwise or  CCW  -  counter  clockwise.
81              Disables HW Acceleration and HW Cursor, uses ShadowFB.  Default:
82              no rotation.
83
84       Option "XVideo" ["boolean"]
85              Disable XVideo support by using the off  option.   This  changes
86              FIFO  settings  which  prevent  screen noise for high-res modes.
87              Default: on
88
89
90       The following video memory Options are supported:
91
92       Option "slow_edodram"
93              Switch the standard ViRGE to 2-cycle edo mode. Try this  if  you
94              encounter  pixel corruption on the ViRGE. Using this option will
95              cause a large decrease in performance.  Default: off.
96
97       Option "fpm_vram"
98              Switch the ViRGE/VX to fast page mode vram mode.  Default: off.
99
100       Option "slow_dram | fast_dram"
101              Change Trio 3D and 3D/2X  memory  options.   Default:  Use  BIOS
102              defaults.
103
104       Option "early_ras_precharge | late_ras_precharge"
105              adjust  memory  parameters.   One of these will us the same set‐
106              tings as your video card defaults, and using neither in the con‐
107              fig file does the same.  Default: none.
108
109       Option "set_mclk" "integer"
110              sets  the  memory clock, where integer is in kHz, and integer <=
111              100000.  Default: probe the memory clock value, and  use  it  at
112              server start.
113
114       Option "set_refclk" "integer"
115              sets  the  ref  clock  for  ViRGE  MX,  where integer is in kHz.
116              Default: probe the memory clock value,  and  use  it  at  server
117              start.
118
119
120
121       The following acceleration and graphics engine Options are supported:
122
123       Option "NoAccel"
124              Disable acceleration.  Very useful for determining if the driver
125              has problems with drawing and acceleration  routines.   This  is
126              the  first option to try if your server runs but you see graphic
127              corruption on the screen.  Using it decreases performance, as it
128              uses  software emulation for drawing operations the video driver
129              can accelerate with hardware.  Default: acceleration is enabled.
130
131       Option "UseFB"
132              There are two framebuffer rendering methods.  fb and cfb.   Both
133              are  available  in  the  driver.   fb  is  the newer and default
134              method.  To switch back to cfb use this option with no,  off  or
135              other negative parameter.  Default: on.
136
137       Option "fifo_aggressive | fifo_moderate | fifo_conservative"
138              alter  the  settings  for  the threshold at which the pixel FIFO
139              takes over the internal memory bus to refill itself. The smaller
140              this  threshold,  the better the acceleration performance of the
141              card. You may try the fastest setting (fifo_aggressive) and move
142              down  if  you  encounter  pixel corruption.  The optimal setting
143              will probably depend on dot-clock and on color depth. Note  that
144              specifying  any  of  these  options will also alter other memory
145              settings which may increase performance, so trying  fifo_conser‐
146              vative  will  in  most  cases be a slight benefit (this uses the
147              chip defaults).  If pixel corruption or transient  streaking  is
148              observed  during  drawing  operations  then  removing  any  fifo
149              options is recommended.  Default: none.
150
151
152       The following PCI bus Options are supported:
153
154       Option "pci_burst" ["boolean"]
155              will enable PCI burst mode. This should work on all  but  a  few
156              broken  PCI  chipsets,  and will increase performance.  Default:
157              off.
158
159       Option "pci_retry" ["boolean"]
160              will allow the driver to rely on PCI Retry to program the  ViRGE
161              registers.   pci_burst  must  be enabled for this to work.  This
162              will increase performance,  especially  for  small  fills/blits,
163              because  the driver does not have to poll the ViRGE before send‐
164              ing it commands to make sure it is ready. It should work on most
165              recent PCI chipsets.  Default: off.
166
167       The following ViRGE MX LCD Options are supported:
168
169       Option "lcd_center"
170
171       Option "set_lcdclk" "integer"
172              allows setting the clock for a ViRGE MX LCD display.  integer is
173              in Hz.  Default: use probed value.
174
175
176       The following additional Options are supported:
177
178       Option "ShowCache" ["boolean"]
179              Enable or disable viewing offscreen cache memory.  A development
180              debug option.  Default: off.
181
182       Option "mx_cr3a_fix" ["boolean"]
183              Enable or disable a cr3a fix added for ViRGE MX.  Default: on.
184
185

SEE ALSO

187       Xorg(1x), xorg.conf(5x), xorgconfig(1x), Xserver(1x), X(7)
188
189

KNOWN BUGS

191       The  VideoRam  generic  driver  parameter  is  presently ignored by the
192       s3virge driver.  On PPC this is  reported  to  cause  problems  for  2M
193       cards, because they may autodetect as 4M.
194
195

SUPPORT

197       For assistance with this driver, or Xorg in general, check the web site
198       at http://www.x.org.  If you find a problem with Xorg or have  a  ques‐
199       tion  not  answered in the FAQ please use our bug report form available
200       on the web site.  When reporting problems with the driver send as  much
201       detail  as  possible,  including chipset type, a server output log, and
202       operating system specifics.
203
204

AUTHORS

206       Kevin Brosius, Matt Grossman, Harald Koenig, Sebastien  Marineau,  Mark
207       Vojkovich.
208
209
210
211X Version 11               xf86-video-s3virge 1.9.1                 s3virge(4)
Impressum