summaryrefslogtreecommitdiff
path: root/README.r128.sgml
blob: e89ff7d5262841da054bb8201ac1d8d94a2c3b18 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
<!DOCTYPE linuxdoc PUBLIC "-//Xorg//DTD linuxdoc//EN"[
<!ENTITY % defs SYSTEM "defs.ent"> %defs;
]>

<article>
<title>Information for ATI Rage 128 Users
<author>Precision Insight, Inc., SuSE GmbH
<date>13 June 2000

<ident>
$Id$
Based on $XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/r128.sgml,v 1.7 2000/03/08 15:14:48 dawes Exp $
</ident>

<toc>

<sect>Supported Hardware
<p>
<itemize>
  <item>ATI Rage 128 based cards
</itemize>


<sect>Features
<p>
<itemize>
  <item>Full support (including hardware accelerated 2D drawing) for 8, 15,
        16, 24 bit pixel depths.
  <item>Hardware cursor support to reduce sprite flicker.
  <item>Support for high resolution video modes up to 1800x1440 @ 70Hz.
  <item>Support for doublescan video modes (e.g., 320x200 and 320x240).
  <item>Support for gamma correction at all pixel depths.
  <item>Fully programmable clock supported.
  <item>Robust text mode restore for VT switching.
</itemize>


<sect>Technical Notes
<p>
<itemize>
  <item>None
</itemize>


<sect>Reported Working Video Cards
<p>
<itemize>
  <item>Rage Fury AGP 32MB
  <item>XPERT 128 AGP 16MB
  <item>XPERT 99 AGP 8MB
</itemize>


<sect>Configuration
<p>
The driver auto-detects all device information necessary to
initialize the card.  The only lines you need in the "Device"
section of your xorg.conf file are:
<verb>
       Section "Device"
           Identifier "Rage 128"
           Driver     "r128"
       EndSection
</verb>
or let <tt>xorgconfig</tt> do this for you.

However, if you have problems with auto-detection, you can specify:
<itemize>
  <item>VideoRam - in kilobytes
  <item>MemBase  - physical address of the linear framebuffer
  <item>IOBase   - physical address of the memory mapped IO registers
  <item>ChipID   - PCI DEVICE ID
</itemize>


<sect>Driver Options
<p>
<itemize>
  <item>"hw_cursor" - request hardware cursor (default)
  <item>"sw_cursor" - software cursor only
  <item>"no_accel"  - software rendering only
  <item>"dac_8_bit" - use color weight 888 in 8 bpp mode (default)
  <item>"dac_6_bit" - use color weight 666 in 8 bpp mode (VGA emulation)
</itemize>


<sect>Known Limitations
<p>
<itemize>
  <item>None
</itemize>


<sect>Authors
<p>
The X11R&relvers; driver was originally part of XFree86 4.4 rc2.

The XFree86 4 driver was ported from XFree86 3.3.x and enhanced by:
<itemize>
   <item>Rickard E. (Rik) Faith <email>faith@precisioninsight.com</email>
   <item>Kevin E. Martin <email>kevin@precisioninsight.com</email>
</itemize>
<p>
The XFree86 4 driver was funded by ATI and was donated to The XFree86
Project by:
<verb>
    Precision Insight, Inc.
    Cedar Park, TX
    USA
</verb>
<p>
The XFree86 3.3.x driver used for the port was written by:
<itemize>
   <item>Rickard E. (Rik) Faith <email>faith@precisioninsight.com</email>
   <item>Kevin E. Martin <email>kevin@precisioninsight.com</email>
</itemize>
The XFree86 3.3.x driver was funded by ATI and was donated to The XFree86
Project by Precision Insight, Inc.  It was based in part on an earlier
driver that was written by:
<itemize>
   <item>Alan Hourihane <email>alanh@fairlite.demon.co.uk</email>
   <item>Dirk Hohndel <email>hohndel@suse.de</email>
</itemize>
<p>This early driver was funded and donated to The XFree86 Project by:
<verb>
    SuSE GmbH
    Schanzaekerstr. 10
    90443 Nuernberg
    Germany
</verb>

<p>
<htmlurl name="http://www.precisioninsight.com"
          url="http://www.precisioninsight.com">
<p>
<htmlurl name="http://www.suse.com"
          url="http://www.suse.com">


</article>