1SAVAGE(4) Kernel Interfaces Manual SAVAGE(4)
2
3
4
6 savage - S3 Savage video driver
7
9 Section "Device"
10 Identifier "devname"
11 Driver "savage"
12 ...
13 EndSection
14
16 savage is an Xorg driver for the S3 Savage family video accelerator
17 chips. 2D, 3D, and Xv acceleration is supported on all chips except
18 the Savage2000 (2D only). Dualhead operation is supported on MX, IX,
19 and SuperSavage chips. The savage driver supports PCI and AGP boards
20 with the following chips:
21
22 Savage3D (8a20 and 8a21) (2D, 3D)
23
24 Savage4 [22m(8a22) (2D, 3D)
25
26 Savage2000 [22m(9102) (2D only)
27
28 Savage/MX (8c10 and 8c11) (2D, 3D, Dualhead)
29
30 Savage/IX (8c12 and 8c13) (2D, 3D, Dualhead)
31
32 SuperSavage/MX (8c22, 8c24, and 8c26) (2D, 3D, Dualhead)
33
34 SuperSavage/IX (8c2a, 8c2b, 8c2c, 8c2d, 8c2e, and 8c2f) (2D, 3D, Dual‐
35 head)
36
37 ProSavage PM133 (8a25) (2D, 3D)
38
39 ProSavage KM133 (8a26) (2D, 3D)
40
41 Twister (ProSavage PN133)
42 (8d01) (2D, 3D)
43
44 TwisterK (ProSavage KN133)
45 (8d02) (2D, 3D)
46
47 ProSavage DDR [22m(8d03) (2D, 3D)
48
49 ProSavage DDR-K (8d04) (2D, 3D)
50
52 Please refer to xorg.conf(5x) for general configuration details. This
53 section only covers configuration details specific to this driver.
54
55 The following driver Options are supported:
56
57 Option "HWCursor" "boolean"
58
59 Option "SWCursor" "boolean"
60 These two options interact to specify hardware or software cur‐
61 sor. If the SWCursor option is specified, any HWCursor setting
62 is ignored. Thus, either "HWCursor off" or "SWCursor on" will
63 force the use of the software cursor. On Savage/MX and Sav‐
64 age/IX chips which are connected to LCDs, a software cursor will
65 be forced, because the Savage hardware cursor does not correctly
66 track the automatic panel expansion feature. Default: hardware
67 cursor.
68
69 Option "NoAccel" "boolean"
70 Disable or enable acceleration. Default: acceleration is
71 enabled. TP Option "AccelMethod" "string" Chooses between
72 available acceleration architectures. Valid options are XAA and
73 EXA. XAA is the traditional acceleration architecture and sup‐
74 port for it is very stable. EXA is a newer acceleration archi‐
75 tecture with better performance for the Render and Composite
76 extensions, but the rendering code for it is newer and possibly
77 unstable. The default is XAA.
78
79 Option "Rotate" "CW"
80
81 Option "Rotate" "CCW"
82 Rotate the desktop 90 degrees clockwise or counterclockwise.
83 This option forces the ShadowFB option on, and disables acceler‐
84 ation. Default: no rotation.
85
86 Option "ShadowFB" "boolean"
87 Enable or disable use of the shadow framebuffer layer. This
88 option disables acceleration. Default: off.
89
90 Option "LCDClock" "frequency"
91 Override the maximum dot clock. Some LCD panels produce incor‐
92 rect results if they are driven at too fast of a frequency. If
93 UseBIOS is on, the BIOS will usually restrict the clock to the
94 correct range. If not, it might be necessary to override it
95 here. The frequency parameter may be specified as an integer in
96 Hz (135750000), or with standard suffixes like "k", "kHz", "M",
97 or "MHz" (as in 135.75MHz).
98
99 Option "CrtOnly" "boolean"
100 This option disables output to the LCD and enables output to the
101 CRT port only. It is useful on laptops if you only want to use
102 the CRT port or to force the CRT output only on desktop cards
103 that use mobile chips. Default: auto-detect active outputs
104
105 Option "UseBIOS" "boolean"
106 Enable or disable use of the video BIOS to change modes. Ordi‐
107 narily, the savage driver tries to use the video BIOS to do mode
108 switches. This generally produces the best results with the
109 mobile chips (/MX and /IX), since the BIOS knows how to handle
110 the critical but unusual timing requirements of the various LCD
111 panels supported by the chip. To do this, the driver searches
112 through the BIOS mode list, looking for the mode which most
113 closely matches the xorg.conf mode line. Some purists find this
114 scheme objectionable. If you would rather have the savage
115 driver use your mode line timing exactly, turn off the UseBios
116 option. Note: Use of the BIOS is required for dualhead opera‐
117 tion. Default: on (use the BIOS).
118
119 Option "ShadowStatus" "boolean"
120 Enables the use of a shadow status register. There is a chip
121 bug in the Savage graphics engine that can cause a bus lock when
122 reading the engine status register under heavy load, such as
123 when scrolling text or dragging windows. The bug affects about
124 4% of all Savage users without DRI and a large fraction of users
125 with DRI. If your system hangs regularly while scrolling text
126 or dragging windows, try turning this option on. This uses an
127 alternate method of reading the engine status which is slightly
128 more expensive, but avoids the problem. When DRI is enabled
129 then the default is "on" (use shadow status), otherwise the
130 default is "off" (use normal status register).
131
132 Option "DisableCOB" "boolean"
133 Disables the COB (Command Overflow Buffer) on savage4 and newer
134 chips. There is supposedly a HW cache coherency problem on cer‐
135 tain savage4 and newer chips that renders the COB useless. If
136 you are having problems with 2D acceleration you can disable the
137 COB, however you will lose some performance. 3D acceleration
138 requires the COB to work. This option only applies to Savage4
139 and newer chips. Default: "off" (use COB).
140
141 Option "BCIforXv" "boolean"
142 Use the BCI to copy and reformat Xv pixel data. Using the BCI
143 for Xv causes graphics artifacts on some chips. This option
144 only applies to Savage4 and prosavage/twister chips. Default:
145 on for prosavage and twister (use BCI for Xv); off for savage4
146 (do not use the BCI for Xv).
147
148 Option "AGPMode" "integer"
149 Set AGP data transfer rate. (used only when DRI is enabled)
150 1 -- x1 (default)
151 2 -- x2
152 4 -- x4
153 others -- invalid
154
155 Option "AGPSize" "integer"
156 The amount of AGP memory that will allocated for DMA and tex‐
157 tures in MB. Valid sizes are 4, 8, 16, 32, 64, 128 and 256. The
158 default is 16MB.
159
160 Option "DmaMode" "string"
161 This option influences in which way DMA (direct memory access)
162 is used by the kernel and 3D drivers.
163 Any -- Try command DMA first, then vertex DMA (default)
164 Command -- Only use command DMA or don't use DMA at all
165 Vertex -- Only use vertex DMA or don't use DMA at all
166 None -- Disable DMA
167 Command and vertex DMA cannot be enabled at the same time. Which
168 DMA mode is actually used in the end also depends on the DRM
169 version (only >= 2.4.0 supports command DMA) and the hardware
170 (Savage3D/MX/IX doesn't support command DMA).
171
172 Option "DmaType" "string"
173 The type of memory that will be used by the 3D driver for DMA
174 (direct memory access).
175 PCI -- PCI memory (default on PCI cards)
176 AGP -- AGP memory (default on AGP cards)
177 "AGP" only works if you have an AGP card.
178
179 Option "BusType" "string"
180 The bus type that will be used to access the graphics card.
181 PCI -- PCI bus (default on PCI cards)
182 AGP -- AGP bus (default on AGP cards)
183 "AGP" only works if you have an AGP card. If you choose "PCI" on
184 an AGP card the AGP bus speed is not set and no AGP aperture is
185 allocated. This implies DmaType "PCI".
186
188 savage_drv.o
189
191 Xorg(1x), xorg.conf(5x), xorgconfig(1x), Xserver(1x), X(7)
192
194 Authors include Tim Roberts (timr@probo.com) and Ani Joshi
195 (ajoshi@unixbox.com) for this version, and Tim Roberts and S. Marineau
196 for the original driver from which this was derived.
197
198
199
200X Version 11 xf86-video-savage 2.1.2 SAVAGE(4)