[meta-freescale] using openGL via SW

[Daiane Angolini]

On Fri, Aug 28, 2015 at 12:46 PM, Nikolay Dimitrov <picmaster at mail.bg> wrote:
> Hi Daiane,
>
>
> On 08/28/2015 05:53 PM, Daiane Angolini wrote:
>>
>> On Fri, Aug 28, 2015 at 11:02 AM, Prabhu S <prabhusundar at gmail.com> wrote:
>>>
>>> Thats sounds like poky bug. BSP layer should not cause problem I hope.
>>
>>
>> Do you know if there is any kernel (3.14) pieces I should double check?
>>
>> I don't have any DRI on my DISTRO_FEATURE (because I'm using default one)
>>
>>
>> Daiane
>>>
>>>
>>> On Fri, Aug 28, 2015 at 8:32 AM, Daiane Angolini <daiane.list at gmail.com>
>>> wrote:
>>>>
>>>>
>>>> On Thu, Aug 27, 2015 at 5:09 PM, Otavio Salvador
>>>> <otavio.salvador at ossystems.com.br> wrote:
>>>>>
>>>>> On Thu, Aug 27, 2015 at 4:30 PM, Daiane Angolini
>>>>> <daiane.list at gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> I'm trying to enable openGL on a not accelerated board (imx7d).  I
>>>>>> thought it would be out-of-box  but it is not.
>>>>>>
>>>>>> I'm using imx7dsabresd machine, and  to be sure added:
>>>>>>
>>>>>>
>>>>>> CORE_IMAGE_EXTRA_INSTALL += "mesa-demos mesa-glut glmark2"
>>>>>>
>>>>>> on local.conf, and this is the only change on top of master
>>>>>> (core-image-x11) But when I try glmark I get an error message
>>>>>>
>>>>>> $ DISPLAY=:0 glmark2
>>>>>> name of display: :0
>>>>>> Error: couldn't find RGB GLX visual or fbconfig
>>>>>>
>>>>>> I get the same error if I try glxgears. But I see the X11 console on
>>>>>> screen (typical core-image-x11)
>>>>>>
>>>>>> Am I missing something obvious?
>>>>>
>>>>>
>>>>> Try adding mesa-gl in the image.
>>>>
>>>>
>>>> I've tried:
>>>>
>>>> ERROR: Multiple .bb files are due to be built which each provide
>>>> virtual/mesa
>>>>
>>>> (/code/yocto/master/sources/poky/meta/recipes-graphics/mesa/mesa-gl_10.6.3.bb
>>>>
>>>>
>>>> /code/yocto/master/sources/poky/meta/recipes-graphics/mesa/mesa_10.6.3.bb).
>>>>   This usually means one provides something the other doesn't and
>>>> should.
>>>> ERROR: Multiple .bb files are due to be built which each provide
>>>> virtual/libgl
>>>>
>>>> (/code/yocto/master/sources/poky/meta/recipes-graphics/mesa/mesa-gl_10.6.3.bb
>>>>
>>>>
>>>> /code/yocto/master/sources/poky/meta/recipes-graphics/mesa/mesa_10.6.3.bb).
>>>>   This usually means one provides something the other doesn't and
>>>> should.
>>>>
>>>> Even if I clean tmp or  mesa
>>>>
>>>>
>>>> Daiane
>
>
> About the 1st issue - it seems that mesa and mesa-gl are pulled-in at
> the same time, both providing virtual/mesa, thus the error message.
>
> The reason is that core-image-x11 pulls-in the mesa-gl explicitly,
> instead of using virtual/mesa (which I guess is the proper behavior).

Only because I'm not pretty sure I full understand this topic:

When I add "mesa" I get to a image and RGB error
When I add "mesa-gl" I get a build error.

So, I think I understand what you're saying, but instead of "mesa-gl"
being explicitly added, it's "mesa".

And, I don't know mesa or mesa-gl, but the their description is that
mesa has mesa-gl. Or in other words, mesa has everything mesa-gl has,
and mesa-gl has only a sub-set of what mesa has. That, for me it's
pretty OK as I don't care using mesa

However, it's weird (to me, a person who don't know mesa, or openGL
and her sisters) that this does not work out-of-box. It makes me think
I'm missing some kind of -egl or a DISTRO_FEATURE, or a kernel module
(because it's 3.14)

Maybe, another option would ask upstream in poky/OE ML. =(


Daiane


>
> You can verify this:
>
> bitbake -g core-image-x11
> grep core-image-x11 pn-depends.dot | grep mesa-gl
>
> Regards,
> Nikolay