I sent this message once, but I accidentally just sent it to Brian, so here
goes...
On Thu, Oct 17, 2002 at 01:16:13PM -0600, Brian Paul wrote:
In the DRI drivers we keep a bitfield to determine if/why we need a software
fallback. I suppose IsFast() could return a similar bitfield but coming
Over the past year an issue of OpenGL versioning has come up a few times.
Basically, we have conflicting goals of wanting to advertise OpenGL 1.3 or
1.4 but not wanting to advertise extensions that aren't hardware accelerated
(cube textures and shadow maps come to mind).
I believe that a solution
Ian Romanick wrote:
Over the past year an issue of OpenGL versioning has come up a few times.
Basically, we have conflicting goals of wanting to advertise OpenGL 1.3 or
1.4 but not wanting to advertise extensions that aren't hardware accelerated
(cube textures and shadow maps come to mind).
I
Keith Whitwell wrote:
Ian Romanick wrote:
Over the past year an issue of OpenGL versioning has come up a few times.
Basically, we have conflicting goals of wanting to advertise OpenGL
1.3 or
1.4 but not wanting to advertise extensions that aren't hardware
accelerated
(cube textures and shadow
On Thu, Oct 17, 2002 at 04:08:25PM +0100, Keith Whitwell wrote:
Ian Romanick wrote:
Over the past year an issue of OpenGL versioning has come up a few times.
Basically, we have conflicting goals of wanting to advertise OpenGL 1.3 or
1.4 but not wanting to advertise extensions that aren't
Ian Romanick wrote:
From what I have been told, this is how it works on the Nvidia drivers. I
have not verified this first hand.
if ( extension string contains GL_EXT_texture3D )
3D textures are hardware accelerated
else if ( advertised OpenGL version = 1.2 )
3D
Title: RE: [Dri-devel] OpenGL 1.3, 1.4, and extension string issue
From what I have been told, this is how it works on the
Nvidia drivers. I
have not verified this first hand.
if ( extension string contains GL_EXT_texture3D )
3D textures are hardware accelerated
else if ( advertised
Alexander Stohr wrote:
From what I have been told, this is how it works on the
Nvidia drivers. I
have not verified this first hand.
if ( extension string contains GL_EXT_texture3D )
3D textures are hardware accelerated
else if ( advertised OpenGL version = 1.2 )
Title: RE: [Dri-devel] OpenGL 1.3, 1.4, and extension string issue
Nice sheme - this will even allow to check the software paths
by just tuning the GL version (e.g. via environment variable).
But what will you do if your software path is not yet covered
by a specific OpenGL version
On Thu, Oct 17, 2002 at 09:22:37AM -0700, Ian Romanick wrote:
| ...
| So, I asked a couple people around IBM what the accepted practice was. I
| was told that an implementation is not required to export extension strings
| for extensions that are required for its adverteised OpenGL version. I
On Thu, Oct 17, 2002 at 10:09:28AM -0700, Allen Akin wrote:
On Thu, Oct 17, 2002 at 09:22:37AM -0700, Ian Romanick wrote:
| ...
| So, I asked a couple people around IBM what the accepted practice was. I
| was told that an implementation is not required to export extension strings
| for
On Thu, Oct 17, 2002 at 10:35:17AM -0700, Ian Romanick wrote:
| On Thu, Oct 17, 2002 at 10:09:28AM -0700, Allen Akin wrote:
| Also, I wouldn't want to encourage app developers to use the absence of
| an extension string to determine whether a core function is hardware
| accelerated. ...
|
|
Allen Akin wrote:
On Thu, Oct 17, 2002 at 10:35:17AM -0700, Ian Romanick wrote:
| On Thu, Oct 17, 2002 at 10:09:28AM -0700, Allen Akin wrote:
| Also, I wouldn't want to encourage app developers to use the absence of
| an extension string to determine whether a core function is hardware
|
On Thu, Oct 17, 2002 at 01:16:13PM -0600, Brian Paul wrote:
| ...
| If we only return a true/false result from the slow/fast query it may not
| be obvious to the application writer what caused the slow path to be taken,
| or what to do about it.
Yep, it turns into a combinatorial search problem.
14 matches
Mail list logo
