[yocto] [PATCH 4/4] mesa-dri.bbappend: avoid conflict with emgd-driver-bin

[Kamble, Nitin A]

> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton at intel.com]
> Sent: Wednesday, October 31, 2012 10:14 AM
> To: Kamble, Nitin A
> Cc: Zanussi, Tom; Hart, Darren; yocto at yoctoproject.org
> Subject: Re: [yocto] [PATCH 4/4] mesa-dri.bbappend: avoid conflict with
> emgd-driver-bin
> 
> Hi,
> 
> On 31 October 2012 02:23,  <nitin.a.kamble at intel.com> wrote:
> > Extend the mesa-dri recipe from oecore to avoid conflict with files
> > generated by emgd-driver-bin recipe.
> 
> The same problem happens with cdv-pvr-driver, right?
Yes, I have heard about the issue from Rahul.

> 
> It turns out that the binary DRI drivers these closed driver packages install are
> very dependent on the Mesa - so it's likely that they just don't work with our
> Mesa 8.0.4.
> 
> cdv-pvr-driver needs Mesa 7.11.  I can't see anything in the documentation
> about what version of Mesa EMGD expects.

EMGD tarball release notes do mention Mesa version dependencies. We have not seen issues with the newer version of mesa, so went ahead with the newer versions of Mesa, while pinning the Mesa version in the machine.conf.


> 
> I think we've two options: either don't ship libGL in our BSP packages, or ship
> a version that should actually work.  This means shipping a mesa recipe in
> meta-intel so that it's under meta-intel's control, with the useful side effect
> that we can make it just build libGL and nothing else.

These are the right options IMO. We can also get complete mesa recipe in meta-intel, which will override the one from oecore layer completely. Then we have full control of mesa from meta-intel layers. Currently extending the oecore mesa recipe from meta-intel is not very elegant, but at least it is working as we want. Also making few changes to the oecore mesa recipe will make it easier to extend it from other layers. 

Nitin


> 
> Ross