Re: nitrogen6x machine config and imxpxp problems

Gary Bisson

Hi Carlos,

On Fri, Apr 24, 2020 at 09:41:26AM +0200, Carlos Rafael Giani wrote:
Two problems actually.

First, gstreamer1.0-plugins-imx has its PxP plugin enabled.
Sure, that has been acceptable to us as as most customer don't use PxP
on i.MX6 but prefer GPU2D/3D features.

Second, libimxdmabuffer's PxP allocator is enabled. This allocator is then
tested for in the test-alloc program. This program is what's used by
libimxdmabuffer's ptest. test-alloc then detects a failure while trying to
use the PxP allocator (of course, since PxP is not actually present),
causing test-alloc to report a failure.
How did that work on GStreamer-imx before? Because this issue has been
there all along.
Was there a runtime check to enable/disable features? (I don't recall)

I could change libimxdmabuffer's test-alloc to report success if at least
one tested allocator works, but I'm not sure if this is really the right way
to go. This would pave the way for run-time checks that enable/disable
features. From what I know, this kind of thing isn't considered good
practice in Yocto, since it tends to make builds less deterministic.
I know the "build" has to be deterministic but is there "runtime"
recommendations from Yocto?


Join { to automatically receive all group messages.