Dear Philippe,
For odroid, we're working on it internally and still trying to build a proper platform image.
Unfortunately, we haven't made use of any official or open bug tracking system for this feature.
Yes, the purpose of the virtual driver is to enable building the platform image and nothing more.
If you take a look inside the source code, all the functions do nothing except return 0 or null.
Therefore, in order to use OpenGL at all, you must uninstall virtual driver and install an
appropriate GPU driver suitable for your target device, in many cases, ARM Mali 400MP.
As you mentioned, the Mali driver cannot be distributed freely due to licensing issues.
Thanks for the links, I'll dig into them.
Best regards,
Sangwon Ha
------- Original Message -------
Sender : Philippe Coval<[email protected]>
Date : 2014-07-24 23:00 (GMT+09:00)
Title : Re: [Dev] Building platform image with Mesa or Virtual driver in Tizen 3.0
On 24/07/2014 11:08, 하상원 wrote:
> Samsung Enterprise Portal mySingle
>
> Dear anyone interested in OpenGL ES drivers,
>
I do
> Hello everyone.
>
> We work on providing OpenGL ES capability to Tizen, primarily H/W
> accelerated types, such as Mali 400MP and T604.
>
great , like odroid u2 ? I have one to test
are there open bugs to track this feaure ?
>
> As you probably know, previous versions of Tizen (2.x) platform images
> are built with opengl-es-virtual-drv
>
> in order to provide opengl-es capability to other packages during OBS
> build time.
>
> The opengl-es-virtual-drv package itself is just header files with
> implementation left intentionally empty.
>
> Again, it serves only to prevent build breaks in OBS and end-user or
> developer must install appropriate
>
> GPU device driver in order for the target device to get any H/W
> acceleration.
>
I think this opengl-es-virtual-drv package
will be replaced if actual driver are installed over the tizen image
I think the main issue is that the actual mali driver is not floss
and cant be distributed without EULA
> 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.
>
Is this related to gallium ?
> Yet, opengl-es-virtual-drv is much easier to maintain in terms of code
> complexity (almost none) and
>
> can readily adopt new spec upgrades from Khronos.
>
I am no a specialist
> Anyone have suggestions/ideas?
>
Not really but you can use this place as entry point :
https://wiki.tizen.org/wiki/ARM#Mali_GPU_Driver
I'll add some infos I got from allwiners about ARM support
Also about sw rendreding may it be used or this qemu hack
https://wiki.tizen.org/wiki/Emulator
Regards
--
mailto:[email protected] -- gpg:0x467094BC
xmpp:[email protected]
https://dockr.eurogiciel.fr/blogs/embedded/author/pcl/
.
_______________________________________________
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
