| 1 | <?xml version='1.0' encoding="UTF-8"?> |
1 | <?xml version='1.0' encoding="UTF-8"?> |
| 2 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ati-faq.xml,v 1.21 2005/05/29 09:49:55 swift Exp $ --> |
2 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ati-faq.xml,v 1.22 2005/05/29 09:52:24 swift Exp $ --> |
| 3 | <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
3 | <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 4 | |
4 | |
| 5 | <guide link="/doc/en/ati-faq.xml"> |
5 | <guide link="/doc/en/ati-faq.xml"> |
| 6 | <title>Gentoo Linux ATi FAQ</title> |
6 | <title>Gentoo Linux ATi FAQ</title> |
|
|
7 | |
| 7 | <author title="Author"> |
8 | <author title="Author"> |
| 8 | <mail link="lu_zero@gentoo.org">Luca Barbato</mail> |
9 | <mail link="lu_zero@gentoo.org">Luca Barbato</mail> |
| 9 | </author> |
10 | </author> |
| 10 | <author title="Editor"> |
11 | <author title="Editor"> |
| 11 | <mail link="peesh@gentoo.org">Jorge Paulo</mail> |
12 | <mail link="peesh@gentoo.org">Jorge Paulo</mail> |
| … | |
… | |
| 30 | <title>Is my ATI board supported?</title> |
31 | <title>Is my ATI board supported?</title> |
| 31 | <body> |
32 | <body> |
| 32 | |
33 | |
| 33 | <p> |
34 | <p> |
| 34 | Almost every ATI board is supported by <uri |
35 | Almost every ATI board is supported by <uri |
| 35 | link="http://www.freedesktop.org/Software/xorg">xorg-x11</uri>, at least for the 2D accelerated |
36 | link="http://www.freedesktop.org/Software/xorg">xorg-x11</uri>, at least for |
| 36 | features. The 3D support is provided either by <uri |
37 | the 2D accelerated features. The 3D support is provided either by <uri |
| 37 | link="http://dri.sf.net">the DRI project</uri>, which is already present inside |
38 | link="http://dri.sf.net">the DRI project</uri>, which is already present inside |
| 38 | the xorg-x11, or by closed source drivers <uri |
39 | the xorg-x11, or by closed source drivers <uri |
| 39 | link="http://mirror.ati.com/support/drivers/linux/radeon-linux.html"> |
40 | link="http://mirror.ati.com/support/drivers/linux/radeon-linux.html"> |
| 40 | provided</uri> by ATI. |
41 | provided</uri> by ATI. |
| 41 | </p> |
42 | </p> |
| … | |
… | |
| 70 | |
71 | |
| 71 | </body> |
72 | </body> |
| 72 | </section> |
73 | </section> |
| 73 | <section> |
74 | <section> |
| 74 | <title> |
75 | <title> |
| 75 | I have an All-In-Wonder/Vivo board. Are the multimedia features supported? |
76 | I have an All-In-Wonder/Vivo board. Are the multimedia features supported? |
| 76 | </title> |
77 | </title> |
| 77 | <body> |
78 | <body> |
| 78 | |
79 | |
| 79 | <p> |
80 | <p> |
| 80 | The multimedia features are actually supported by <uri |
81 | The multimedia features are actually supported by <uri |
| 81 | link="http://gatos.sf.net">the GATOS project</uri> , the gatos drivers will be merged in the xorg tree shortly. |
82 | link="http://gatos.sf.net">the GATOS project</uri>, the gatos drivers will be |
|
|
83 | merged in the xorg tree shortly. |
| 82 | </p> |
84 | </p> |
| 83 | |
85 | |
| 84 | </body> |
86 | </body> |
| 85 | </section> |
87 | </section> |
| 86 | <section> |
88 | <section> |
| … | |
… | |
| 90 | <p> |
92 | <p> |
| 91 | You have almost the same x11 support on ppc or alpha platform but you can't |
93 | You have almost the same x11 support on ppc or alpha platform but you can't |
| 92 | use the ATI closed source drivers. That means that you can't use the r300 3d |
94 | use the ATI closed source drivers. That means that you can't use the r300 3d |
| 93 | features at all. If you have such a board and you want it supported by x11, |
95 | features at all. If you have such a board and you want it supported by x11, |
| 94 | you should contact <uri link="http://www.ati.com">ATI</uri> and ask them to open |
96 | you should contact <uri link="http://www.ati.com">ATI</uri> and ask them to open |
| 95 | the specs. Recently the amd64 closed source driver has been released. amd64 users can use it as the x86 users. |
97 | the specs. Recently the amd64 closed source driver has been released. amd64 |
|
|
98 | users can use it as the x86 users. |
| 96 | </p> |
99 | </p> |
| 97 | |
100 | |
| 98 | <impo> |
101 | <impo> |
| 99 | In order to enable the agpgart for certain amd64 chipsets you have to disable the K8 IOMMU support |
102 | In order to enable the agpgart for certain amd64 chipsets you have to disable |
|
|
103 | the K8 IOMMU support |
| 100 | </impo> |
104 | </impo> |
| 101 | |
105 | |
| 102 | </body> |
106 | </body> |
| 103 | </section> |
107 | </section> |
| 104 | <section> |
108 | <section> |
| … | |
… | |
| 120 | <section> |
124 | <section> |
| 121 | <title>Packages</title> |
125 | <title>Packages</title> |
| 122 | <body> |
126 | <body> |
| 123 | |
127 | |
| 124 | <ul> |
128 | <ul> |
| 125 | |
|
|
| 126 | <li>The <c>xorg-x11</c> ebuild provides the X11 implementation. </li> |
129 | <li>The <c>xorg-x11</c> ebuild provides the X11 implementation</li> |
| 127 | |
130 | <li> |
| 128 | <li>For a 2.6.x kernel the DRI modules can be built with the kernel or be |
131 | For a 2.6.x kernel the DRI modules can be built with the kernel or be |
| 129 | provided by the <c>x11-drm</c> ebuild</li> |
132 | provided by the <c>x11-drm</c> ebuild |
| 130 | |
133 | </li> |
|
|
134 | <li> |
| 131 | <li>For a 2.4.x kernel series you must use the <c>x11-drm</c> ebuild</li> |
135 | For a 2.4.x kernel series you must use the <c>x11-drm</c> ebuild |
| 132 | |
136 | </li> |
|
|
137 | <li> |
| 133 | <li>The <c>ati-drivers</c> ebuild provides the ATI closed source X drivers |
138 | The <c>ati-drivers</c> ebuild provides the ATI closed source X drivers |
| 134 | and kernel modules, for both the 2.4 and 2.6 series kernels</li> |
139 | and kernel modules, for both the 2.4 and 2.6 series kernels |
| 135 | |
140 | </li> |
| 136 | </ul> |
141 | </ul> |
| 137 | |
142 | |
| 138 | <p> |
143 | <p> |
| 139 | If you want to use ATI's <e>internal</e> agpgart support instead of the Linux |
144 | If you want to use ATI's <e>internal</e> agpgart support instead of the Linux |
| 140 | kernel one, the agpgart driver and the chipset-specific driver (in your kernel |
145 | kernel one, the agpgart driver and the chipset-specific driver (in your kernel |