Hi Damian,
I don't think all drivers being supported thru Mesa is a good idea.
There are probably more GPU vendors who don't provide Mesa compatible drivers.
Anyway, I think there're two sides to consider: build-time and runtime requirements.
For build-time, opengl-es-virtual-drv seems to be enough and being very lightweight,
it wouldn't need any upkeep in terms of bugs and fixes.
Mesa could also be used during build time instead of the opegl-es-virtual-drv.
Although being relatively bulky, it could provide run-time OpenGL ES capability,
if the user/developer decides not to install non floss drivers,
whereas opengl-es-virtual-drv mandates an installation of GPU driver.
As for the glesv2 issue, we'll look into it and see if we can provide a nice solution.
Thank you.
Best regards,
Sangwon Ha
------- Original Message -------
Sender : Damian Hobson-Garcia<[email protected]>
Date : 2014-07-25 10:43 (GMT+09:00)
Title : Re: [Dev] Building platform image with Mesa or Virtual driver in Tizen 3.0
Hi Sangwon,
>> Now with Tizen 3.0 and seeing Mesa3D in the repository, I'm confused
>> about the conceptual conflict between
>>
>> Mesa3D and opengl-es-virtual-drv as Mesa3D allows other packages which
>> depend on OpenGL ES to be built
>>
>> and also provide S/W rendering of OpenGL ES commands.
Do you mean that you are wondering if all of the OpenGL ES drivers are
expected to be supported through Mesa? I don't think that that is the
case. I think that, as Philippe said, the expectation is that non floss
drivers would still be installed after the fact. The Mesa drivers
provide the actual implementation of the Intel graphics drivers.
But that means that as of today there is no nice placeholder library
that can be easily used to satisfy the build requirements like
opengl-es-virtual-drv did in Tizen 2.x.
I've tried building Tizen 3.0 with opengl-es-virtual-drv instead of
Mesa, but the Tizen 3.0 packages all look for a OpenGL ES library called
glesv2, while opengl-es-virtual-drv provides gles20. It looks like the
configure scripts for the packages that were inherited from Tizen 2.x
have been massaged to look for gles20 instead of (or in addition to)
glesv2. Does anyone know what the reasoning behind this was?
Does it make sense to have opengl-es-virtual-drv provide glesv2? I think
this would make it a drop-in replacement for Mesa in the build process.
Thank you,
Damian
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
|
|
|
HA, SANGWON, Ph.D. SAMSUNG ELECTRONICS CO., LTD. TEL: +82-31-279-1091 |
|
|
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
