Hi,
On 11-09-15 18:48, Ilia Mirkin wrote:
On Fri, Sep 11, 2015 at 10:46 AM, Hans de Goede <hdego...@redhat.com> wrote:
Hi,
I've been working on trying to fix this one:
https://bugs.freedesktop.org/show_bug.cgi?id=90871
And today I've more or less root caused this, it seems
that some code is making glTexImage2D calls with npot
width / height, which fails on nv3x (where as it works
on nv4x).
The bug has a simple reproducer attached, but that is
not directly calling glTexImage2D, so it seems that
the npot values are coming from some helper library
used (glXBindTexImageEXT ?).
2 questions:
1) Does anyone know / suspect where the glTexImage2D call
is originating from (see the test-program attachment
in bugzilla.
2) Is this a bug in glXBindTexImageEXT (assuming that is
the culprit), or should the test program take into account
that the card does not support npot when calling this ?
Without directly answering your questions (as I don't know the
answers), without NPOT support (which nv3x doesn't have), you can only
use non-power-of-two textures with GL_TEXTURE_RECTANGLE, not
GL_TEXTURE_2D. The program that you have does appear to detect this
though, and uses the rect target if ARB_texture_rectangle is
available, which it should be. I guess it should just bail if both
ARB_texture_rectangle and ARB_texture_non_power_of_two aren't
available...
Perhaps code in src/glx messes up? You could put a breakpoint in
_mesa_error and see where it's coming from...
Thanks for the input. I will be travelling to XDC this week, I will
continue debugging this next week.
Regards,
Hans
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
