Re: [Mesa-dev] glTexImage3D GL_INVALID_VALUE on 512x128

2010-11-19 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/18/2010 07:12 AM, Török Edwin wrote: > Well in this case it is 512x128x16, so 4MB only. Maybe the limit should > be on total texture size, not on one dimension only. > Will the GL spec allow you to do that? i.e. claim you support N > for width b

Re: [Mesa-dev] glTexImage3D GL_INVALID_VALUE on 512x128

2010-11-18 Thread Brian Paul
On 11/18/2010 08:12 AM, Török Edwin wrote: On Thu, 18 Nov 2010 07:36:36 -0700 Brian Paul wrote: On 11/18/2010 01:10 AM, Török Edwin wrote: On Wed, 17 Nov 2010 15:23:47 -0700 Brian Paul wrote: 2010/11/17 Török Edwin: Hi, Thought I'd do a Bugle trace to see if it logs any errors that coul

Re: [Mesa-dev] glTexImage3D GL_INVALID_VALUE on 512x128

2010-11-18 Thread Brian Paul
On 11/18/2010 07:56 AM, Marek Olšák wrote: 2010/11/18 Brian Paul mailto:bri...@vmware.com>> On 11/18/2010 01:10 AM, Török Edwin wrote: On Wed, 17 Nov 2010 15:23:47 -0700 Brian Paulmailto:brian.e.p...@gmail.com>> wrote: 2010/11/17 Török Edwinmailto:edwinto...@gma

Re: [Mesa-dev] glTexImage3D GL_INVALID_VALUE on 512x128

2010-11-18 Thread Török Edwin
On Thu, 18 Nov 2010 07:36:36 -0700 Brian Paul wrote: > On 11/18/2010 01:10 AM, Török Edwin wrote: > > On Wed, 17 Nov 2010 15:23:47 -0700 > > Brian Paul wrote: > > > >> 2010/11/17 Török Edwin: > >>> Hi, > >>> > >>> Thought I'd do a Bugle trace to see if it logs any errors that > >>> could cause f

Re: [Mesa-dev] glTexImage3D GL_INVALID_VALUE on 512x128

2010-11-18 Thread Marek Olšák
2010/11/18 Brian Paul > On 11/18/2010 01:10 AM, Török Edwin wrote: > >> On Wed, 17 Nov 2010 15:23:47 -0700 >> Brian Paul wrote: >> >> 2010/11/17 Török Edwin: >>> Hi, Thought I'd do a Bugle trace to see if it logs any errors that could cause f.d.o bug #31667. I've s

Re: [Mesa-dev] glTexImage3D GL_INVALID_VALUE on 512x128

2010-11-18 Thread Brian Paul
On 11/18/2010 01:10 AM, Török Edwin wrote: On Wed, 17 Nov 2010 15:23:47 -0700 Brian Paul wrote: 2010/11/17 Török Edwin: Hi, Thought I'd do a Bugle trace to see if it logs any errors that could cause f.d.o bug #31667. I've seen just these two: glTexImage3D(GL_TEXTURE_3D, 0, GL_RGBA, 512, 128

Re: [Mesa-dev] glTexImage3D GL_INVALID_VALUE on 512x128

2010-11-18 Thread Török Edwin
On Wed, 17 Nov 2010 15:23:47 -0700 Brian Paul wrote: > 2010/11/17 Török Edwin : > > Hi, > > > > Thought I'd do a Bugle trace to see if it logs any errors that could > > cause f.d.o bug #31667. > > > > I've seen just these two: > > glTexImage3D(GL_TEXTURE_3D, 0, GL_RGBA, 512, 128, 16, > > 0, GL_RG

Re: [Mesa-dev] glTexImage3D GL_INVALID_VALUE on 512x128

2010-11-17 Thread Brian Paul
2010/11/17 Török Edwin : > Hi, > > Thought I'd do a Bugle trace to see if it logs any errors that could > cause f.d.o bug #31667. > > I've seen just these two: > glTexImage3D(GL_TEXTURE_3D, 0, GL_RGBA, 512, 128, 16, > 0, GL_RGBA, GL_UNSIGNED_BYTE, 0x1af93cf0 - > ^[NOTICE] showerror.gl:  GL_INVALID_

[Mesa-dev] glTexImage3D GL_INVALID_VALUE on 512x128

2010-11-17 Thread Török Edwin
Hi, Thought I'd do a Bugle trace to see if it logs any errors that could cause f.d.o bug #31667. I've seen just these two: glTexImage3D(GL_TEXTURE_3D, 0, GL_RGBA, 512, 128, 16, 0, GL_RGBA, GL_UNSIGNED_BYTE, 0x1af93cf0 - ^[NOTICE] showerror.gl: GL_INVALID_VALUE in glTexImage3D glTexImage3D(GL_T