[Mesa-dev] Drooping multiple driver support in EGL?

[Ian Romanick]

On 12/23/2011 07:20 AM, Jose Fonseca wrote:
> ----- Original Message -----
>> Hi list,
>>
>> Multiple driver support in EGL is hard to get right, if not
>> impossible.
>> On Linux desktop, we almost always want to use egl_dri2.  It allows
>> EGL
>> to loads DRI2 drivers, thus allowing it to share DRI2 drivers with
>> libGL.
>>
>> In one case where the app wants to use OpenVG, libEGL needs to load
>> egl_gallium instead.  The problem comes from that we cannot know that
>> an
>> OpenVG context is to be created until it is created.  But before a
>> context can be created, EGL needs to be initialized and an EGLConfig
>> needs to be chosen.  So when EGL is to be initialized, we need to
>> load
>> and initilaize all EGL drivers.  When an EGLConfig is to be picked,
>> we
>> need to pick it from all drivers.
>
> Couldn't we restructure this such that OpenVG (and all other state
> trackers on Linux) still use a dri2 driver, but one which exposes an
> additional (gallium specific) interface?

I was going to suggest something similar.  I think we want fewer EGL 
backends to test and maintain, not more.  Right?