When building code with support for DMA-BUF heaps ( https://github.com/torvalds/linux/blob/master/include/uapi/linux/dma-heap.h ), I noticed that my code was detecting the dma-heap.h userspace API hea

I tried building latest master. core-image-base builds fine. core-image-weston fails with this error: nothing provides xserver-xorg-xwayland needed by weston-xwayland-9.0.0.imx-r0.cortexa53-crypto-mx8

Ah, right. I'm still not that used to going to Github for meta-freescale issues :)

Beginning with version 21, swrast is no more: https://www.phoronix.com/scan.php?page=news_item&px=Mesa-Kills-SWRAST As a consequence, trying to build mesa with the meta-freescale bbappends and openemb

Yes, this happened in the past. However, the benefits of DMA-BUF outweigh this IMO. I also have the libimxdmabuffer library to encapsulate such details. The alternative is to rely on IPU/VPU/etc. spec

For i.MX8 it is enabled already.

On i.MX6 machines, it is currently not possible to use the ION allocator. However, there is no hardware limitation that requires ION to be disabled. If ION were enabled, with a CMA heap, then it would

I have the same problem. imx8mmevk does not boot with Yocto Dunfell. Booting stops at "PCIe PLL lock timeout" or "Initialized imx-drm 1.0.0 20120507 for soc@0:bus@32c00000:display-subsystem on minor 0

Hi, when I generate a SDK (for example by running MACHINE=imx8mmevk bitbake -c populate_sdk core-image-weston), I notice that the headers from linux-imx-headers are missing even though linux-imx-heade

Two problems actually. First, gstreamer1.0-plugins-imx has its PxP plugin enabled. Second, libimxdmabuffer's PxP allocator is enabled. This allocator is then tested for in the test-alloc program. This

The nitrogen6x machine config also supports other machines according to the comment block inside the .conf file: This is the reason for this line in the config: MACHINEOVERRIDES =. "mx6:mx6dl:mx6q:" T

Thanks, that fixed it. I'll send a PR.

I tried to build a nitrogen8m image with the current master branches of poky, meta-freescale, meta-freescale-3rdparty, and meta-openembedded. However, I immediately got this error: ${PACKAGE_EXTRA_ARC

This issue came up when I noticed that the ION and DWL allocators in libimxdmabuffer failed. (DWL is an API from the Hantro VPU libraries, and it fails, because internally it itself uses ION.) This is

Hm I thought there was some sort of imx-kernel base class. Apparently there isn't. If there were, it could then be merged with the linux-imx-headers recipe, and perhaps create something like a -dev pa

The linux-imx-headers recipe gathers certain headers from the kernel source so that other recipes which do access these headers don't have to mark the entire kernel as a dependency. However, if a plat

etnaviv takes care of GPU support, which is related to scaling, but unrelated to video decoding - the latter one is handled by the CODA960 VPU. For using etnaviv, just use glimagesink. For using the V

libimxdmabuffer provides an API for allocating and handling physically contiguous buffers ("DMA buffers") on imx6, imx7, imx8 machines with the imx-kernel. The underlying allocation can be backed by t

This follows the OE-Core upgrade. Signed-off-by: Carlos Rafael Giani <crg7475@...> --- ..._1.14.%.bbappend => gstreamer1.0-plugins-base_1.16.%.bbappend} | 0 1 file changed, 0 insertions(+), 0

When I try to build an image, the rootfs generation fails, because both firmware-qca9377 and firmware-qca6174 want to install /etc/bluetooth/firmware.conf . This happens with both core-image-base and