From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: Sriraman Ravi <Sriraman.Ravi@microsys.de>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: REGRESSION: Qt5 EGLFS support is broken 3.10.53-1.1.x and 3.14.28-1.0.x GPU
Date: Tue, 1 Sep 2015 13:40:23 -0300 [thread overview]
Message-ID: <CAP9ODKob-=fnBUGMjg8nBFzhrHCdBO7g_849qtL8dmyev9bckQ@mail.gmail.com> (raw)
In-Reply-To: <AM3PR06MB102846E18ADCBA0C9AEF3C24ED6A0@AM3PR06MB1028.eurprd06.prod.outlook.com>
On Tue, Sep 1, 2015 at 9:11 AM, Sriraman Ravi <Sriraman.Ravi@microsys.de> wrote:
> How do i go about resolving the issue any suggestions ?
>
> Should I try to build meta-qt5 master branch which says qt5.5 has been ported or is it possible to find the recipe that you mentioned for custom qtmultimedia5.5
I am not sure; it all depends on many things so I think you need to
debug and see which solution works better for your customer.
--
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
prev parent reply other threads:[~2015-09-01 16:40 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
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 [this message]
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='CAP9ODKob-=fnBUGMjg8nBFzhrHCdBO7g_849qtL8dmyev9bckQ@mail.gmail.com' \
--to=otavio.salvador@ossystems.com.br \
--cc=Sriraman.Ravi@microsys.de \
--cc=meta-freescale@yoctoproject.org \
/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.