Re: dri cvs builds

2004-06-02 Thread Patrick McFarland
On 03-Jun-2004, Felix K?hling wrote: > On Wed, 2 Jun 2004 15:09:48 -0400 > Patrick McFarland <[EMAIL PROTECTED]> wrote: > > > Is anyone currently doing daily dri cvs builds for x86? > > Yes. There is a cron job at freedesktop.org producing nightly snapshots. > They can be downloaded from http://f

Re: S3TC/DXTC patch status

2004-06-02 Thread Roland Scheidegger
[EMAIL PROTECTED] wrote: Hi, I'd like to know where is the texture compression now? Has it been integrated to the mesa tree or is it still provided in a separate library ? It is still in a separate library, the legal issues have not changed. If so where can i download it ? patch here: http://homepa

Re: mach64 compiler warnings

2004-06-02 Thread Dave Airlie
It's been on my todo at home list for a while ... I'll see about getting it done this evening, I wanted to test the mach64 but I needed to wait for the DRI to get back to working ... Dave. On Wed, 2 Jun 2004, Jon Smirl wrote: > Does anyone know how to get rid of the 500 warnings from the Mach64

S3TC/DXTC patch status

2004-06-02 Thread areversat
Hi, I'd like to know where is the texture compression now? Has it been integrated to the mesa tree or is it still provided in a separate library ? If so where can i download it ? Thanks Antoine REVERSAT aka Crevetor --- This SF.Net email is s

[Bug 716] MGA: text sometimes rendered unreadably if texturing on.

2004-06-02 Thread bugzilla-daemon
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://freedesktop.org/bugzilla/show_bug.cgi?id=716 --- Additional Comments From [EMAIL PROTECTED] 2004-06-03 08:43 --- Nope, that's exactly i

[Bug 716] MGA: text sometimes rendered unreadably if texturing on.

2004-06-02 Thread bugzilla-daemon
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://freedesktop.org/bugzilla/show_bug.cgi?id=716 --- Additional Comments From [EMAIL PROTECTED] 2004-06-03 08:34 --- If it looks like http:

Re: dri cvs builds

2004-06-02 Thread Felix Kühling
On Wed, 2 Jun 2004 15:09:48 -0400 Patrick McFarland <[EMAIL PROTECTED]> wrote: > Is anyone currently doing daily dri cvs builds for x86? Yes. There is a cron job at freedesktop.org producing nightly snapshots. They can be downloaded from http://freedesktop.org/~dri/snapshots/. Cheers, Felix |

[Bug 716] New: MGA: text sometimes rendered unreadably if texturing on.

2004-06-02 Thread bugzilla-daemon
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://freedesktop.org/bugzilla/show_bug.cgi?id=716 Summary: MGA: text sometimes rendered unreadably if texturing on.

Re: [Mesa3d-dev] Current build state of DRI drivers in both trees

2004-06-02 Thread Ian Romanick
Jon Smirl wrote: --- Ian Romanick <[EMAIL PROTECTED]> wrote: The next step is to remove the one place where glxclient.h is still used (in dri_util.h). This means some clean-up is need in glcontextmodes.[ch]. That's the easy part. The harder part is dealing with the various GLX_ defines used a

[Bug 715] New: MGA (CVS snapshot + XF86 4.x): Hard lockups ("[dri] Idle timed out") during heavy texture use, requiring system reset.

2004-06-02 Thread bugzilla-daemon
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://freedesktop.org/bugzilla/show_bug.cgi?id=715 Summary: MGA (CVS snapshot + XF86 4.x): Hard lockups ("[dri] Idle timed

mach64 compiler warnings

2004-06-02 Thread Jon Smirl
Does anyone know how to get rid of the 500 warnings from the Mach64 driver? None of the other drivers have this problem. mach64_native_vbtmp.h:477: warning: use of cast expressions as lvalues is deprecated mach64_native_vbtmp.h:477: warning: use of cast expressions as lvalues is deprecated mach64_

Re: [Mesa3d-dev] Current build state of DRI drivers in both trees

2004-06-02 Thread Jon Smirl
--- Ian Romanick <[EMAIL PROTECTED]> wrote: > The next step is to remove the one place where glxclient.h is still used > (in dri_util.h). This means some clean-up is need in > glcontextmodes.[ch]. That's the easy part. The harder part is dealing > with the various GLX_ defines used around the

dri cvs builds

2004-06-02 Thread Patrick McFarland
Is anyone currently doing daily dri cvs builds for x86? -- Patrick "Diablo-D3" McFarland || [EMAIL PROTECTED] "Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music.

Re: [Mesa3d-dev] Current build state of DRI drivers in both trees

2004-06-02 Thread Ian Romanick
Ian Romanick wrote: The DRI driver builds are currently toast in both trees. I'm working like mad to get the rest of my changes worked in, but I keep hitting road blocks. At times it feels like things were disigned with the primary goal of making this more difficult. I have to leave for a bit

Re: r200 multiple app lockups, possible explanation

2004-06-02 Thread Keith Whitwell
Roland Scheidegger wrote: So, when I updated radeon_maos_arrays.c and compiled that (btw really brave souls can try it out, just define RADEON_OLD_PACKETS to 0 in radeon_context.h and RADEON_MAOS_VERTS to 0 in radeon_maos.c, that codepath was only enabled in april 2002 for 9 days and probably ca

Re: What's the story with drmGetBufInfo?

2004-06-02 Thread Keith Whitwell
Dave Airlie wrote: BUT nothing uses it. Since it's broken, I'd like to remove all traces of it (from both user mode and kernel mode). Is there any reason not to? If we need that functionality later, we can design a better interface for it that will less fragile. http://dri.sourceforge.net/doc/

Re: sis changes to DRM

2004-06-02 Thread Eric Anholt
On Mon, 2004-05-31 at 05:32, Dave Airlie wrote: > Hi Eric, > > you commited some changes to the DRM in a merge from FreeBSD-current, you > made changes to the SIS driver that look like they will break 64-bit Linux > systems, although we intend doing this, I would prefer to have it all > together i