On 26 April 2016 at 12:36, Burton, Ross wrote:
> We used virtual/mesa to mean "the Mesa APIs and so on" so libgbm is
> covered by this. Of course at the time there was only one implementation
> in mesa. Now that there are genuine alternative reimplementations of
> libgdm then I agree that a vir
On Tue, Apr 26, 2016 at 11:27 AM, Denys Dmytriyenko wrote:
> On Tue, Apr 26, 2016 at 03:00:59PM +0100, Burton, Ross wrote:
>> On 26 April 2016 at 12:59, Burton, Ross wrote:
>>
>> > I added a PACKAGECONFIG for libgbm to mesa.inc, enabled it for mesa and
>> > disabled it for mesa-gl, and mesa-gl st
On Tue, Apr 26, 2016 at 03:00:59PM +0100, Burton, Ross wrote:
> On 26 April 2016 at 12:59, Burton, Ross wrote:
>
> > I added a PACKAGECONFIG for libgbm to mesa.inc, enabled it for mesa and
> > disabled it for mesa-gl, and mesa-gl still build fine but didn't ship a
> > libgbm.
> >
> > I've forgott
On Tue, Apr 26, 2016 at 12:59:05PM +0100, Burton, Ross wrote:
> On 25 April 2016 at 17:50, Denys Dmytriyenko wrote:
>
> > One other thing I was thinking is how to avoid conflict between separate
> > libgbm and the one provided by mesa-gl. As mesa-gl may be useful for
> > providing
> > SW renderin
On Tue, Apr 26, 2016 at 12:36:10PM +0100, Burton, Ross wrote:
> On 22 April 2016 at 01:27, Christopher Larson wrote:
>
> > 1. Change weston recipe in oe-core to depend on libgbm instead of
> >> virtual/mesa
> >> assuming that it is provided by mesa recipe and it works for other
> >> platforms.
>
On 26 April 2016 at 12:59, Burton, Ross wrote:
> I added a PACKAGECONFIG for libgbm to mesa.inc, enabled it for mesa and
> disabled it for mesa-gl, and mesa-gl still build fine but didn't ship a
> libgbm.
>
> I've forgotten the details about all of this: does mesa-gl shipping libgbm
> make sense
On 25 April 2016 at 17:50, Denys Dmytriyenko wrote:
> One other thing I was thinking is how to avoid conflict between separate
> libgbm and the one provided by mesa-gl. As mesa-gl may be useful for
> providing
> SW rendering for OpenGL, while leaving OpenGLES to a separate provider,
> like
> SGX.
On 22 April 2016 at 01:27, Christopher Larson wrote:
> 1. Change weston recipe in oe-core to depend on libgbm instead of
>> virtual/mesa
>> assuming that it is provided by mesa recipe and it works for other
>> platforms.
>>
>
> I'd say this, either libgbm or virtual/libgbm.
>
We used virtual/mes
On Fri, Apr 22, 2016 at 12:27:16AM +, Christopher Larson wrote:
> On Thu, Apr 21, 2016 at 5:06 PM Denys Dmytriyenko wrote:
>
> > All,
> >
> > I've been meaning to ask this for quite some time. It appears that Weston's
> > DRM compositor enabled with "kms" PACKAGECONFIG doesn't really need the
On Thu, Apr 21, 2016 at 5:06 PM Denys Dmytriyenko wrote:
> All,
>
> I've been meaning to ask this for quite some time. It appears that Weston's
> DRM compositor enabled with "kms" PACKAGECONFIG doesn't really need the
> entire
> mesa, but it only needs libgbm. Now, mesa in OE-Core provides libgbm
All,
I've been meaning to ask this for quite some time. It appears that Weston's
DRM compositor enabled with "kms" PACKAGECONFIG doesn't really need the entire
mesa, but it only needs libgbm. Now, mesa in OE-Core provides libgbm as one of
its packages, hence virtual/mesa is added in DEPENDS for
11 matches
Mail list logo
