From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id CC63BE00B72; Tue, 1 Sep 2015 00:49:28 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (picmaster[at]mail.bg) * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [193.201.172.119 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mx3.mail.bg (mx3.mail.bg [193.201.172.119]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 1748EE00AB5 for ; Tue, 1 Sep 2015 00:49:24 -0700 (PDT) Received: from [192.168.43.84] (85-118-69-113.mtel.net [85.118.69.113]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx3.mail.bg (Postfix) with ESMTPSA id 4C23420549EE; Tue, 1 Sep 2015 10:49:22 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1441093762; bh=Rn6Ao3NC3JdUW0fpGYifzsdrJpF4K2drzvtM8DM2xg8=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=Wsf2NbNII/4hyLwhsy/byx45nACx07R/NrSbxmvwQEy2oH1UnbMP+bCC5gJf+o2gC tGso1dIJJfdtE5lNQfL3mUnG5xAEZDJtxKKvdgwERc2ZQaVzqOaQ0xdSM/5G9wT0HD Ac0ORdc6t3ZlnBjTLTCvREAf+Vcom693fEsqfs8Q= Message-ID: <55E55880.6070307@mail.bg> Date: Tue, 01 Sep 2015 10:49:20 +0300 From: Nikolay Dimitrov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.8.0 MIME-Version: 1.0 To: Daiane Angolini References: <55E0824E.4020507@mail.bg> In-Reply-To: Cc: "meta-freescale@yoctoproject.org" , Otavio Salvador Subject: Re: using openGL via SW X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Sep 2015 07:49:28 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi Daiane, On 08/28/2015 07:26 PM, Daiane Angolini wrote: > On Fri, Aug 28, 2015 at 12:46 PM, Nikolay Dimitrov wrote: >> Hi Daiane, >> >> >> On 08/28/2015 05:53 PM, Daiane Angolini wrote: >>> >>> On Fri, Aug 28, 2015 at 11:02 AM, Prabhu S 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 >>>> wrote: >>>>> >>>>> >>>>> On Thu, Aug 27, 2015 at 5:09 PM, Otavio Salvador >>>>> wrote: >>>>>> >>>>>> On Thu, Aug 27, 2015 at 4:30 PM, Daiane Angolini >>>>>> >>>>>> 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) Sorry if my comment sounded like teaching, as it was definitely not the case. I'm exactly in the "same shoes" as you regarding the GL stuff (eg non-expert), just tried to double-check for you on my build-box and look for some obvious things, following yours and Otavio's comments. So far my limited understanding of the issue is quite similar to yours - we either lack a proper config option/flag, or some recipes are broken for imx7. As one friend of mine said once, "This will require thinking" :). > > 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