GL4ES support

[tareksander]

• [ ] Is it worth it? The highest supported version is 2.x, and that is also supported by Zink.
• [ ] Is using GL4ES as a library feasible?
• [ ] Can you use the ES1.1 and ES2.0 backends simultaneously or switch at runtime? ES2 has worse support for GL1.5, though that may not be that important.

[twaik]

Actually there is one option to use GL of higher versions on our devices, but it will require lots of porting work. It is vrend used in virglrenderer. It is possible to port vrend to mesa's virpipe driver and omit transport and ipc code (to make it work in the same process and get rid of additional unwanted CPU and RAM resource consumption).

[tareksander]

Actually there is one option to use GL of higher versions on our devices, but it will require lots of porting work. It is vrend used in virglrenderer. It is possible to port vrend to mesa's virpipe driver and omit transport and ipc code (to make it work in the same process and get rid of additional unwanted CPU and RAM resource consumption).

I think I could do something like this. I looked a bit at the Gallium API, and if I look at the Mesa virgl driver and virglrenderer-android, I'm sure I can fuse them, although I think I'll use it only as a guide to make a GL-on-GLES2.0 Gallium driver. That way I can also fit the existing swapchain implementation of the wrapper in, and eventually make use of HardwareBuffers for optimized rendering. Do you know if virgl also supports GL1.0? If yes, there really is no need for GL4ES.

[twaik]

Do you know if virgl also supports GL1.0?

I never checked this.