From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: vmach@ramet.as
Cc: meta-freescale Mailing List <meta-freescale@yoctoproject.org>
Subject: Re: Odp: Re: Troubles with Qt after upgrade from Morty to Pyro (plaintext email)
Date: Wed, 25 Apr 2018 14:37:36 -0300 [thread overview]
Message-ID: <CAP9ODKoiQm8HUXhR3v1AWtecFGGobgYiSR7Yg-1YHUy2NSakqg@mail.gmail.com> (raw)
In-Reply-To: <OFD566A973.D0D22AD4-ONC1258275.00449DD8-C1258275.00473DE2@ramet.as>
On Fri, Apr 20, 2018 at 9:58 AM, <vmach@ramet.as> wrote:
> I finally moved to Rocko branch, avoided the meta-boundary layer and made an
> image. Kernel version is linux_boundary_4.1.15, Gstreamer version is 1.12.2.
> The behavior is very similar:
>
> 1) export DISPLAY=:0.0 && gst-launch-1.0 videotestsrc ! imxg2dvideotransform
> ! imxg2dvideosink
> works fine without any troubles
>
> 2) export DISPLAY=:0.0 && gst-launch-1.0 videotestsrc ! imxg2dvideotransform
> ! imxeglvivsink
> a) crashes with segfault during the first run after power on of the
> Nitrogen6x_MAX QP
> b) second and every other following run of this pipeline causes X window
> with black screen. No videotest pictures.
>
> In all cases, GST_DEBUG=3 has no warnings or errors. Do you have any
> suggestion how to make the imxeglvivsink work?
This is mostly likely to be due the different between the GPU driver
module inside the kernel source versus the binary drivers.
Check if you are using our external module and it should work.
--
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
next prev parent reply other threads:[~2018-04-25 17:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 15:38 Troubles with Qt after upgrade from Morty to Pyro (plaintext email) vmach
2018-01-18 0:44 ` Ian Coolidge
2018-04-20 12:58 ` Odp: " vmach
2018-04-25 17:37 ` Otavio Salvador [this message]
2018-04-27 10:57 ` Odp: " vmach
2018-04-27 12:44 ` Otavio Salvador
2018-04-27 13:20 ` Odp: " vmach
2018-04-27 13:40 ` Otavio Salvador
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP9ODKoiQm8HUXhR3v1AWtecFGGobgYiSR7Yg-1YHUy2NSakqg@mail.gmail.com \
--to=otavio.salvador@ossystems.com.br \
--cc=meta-freescale@yoctoproject.org \
--cc=vmach@ramet.as \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.