Hello Damian,
Sorry for the delayed reply.
gbm and wayland-egl both seem to be very brief in terms of code length.
Providing GBM and Wayland-EGL functionalities in virtual driver is not a problem,
at least during build time.
Now the issue is with the actual run-time.
One option (temporarily implemented within our team) would be to make GBM and Wayland-EGL
packages out of Mesa3D and port the GBM backend.
We could have the GPU vendors to do the ported backend and we could maintain
the non-H/W dependent portion of those two packages.
Besides ARM GPUs, this could take time though, as vendors will not be willing to
develop anything unless we have a product under commercialization stage based on their GPU.
Any suggestions?
BR,
Sangwon Ha
------- Original Message -------
Sender : Damian Hobson-Garcia<[email protected]>
Date : 2014-08-01 17:00 (GMT+09:00)
Title : Re: [Dev] Building platform image with Mesa or Virtual driver in Tizen 3.0
Hi Sangwon,
> my original intention was to have a more general topic on which is
better for
> the long run,
>
> opengl-es-virtual-drv? or Mesa?
>
> Any suggestions?
If you are thinking about replacing Mesa with opengl-es-virtual-drv I
think that there is also one more thing to consider. Currently Mesa
provides the implementation for wayland-egl and gbm which are used by
weston.
I know that there is a standalone version of gbm (libgbm) floating
around out there, but it doesn't seem to be maintained and is (already?)
not fully binary compatible with the Mesa version (it defines some extra
symbols).
If you want to replace Mesa, do you know how you can provide gbm and
wayland-egl?
Thank you,
Damian
|
|
|
HA, SANGWON, Ph.D. SAMSUNG ELECTRONICS CO., LTD. TEL: +82-31-301-0057 |
|
|
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
