From: "Eric Bénard" <eric@eukrea.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: mesa-dri vs amd-gpu-x11-bin-mx51
Date: Sat, 12 Jan 2013 19:00:04 +0100 [thread overview]
Message-ID: <20130112190004.18ce097c@e6520eb> (raw)
In-Reply-To: <CAP9ODKpGit+B=kM69ZjYXxXz4vqaEBdRU8L1wcgQ+py6F9KuMw@mail.gmail.com>
Le Sat, 12 Jan 2013 15:52:46 -0200,
Otavio Salvador <otavio@ossystems.com.br> a écrit :
> On Sat, Jan 12, 2013 at 3:49 PM, Eric Bénard <eric@eukrea.com> wrote:
> > Le Sat, 12 Jan 2013 17:54:13 +0200,
> > Andrei Gherzan <andrei@gherzan.ro> a écrit :
> >
> >> On Sat, Jan 12, 2013 at 4:15 PM, Otavio Salvador <otavio@ossystems.com.br>wrote:
> >>
> >> > On Sat, Jan 12, 2013 at 11:59 AM, Eric Bénard <eric@eukrea.com> wrote:
> >> > > Hi,
> >> > >
> >> > > has anyone here already seen this messages ?
> >> >
> >> > Yes; I started checking it but I still do not have an absolute answer
> >> > to how to fix it.
> >> >
> >> > The problem is xserver-xorg (when it has glx enabled) it depends on
> >> > mesa-dri. Both mesa-dri and GPU package libraries (the mx5 and mx6
> >> > ones) provide same (theorical) functionality of mesa-dri, libraries
> >> > and (most) headers leading to those errors.
> >> >
> >> > I did check how Xorg is compiled in LTIB and it doesn't has glx
> >> > enabled so my idea is to disable glx in Xorg and try to go this route.
> >> > This would allow for a clean build at cost of making xserver-xorg
> >> > machine specific. Do you have any other idea?
> >> >
> >>
> >> Why do you need glx after all? We don't have opengl for imx53 right?
> >> And about the fix. Xorg with glx should depend on virtual/libgl (or gl)
> >> not mesa-dri.
> >>
> > mesa-dri provides virtual/libgl which can explain why we find it here.
>
> In fact mesa provides all them (GL ES2 and GL ES1 too).
yes, I was in Andrei's email context here.
meta-ti has the following lines in libgles-omap3.inc :
PROVIDES += "virtual/egl virtual/libgles1 virtual/libgles2"
RREPLACES_${PN} = "libegl libgles1 libgles2"
RREPLACES_${PN}-dev = "libegl-dev libgles1-dev libgles2-dev"
RREPLACES_${PN}-dbg = "libegl-dbg"
note they have the RREPLACES which are not in meta-fsl-arm's recipes.
Eric
next prev parent reply other threads:[~2013-01-12 18:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 13:59 mesa-dri vs amd-gpu-x11-bin-mx51 Eric Bénard
2013-01-12 14:15 ` Otavio Salvador
2013-01-12 15:54 ` Andrei Gherzan
2013-01-12 16:44 ` Otavio Salvador
2013-01-12 17:49 ` Eric Bénard
2013-01-12 17:52 ` Otavio Salvador
2013-01-12 18:00 ` Eric Bénard [this message]
2013-01-12 18:08 ` Otavio Salvador
2013-01-13 0:57 ` Andrei Gherzan
2013-01-13 1:20 ` Andrei Gherzan
2013-01-13 1:00 ` Andrei Gherzan
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=20130112190004.18ce097c@e6520eb \
--to=eric@eukrea.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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.