Re: raspberry Pi core-image-sato booted okay

[Gary Thomas <gary@mlbassoc.com>]

On 2015-07-23 09:53, Edward Vidal wrote:
> i Gary,
>
> I added to my the 2 lines mentioned in the e-mail to my conf/local.conf
>
> PREFERRED_PROVIDER_virtual/egl ?= "vc-graphics-hardfp"
> PREFERRED_PROVIDER_virtual/libgles2 ?= "vc-graphics-hardfp"
>
> I had saved the original local.conf in ~/wkg/yocto/local.conf before making any changes.
>
> diff -u ~/wkg/yocto/local.conf conf/local.conf
> --- /home/vidal/wkg/yocto/local.conf    2015-07-21 08:15:40.228867905 -0600
> +++ conf/local.conf    2015-07-23 09:11:45.095116784 -0600
> @@ -10,6 +10,25 @@
>   # default values are provided as comments to show people example syntax. Enabling
>   # the option is a question of removing the # character and making any change to the
>   # variable as required.
> +PREFERRED_PROVIDER_virtual/egl ?= "vc-graphics-hardfp"
> +PREFERRED_PROVIDER_virtual/libgles2 ?= "vc-graphics-hardfp"
> +#
> +# Parallelism Options
> +#
> +# These two options control how much parallelism BitBake should use. The first
> +# option determines how many tasks bitbake should run in parallel:
> +#
> +BB_NUMBER_THREADS = "12"
> +#
> +# The second option controls how many processes make should run in parallel when
> +# running compile tasks:
> +#
> +PARALLEL_MAKE = "-j 12"
> +#
> +# For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
> +# be appropriate for example.
> +
> +#
>
>   #
>   # Machine Selection
> @@ -34,7 +53,10 @@
>   #MACHINE ?= "edgerouter"
>   #
>   # This sets the default machine to be qemux86 if no other machine is selected:
> -MACHINE ??= "qemux86"
> +#MACHINE ??= "qemux86"
> +#MACHINE = "raspberrypi2"
> +MACHINE ??= "raspberrypi2"
> +GPU_MEM = "16"
>
>   #
>   # Where to place downloads
> @@ -48,7 +70,7 @@
>   # The default is a downloads directory under TOPDIR which is the build directory.
>   #
>   #DL_DIR ?= "${TOPDIR}/downloads"
> -
> +DL_DIR ?= "/home/vidal/wkg/yocto/downloads"
>   #
>   # Where to place shared-state files
>   #
>
> bitbake userland -c cleansstate
>
> bitbake core-image-sato
>
> WARNING: QA Issue: gstreamer1.0-plugins-bad: configure was passed unrecognised options: --with-egl-window-system [unknown-configure-option]
> NOTE: Tasks Summary: Attempted 5356 tasks of which 4131 didn't need to be rerun and all succeeded.
>
> Summary: There was 1 WARNING message shown.
> As root I created the SD
>
>
> dd if=tmp/deploy/images/raspberrypi2/core-image-sato-raspberrypi2.rpi-sdimg | pv | sudo dd of=/dev/sdb bs=16M
>
> The Raspberry Pi 2 B boot to graphical sato interface.
>
> Is there anything else that I can provide.
> How do you when to use -c cleansstate on a recipe?  This appears to be a handy command.

Whenever you want to forcibly remove some recipe/package.  This
cleans up the work (build) tree as well as removes any packaging
which is kept in the sstate-cache, i.e. it's as if you had never
built the recipe in the first place.  In your case, this was needed
because the 'userland' recipe had been previously built which staged
a lot of the libegl* files.  Those conflicted with what the  vc-graphics-hardfp
wanted to install, hence the need to "erase" the userland artifacts.

One little suggestion: when sending questions, provide as much
detail as you can as most folks reading these lists are not
experienced mind-readers :-)

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------