From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 5BA31E009A7; Tue, 30 Jun 2015 07:13:11 -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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mail.chez-thomas.org (mail.mlbassoc.com [65.100.170.105]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 6A34CE00992 for ; Tue, 30 Jun 2015 07:13:04 -0700 (PDT) Received: by mail.chez-thomas.org (Postfix, from userid 1998) id 0BC94F811DB; Tue, 30 Jun 2015 08:13:03 -0600 (MDT) Received: from [192.168.1.114] (zeus [192.168.1.114]) by mail.chez-thomas.org (Postfix) with ESMTP id 5A756F811DB; Tue, 30 Jun 2015 08:13:03 -0600 (MDT) Message-ID: <5592A41C.3060803@mlbassoc.com> Date: Tue, 30 Jun 2015 08:13:48 -0600 From: Gary Thomas User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: meta-freescale@yoctoproject.org References: In-Reply-To: Subject: Re: Removing gpu-viv-bin-mx6q from custom image 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, 30 Jun 2015 14:13:11 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 2015-06-30 08:04, Jean-Michel Hautbois wrote: > 2015-06-30 15:49 GMT+02:00 Daiane Angolini : >> On Tue, Jun 30, 2015 at 10:37 AM, Jean-Michel Hautbois >> wrote: >>> 2015-06-30 15:29 GMT+02:00 Daiane Angolini : >>>> On Tue, Jun 30, 2015 at 10:20 AM, Jean-Michel Hautbois >>>> wrote: >>>>> 2015-06-30 14:13 GMT+02:00 Daiane Angolini : >>>>>> On Tue, Jun 30, 2015 at 9:01 AM, Jean-Michel Hautbois >>>>>> wrote: >>>>>>> Hi Daiane, >>>>>>> >>>>>>> 2015-06-30 13:37 GMT+02:00 Daiane Angolini : >>>>>>>> On Tue, Jun 30, 2015 at 2:33 AM, Jean-Michel Hautbois >>>>>>>> wrote: >>>>>>>>> Hi ! >>>>>>>>> >>>>>>>>> I have a custom image for a I.MX6 board and I don't need to have the >>>>>>>>> gpu-viv-bin-mx6q package installed. I am depending in my image on >>>>>>>>> core-image-base and I don't add it in the EXTRA_IMAGE_INSTALL variable. But >>>>>>>>> I still get it installed. >>>>>>>>> >>>>>>>>> What is it installed by and how can I remove it ? >>>>>>>> >>>>>>>> The complete BSP is built targeting the maximum use of GPU >>>>>>>> acceleration for any imx6Q boards. That's why you cannot "remove" GPU >>>>>>>> packages. Too many dependencies making you use it by default. >>>>>>>> >>>>>>>> You can try to blacklist it >>>>>>>> (http://www.yoctoproject.org/docs/1.8/mega-manual/mega-manual.html#ref-classes-blacklist) >>>>>>>> >>>>>>>> Or, you can override several BSP configurations: >>>>>>>> >>>>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/conf/machine/include/imx-base.inc#n23 >>>>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/conf/machine/include/imx-base.inc#n94 >>>>>>>> (from line 94 to 108) >>>>>>> >>>>>>> Just tested to add this to my custom machine : >>>>>>> XSERVER_DRIVER_mx6 ?= "" >>>>>>> PREFERRED_PROVIDER_virtual/egl_mx6 ?= "" >>>>>>> PREFERRED_PROVIDER_virtual/libgles1_mx6q ?= "" >>>>>>> PREFERRED_PROVIDER_virtual/libgles1_mx6dl ?= "" >>>>>>> PREFERRED_PROVIDER_virtual/libgles1_mx6sx ?= "" >>>>>>> PREFERRED_PROVIDER_virtual/libgles1_mx6sl ?= "" >>>>>>> PREFERRED_PROVIDER_virtual/libgles2_mx6q ?= "" >>>>>>> PREFERRED_PROVIDER_virtual/libgles2_mx6dl ?= "" >>>>>>> PREFERRED_PROVIDER_virtual/libgles2_mx6sx ?= "" >>>>>>> PREFERRED_PROVIDER_virtual/libgles2_mx6sl ?= "" >>>>>>> PREFERRED_PROVIDER_virtual/libgl_mx6q ?= "" >>>>>>> PREFERRED_PROVIDER_virtual/libgl_mx6dl ?= "" >>>>>>> PREFERRED_PROVIDER_virtual/libgl_mx6sx ?= "" >>>>>>> PREFERRED_PROVIDER_virtual/libgl_mx6sl ?= "" >>>>>>> PREFERRED_PROVIDER_virtual/libg2d_mx6 ?= "" >>>>>>> >>>>>>> But the following command still shows gpu-viv-bin-mx6q : >>>>>>> bitbake -g my-image && cat pn-depends.dot | grep -v -e '-native' | >>>>>>> grep -v digraph | grep -v -e '-image' | awk '{print $1}' | sort | uniq >>>>>> >>>>>> >>>>>> I would use a stronger assignemnt instead of ?= >>>>>> (http://www.yoctoproject.org/docs/1.6/bitbake-user-manual/bitbake-user-manual.html#setting-a-default-value) >>>>>> >>>>>> Maybe imx-base.inc from BSP is stronger than you machine config file. >>>>>> >>>>>> However, maybe I forgot one BSP dependency. Which package your >>>>>> dependency graph say is bringing the vpu package? >>>>> >>>>> You mean bitbake -g gpu-viv-bin-mx6q ? >>>>> Or something else ? >>>> >>>> I though about using the same command line you shared before: >>>> >>>>>>> bitbake -g my-image && cat pn-depends.dot | grep -v -e '-native' | >>>>>>> grep -v digraph | grep -v -e '-image' | awk '{print $1}' | sort | uniq >>>> >>>> But without the grep's >>>> >>>> Daiane >>>>> >>>>> JM >>> >>> Well, it is quite big, I grepped on "gpu-viv" to start : >>> "gpu-viv-bin-mx6q" [label="gpu-viv-bin-mx6q >>> 1:3.10.17-1.0.2-hfp-r0\n/run/media/jm/SSD_JM/Projets/veobox3/poky/meta-fsl-arm/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q_3.10.17-1.0.2-hfp.bb"] >>> "gpu-viv-bin-mx6q" -> "virtual/arm-poky-linux-gnueabi-gcc" >>> "gpu-viv-bin-mx6q" -> "mesa" >>> "gpu-viv-bin-mx6q" -> "libxext" >>> "gpu-viv-bin-mx6q" -> "virtual/arm-poky-linux-gnueabi-compilerlibs" >>> "gpu-viv-bin-mx6q" -> "virtual/libc" >>> "gpu-viv-bin-mx6q" -> "libxfixes" >>> "gpu-viv-bin-mx6q" -> "libxdamage" >>> "gpu-viv-bin-mx6q" -> "virtual/libx11" >>> "gpu-viv-bin-mx6q" -> "libdrm" [style=dashed] >>> "gpu-viv-bin-mx6q" -> "libclc-mx6" [style=dashed] >>> "gpu-viv-bin-mx6q" -> "libglslc-mx6" [style=dashed] >>> "gpu-viv-bin-mx6q" -> "gpu-viv-bin-mx6q" [style=dashed] >>> "gpu-viv-bin-mx6q" -> "gpu-viv-bin-mx6q-dev" [style=dashed] >>> >>> >>> If you want everything, I will paste it, but not sure it would be useful ? >> >> Well I expected it to be huge. The idea here is to try to understand >> which are the configuration which is bringing the features vivante >> PROVIDES. >> >> For example, it looks like you are using X11, even not using X11. You >> can think about remove it from DISTRO_FEATURES. >> >> What happens is something like: x11 lib -> GL -> vivante > > Thanks a *lot* !! > It seems far better, as mesa disappeared :). > I will go deeply into this, it seems to be the good way ! > I still have gpu-viv-bin-mx6q but only with : > "gpu-viv-bin-mx6q" [label="gpu-viv-bin-mx6q > 1:3.10.17-1.0.2-hfp-r0\n/run/media/jm/SSD_JM/Projets/veobox3/poky/meta-fsl-arm/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q_3.10.17-1.0.2-hfp.bb"] > "gpu-viv-bin-mx6q" -> "virtual/arm-poky-linux-gnueabi-gcc" > "gpu-viv-bin-mx6q" -> "virtual/arm-poky-linux-gnueabi-compilerlibs" > "gpu-viv-bin-mx6q" -> "virtual/libc" > "gpu-viv-bin-mx6q" -> "gpu-viv-bin-mx6q" [style=dashed] > "gpu-viv-bin-mx6q" -> "gpu-viv-bin-mx6q-dev" [style=dashed] > "gpu-viv-bin-mx6q" -> "libdrm" [style=dashed] > "gpu-viv-bin-mx6q" -> "libclc-mx6" [style=dashed] > "gpu-viv-bin-mx6q" -> "libglslc-mx6" [style=dashed] > > I removed opengl from DISTRO_FEATURES, but there may be something else... > >> What was the result of blacklist'ing the package name? > > Not better. > JM > What kind of image are you trying to build (without X11)? What did you base your image on, e.g. core-image-minimal? I routinely build minimal images for the i.MX6 without X (and without removing x11 from DISTRO_FEATURES) and don't end up with any of this extra stuff... -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------