From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: John Rigby <jcrigby@gmail.com>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
Prabhu Sundararaj <prabhu.sundararaj@freescale.com>,
Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: REGRESSION: Qt5 EGLFS support is broken 3.10.53-1.1.x and 3.14.28-1.0.x GPU
Date: Wed, 15 Jul 2015 08:59:35 -0300 [thread overview]
Message-ID: <CAP9ODKrs3k-gshmubjJ1OStQ4QZw27S7Qxub9yGNdd1a1=5urw@mail.gmail.com> (raw)
In-Reply-To: <CAAmKreQx2+-GDg20HQ8xMskZcnYQSvxGYJ3DBO6C7EWwa-du3A@mail.gmail.com>
On Wed, Jul 15, 2015 at 12:04 AM, John Rigby <jcrigby@gmail.com> wrote:
> I need EGLFS on mx6, does this question mean there are issues with fido and
> that I should stick with dizzy for now?
It seems I was the only one seeing this failure and I couldn't yet get
back to debug this. We are finishing a demo and this will be upgraded
for Fido just after it is finished and will than debug this at that
time.
--
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:[~2015-07-15 11:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 18:05 REGRESSION: Qt5 EGLFS support is broken 3.10.53-1.1.x and 3.14.28-1.0.x GPU Otavio Salvador
2015-06-21 21:48 ` Andreas Müller
2015-07-15 3:04 ` John Rigby
2015-07-15 11:59 ` Otavio Salvador [this message]
2015-07-15 15:33 ` Alfonso Tamés
2015-07-20 18:46 ` Caio
2015-07-20 20:09 ` Max Krummenacher
2015-08-06 20:53 ` Qt5CinematicExperience with 3.14.38 beta? randy
2015-08-07 13:55 ` Otavio Salvador
2015-08-07 14:01 ` randy
2015-08-07 16:45 ` Otavio Salvador
2015-09-01 8:20 ` REGRESSION: Qt5 EGLFS support is broken 3.10.53-1.1.x and 3.14.28-1.0.x GPU Sriraman Ravi
2015-09-01 11:48 ` Otavio Salvador
2015-09-01 12:11 ` Sriraman Ravi
2015-09-01 16: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='CAP9ODKrs3k-gshmubjJ1OStQ4QZw27S7Qxub9yGNdd1a1=5urw@mail.gmail.com' \
--to=otavio.salvador@ossystems.com.br \
--cc=jcrigby@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
--cc=prabhu.sundararaj@freescale.com \
/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.