[meta-freescale] [meta-fsl-arm][PATCH] libimxvpuapi: Add new recipe

[Otavio Salvador]

On Wed, Nov 4, 2015 at 8:22 AM, Carlos Rafael Giani
<dv at pseudoterminal.org> wrote:
> A few notes:
>
> * Even though COMPATIBLE_MACHINE is set to (mx6), the packages are still in
> the cortexa9hf-vfp-neon folder, not in the
> tmp/deploy/ipk/cortexa9hf-vfp-neon-mx6qdl. Not sure if this is OK. The
> library's API contains no bits and #includes that are machine specific in
> any way.

Please include imx-vpu in the MACHINE_ARCH_FILTER, on imx-base.inc;
this fix is independent of this change but it is clearly a need.

> * I noticed that libfslvpuwrap recipe sets PACKAGE_ARCH = "${MACHINE_ARCH}"
> . I am wondering if this would make sense for the libimvpuapi one as well.
> It does depend on imx-vpu, which contains machine specific bits in its
> headers (like, "#if defined(IMX6Q)"). Or is there a different reason why the
> libfslvpuwrap recipe sets the PACKAGE_ARCH to MACHINE_ARCH?

It needs to be MACHINE_ARCH as it depends on the kernel. You don't
need it here as it will be handled automatically.

> * The libfslvpuwrap recipe use COMPATIBLE_MACHINE = "(mx6q|mx6dl)" instead
> of COMPATIBLE_MACHINE = "(mx6)" . I am not aware of the entire mx6
> production line. Are there imx6 machines without a VPU? If so, does
> "(mx6q|mx6dl)" include all machines that *do* have a VPU?

Yes, it does. SoloLite and UltraLite does not provide a VPU.

-- 
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