to add to this, I went back to my mesa 3.2 cvs from two weeks ago and now
everything works just fine. Is the current 3.2 broke or did I miss some
new update or compile method?
mitch wrote:
> I install todays Mesa 3.2 cvs just as I always have, and now none of my
> opengl apps work and I can't c
I install todays Mesa 3.2 cvs just as I always have, and now none of my
opengl apps work and I can't compile anything for opengl now. It also
named the libs very oddly. Anyway, I'm going to have to convert back to
the older mesa 3.2 cvs from 2 weeks ago that I still have.
oh, BTW, I installed it f
If I compile SSE support into mesa, can it access the registers without
patching the kernel? Does the kernel patch just allow multiple uses or
how does that work and what do I need to do? It would be nice if I could
just compile with SSE support and not have to recompile my kernel.
--
Mitch Allmo
mitch wrote:
>
> Mesa 3.2 compiles just fine but when I tried to build the current 3.3
> cvs with SSE support, I got the following error
>
> svgamesa.c:246: structure has no member named `SetBuffer'
> svgamesa.c: In function `SVGAMesaCreateContext':
> svgamesa.c:388: too few arguments to functio
Mesa 3.2 compiles just fine but when I tried to build the current 3.3
cvs with SSE support, I got the following error
svgamesa.c:246: structure has no member named `SetBuffer'
svgamesa.c: In function `SVGAMesaCreateContext':
svgamesa.c:388: too few arguments to function `gl_create_framebuffer'
s
Okay, I'm confident the internal intersection handling is correct now. The
four possible MAX_MIN cases are being handled the same as for the boundary
cases, and any positioning of the four vertices:
24
|\ |
| \ |
| \ |
If you run only one SSE app, without patching the kernel with SSE
support, can you take advantage of SSE?
--
Mitch Allmond
Georgia Institute of Technology, Physics & Computer Science major
[EMAIL PROTECTED]
lca13.eastnet.gatech.edu
"God does not play dice, but I do"
_
Hi!
I get SIGSEGVs in feedback.c:gl_do_feedback_vertex()
at the line
gl_feedback_vertex( ctx, win, color, VB->IndexPtr->data[v], tc );
VB->IndexPtr is NULL.
The fault is on my side, though as I rendered geometry without
Normals in twoside-lightning mode.
But at least, it shouldnt segfault!?
Gareth Hughes wrote:
>
> Okay, I'll target the work for 3.5 then. I've reread the specs
> (including the patent issue stuff) - are we even allowed to do this?
> Can we get permission from SGI to implement both extensions?
I don't know. Someone will have to ask SGI. I'm too busy.
-Brian
___
