[Dri-devel] Your buglist for The XFree86 Project's Bugzilla needs attention.

2003-07-05 Thread bugadmin
[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bugsystem (http://bugs.xfree86.org/) that require attention. All of these bugs are in the NEW state, and have not been touched in 7 days or more. You need to take a look at

[Dri-devel] how to enable Mesa Verbose Debugging in the DRI-tree?

2003-07-05 Thread Andreas Stenglein
how to enable Mesa Verbose Debugging in the DRI-tree? http://mesa3d.org/debugging.html didnt help much --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now.

Re: [Dri-devel] ERROR COMPILING - DRI Driver Installation (R E P OS T)

2003-07-05 Thread Paul Heldens
make -f Makefile.linux radeon.o I thought the compilation guide covered this ! $ make TREE=/usr/src/linuxversion/include -f Makefile.linux radeon.o Goodluck. Paul Heldens. --- This SF.Net email sponsored by: Free pre-built ASP.NET

Re: [Dri-devel] R200: Why is SW TCL faster?

2003-07-05 Thread Paul Heldens
I have a Radeon 9000 64 MB DDR AGP card and I've been running it on a 2Ghz Intel Pentium IV machine running the latest madrake distribution. We argued that TCL means that the graphics card has to do more work and the CPU less. If your CPU is not otherwise occupied you can get higher

[Dri-devel] [Bug 44] Radeon Driver hard locks during VT switches/resolution changes 8500DV DRI only

2003-07-05 Thread bugzilla-daemon
[This e-mail has been automatically generated.] Please do not reply to this email. if you want to comment on the bug, go to the URL shown below and enter your comments there. http://bugs.xfree86.org//cgi-bin/bugzilla/show_bug.cgi?id=44 --- Additional Comments From [EMAIL

Re: [Dri-devel] how to enable Mesa Verbose Debugging in the DRI-tree?

2003-07-05 Thread Ian Romanick
Andreas Stenglein wrote: how to enable Mesa Verbose Debugging in the DRI-tree? http://mesa3d.org/debugging.html didnt help much It depends on the driver. Most of the drivers have an environment variable that's *_DEBUG (i.e., for the Radeon it's RADEON_DEBUG) that can be set to different values