Am Sa, den 30.10.2004 schrieb Daniel J. Michael um 0:51:
You are correct about the unresolved symbols, they seem to happen with
the cvs code also (but I think they must be new in the last couple of
weeks sometime). Here is the output of my LIBGL_DEBUG=verbose glxinfo:
[EMAIL PROTECTED] ~ $
The latest Mesa did the trick. Thanks for the help. So far the drivers
are working just fine (although I've only tested woith glxgears and
narmal x useage so far). As far as these errors are concerned:
Symbol SavageInitStreamsNew from module
/usr/X11R6/lib/modules/drivers/savage_drv.o is
To fix this, somebody just has to add mesa/src/shaders/shaderobjects.c
to the Makefiles.
-Brian
Sérgio Monteiro Basto wrote:
Sorry I have to correct this information but
with last Mesa CVS this is not correct and I can't compile Mesa anymore.
I get this error that can't workaround
Hello,
I'm looking into the management of DMA buffers in the Savage driver now.
I took a look at the Radeon and MGA drivers. They take very different
approaches to the problem. Radeon searches all buffers to find one that
is free while MGA has its own list of free buffers from which it always
Am Samstag, 30. Oktober 2004 19:01 schrieb Brian Paul:
To fix this, somebody just has to add mesa/src/shaders/shaderobjects.c
to the Makefiles.
For XFree86 DRI it could looks like this:
--- xc/lib/GL/mesa/shader/Imakefile.inc 2004-10-30 22:14:42.735599211 +0200
+++
Am Freitag, 29. Oktober 2004 21:36 schrieb Roland Scheidegger:
Dieter Nützel wrote:
Addition:
XFree86 DRI CVS build works, but libGLcore.a have unresolved symbols.
Symbol _mesa_Uniform2iARB from
module /usr/X11R6/lib/modules/extensions/libGLcore.a is unresolved!
I suspect you need
Currenly in linux-core the driver callback reclaim_buffers is called
with a single argument filp. In reclaim_buffers you need OS-specific
knowledge to extract the device pointer from the filp. In the BSD DRM
reclaim_buffers takes two arguments, dev and filp. Could we change
the linux version to
