* No GLESv1 support on Morty?
@ 2017-12-15 22:44 Joshua Watt
2017-12-18 16:59 ` Joshua Watt
0 siblings, 1 reply; 2+ messages in thread
From: Joshua Watt @ 2017-12-15 22:44 UTC (permalink / raw)
To: meta-ti@yoctoproject.org
Hello,
I'm attempting to build an application that uses the PVR GLESv1
libraries (ti-sgx-ddk-um) off of the morty branch. However, it appears
that when I call eglGetConfigs(), it doesn not return any GLESv1
compatible configs, and so eglChooseConfigs() failes to find one that
works. I have printed out the configs that are returned and it looks
like all of them are GLESv2 only:
Config 0x1:
color=8,8,8
alpha=8
depth=24
type=(0x4) GLESv2
Config 0x2:
color=8,8,8
alpha=8
depth=0
type=(0x4) GLESv2
Config 0x3:
color=8,8,8
alpha=8
depth=24
type=(0x4) GLESv2
Config 0x4:
color=8,8,8
alpha=0
depth=24
type=(0x4) GLESv2
Config 0x5:
color=8,8,8
alpha=0
depth=0
type=(0x4) GLESv2
Config 0x6:
color=8,8,8
alpha=0
depth=24
type=(0x4) GLESv2
Config 0x7:
color=5,6,5
alpha=0
depth=24
type=(0x4) GLESv2
Config 0x8:
color=5,6,5
alpha=0
depth=0
type=(0x4) GLESv2
Config 0x9:
color=5,6,5
alpha=0
depth=24
type=(0x4) GLESv2
I made sure I was linking against libGLES_CM and libEGL (but *not*
libGLESv2). I beleive this same code worked on the daisy branch.
Is there something I'm missing to enable GLESv1 support?
Thank,
Joshua Watt
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: No GLESv1 support on Morty?
2017-12-15 22:44 No GLESv1 support on Morty? Joshua Watt
@ 2017-12-18 16:59 ` Joshua Watt
0 siblings, 0 replies; 2+ messages in thread
From: Joshua Watt @ 2017-12-18 16:59 UTC (permalink / raw)
To: meta-ti@yoctoproject.org
On Fri, 2017-12-15 at 16:44 -0600, Joshua Watt wrote:
> Hello,
>
> I'm attempting to build an application that uses the PVR GLESv1
> libraries (ti-sgx-ddk-um) off of the morty branch. However, it
> appears
> that when I call eglGetConfigs(), it doesn not return any GLESv1
> compatible configs, and so eglChooseConfigs() failes to find one that
> works. I have printed out the configs that are returned and it looks
> like all of them are GLESv2 only:
>
> Config 0x1:
> color=8,8,8
> alpha=8
> depth=24
> type=(0x4) GLESv2
> Config 0x2:
> color=8,8,8
> alpha=8
> depth=0
> type=(0x4) GLESv2
> Config 0x3:
> color=8,8,8
> alpha=8
> depth=24
> type=(0x4) GLESv2
> Config 0x4:
> color=8,8,8
> alpha=0
> depth=24
> type=(0x4) GLESv2
> Config 0x5:
> color=8,8,8
> alpha=0
> depth=0
> type=(0x4) GLESv2
> Config 0x6:
> color=8,8,8
> alpha=0
> depth=24
> type=(0x4) GLESv2
> Config 0x7:
> color=5,6,5
> alpha=0
> depth=24
> type=(0x4) GLESv2
> Config 0x8:
> color=5,6,5
> alpha=0
> depth=0
> type=(0x4) GLESv2
> Config 0x9:
> color=5,6,5
> alpha=0
> depth=24
> type=(0x4) GLESv2
>
> I made sure I was linking against libGLES_CM and libEGL (but *not*
> libGLESv2). I beleive this same code worked on the daisy branch.
>
> Is there something I'm missing to enable GLESv1 support?
I think I figured this out. libGLES_CM.so was missing on the filesystem
(even though the libGLES_CM.so.1 symlink and actualy .so library were
present). Apparently this symlink is required in order for the EGL
implementation to report that it support GLESv1. See:
https://lists.yoctoproject.org/pipermail/meta-ti/2017-December/010565.h
tml
>
> Thank,
> Joshua Watt
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-12-18 16:59 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-12-15 22:44 No GLESv1 support on Morty? Joshua Watt
2017-12-18 16:59 ` Joshua Watt
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.