Charl P. Botha wrote:
Dear list,I found the problem. The call to R200_FIREVERTICES() was in the wrong place
This bug has so far been reproduced on my M7 (mobile 7500) laptop with DRI
CVS as well as on a TiBook (i.e. PPC) with 7500 (thanks Wouter).
Download http://cpbotha.net/thingies/glthreads.c and compile it with
something like:
gcc -I../include -O3 -ansi -pedantic -fPIC -ffast-math -D_SVID_SOURCE \
-D_BSD_SOURCE -DUSE_XSHM -DPTHREADS -I/usr/X11R6/include glthreads.c \
-L../lib -lglut -lGLU -lGL -lm -o glthreads
This is an example from the mesademos I've modified to show the bug. You
have to run with RADEON_TCL_FORCE_DISABLE=1 (if you have TCL hardware) else
you will get the VTXFMT assert bug or your X will lock up. This is the case
with the stock glthreads too. If you have an R200, try with R200_NO_TCL=1
Run glthreads with something like: glthreads -n 5
Focus one of the windows and press any key. This will terminate the thread,
wait for it and then kill the glxcontext and window (my modification). At
this point, if you're using a radeon, you should see: drmCmdBuffer: -22 and
the app will terminate.
Does anyone have any ideas on this?
(as someone suggested). It's supposed to be near the top. I'll check in the
fix for both the radeon and r200 driver soon.
glthreads seems to work fine now (with or without h/w tcl) on the r200.
-Brian
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
