Definitely doing CPU decoding. I don't see any kernel messages that indicate the VPU has been detected even though I have CONFIG_VIDEO_IMX_PXP=y in the kernel config. Is that the correct option? Are t

Does anyone know definitively if etnaviv/gstreamer has support for accelerated h264 decoding/rescaling? I can play video through both the fbcondev and wayland sinks, but both consume a great deal of C

Trying to get linux-fslc-imx running on a new custom carrier board running a Karo-8133 module and I'm stuck trying to get the root filesystem to detect. Trying different things the boot process can ne

Of course the moment I said that I realized I had not tried the "--ignore-gpu-blacklist" option. Now it at least starts.

Has anyone successfully run Chromium on Krogoth using Wayland/weston? I'm stuck on the "InitializeSandbox() called with multiple threads in process gpu-process" bug that a lot of people seem to have r

If our app runs video using gstreamer and the imx gstreamer drivers if works great for about 24-50 hours, then weston gets stuck on a black white or blank black screen. Our app can still be heard play

We are running an embedded application written against GTK3 running atop Weston 1.9.0 and we see crashes occasionally with "caught signal: 6 `weston' : corrupted double-linked list (not small): We hav

<dv@...> wrote: Sorry (updated): Everything is from the current fsl-krogath branch. gstreamer1.0_1.6.3 imx-gst1.0-plugin_4.0.9 gstreamer1.0-plugins-imx_0.12.2 kernel-module-imx-gpu-viv_

<dv@...> wrote: Everything is from the current fsl-krogath branch. gstreamer1.0_1.6.3 imx-gst1.0-plugin_4.0.9 kernel-module-imx-gpu-viv_5.0.11.p8.4+fslc kernel is 4.1.15 The hardware is

Having an intermittent issue, and I'm not really sure where to turn, or what the solution might be. We have a kiosk that plays a series of videos in a repeating loop via GTK+/Weston and GStreamer. Occ

Has anyone done any work or thinking about bringing the uboot-sign class into fsl? I've been playing with it, but the process used for generating the u-boot image doesn't generate the right artifacts.

Just for posterity's sake, the fix for the above issue was that the "default_bpp" setting in the mxcfb1 device tree entry of my custom kernel was set to 24. Changing it to 16 resolved the issue. mxcfb

On Aug 21, 2016 6:40 PM, "Burton, Ross" <ross.burton@...> wrote: > > So libGL is explicitly GLX, so obviously needs X11. > Yes, removing x11 from DISTRO_FEATURES will remove every trace of X11 f

It seems like libSDL2-ttf has an ability to render fonts using OpenGL. This feature is enabled by the successful compilation of a test program in .configure. Why if I remove x11 from DISTRO_FEATURES d

I attempted to make a image based on core-image-weston with the addition of just libsld2-ttf and it seems to get hung up with libGL referencing libX11 functions: Log data follows: | DEBUG: SITE files