All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Issues with Qt5/mesa and eglfs
Date: Tue, 25 Jun 2013 16:19:20 +0100	[thread overview]
Message-ID: <3374023.12gJcMyuIe@helios> (raw)
In-Reply-To: <CAP71WjygMhCMdrbrj8uUKeJZuRu1_cjmhE4cLjsuhJ5wJpxnuQ@mail.gmail.com>

On Tuesday 25 June 2013 13:59:55 Nicolas Dechesne wrote:
> On Thu, Jun 20, 2013 at 8:15 PM, Nicolas Dechesne <
> nicolas.dechesne@linaro.org> wrote:
> > On Thu, Jun 20, 2013 at 11:46 AM, Nicolas Dechesne <
> > 
> > nicolas.dechesne@linaro.org> wrote:
> >> On Thu, Jun 20, 2013 at 11:42 AM, Paul Eggleton <
> >> 
> >> paul.eggleton@linux.intel.com> wrote:
> >>> I wasn't watching closely but my impression is there were a large number
> >>> of
> >>> changes associated with the mesa upgrade. Is the upgrade itself
> >>> necessary for
> >>> the fix?
> >> 
> >> no, i don't think so. I think we might be able to just update the patches
> >> that deal with the X11/no X11 support. but i haven't tested that yet. i
> >> just did a quick test by cherry picking the complete commit (e.g. mesa
> >> upgrade) to verify that it's actually fixing my problem. now that i know
> >> it
> >> does, i will try to just upgrade the patches without the mesa upgrade and
> >> report how it goes.
> > 
> > ok, i was able to backport the mesa patch from 9.1.3 to 9.0.2
> > (EGL-Mutate-NativeDisplayType-depending-on-config.patch) , the backport
> > was
> > more or less trivial. and then i did this in dylan branch:
> > 
> > --- a/meta/recipes-graphics/mesa/mesa-9.0.2.inc
> > +++ b/meta/recipes-graphics/mesa/mesa-9.0.2.inc
> > @@ -2,7 +2,7 @@ SRC_URI = "
> > ftp://ftp.freedesktop.org/pub/mesa/${PV}/MesaLib-${PV}.tar.bz2 \
> > 
> >             file://0002-cross-compile.patch \
> >             file://cross-glsl.patch \
> >             file://dont-fail-if-libX11-isnt-installed.patch \
> > 
> > -           file://fix-egl-compilation-without-x11-headers.patch \
> > +           file://EGL-Mutate-NativeDisplayType-depending-on-config.patch
> > \
> > 
> >             "
> > 
> > and it does fix the build issue i had (mesa/qt5/non X11 distro).
> > should that be merged into dylan (since it's merged in master already) or
> > do we need to wait for the 'final' patch in upstream to be ready?
> 
> Paul, Martin, what do you think about this? i have the (trivial) dylan
> backport ready. Do you think it's the right time to get it merged?

I'd say please send the patch to the mailing list (marked with [dylan]) and 
then we can review it. By the sounds of things it should be OK.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  parent reply	other threads:[~2013-06-25 15:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 13:15 Issues with Qt5/mesa and eglfs Nicolas Dechesne
2013-06-20 13:33 ` Burton, Ross
2013-06-20 13:46 ` Nicolas Dechesne
2013-06-20 15:42   ` Paul Eggleton
2013-06-20 15:46     ` Nicolas Dechesne
2013-06-20 18:15       ` Nicolas Dechesne
2013-06-25 11:59         ` Nicolas Dechesne
2013-06-25 12:22           ` Martin Jansa
2013-06-25 15:19           ` Paul Eggleton [this message]
2013-06-20 15:06 ` Martin Jansa
2013-06-20 15:25   ` Nicolas Dechesne

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=3374023.12gJcMyuIe@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=nicolas.dechesne@linaro.org \
    --cc=openembedded-core@lists.openembedded.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.