Re: [Dri-devel] That's the two side of the medal: Advertisingfor .NET on SF 8-(

2003-06-30 Thread Michel Dänzer
On Sun, 2003-06-29 at 16:18, Dieter Nützel wrote: Am Sonntag, 29. Juni 2003 15:59 schrieb Dieter Nützel: Some numbers: http://www.xig.com/Pages/Atop/Summit-Linux-vsWindows.html http://www.xig.com/Pages/Atop/SummitBenchmarks-CARDS.html [...]

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

2003-06-30 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

Re: [Dri-devel] Only normal DRI and Mesa CVS access =?iso-8859-15?q?as developer?=, now?

2003-06-30 Thread Alan Hourihane
On Sun, Jun 29, 2003 at 11:04:47PM +0100, Keith Whitwell wrote: José Fonseca wrote: On Sat, Jun 28, 2003 at 04:18:15PM +0200, Dieter Nützel wrote: Mesa3d seems to be affected, too. No mesa CVS update for 10 days, now ;-( My DRI CVS is 12 days old... No chance from old Europe anymore?

Re: [Dri-devel] disabling debugging from binaries?

2003-06-30 Thread Keith Whitwell
Jacek Popawski wrote: There are many places in code like: if (R200_DEBUG DEBUG_PRIMS) but I don't see how to disable debugging at all from binaries. Should not these ifs be in: #ifdef DEBUG #endif Have a look at r200_context.h - you can get the same effect by defining DO_DEBUG to zero. It's

Re: [Dri-devel] Only normal DRI and Mesa CVS access as developer, now?

2003-06-30 Thread Jos Fonseca
On Mon, Jun 30, 2003 at 01:04:18AM +0100, Alan Hourihane wrote: On Sun, Jun 29, 2003 at 11:04:47PM +0100, Keith Whitwell wrote: This is a reasonable proposition -- let's start putting a draft together, then. --- SF admins, We're concerned about the recent changes to

[Dri-devel] glxproxy and dmx with DRI

2003-06-30 Thread Alex Deucher
The DMX (distributed multihead X) project has support for the GLX extesion using some code from SGI called GLXproxy. I'm not familiar with how it works exactly. Could this code be used to add support for DRI for multiple video cards in the same machine? Or perhaps indirect rendering? like

Re: [Dri-devel] radeon 9200 tester available

2003-06-30 Thread Michel Dänzer
On Fri, 2003-06-27 at 21:05, Rupert Levene wrote: I'm using X 4.3 (a backport on debian woody) with the precompiled drivers from dri.sf.net and a radeon 9200. I currently have 3 issues which I think may be down to the drivers: 1. In tuxracer, noegnud and some other programs, it seems that

[Dri-devel] [PATCH] Make mach64.o kernel module work with 2.5

2003-06-30 Thread Colin Leroy
Hi, this patch fixes compilation of mach64 kernel module for kernel 2.5. (module will be named mach64.ko for these kernels). apply with -p0 in xc/programs/Xserver/hw/xfree86/os-support. HTH, -- Colin Random BOFH excuse: Your packets were eaten by the terminator ?

[Dri-devel] [PATCH] Make mach64.o kernel module work with 2.5

2003-06-30 Thread Colin Leroy
Hi, this patch fixes compilation of mach64 kernel module for kernel 2.5. (module will be named mach64.ko for these kernels). apply with -p0 in xc/programs/Xserver/hw/xfree86/os-support. HTH, -- Colin Random BOFH excuse: Your packets were eaten by the terminator ?

Re: [Dri-devel] Building from Savage-1_0_0-branch

2003-06-30 Thread James Jones
Speaking of virge, does anyone have any info on TV Out with virge cards? I would like to work on this, I have a GX card sitting in a box somewhere I believe that I would like to use to set up a media center in my living room. -James Alex Deucher wrote: and virge too

[Dri-devel] Weekly IRC meeting reminder

2003-06-30 Thread Ian Romanick
This is just a friendly reminder that the weekly dri-devel IRC meeting will be starting in the #dri-devel channel on irc.freenode.net at 2100 UTC (or 5:00PM EDT or 2:00PM PDT, if you prefer). Time zone conversion available at: http://www.timezoneconverter.com/cgi-bin/tzc.tzc Logs of previous

Re: [Dri-devel] Only normal DRI and Mesa CVS access as developer, now?

2003-06-30 Thread Jos Fonseca
On Mon, Jun 30, 2003 at 12:06:05PM +0100, José Fonseca wrote: I'm going to follow Alan suggestion and setup a rsync mirror of the CVS trunk checkout on my machine at the Uni. I just don't know wether I'll do the update from a cronjob (if so how frequent?), or if trigered by the commits (e.g.,

Re: [Dri-devel] [PATCH] Make mach64.o kernel module work with 2.5

2003-06-30 Thread Jos Fonseca
Colin, On Mon, Jun 30, 2003 at 04:58:37PM +0200, Colin Leroy wrote: Hi, this patch fixes compilation of mach64 kernel module for kernel 2.5. (module will be named mach64.ko for these kernels). apply with -p0 in xc/programs/Xserver/hw/xfree86/os-support. HTH, -- Colin Random BOFH

[Dri-devel] [Bug 217] mga dri breaks xawtv

2003-06-30 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=217 --- Additional Comments From

Re: [Dri-devel] [PATCH] Make mach64.o kernel module work with 2.5

2003-06-30 Thread Michel Dänzer
On Mon, 2003-06-30 at 16:58, Colin Leroy wrote: this patch fixes compilation of mach64 kernel module for kernel 2.5. (module will be named mach64.ko for these kernels). apply with -p0 in xc/programs/Xserver/hw/xfree86/os-support. [...] Index: linux/drm/kernel/drmP.h

Re: [Dri-devel] [PATCH] Make mach64.o kernel module work with 2.5

2003-06-30 Thread Michel Dänzer
On Tue, 2003-07-01 at 01:13, Michel Dänzer wrote: On Mon, 2003-06-30 at 16:58, Colin Leroy wrote: Index: linux/drm/kernel/drmP.h === RCS file:

Re: [Dri-devel] Only normal DRI and Mesa CVS access as developer,now?

2003-06-30 Thread Linus Torvalds
On Mon, 30 Jun 2003, [iso-8859-15] José Fonseca wrote: Half done. For everybody eager to get the latest DRI trunk do something like: rsync -avz --delete rsync://mefriss1.swan.ac.uk/dri/ HEAD/ Thanks. CVS was getting to be useless. Linus

[Dri-devel] RTCW ET quick benchmark

2003-06-30 Thread Jacek Popawski
I have Radeon 9100, Athlon XP 1800+, 256MB RAM and Linux-2.4.21. I was benchmarking RTCW ET with DRI. I tried to change value 216 to something bigger in xc/xc/extras/Mesa/src/tnl/t_context.h: #define IMM_MAX_COPIED_VERTS 3 #define IMM_MAXDATA (216 + IMM_MAX_COPIED_VERTS) #define

Re: [Dri-devel] That's the two side of the medal: Advertising for .NET on SF 8-(

2003-06-30 Thread Dieter Nützel
Am Montag, 30. Juni 2003 11:28 schrieb Michel Dänzer: On Sun, 2003-06-29 at 16:18, Dieter Nützel wrote: Am Sonntag, 29. Juni 2003 15:59 schrieb Dieter Nützel: Some numbers: http://www.xig.com/Pages/Atop/Summit-Linux-vsWindows.html

Re: [Dri-devel] [PATCH] Make mach64.o kernel module work with 2.5

2003-06-30 Thread Colin Leroy
On 01 Jul 2003 at 01h13, Michel Dänzer wrote: Hi, +#if LINUX_VERSION_CODE KERNEL_VERSION(2,5,1) +#include linux/wrapper.h +#endif What's this for? The linux/wrapper.h header seems to have been around since 2.2 at least. It isn't there anymore :) +#if LINUX_VERSION_CODE

Re: [Dri-devel] [ dri-Bugs-735997 ] control vertices in Maya arehardly visible

2003-06-30 Thread Paul Heldens
On Sun, 2003-05-25 at 01:07, Paul Heldens wrote: On Sun, 2003-05-11 at 15:08, SourceForge.net wrote: Bugs item #735997, was opened at 2003-05-11 13:08 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting:

[Dri-devel] [Bug 217] mga dri breaks xawtv

2003-06-30 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=217 [EMAIL PROTECTED] changed:

Re: [Dri-devel] Building from Savage-1_0_0-branch

2003-06-30 Thread Jos Fonseca
On Fri, Jun 27, 2003 at 04:58:52PM -0700, Ian Romanick wrote: Alan Cox wrote: On Gwe, 2003-06-27 at 18:42, Alan Hourihane wrote: The savage-1_0_0-branch wont work until the 3D driver is fixed up for Mesa 4.x - it's still based on Mesa 3.4. Is there any good info on doing this since the