Different use of libOpenVG in meta-fsl-arm and official meta-fsl-bsp-release

Different use of libOpenVG in meta-fsl-arm and official meta-fsl-bsp-release

[Viguera, Javier]

Hi all,

I have a question regarding the use of libOpenVG in MX6 platforms.

Allow me to write a bit of background. Using meta-fsl-arm, the package including the libraries is 'libopenvg-mx6':

root@ccimx6sbc:/usr/lib# ls -l libOpenVG.*
-rw-r--r--    1 root     root       2186417 Nov  4 11:59 libOpenVG.2d.so
-rw-r--r--    1 root     root       1321465 Nov  4 11:59 libOpenVG.3d.so
-rw-r--r--    1 root     root       1321465 Nov  4 11:59 libOpenVG.so

root@ccimx6sbc:~# md5sum /usr/lib/libOpenVG.*
1ee20add86cdaf388e0bc406528a777c  /usr/lib/libOpenVG.2d.so
62613ac1a5266831e47eb6d617ced58e  /usr/lib/libOpenVG.3d.so
62613ac1a5266831e47eb6d617ced58e  /usr/lib/libOpenVG.so

As you can see, file 'libOpenVG.so' is just a copy of 'libOpenVG.3d.so'. When you install the package with the package manager a warning is shows:

/sbin/ldconfig: /usr/lib/libOpenVG.so is not a symbolic link

Now, using the official FSL BSP (branch 'fido_3.14.38_6UL_patch' which uses the same GPU libs versions than current meta-fsl-arm), a boot script is installed, that updates at runtime the symlink of that library *depending* on the CPU:

http://git.freescale.com/git/cgit.cgi/imx/meta-fsl-bsp-release.git/tree/imx/meta-bsp/recipes-core/sysvinit/sysvinit-inittab/mx6/rc_gpu.S?h=fido_3.14.38_6UL_patch

If you look at the script it results that:

  * for i.MX6DL (duallite):  the symlink points to /usr/lib/libOpenVG.3d.so
  * for i.MX6Q (quad): the symlink points to /usr/lib/libOpenVG.2d.so

In meta-fsl-arm we use libOpenVG.3d.so regardless of the CPU.

Can someone in the list (probably FSL employee) shed a bit of light on this?

Which version of the lib should be used for each of the MX6 CPU flavors?

_____

JAVIER VIGUERA
SOFTWARE ENGINEERING

Digi International Spain S.A.U.

Re: Different use of libOpenVG in meta-fsl-arm and official meta-fsl-bsp-release

[Otavio Salvador]

Hello Javier,

On Mon, Nov 9, 2015 at 3:57 PM, Viguera, Javier <Javier.Viguera@digi.com> wrote:
> I have a question regarding the use of libOpenVG in MX6 platforms.
>
> Allow me to write a bit of background. Using meta-fsl-arm, the package including the libraries is 'libopenvg-mx6':
>
> root@ccimx6sbc:/usr/lib# ls -l libOpenVG.*
> -rw-r--r--    1 root     root       2186417 Nov  4 11:59 libOpenVG.2d.so
> -rw-r--r--    1 root     root       1321465 Nov  4 11:59 libOpenVG.3d.so
> -rw-r--r--    1 root     root       1321465 Nov  4 11:59 libOpenVG.so
>
> root@ccimx6sbc:~# md5sum /usr/lib/libOpenVG.*
> 1ee20add86cdaf388e0bc406528a777c  /usr/lib/libOpenVG.2d.so
> 62613ac1a5266831e47eb6d617ced58e  /usr/lib/libOpenVG.3d.so
> 62613ac1a5266831e47eb6d617ced58e  /usr/lib/libOpenVG.so
>
> As you can see, file 'libOpenVG.so' is just a copy of 'libOpenVG.3d.so'. When you install the package with the package manager a warning is shows:
>
> /sbin/ldconfig: /usr/lib/libOpenVG.so is not a symbolic link
>
> Now, using the official FSL BSP (branch 'fido_3.14.38_6UL_patch' which uses the same GPU libs versions than current meta-fsl-arm), a boot script is installed, that updates at runtime the symlink of that library *depending* on the CPU:
>
> http://git.freescale.com/git/cgit.cgi/imx/meta-fsl-bsp-release.git/tree/imx/meta-bsp/recipes-core/sysvinit/sysvinit-inittab/mx6/rc_gpu.S?h=fido_3.14.38_6UL_patch
>
> If you look at the script it results that:
>
>   * for i.MX6DL (duallite):  the symlink points to /usr/lib/libOpenVG.3d.so
>   * for i.MX6Q (quad): the symlink points to /usr/lib/libOpenVG.2d.so
>
> In meta-fsl-arm we use libOpenVG.3d.so regardless of the CPU.
>
> Can someone in the list (probably FSL employee) shed a bit of light on this?
>
> Which version of the lib should be used for each of the MX6 CPU flavors?

This highlights a serious problem. Freescale says the QDL are software
compatible however this symlink mangle breaks this assumption. Mainly
it is not possible to use same rootfs, in read-only, for them all.

I added few Freescale people on Cc so they can comment on it.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: Different use of libOpenVG in meta-fsl-arm and official meta-fsl-bsp-release

[Viguera, Javier]

Hi Otavio,

> -----Original Message-----
> From: Otavio Salvador [mailto:otavio.salvador@ossystems.com.br]
> 
> 
> This highlights a serious problem. Freescale says the QDL are software
> compatible however this symlink mangle breaks this assumption. Mainly
> it is not possible to use same rootfs, in read-only, for them all.
> 
> I added few Freescale people on Cc so they can comment on it.

Did you get any feedback on this?

Anyone?

--
JAVIER VIGUERA
SOFTWARE ENGINEERING

Digi International Spain S.A.U.

Re: Different use of libOpenVG in meta-fsl-arm and official meta-fsl-bsp-release

[Otavio Salvador]

On Mon, Nov 16, 2015 at 1:07 PM, Viguera, Javier
<Javier.Viguera@digi.com> wrote:
>> -----Original Message-----
>> From: Otavio Salvador [mailto:otavio.salvador@ossystems.com.br]
>>
>>
>> This highlights a serious problem. Freescale says the QDL are software
>> compatible however this symlink mangle breaks this assumption. Mainly
>> it is not possible to use same rootfs, in read-only, for them all.
>>
>> I added few Freescale people on Cc so they can comment on it.
>
> Did you get any feedback on this?
>
> Anyone?

I am still waiting; I discussed this with Lauren and she said she were
going to check this internally. I added her on Cc so she can comment
on this.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: Different use of libOpenVG in meta-fsl-arm and official meta-fsl-bsp-release

[Sundararaj Prabhu]

It is customer preference to choose libOpenVG.3d or libOpenVG.2d and it is build time decision. Not sure whether the current recipe provide the build options to choose libOpenVG.3d or libOpenVG.2d for DQ. But this is easily fixable.

But it is hard to use the same rootfs when need for OpenVG.3D on DL/solo and OpenVG.2D for i.MX6DQ. 
We know the expectation is runtime identification or export variable switch, but currently not supported.

-----Original Message-----
From: Otavio Salvador [mailto:otavio.salvador@ossystems.com.br] 
Sent: Monday, November 16, 2015 9:24 AM
To: Viguera, Javier <Javier.Viguera@digi.com>; Post Lauren-RAA013 <Lauren.Post@freescale.com>; Hochstein Tom-R60874 <Tom.Hochstein@freescale.com>
Cc: meta-freescale@yoctoproject.org; Sundararaj Prabhu-B36876 <Prabhu.Sundararaj@freescale.com>
Subject: Re: [meta-freescale] Different use of libOpenVG in meta-fsl-arm and official meta-fsl-bsp-release

On Mon, Nov 16, 2015 at 1:07 PM, Viguera, Javier <Javier.Viguera@digi.com> wrote:
>> -----Original Message-----
>> From: Otavio Salvador [mailto:otavio.salvador@ossystems.com.br]
>>
>>
>> This highlights a serious problem. Freescale says the QDL are 
>> software compatible however this symlink mangle breaks this 
>> assumption. Mainly it is not possible to use same rootfs, in read-only, for them all.
>>
>> I added few Freescale people on Cc so they can comment on it.
>
> Did you get any feedback on this?
>
> Anyone?

I am still waiting; I discussed this with Lauren and she said she were going to check this internally. I added her on Cc so she can comment on this.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: Different use of libOpenVG in meta-fsl-arm and official meta-fsl-bsp-release

[Otavio Salvador]

On Mon, Nov 16, 2015 at 2:00 PM, Sundararaj Prabhu
<Prabhu.Sundararaj@freescale.com> wrote:
> It is customer preference to choose libOpenVG.3d or libOpenVG.2d and it is build time decision. Not sure whether the current recipe provide the build options to choose libOpenVG.3d or libOpenVG.2d for DQ. But this is easily fixable.
>
> But it is hard to use the same rootfs when need for OpenVG.3D on DL/solo and OpenVG.2D for i.MX6DQ.
> We know the expectation is runtime identification or export variable switch, but currently not supported.

The runtime selection is need for proper runtime compatibility across
SoC family. This is one of sales point of i.MX6QDL and thus seems to
be a critical issue for me.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: Different use of libOpenVG in meta-fsl-arm and official meta-fsl-bsp-release

[Sébastien Taylor]

Also related to this subject, it is not clear to me what these two libraries provide exactly.  If either are available does that mean emulating OpenVG using the 3D GPU when using the 3d flavour of the library?  What is the use-case for this?  Are there issues with the 2d library that might cause a user to want to emulate OpenVG?



On 2015-11-16, 9:00 AM, "Sundararaj Prabhu" <meta-freescale-bounces@yoctoproject.org on behalf of Prabhu.Sundararaj@freescale.com> wrote:

>It is customer preference to choose libOpenVG.3d or libOpenVG.2d and it is build time decision. Not sure whether the current recipe provide the build options to choose libOpenVG.3d or libOpenVG.2d for DQ. But this is easily fixable.
>
>But it is hard to use the same rootfs when need for OpenVG.3D on DL/solo and OpenVG.2D for i.MX6DQ. 
>We know the expectation is runtime identification or export variable switch, but currently not supported.
>
>-----Original Message-----
>From: Otavio Salvador [mailto:otavio.salvador@ossystems.com.br] 
>Sent: Monday, November 16, 2015 9:24 AM
>To: Viguera, Javier <Javier.Viguera@digi.com>; Post Lauren-RAA013 <Lauren.Post@freescale.com>; Hochstein Tom-R60874 <Tom.Hochstein@freescale.com>
>Cc: meta-freescale@yoctoproject.org; Sundararaj Prabhu-B36876 <Prabhu.Sundararaj@freescale.com>
>Subject: Re: [meta-freescale] Different use of libOpenVG in meta-fsl-arm and official meta-fsl-bsp-release
>
>On Mon, Nov 16, 2015 at 1:07 PM, Viguera, Javier <Javier.Viguera@digi.com> wrote:
>>> -----Original Message-----
>>> From: Otavio Salvador [mailto:otavio.salvador@ossystems.com.br]
>>>
>>>
>>> This highlights a serious problem. Freescale says the QDL are 
>>> software compatible however this symlink mangle breaks this 
>>> assumption. Mainly it is not possible to use same rootfs, in read-only, for them all.
>>>
>>> I added few Freescale people on Cc so they can comment on it.
>>
>> Did you get any feedback on this?
>>
>> Anyone?
>
>I am still waiting; I discussed this with Lauren and she said she were going to check this internally. I added her on Cc so she can comment on this.
>
>-- 
>Otavio Salvador                             O.S. Systems
>http://www.ossystems.com.br        http://code.ossystems.com.br
>Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>-- 
>_______________________________________________
>meta-freescale mailing list
>meta-freescale@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/meta-freescale

Re: Different use of libOpenVG in meta-fsl-arm and official meta-fsl-bsp-release

[Viguera, Javier]

> -----Original Message-----
> From: Sundararaj Prabhu [mailto:Prabhu.Sundararaj@freescale.com]
> 
> It is customer preference to choose libOpenVG.3d or libOpenVG.2d and it
> is build time decision. Not sure whether the current recipe provide the
> build options to choose libOpenVG.3d or libOpenVG.2d for DQ. But this
> is easily fixable.

I'm not sure if I understood your reply.

Do you mean that both libraries provide different functionality and is up to the customer to select one or the other regardless of the CPU flavor (quad/dual, duallite/solo)?

-- jviguera

Re: Different use of libOpenVG in meta-fsl-arm and official meta-fsl-bsp-release

[Sundararaj Prabhu]

[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]

Both the libraries offers exact same functionality but uses different GPUs. DQ and SL have dedicated GPU for OpenVG.


_____________________________
From: Viguera, Javier <javier.viguera@digi.com<mailto:javier.viguera@digi.com>>
Sent: Monday, November 16, 2015 10:23 AM
Subject: RE: [meta-freescale] Different use of libOpenVG in meta-fsl-arm and official meta-fsl-bsp-release
To: Hochstein Tom-R60874 <tom.hochstein@freescale.com<mailto:tom.hochstein@freescale.com>>, 'Otavio Salvador' <otavio.salvador@ossystems.com.br<mailto:otavio.salvador@ossystems.com.br>>, Sundararaj Prabhu-B36876 <prabhu.sundararaj@freescale.com<mailto:prabhu.sundararaj@freescale.com>>, Post Lauren-RAA013 <lauren.post@freescale.com<mailto:lauren.post@freescale.com>>
Cc: 'meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>' <meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>>


> -----Original Message-----
> From: Sundararaj Prabhu [mailto:Prabhu.Sundararaj@freescale.com]
>
> It is customer preference to choose libOpenVG.3d or libOpenVG.2d and it
> is build time decision. Not sure whether the current recipe provide the
> build options to choose libOpenVG.3d or libOpenVG.2d for DQ. But this
> is easily fixable.

I'm not sure if I understood your reply.

Do you mean that both libraries provide different functionality and is up to the customer to select one or the other regardless of the CPU flavor (quad/dual, duallite/solo)?

-- jviguera



[-- Attachment #2: Type: text/html, Size: 3005 bytes --]

Re: Different use of libOpenVG in meta-fsl-arm and official meta-fsl-bsp-release

[Otavio Salvador]

On Mon, Nov 16, 2015 at 2:52 PM, Sundararaj Prabhu
<Prabhu.Sundararaj@freescale.com> wrote:
> Both the libraries offers exact same functionality but uses different GPUs.
> DQ and SL have dedicated GPU for OpenVG.

This is why I said it ought to be a wrapper and have a runtime way to
change the behavior; so same rootfs can be used for QDL SoCs.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: Different use of libOpenVG in meta-fsl-arm and official meta-fsl-bsp-release

[Sundararaj Prabhu]

comments inline


-----Original Message-----
From: Sébastien Taylor [mailto:sebastientaylor@gmail.com] On Behalf Of Sébastien Taylor
Sent: Monday, November 16, 2015 10:20 AM
To: Sundararaj Prabhu-B36876 <Prabhu.Sundararaj@freescale.com>; Otavio Salvador <otavio.salvador@ossystems.com.br>; Viguera, Javier <Javier.Viguera@digi.com>; Post Lauren-RAA013 <Lauren.Post@freescale.com>; Hochstein Tom-R60874 <Tom.Hochstein@freescale.com>
Cc: meta-freescale@yoctoproject.org
Subject: Re: [meta-freescale] Different use of libOpenVG in meta-fsl-arm and official meta-fsl-bsp-release

Also related to this subject, it is not clear to me what these two libraries provide exactly.  
>> https://www.khronos.org/openvg/

If either are available does that mean emulating OpenVG using the 3D GPU when using the 3d flavour of the library?  
>> yes

What is the use-case for this?  
>> https://www.khronos.org/openvg/
Target Applications

Are there issues with the 2d library that might cause a user to want to emulate OpenVG?
>> No issues




On 2015-11-16, 9:00 AM, "Sundararaj Prabhu" <meta-freescale-bounces@yoctoproject.org on behalf of Prabhu.Sundararaj@freescale.com> wrote:

>It is customer preference to choose libOpenVG.3d or libOpenVG.2d and it is build time decision. Not sure whether the current recipe provide the build options to choose libOpenVG.3d or libOpenVG.2d for DQ. But this is easily fixable.
>
>But it is hard to use the same rootfs when need for OpenVG.3D on DL/solo and OpenVG.2D for i.MX6DQ. 
>We know the expectation is runtime identification or export variable switch, but currently not supported.
>
>-----Original Message-----
>From: Otavio Salvador [mailto:otavio.salvador@ossystems.com.br]
>Sent: Monday, November 16, 2015 9:24 AM
>To: Viguera, Javier <Javier.Viguera@digi.com>; Post Lauren-RAA013 
><Lauren.Post@freescale.com>; Hochstein Tom-R60874 
><Tom.Hochstein@freescale.com>
>Cc: meta-freescale@yoctoproject.org; Sundararaj Prabhu-B36876 
><Prabhu.Sundararaj@freescale.com>
>Subject: Re: [meta-freescale] Different use of libOpenVG in 
>meta-fsl-arm and official meta-fsl-bsp-release
>
>On Mon, Nov 16, 2015 at 1:07 PM, Viguera, Javier <Javier.Viguera@digi.com> wrote:
>>> -----Original Message-----
>>> From: Otavio Salvador [mailto:otavio.salvador@ossystems.com.br]
>>>
>>>
>>> This highlights a serious problem. Freescale says the QDL are 
>>> software compatible however this symlink mangle breaks this 
>>> assumption. Mainly it is not possible to use same rootfs, in read-only, for them all.
>>>
>>> I added few Freescale people on Cc so they can comment on it.
>>
>> Did you get any feedback on this?
>>
>> Anyone?
>
>I am still waiting; I discussed this with Lauren and she said she were going to check this internally. I added her on Cc so she can comment on this.
>
>-- 
>Otavio Salvador                             O.S. Systems
>http://www.ossystems.com.br        http://code.ossystems.com.br
>Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>--
>_______________________________________________
>meta-freescale mailing list
>meta-freescale@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/meta-freescale

Re: Different use of libOpenVG in meta-fsl-arm and official meta-fsl-bsp-release

[Sébastien Taylor]

Pointing out the OpenVG spec for an OpenVG library isn’t very useful, obviously that’s what this provides.

So if the 3D version of the driver simply emulates OpenVG on the 3D GPU, and since you claim there is no issues with the 2D version.  Then what possible reason is there for having the 3D emulation be the default?



On 2015-11-16, 2:30 PM, "Sundararaj Prabhu" <Prabhu.Sundararaj@freescale.com> wrote:

>comments inline
>
>
>-----Original Message-----
>From: Sébastien Taylor [mailto:sebastientaylor@gmail.com] On Behalf Of Sébastien Taylor
>Sent: Monday, November 16, 2015 10:20 AM
>To: Sundararaj Prabhu-B36876 <Prabhu.Sundararaj@freescale.com>; Otavio Salvador <otavio.salvador@ossystems.com.br>; Viguera, Javier <Javier.Viguera@digi.com>; Post Lauren-RAA013 <Lauren.Post@freescale.com>; Hochstein Tom-R60874 <Tom.Hochstein@freescale.com>
>Cc: meta-freescale@yoctoproject.org
>Subject: Re: [meta-freescale] Different use of libOpenVG in meta-fsl-arm and official meta-fsl-bsp-release
>
>Also related to this subject, it is not clear to me what these two libraries provide exactly.  
>>> https://www.khronos.org/openvg/
>
>If either are available does that mean emulating OpenVG using the 3D GPU when using the 3d flavour of the library?  
>>> yes
>
>What is the use-case for this?  
>>> https://www.khronos.org/openvg/
>Target Applications
>
>Are there issues with the 2d library that might cause a user to want to emulate OpenVG?
>>> No issues
>
>
>
>
>On 2015-11-16, 9:00 AM, "Sundararaj Prabhu" <meta-freescale-bounces@yoctoproject.org on behalf of Prabhu.Sundararaj@freescale.com> wrote:
>
>>It is customer preference to choose libOpenVG.3d or libOpenVG.2d and it is build time decision. Not sure whether the current recipe provide the build options to choose libOpenVG.3d or libOpenVG.2d for DQ. But this is easily fixable.
>>
>>But it is hard to use the same rootfs when need for OpenVG.3D on DL/solo and OpenVG.2D for i.MX6DQ. 
>>We know the expectation is runtime identification or export variable switch, but currently not supported.
>>
>>-----Original Message-----
>>From: Otavio Salvador [mailto:otavio.salvador@ossystems.com.br]
>>Sent: Monday, November 16, 2015 9:24 AM
>>To: Viguera, Javier <Javier.Viguera@digi.com>; Post Lauren-RAA013 
>><Lauren.Post@freescale.com>; Hochstein Tom-R60874 
>><Tom.Hochstein@freescale.com>
>>Cc: meta-freescale@yoctoproject.org; Sundararaj Prabhu-B36876 
>><Prabhu.Sundararaj@freescale.com>
>>Subject: Re: [meta-freescale] Different use of libOpenVG in 
>>meta-fsl-arm and official meta-fsl-bsp-release
>>
>>On Mon, Nov 16, 2015 at 1:07 PM, Viguera, Javier <Javier.Viguera@digi.com> wrote:
>>>> -----Original Message-----
>>>> From: Otavio Salvador [mailto:otavio.salvador@ossystems.com.br]
>>>>
>>>>
>>>> This highlights a serious problem. Freescale says the QDL are 
>>>> software compatible however this symlink mangle breaks this 
>>>> assumption. Mainly it is not possible to use same rootfs, in read-only, for them all.
>>>>
>>>> I added few Freescale people on Cc so they can comment on it.
>>>
>>> Did you get any feedback on this?
>>>
>>> Anyone?
>>
>>I am still waiting; I discussed this with Lauren and she said she were going to check this internally. I added her on Cc so she can comment on this.
>>
>>-- 
>>Otavio Salvador                             O.S. Systems
>>http://www.ossystems.com.br        http://code.ossystems.com.br
>>Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>>--
>>_______________________________________________
>>meta-freescale mailing list
>>meta-freescale@yoctoproject.org
>>https://lists.yoctoproject.org/listinfo/meta-freescale
>