Stephen J Baker wrote:
>
> However, if you want to know how the MIP selection works, this is the only
> place to read about it. (the OpenGL 1.1 spec is in HTML, for some
> reason, the 1.2 spec is only in PDF (yuk) or Postscript (double-yuk):
>
> http://www.opengl.org/Documentation/Specs.htm
Stephen J Baker wrote:
>
> On Thu, 25 Mar 1999, Brian Paul wrote:
>
> > > Since there are rumours of a couple of the IHV's getting geared up
> > > to putting geometry hardware onto low end cards (in the next year or
> > > so), it may be time to anticipate what that would do to the
> > > Mesa
On Thu, 25 Mar 1999, Marc Jauvin wrote:
> Brian Paul wrote:
> >
> > Marc Jauvin wrote:
> > >
> > > Hi,
> > >
> > > I have some work to do with respect to MIP mapping and I would like to know
> > > where I can find information on how the texture selection works and where
> > > exactly in the code
Brian Paul wrote:
>
> Marc Jauvin wrote:
> >
> > Hi,
> >
> > I have some work to do with respect to MIP mapping and I would like to know
> > where I can find information on how the texture selection works and where
> > exactly in the code it can be found.
>
> The OpenGL spec is a good place to l
On Thu, 25 Mar 1999, Brian Paul wrote:
> > Since there are rumours of a couple of the IHV's getting geared up
> > to putting geometry hardware onto low end cards (in the next year or
> > so), it may be time to anticipate what that would do to the
> > Mesa core. It's kindof a similar problem to t
On Wed, 24 Mar 1999, charlie wallace wrote:
> is dlopen available on every platform that mesa is ? If it
> is then i can`t see why not, if not then it wouldn`t work
> and we`d have to roll our own.
dlopen is available on most (maybe all) UNIX/Linux/IRIX/Solaris
type boxes - but not under Windo
On Wed, 24 Mar 1999, Brian Paul wrote:
> Marc Jauvin wrote:
> >
> > Hi,
> >
> > I have some work to do with respect to MIP mapping and I would like to know
> > where I can find information on how the texture selection works and where
> > exactly in the code it can be found.
>
> The OpenGL spec
Stephen J Baker wrote:
>
> On Wed, 24 Mar 1999, Brian Paul wrote:
>
> > Keith W,
> >
> > I was browsing the latest code to see where assembly language
> > optimizations will hook into the transformation code. It wasn't
> > obvious to me where this would happen.
> >
> > Someone from Intel wrote
On Wed, 24 Mar 1999, Brian Paul wrote:
> Keith W,
>
> I was browsing the latest code to see where assembly language
> optimizations will hook into the transformation code. It wasn't
> obvious to me where this would happen.
>
> Someone from Intel wrote me today that they've been testing PIII
>
Keith Whitwell wrote:
>
> Brian Paul wrote:
> >
> > texture.c - fixed border sampling bug in sample_3d_linear()
> >
> > Cleaned-up IRIX compiler warnings in a bunch of source files.
> > Changed void foo() declarations to void foo(void), for example.
> >
> > When compiling shade.c there's a war
David Miller wrote:
> I think the hook to install the routines should be all hidden away in
> some header file and all ugly ifdefs removed. Here is a suggested
> layout:
>
> 1) Create a directory src/asm, here goes things like asm_386_xxx.S,
>asm_sparc_xxx.S etc.
>
> 2) Create src/asm.h w
Josh Vanderhoof wrote:
>
> Brian Paul <[EMAIL PROTECTED]> writes:
> > Have you given any thought to this? In the original Mesa 3.1 beta
> > there was a simple framework for hooking in optimized FP code.
>
> I have the assembly language working with the newest Mesa. I just
> added a new file, x
charlie wallace wrote:
>
> i`ve been working on something similar, the
> solution we`re looking at is to use a run time linker
> that links in the correct module for the cpu/renderer
> in use. kind of like shared libs on unix, that way all
> the routines are pointers or table lookups. It doesn`t
Josh Vanderhoof wrote:
>
> Brian Paul <[EMAIL PROTECTED]> writes:
>
> > I was browsing the latest code to see where assembly language
> > optimizations will hook into the transformation code. It wasn't
> > obvious to me where this would happen.
> >
> > Someone from Intel wrote me today that the
Brian Paul wrote:
>
> Keith W,
>
> I was browsing the latest code to see where assembly language
> optimizations will hook into the transformation code. It wasn't
> obvious to me where this would happen.
>
> Someone from Intel wrote me today that they've been testing PIII
> instructions in Mes
Brian Paul <[EMAIL PROTECTED]> writes:
> I was browsing the latest code to see where assembly language
> optimizations will hook into the transformation code. It wasn't
> obvious to me where this would happen.
>
> Someone from Intel wrote me today that they've been testing PIII
> instructions i
16 matches
Mail list logo
