[meta-freescale] [meta-fsl-arm][PATCH 2/4] xserver-xorg: Add bbappend to include dri and exclude glx for imx6

[Andrei Gherzan]

On Sun, Jan 13, 2013 at 9:48 PM, Eric Bénard <eric at eukrea.com> wrote:

> Le Sun, 13 Jan 2013 21:23:18 +0200,
> Andrei Gherzan <andrei at gherzan.ro> a écrit :
> > On Sun, Jan 13, 2013 at 7:41 PM, Eric Bénard <eric at eukrea.com> wrote:
> > > in openembedded-core, dri (and glx) are enabled only if opengl is a
> > > DISTRO_FEATURE so the choice to enable these feature is done at distro
> > > level and not at machine level.
> > > So to be consistent with that, you could split dri/glx but I think
> > > dri should be enabled only when the distro has enabled opengl.
> > >
> > > Note that we have the same problem in the qt4 recipes : in oe-core,
> > > opengl is enabled ony if DISTRO_FEATURE has opengl, in meta-fsl-arm
> > > opengl (and openvg) are enabled by default. I'm not sure a BSP should
> > > force these settings if the distro doesn't want them.
> > >
> >
> > So. I know the way oe-core chooses to use opengl and it's right. As long
> as
> > gl is provided as a distro / mesa-dri provider. But after all libgl / egl
> > and so on can be hardware dependent binaries. And this is why i want to
> > treat them like that. I would consider this a workaround until things
> will
> > be completed in oe-core. But right now this, in my opinion, the only good
> > way to fix an issue like this.
> >
> I agree with you that this could be hardware dependent and not distro
> dependent. So if I understand well you plan to migrate that in
> oe-core from DISTRO_FEATURES to MACHINE_FEATURES ?
>

Yes. This is want. But things will be tricky. Need to think how to do it.
We had a talk in oe-core ago. Things didn't come to a conclusion yet.

ag
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-freescale/attachments/20130113/f1510777/attachment.html>