is an Xorg driver for S3 based video cards. The driver is fully
accelerated, and provides support for the following framebuffer depths:
8, 15, 16, and 24. All
visual types are supported for depth 8, and TrueColor
visuals are supported for the other depths. XVideo hardware up scaling
is supported in depth 16 and 24 on the DX, GX, GX2, MX, MX+, and
Trio3D/2X. Doublescan modes are supported and tested in depth 8
and 16 on DX, but disable XVideo. Doublescan modes on other chipsets
driver supports PCI and AGP video cards based on the following S3 chips:
Please refer to xorg.conf(5) for general configuration
details. This section only covers configuration details specific to this
driver. All options names are case and white space insensitive when
parsed by the server, for example, "virge vx" and "VIRGEvx" are equivalent.
The driver auto-detects the chipset type, but the following
names may optionally be specified in the config file
section, and will override the auto-detection:
adjust memory parameters. One
of these will us the same settings as your video card defaults, and
using neither in the config file does the same. Default: none.
Option N'34'set_mclkN'34' N'34'integerN'34'
sets the memory clock, where
is in kHz, and
<= 100000. Default: probe the memory clock value,
and use it at server start.
Option N'34'set_refclkN'34' N'34'integerN'34'
sets the ref clock for ViRGE MX, where
is in kHz. Default: probe the memory clock value,
and use it at server start.
The following acceleration and graphics engine
Disable acceleration. Very useful for determining if the
driver has problems with drawing and acceleration routines. This is the first
option to try if your server runs but you see graphic corruption on the screen.
Using it decreases performance, as it uses software emulation for drawing
operations the video driver can accelerate with hardware.
Default: acceleration is enabled.
There are two framebuffer rendering methods. fb and cfb. Both are
available in the driver. fb is the newer and default method. To switch
back to cfb use this option with no, off or other negative parameter.
alter the settings
for the threshold at which the pixel FIFO takes over the internal
memory bus to refill itself. The smaller this threshold, the better
the acceleration performance of the card. You may try the fastest
and move down if you encounter pixel corruption.
The optimal setting will probably depend on dot-clock and on color
depth. Note that specifying any of these options will also alter other
memory settings which may increase performance, so trying
will in most cases be a slight benefit (this uses the chip defaults).
If pixel corruption or transient streaking is observed during drawing
operations then removing any fifo options is recommended. Default: none.
The following PCI bus
Option N'34'pci_burstN'34' [N'34'booleanN'34']
will enable PCI burst mode. This should work on all but a
few broken PCI chipsets, and will increase performance. Default: off.
Option N'34'pci_retryN'34' [N'34'booleanN'34']
will allow the driver to rely on PCI Retry to program the
must be enabled for this to work.
This will increase performance, especially for small fills/blits,
because the driver does not have to poll the ViRGE before sending it
commands to make sure it is ready. It should work on most
recent PCI chipsets. Default: off.
The following ViRGE MX LCD
Option N'34'set_lcdclkN'34' N'34'integerN'34'
allows setting the clock for a ViRGE MX LCD display.
is in Hz. Default: use probed value.
The following additional
Option N'34'ShowCacheN'34' [N'34'booleanN'34']
Enable or disable viewing offscreen cache memory. A
development debug option. Default: off.
Option N'34'mx_cr3a_fixN'34' [N'34'booleanN'34']
Enable or disable a cr3a fix added for ViRGE MX. Default: on.
The VideoRam generic driver parameter is presently ignored by the
s3virge driver. On PPC this is reported to cause problems for 2M
cards, because they may autodetect as 4M.
For assistance with this driver, or Xorg in general, check the web
site at http://www.x.org. If you find a problem with Xorg or have a
question not answered in the FAQ please use our bug report form available on
the web site. When reporting problems
with the driver send as much detail as possible, including chipset type, a
server output log, and operating system specifics.