On 06/16/2016 06:36 AM, Mike Gorchak wrote:
> Hi,
>
>> You're supposed to get at these functions with eglGetProcAddress() and
> such
>
> A'm afraid EGL v1.4 spec forbids obtaining core functions through
> eglGetProcAddress(), they should be visible at dynamic linker level.
Unless you have the EG
On 06/15/2016 11:23 AM, Mike Gorchak wrote:
> Hello,
>
> Just found that latest Mesa 11.2.2 and 12.0.0rc3 exposes version 3.1 of
> OpenGL ES instead of 3.0 if i965 DRI driver is used on Intel Gen8
> (Broadwell) or Gen9 (AppolloLake/Broxton) hardware.
>
> At the same time some of GLES 3.1 function
Hi,
> You're supposed to get at these functions with eglGetProcAddress() and
such
A'm afraid EGL v1.4 spec forbids obtaining core functions through
eglGetProcAddress(), they should be visible at dynamic linker level.
Anyway, thanks!
On Wed, Jun 15, 2016 at 3:06 PM, Ilia Mirkin wrote:
> On We
On Wed, Jun 15, 2016 at 2:55 PM, Mike Gorchak
wrote:
> Hi,
>
> hm, could you check "cat ./src/mapi/es2api/glapi_mapi_tmp.h | grep
> glFramebufferParameteri" ?
>
> I can see void APIENTRY gl_dispatch_stub_888(GLenum target, GLenum pname,
> GLint param); instead of glFramebufferParameteri there.
>
>
BTW, glDispatchCompute() is from 3.1, and it is present.
glFramebufferParameteri() is from 3.1, but it is absent.
On Wed, Jun 15, 2016 at 2:55 PM, Mike Gorchak
wrote:
> Hi,
>
> hm, could you check "cat ./src/mapi/es2api/glapi_mapi_tmp.h | grep
> glFramebufferParameteri" ?
>
> I can see void APIE
Hi,
hm, could you check "cat ./src/mapi/es2api/glapi_mapi_tmp.h | grep
glFramebufferParameteri" ?
I can see void APIENTRY gl_dispatch_stub_888(GLenum target, GLenum pname,
GLint param); instead of glFramebufferParameteri there.
Also objdump -x for GLES 2.0 API shows absence of glFramebufferParam
Hm... those should be exposed:
https://cgit.freedesktop.org/mesa/mesa/tree/src/mapi/glapi/gen/ARB_framebuffer_no_attachments.xml
And the dEQP tests that check these also work correctly. What makes
you think they're not properly exposed? (Perhaps I'm confused re what
the "MAPI" interface is?)
-
Hello,
Just found that latest Mesa 11.2.2 and 12.0.0rc3 exposes version 3.1 of
OpenGL ES instead of 3.0 if i965 DRI driver is used on Intel Gen8
(Broadwell) or Gen9 (AppolloLake/Broxton) hardware.
At the same time some of GLES 3.1 functions are not available through MAPI
interface like glFramebuf
Thank you very much for this helpful advice Kenneth. Using the verbose output I
can see that the problem was caused by a mismatch in the C library used by the
program and by my system. The problem arose because the newer mesa package was
built with a newer version of gcc.
Thanks again,
Vanja
>
On Saturday, May 14, 2016 8:55:12 AM PDT Vanja Z wrote:
> Hi all,
>
> I'm sorry if this is the wrong place to post this. Upgrading from mesa
11.2.1 to 11.2.2 on Arch Linux results in several programs not working. I am
getting the following errors when launching Paraview for example,
>
> libGL e
Hi all,
I'm sorry if this is the wrong place to post this. Upgrading from mesa 11.2.1
to 11.2.2 on Arch Linux results in several programs not working. I am getting
the following errors when launching Paraview for example,
libGL error: unable to load driver: i965_dri.so
libGL error: driver point
Hi all,
Mesa 11.2.2 is now available.
With this release we have dri2/dri3 fixes for libGL, libEGL now works for
OpenBSD platforms, big endian support for radeons has improved, and the i965,
nouveau and vc4 drivers have gained misc fixes. MangledGL GetProcAddress works
correctly and the dri module
12 matches
Mail list logo
