<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>XF86Config Options </TITLE>
</HEAD>
<BODY BGCOLOR="#efefef" TEXT="black" LINK="blue" VLINK="#551A8B" ALINK="red">

<A HREF="SiS.html"><EM> Information for SiS Users</EM></A>
 <b>:</b> <EM>XF86Config Options </EM><BR>
<b>Previous:</b> <A HREF="SiS2.html"><EM>Supported chips </EM></A><BR>
<b>Next:</b> <A HREF="SiS4.html"><EM>Modelines </EM></A>


<HR NOSHADE>
  <H2><A NAME="3"></A>3. XF86Config Options </H2>

<p>The following options are of particular interest for the SiS driver. Each of
them must be specified in the `svga' driver section of the XF86Config file,
within the Screen subsections of the depths to which they are applicable
(you can enable options for all depths by specifying them in the Device
section).</p>
<p>
<dl>
<dt><b>Option "set_mclk"</b><dd><p>This option lets you to modify the memory clocking of your card.
(only for 5597 and 6326) Modifying the memory timings can destroy the 
device, but usually the only ill effects of overclocking is to 
have some noise an drawing errors, but BE CAREFUL. Usually a little 
increment can improve the drawing speed, and allows also higher dotclocks. 
The server reports default memclock on starting messages, so take it
as a base. Units are in MHZ.</p>
<dt><b>Option "dac_speed"</b><dd><p>This option lets you to modify the maximum allowed dotclock (only for
5597 and 6326).	Without it, the server makes a conservative guess 
based on memory clock, speed and number of banks. If your monitor 
supports higher dotclocks and you know that your card can do it, give a 
try. If the speed is too high for your configuration (but not for your
monitor), the effects can vary from some noise on screen to a black 
screen. Don't use speeds greater than 135 Mhz, (175 for 6326), even 
if your monitor supports the dot-clock. </p>
<dt><b>Option "noaccel"</b><dd><p>By default the XAA (XFree86 Acceleration Architecture) is used.
This option will disable the use of the XAA and will enable the old
BitBlt acceleration operations. (see below).</p>
<dt><b>Option "hw_clocks"</b><dd><p>On chips 86c202 and later, the default is to use the programmable
clock for all clocks. It is possible to use the fixed clocks
supported by the chip instead of using this option (manufacturer
dependent).</p>
<dt><b>Option "sw_cursor", "hw_cursor"</b><dd><p>The default is for using the hardware cursor.</p>
<dt><b>Option "no_linear"</b><dd><p>By default linear addressing is used on all chips.
However this might be broken in some implementations. It is
possible to turn the linear addressing off with this option.
Note that H/W acceleration and 16/24bpp are only supported with
linear addressing.</p>
<dt><b>Option "no_bitblt"</b><dd><p>This option will disable the use of all the BitBLT engine.
It is useful for problems related to acceleration problems.
In general this will result in a reduced performance.</p>
<dt><b>Option "no_imageblt"</b><dd><p>It is useful for problems related to image writing, and possible                 
stipple acceleration problems. In general this will result in a reduced          
performance.                                                                     </p>
<dt><b>Option "ext_eng_queue"</b><dd><p>5597/8 and 6326 have the option to extend the engine command queue on
VRAM. With extended queue length, the driver only checks queue status 
on some color-expansion commands. This gives some performance improvement, 
but is possible to lose some commands, corrupting screen output. As the 
size of extended command queue is 16-32K, the probability is very low, but
exists. The performance gain observed is around 8-10%. Currently, using
this option with xaa_benchmark freezes the acceleration engine, causing 
weird image display.</p>
<dt><b>Option "pci_burst_on"</b><dd><p>This set a bit on some registers. Although documented, the utility of 
this option is unknown for me. I can't see any difference on stability 
or performance.</p>
<dt><b>Option "fast_vram"</b><dd><p>Enables 1 cycle memory access. Try it. Increased memory bandwidth reduces
the possibility of glitches and noise on high resolution modes. </p>
<dt><b>Option "fifo_moderate","fifo_conservative","fifo_aggressive"</b><dd><p>These options modify the arbitration thresholds on CRT FIFO. Fifo_aggressive
gives more time to CPU for accessing the VRAM. Fifo_conservative reduces 
the possibility of noise caused when the CRT tries to read memory when 
it is used by CPU, but reduces performance. The default is between 
aggressive and moderate (more aggressive than moderate).</p>


</dl>
</p>


 <HR NOSHADE>
<A HREF="SiS.html"><EM> Information for SiS Users</EM></A>
 <b>:</b> <EM>XF86Config Options </EM><BR>
<b>Previous:</b> <A HREF="SiS2.html"><EM>Supported chips </EM></A><BR>
<b>Next:</b> <A HREF="SiS4.html"><EM>Modelines </EM></A>



</BODY>
</HTML>
