[Dri-devel] Game Developers Conference

2002-03-06 Thread Jens Owen
Sorry, this is a bit off topic, but... After SigGraph, this has to be one of the more graphics intense conferences of the year. Lot's of highly technical research, architectural overviews and generally interesting graphics topics are covered. A manual search of this years agenda revealed many i

Re: [Dri-devel] Sony Vaio - PCG C1VP - mach64 branch

2002-03-06 Thread José Fonseca
On 2002.03.06 21:12 Tony Rogvall wrote: > Leif Delgass wrote: > > > On Tue, 5 Mar 2002 [EMAIL PROTECTED] wrote: > > > > > Tony, > > > > > > On 2002.03.05 21:04 Tony Rogvall wrote: > > > > > > > > Hi everyone! > > > > > > > > I am new on the list, I am currently struggling with getting the > dri o

Re: [Dri-devel] CVS problems w/RedHat 7.2?

2002-03-06 Thread Keith Whitwell
Ian Romanick wrote: > > I'm having some really weird problems with a CVS build on Red Hat 7.2. > Everything works fine on 7.1, but on 7.2 sawfish seg faults in > Fstructure_define. Has anyone seen this before? Nope. Are you sure you built correctly? Keith

[Dri-devel] CVS problems w/RedHat 7.2?

2002-03-06 Thread Ian Romanick
I'm having some really weird problems with a CVS build on Red Hat 7.2. Everything works fine on 7.1, but on 7.2 sawfish seg faults in Fstructure_define. Has anyone seen this before? -- Tell that to the Marines! ___ Dri-devel mailing list [EMAIL PROTE

Re: [Dri-devel] Sony Vaio - PCG C1VP - mach64 branch

2002-03-06 Thread Tony Rogvall
Leif Delgass wrote: > On Tue, 5 Mar 2002 [EMAIL PROTECTED] wrote: > > > Tony, > > > > On 2002.03.05 21:04 Tony Rogvall wrote: > > > > > > Hi everyone! > > > > > > I am new on the list, I am currently struggling with getting the dri on > > > my > > > sony working. I have been able to set it up, co

Re: [Dri-devel] Premultiplication of the texture homogeneouscoordinates in mach64

2002-03-06 Thread Jose Fonseca
On Wed, 2002-03-06 at 17:24, Ian Romanick wrote: > On Wed, Mar 06, 2002 at 12:38:38PM +, José Fonseca wrote: > > I finally figured out what I was doing wrong when attempting to do > > premultiply the tex coords. Unfortunately I was making a lot of mistakes > > (such as remultiplying in reuse

Re: [Dri-devel] Premultiplication of the texture homogeneous coordinates in mach64

2002-03-06 Thread Ian Romanick
On Wed, Mar 06, 2002 at 12:38:38PM +, José Fonseca wrote: > I finally figured out what I was doing wrong when attempting to do > premultiply the tex coords. Unfortunately I was making a lot of mistakes > (such as remultiplying in reused vertices on primitive drawing functions, > igoring the

Re: [Dri-devel] Useful debug arrangement

2002-03-06 Thread Ian Romanick
On Wed, Mar 06, 2002 at 08:16:34AM +, Keith Whitwell wrote: > The mach64 people may find this a useful thing to do on their driver: > > I've just recently done what John C. had always said we should be doing: Keep > the debug 'printfs' compiled in all the time and be able to switch them on/o

Re: [Dri-devel] Premultiplication of the texture homogeneous coordinates in mach64

2002-03-06 Thread José Fonseca
On 2002.03.06 13:17 Keith Whitwell wrote: > José Fonseca wrote: > > > > ... > > > > In the end I come up to the conclusion that this is neither one is the > way > > to do it: > > > > - Premultipling in the _emit function is not enough because clipping is > > made after. Even if we premultiply the

Re: [Dri-devel] Premultiplication of the texture homogeneous coordinates in mach64

2002-03-06 Thread Keith Whitwell
José Fonseca wrote: > > I finally figured out what I was doing wrong when attempting to do > premultiply the tex coords. Unfortunately I was making a lot of mistakes > (such as remultiplying in reused vertices on primitive drawing functions, > igoring the coordinate pointer increment in _vbtmp.h

Re: [Dri-devel] Useful debug arrangement

2002-03-06 Thread José Fonseca
On 2002.03.06 09:02 Leif Delgass wrote: > It sounds like a good idea to me. The thought had crossed my mind while > continuously recompiling to switch between checking performance/running > at > full speed and seeing debug output. > I agree too. > btw, I added culling back on the mach64-0-0-3-

[Dri-devel] Premultiplication of the texture homogeneous coordinates in mach64

2002-03-06 Thread José Fonseca
I finally figured out what I was doing wrong when attempting to do premultiply the tex coords. Unfortunately I was making a lot of mistakes (such as remultiplying in reused vertices on primitive drawing functions, igoring the coordinate pointer increment in _vbtmp.h so effectively reading the

Re: [Dri-devel] Sony Vaio - PCG C1VP - mach64 branch

2002-03-06 Thread José Fonseca
On Tue, Mar 05, 2002 at 07:06:22PM -0500, Leif Delgass wrote: > On Tue, 5 Mar 2002, José Fonseca wrote: > > > BTW, I've isolated the problem with the texture locking, it only > happens > when the code between if(mmesa->multitex) { .. } in the _tris > is run. > Don't know why. I've been trying t

Re: [Dri-devel] Useful debug arrangement

2002-03-06 Thread Leif Delgass
It sounds like a good idea to me. The thought had crossed my mind while continuously recompiling to switch between checking performance/running at full speed and seeing debug output. btw, I added culling back on the mach64-0-0-3-branch by basically copying the Mesa software culling code (as Keit

[Dri-devel] Useful debug arrangement

2002-03-06 Thread Keith Whitwell
The mach64 people may find this a useful thing to do on their driver: I've just recently done what John C. had always said we should be doing: Keep the debug 'printfs' compiled in all the time and be able to switch them on/off from the command line. This has been a huge help both tracking down