Aun no me canso de buscar...<br>-----------------------------------<br>



Unichrome



<p><b>THIS DOCUMENT MIGHT CONTAIN OLDER AND DEPRECATED INFORMATION</b></p>
Original
document by Jaxon Lee.&nbsp; Created: 2/1/05<br>
Last edit: 2/13/05<br>
<br>
VIA
Unichrome and DRI HOWTO<br>
<br>
(This document was produced as a tool to support both the end-users and
the developers of the opensource unichrome drivers.&nbsp; Clear and
up-to-date documentation will only make the drivers more accessible to
a wider range of users, thus providing developers with more feedback
from users with a wider range of hardware.&nbsp; Like the drivers,
this
HOWTO should be considered under heavy development.&nbsp; It will
evolve as the drivers evolve.)<br>
<br>
I.
Assumptions<br>
<br>
a. At this point, it is assumed that you are NOT a newcomer to
linux.&nbsp; Installing all of the elements that will enable DRI is
a
task that will involve compiling and possibly troubleshooting from the
command line.&nbsp; At some date in the near future, all of the
elements should be incorporated into their respective parent projects
(2.6 kernel, <a href="http://X.org">X.org</a>, etc.).&nbsp; Until then, the end-user needs to
put
the pieces together.<br>
<br>
b. You have at least a 2.6 kernel, your kernel sources, your xorg
source files, and all standard linux developer tools.&nbsp; I
understand that this project works with a 2.4 kernel, but I haven't
used the 2.4 kernel in about nine months, so I can provide little
guidance
in that area.&nbsp;&nbsp; Also, many linux distributions
(especially
those that install off of live CD's) do not include the kernel sources
or any compilers.&nbsp; These obviously need to be installed before
you
proceed.<br>
<br>
c. You need to have the hardware.&nbsp; The Unichrome project
supports
the VIA unichrome 3D graphics controller.&nbsp; These controllers
are
found in the VIA CLE266, KM400/KN400, K8M8000 and PM800/CN400
motherboard chipsets.&nbsp; Commercially, these products include
the
VIA Epia-M systems and several laptops lines such as the lovely and
economical Averatec 3200
series. (Can you guess what I have???)<br>
<br>
II.
Kit of
Parts<br>
<br>
a. The
DRM kernel modules
- These are called
via.ko and drm.ko, respectively.&nbsp; They will appear simply as
&quot;via&quot;
and &quot;drm&quot; after loading and listing with
lsmod.&nbsp; (The other two modules needed for DRM to
function&nbsp;
[via_agp &amp; agpgart]
should already be loaded and configured if you're using any of the most
popular linux distributions.&nbsp; If they are not, this will
require a
kernel recompile to enable them, and that goes beyond the scope of this
document.)&nbsp; Several DRM modules are made available by the
linux
kernel, but Via is not one of them, at least not yet (2.6.11-rc2 has
finally put it in).&nbsp; So, essentially we must build it and put
it
in the right place.&nbsp; Via DRM is not part of the
Unichrome project.&nbsp; It currently has a home at
<a href="http://freedesktop.org">freedesktop.org</a>,
where you can download CVS snapshots.&nbsp; The one I have tested
and
know is working is dated 2/12/2005.&nbsp; Download it
here:&nbsp;
<a href="http://dri.freedesktop.org/snapshots/">http://dri.freedesktop.org/snapshots/</a><br>
<br>
b. The
Unichrome Xorg
display driver - This package
is listed on the
Unichrome Sourceforge page:&nbsp;
<a href="http://sourceforge.net/projects/unichrome">http://sourceforge.net/projects/unichrome</a>, under
unichrome-xfree86.&nbsp; (Don't let that heading discourage you; it
works just fine with xorg!)&nbsp; Get the release-30 file dated
1/26/2005.&nbsp; This package will ultimately give you an xorg
driver
called via_drv.o.&nbsp; By itself, it is a fine alternative to the
vesa
driver you are currently using.&nbsp; It enhances video playback,
and
your screen can now blank-out.&nbsp; But there is no DRI
magic.&nbsp;
Yet!<br>
<br>
c. The
unichrome-3D-drivers
- Here's the magic.&nbsp; Get this package
also from the Unichrome Sourceforge page.&nbsp; The most recent is
dated 2/12/2005.&nbsp; The package
includes two
tiny files that make everything happen.&nbsp; LibGL.so.1.2 and
unichrome_dri.so.<br>
<br>
<br><br>
(II) VIA(0): [drm] added 8192 byte SAREA at 0xdebd3000<br>
(II) VIA(0): [drm] mapped SAREA 0xdebd3000 to 0xb5c9c000<br>
(II) VIA(0): [drm] framebuffer handle = 0xd8000000<br>
(II) VIA(0): [drm] added 1 reserved context for kernel<br>
(II) VIA(0): [dri] visual configs initialized.<br>
(II) VIA(0): [drm] register handle = 0xde000000<br>
(II) VIA(0): [drm] mmio Registers = 0xde000000<br>
(II) VIA(0): [dri] mmio mapped.<br>
(II) VIA(0): VIAInternalScreenInit<br>
(II) VIA(0): Using XFree86 Acceleration Architecture (XAA)<br>
&nbsp;&nbsp;&nbsp; Screen to screen bit blits<br>
&nbsp;&nbsp;&nbsp; Solid filled rectangles<br>
&nbsp;&nbsp;&nbsp; 8x8 mono pattern filled rectangles<br>
&nbsp;&nbsp;&nbsp; 8x8 color pattern filled rectangles<br>
&nbsp;&nbsp;&nbsp; Solid Lines<br>
&nbsp;&nbsp;&nbsp; Dashed Lines<br>
&nbsp;&nbsp;&nbsp; Image Writes<br>
&nbsp;&nbsp;&nbsp; Offscreen Pixmaps<br>
&nbsp;&nbsp;&nbsp; Setting up tile and stipple cache:<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 32
128x128 slots<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 10
256x256 slots<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 32 8x8
color pattern slots<br>
(==) VIA(0): Backing store disabled<br>
(II) VIA(0): [drm] drmAgpEnabled succeeded<br>
(II) VIA(0): [drm] agpAddr = 0xe0000000<br>
(II) VIA(0): [drm] agpBase = (nil)<br>
(II) VIA(0): [drm] agpAddr = 0xe0000000<br>
(II) VIA(0): [drm] agpSize = 0x01e00000<br>
(II) VIA(0): [drm] agp physical addr = 0x00000000<br>
(II) VIA(0): [dri] use agp.<br>
(II) VIA(0): [drm] FBFreeStart= 0x00400000 FBFreeEnd= 0x01fbe000
FBSize= 0x01bbe000<br>
(II) VIA(0): [dri] frame buffer initialized.<br>
(II) VIA(0): X context handle = 0x00000001<br>
(II) VIA(0): [drm] installed DRM signal handler<br>
(II) VIA(0): [DRI] installation complete<br>
(II) VIA(0): [dri] kernel data initialized.<br>
(II) VIA(0): [drm] Initialized AGP ring-buffer, size 0x200000 at AGP
offset 0x1e00000.<br>
(II) VIA(0): direct rendering enabled<br>
<br>
If not, again, you should at least see some valuable troubleshooting
info.<br>
<br>
g. If dri is not working, get thee to the mailing list archives.<br>
Here: <a href="http://sourceforge.net/mailarchive/forum.php?foru">http://sourceforge.net/mailarchive/forum.php?foru</a><div id="innerframe" class="docs">m_id=38837<br>
And<br>
Here:&nbsp;
<a href="http://sourceforge.net/mailarchive/forum.php?foru">http://sourceforge.net/mailarchive/forum.php?foru</a>m_id=38615<br>
<br>
h. If you still are stumped, subscribe and post to the mailing
list.&nbsp; Be sure to have a copy of your glxinfo and xorg.0.log,
as
well as your system config, kernel version, and xorg version.</div><br>--------------------------------------<br><br>Este documento hace parte de la documentacion de OTRO driver para Linux. Este driver esta bajo los proyectos de sourceforge..
<br><br>Ayuda... no entiendo mucho.<br>Necesito que me ayuden.... Bueno tambien es claro decir que existen los sources para los chips (ACABE DE ENCONTRARLOS!!) OFICIALES.. pero SOLO soportan 2D XvMC y v4l.. es un gran avance pero los otros dos drivers (unichrome y openchrome) tambien soportan las mismas funciones y en muchos foros recomiendan alguno de estos dos pero no el de la pagina oficial.
<br><br>Asi que, cualquiera de los dos, AYUDENME para tener soporte 3D..<br><br>PDT:<br>El openchrome es el que tengo ya instalado en mi maquina con SUSE Linux 10.1, y el unichrome aun no entiendo muy bien como instalarlo..
<br><br>Gracias<br>