[Mesa-dev] [PATCH 0/4] Resolving Android + desktop OpenGL 'hack'

[Tomasz Figa]

On Fri, Aug 26, 2016 at 1:06 PM, Ryan Houdek <sonicadvance1 at gmail.com> wrote:
> Dolphin Emulator does ;)

Do we really have any devices that provide desktop OpenGL? If yes, any
idea how front buffers are implemented there? Android's windowing
system is quite specific and in my understanding it generally provides
only a back buffer to the producer.

What are the specific features that Dolphin relies on? Are they
missing even on newer versions of OpenGL ES (3.0/3.1)?

Best regards,
Tomasz

>
> On Thu, Aug 25, 2016 at 4:47 PM, Tomasz Figa <tfiga at chromium.org> wrote:
>>
>> Hi Emil,
>>
>> On Fri, Aug 26, 2016 at 1:07 AM, Emil Velikov <emil.l.velikov at gmail.com>
>> wrote:
>> > Hi all,
>> >
>> > While in the area, I've noticed an odd behaviour (and somewhat of a bug)
>> > in the egl/android code.
>> >
>> > Namely: although we allow binding the EGL_OPENGL_API we explicitly clear
>> > the OPENGL_BIT for all the configs at eglInitalize time.
>> >
>> > I've reworked things in a less(?) hacky way, although there's the
>> > question of - is any of that needed and should we bother all together.
>> >
>> > IIRC on the dispatch side desktop GL isn't supported by libGLES_mesa.so
>> > (which is essentially libEGL.so with a fancy name).
>> >
>> > Tomasz, is desktop OpenGL a thing for ARC ? Can you check with
>> > someone from the team(s) on the above.
>>
>> AFAIK nothing in Android really cares about desktop OpenGL.
>>
>> For the complete series:
>> Reviewed-by: Tomasz Figa <tfiga at chromium.org>
>>
>> Thanks,
>> Tomasz
>> _______________________________________________
>> mesa-dev mailing list
>> mesa-dev at lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/mesa-dev
>
>