On Wed, Dec 18, 2002 at 08:10:30PM -0800, Linus Torvalds wrote:
>
> You have to balance things out. Yes, the US is litiginous, and clearly way
> too much so. Is the answer to just cower in a hole and hope it passes?
> Maybe. And maybe not.
Maybe the proper course of action would be to try to come
Am Donnerstag, 19. Dezember 2002 05:40 schrieb Dieter Nützel:
> Am Donnerstag, 19. Dezember 2002 05:10 schrieb Linus Torvalds:
> Marry Christmas
Ever anger with Marry... *LOL*
Merry Christmas!
-Dieter
---
This SF.NET email is sponsored by: O
On Wed, 18 Dec 2002, magenta wrote:
>
> By implementing S3TC without a patent license, the DRI team would be
> opening the DRI project up for potential litigation.
On the other hand, by being too timid, the DRI team can also eventually
doom itself to obscurity. If everybody else supports S3TC, a
On Wed, Dec 18, 2002 at 10:14:16PM -0500, Geoffrey Antos wrote:
> I believe that it is safe to go ahead and implement S3TC texture
> decompression code in DRI.
>
>
>
> Thus, there are many indications that S3TC can be used for Open Source
> projects without fear.
You don't understand how patent
I believe that it is safe to go ahead and implement S3TC texture
decompression code in DRI.
Microsoft has licensed S3TC to put in DirectX, and since DirectX 6, S3TC
has been called DXTn or DXTC, and has been part of the DirectX Specification
The DirectX Documentation is semi-freely available.
Th
On Son, 2002-12-15 at 09:25, Nick Kurshev wrote:
>
> I've found out the strange things in DRI-CVS!
> My regular upgrade of Xfree86 and DRI looks like this:
> 1. I do checkout of both Xfree86-CVS and DRI-CVS
> 2. After installing and executing of Xfree86-CVS - glxgears shows me 430 FPS
> 3. After
> BTW: Did you go with "wait for scanline" or "wait for vblank"? The
> latter is more invasive... if you were doing multiple windowed
> clients there would only be ONE buffer flip per retrace to be shared
> between the clients.
I just went with the wait for vblank (patch attached for demonstratio
PARSEC V0.99 build 0197.
r200AgeTextures 0
r200AgeTextures 1
OpenGL driver info--
Vendor:
Tungsten Graphics, Inc.
Renderer:
Mesa DRI R200 20021125 AGP 4x x86/MMX/3DNow! TCL
Version:
1.2 Mesa 5.0
Extensions:
GL_ARB_imaging
GL_ARB_multitexture
GL_ARB_texture_border_clamp
GL_ARB_texture_cube_m
Hi all,
I have a pb with my card on my laptop. I would like to know what to do.
First here is the configuration:
1) IBM thinkpad A31p Linux Redhat 8.0 XFree86-4.2.0-72
2) Graphic card ATI Radeon Mobility FireGL 7800
The problem occurs when I try to use my C++ code which works wit
On Wed, Dec 18, 2002 at 09:28:24AM -0800, Sottek, Matthew J wrote:
> Does OpenGL make any requirements on the atomic-ness (atomicity?) of
> a buffer flip? If so, I would assert that allowing part of a flip to
> be visible on one frame and the rest visible on the next is not
> a valid implementatio
Hmm.. I just went back to the CVS head and did the kernel merge part, and
had some time to do some testing.
The texture problems I've seen in tuxracer, which I _thought_ were fixed
by the Mesa-5.0 update are still there on HEAD. Apparently the real fix is
on the texmem branch, and the reason I th
Does OpenGL make any requirements on the atomic-ness (atomicity?) of
a buffer flip? If so, I would assert that allowing part of a flip to
be visible on one frame and the rest visible on the next is not
a valid implementation and therefore the non-tearing implementation is
a requirement not a featu
There has been a problem with DRI CVS trunk with Radeon r200 for some
time w.r.t restarting the graphics engines of various games. I don't
know if this is also the case for other chipsets but suspect that it is
not, otherwise it would have been fixed?
In quake3 based games, vid_restart causes
13 matches
Mail list logo
