Dave Airlie wrote:
I know someone asked a while back but I'm not sure anyone concluded what
was happening...
Last night I decided to give the d3demo a go on my r9200 under DRI, my
first attempt involved pointing LIBGL_DRIVERS_PATH to my S3TC enabled
Mesa tree, this works for me for a number of games and seems fine,
however Doom 3 report indirect rendering when I do this, it looks like it
is something to do with the way it dlopens, if I build the dri driver via
my Xorg tree (i.e. just point extras/Mesa at my Mesa tree and rebuild the
r200 driver), it works fine..
So whats the major difference between a dri driver built in mesa and in
Xorg? (should I suspect PTHREADS?)
The major difference (at least it's what makes doom III fails) is that
the Mesa built dri drivers are not linked against libGL. They have lots
of undefined symbols when you look at them with ldd and rely on libGL to
provide these when they are loaded. But Doom III does not set
RTLD_GLOBAL when dlopening libGL.so, so this fails. Ttimo said he's
going to fix it, but of course I have no idea when a new version will
appear. As a workaround, you can simply use LD_PRELOAD=/usr/lib/libGL.so
when starting Doom III, which gets around that problem.
Roland
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
