[BL training-materials-updates] yocto: change name from felabs to bootlinlabs

[Quentin Schulz]

Repository : git://git.free-electrons.com/training-materials.git
On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=25d46160dc867a098412e04574e3ba07977ca841

>---------------------------------------------------------------

commit 25d46160dc867a098412e04574e3ba07977ca841
Author: Quentin Schulz <quentin.schulz at bootlin.com>
Date:   Fri Jul 27 07:34:28 2018 +0200

    yocto: change name from felabs to bootlinlabs
    
    Signed-off-by: Quentin Schulz <quentin.schulz at bootlin.com>


>---------------------------------------------------------------

25d46160dc867a098412e04574e3ba07977ca841
 labs/yocto-custom-image/yocto-custom-image.tex     |  8 ++++----
 labs/yocto-custom-machine/yocto-custom-machine.tex | 14 ++++++--------
 labs/yocto-layer/yocto-layer.tex                   | 15 +++++++--------
 labs/yocto-sdk/yocto-sdk.tex                       |  4 ++--
 4 files changed, 19 insertions(+), 22 deletions(-)

diff --git a/labs/yocto-custom-image/yocto-custom-image.tex b/labs/yocto-custom-image/yocto-custom-image.tex
index 27f7c91..4c70739 100644
--- a/labs/yocto-custom-image/yocto-custom-image.tex
+++ b/labs/yocto-custom-image/yocto-custom-image.tex
@@ -17,8 +17,8 @@ used in the industry we will, in addition to the production image recipe you
 will use in the final product, create a development one including debug tools
 and show how to link the two of them to avoid configuration duplication.
 
-First add a custom image recipe in the \code{meta-felabs} layer. We will name it
-\code{felabs-image-minimal}. You can find information on how to create a custom
+First add a custom image recipe in the \code{meta-bootlinlabs} layer. We will name it
+\code{bootlinlabs-image-minimal}. You can find information on how to create a custom
 image on the dedicated Yocto Project development manual at
 \url{http://www.yoctoproject.org/docs/1.5.1/dev-manual/dev-manual.html}. There
 are different ways to customize an image, we here want to create a full recipe,
@@ -50,7 +50,7 @@ We just saw it is possible to use package groups to organize and select the
 packages instead of having a big blob of configuration in the image recipe
 itself. We will here create a custom package for game related recipes.
 
-With the above documentation, create a \code{packagegroup-felabs-games} group
+With the above documentation, create a \code{packagegroup-bootlinlabs-games} group
 which inherits from the \code{packagegroup} class. Add the nInvaders program
 into its runtime dependencies.
 
@@ -65,7 +65,7 @@ base for both the production and the debug images, but also take into account th
 possible differences. In our example only the built package list will change.
 
 Create a debug version of the previous image recipe, and name it
-\code{felabs-image-minimal-dbg}. Try to avoid duplicating code! Then add the
+\code{bootlinlabs-image-minimal-dbg}. Try to avoid duplicating code! Then add the
 \code{dbg-pkgs} to the image features list. It is also recommended to
 update the recipe's description, and to add extra debugging tools.
 
diff --git a/labs/yocto-custom-machine/yocto-custom-machine.tex b/labs/yocto-custom-machine/yocto-custom-machine.tex
index 5204385..aaeb883 100644
--- a/labs/yocto-custom-machine/yocto-custom-machine.tex
+++ b/labs/yocto-custom-machine/yocto-custom-machine.tex
@@ -14,10 +14,8 @@ what we did in lab1, when we chose the \code{beaglebone} one. While it
 is not necessary to make our custom machine image here, we'll create a
 new one to demonstrate the process.
 
-Add a new \code{felabs} machine to the previously created layer, which
-will make the BeagleBone Black board properly boot. Since the
-\code{meta-felabs} layer is already created, do not use the
-\code{yocto-bsp} tool.
+Add a new \code{bootlinlabs} machine to the previously created layer, which
+will make the BeagleBone Black board properly boot.
 
 This machine describes a board using the \code{cortexa8thf-neon} tune
 and is a part of the \code{ti33x} SoC family. Add the following lines
@@ -38,7 +36,7 @@ UBOOT_LOADADDRESS = "0x80008000"
 
 \section{Populate the machine configuration}
 
-This \code{felabs} machine needs:
+This \code{bootlinlabs} machine needs:
 
 \begin{itemize}
   \item To select \code{linux-ti-staging} as the preferred provider
@@ -65,15 +63,15 @@ and start a fresh build.
 
 \section{Have a look at the generated files}
 
-Once the generated images supporting the new \code{felabs} machine are
+Once the generated images supporting the new \code{bootlinlabs} machine are
 generated, you can check all the needed images were generated
 correctly.
 
 Have a look in the output directory, in
-\code{$BUILDDIR/tmp/deploy/images/felabs/}. Is there something
+\code{$BUILDDIR/tmp/deploy/images/bootlinlabs/}. Is there something
 missing?
 
 \section{Update the rootfs}
 
 You can now update your root filesystem, to use the newly
-generated image supporting our \code{felabs} machine!
+generated image supporting our \code{bootlinlabs} machine!
diff --git a/labs/yocto-layer/yocto-layer.tex b/labs/yocto-layer/yocto-layer.tex
index 172973a..10cac62 100644
--- a/labs/yocto-layer/yocto-layer.tex
+++ b/labs/yocto-layer/yocto-layer.tex
@@ -29,7 +29,7 @@ the \code{create} argument.
 \section{Create a new layer}
 
 With the above commands, create a new Yocto layer named
-\code{meta-felabs} with a priority of \code{7}.
+\code{meta-bootlinlabs} with a priority of \code{7}.
 
 Before using the new layer, we need to configure its generated configuration
 files. You can start with the \code{README} file which is not used in the build
@@ -37,32 +37,31 @@ process but contains information related to layer maintenance. You can then
 check, and adapt if needed, the global layer configuration file located in the
 \code{conf} directory of your custom layer.
 
-Tips: the \code{yocto-layer} command creates a layer in the current directory
-unless otherwise stated. Also be careful, the \code{meta-} keyword is mandatory.
-
 \section{Integrate a layer to the build}
 
 To be fair, we already used and integrated a layer in our build configuration
 during the first lab, with \code{meta-ti}. This layer was responsible for
 BeagleBone Black support in Yocto. We have to do the same for our
-\code{meta-felabs} now.
+\code{meta-bootlinlabs} now.
 
 There is a file which contains all the paths of the layers we use. Try to find it
 without looking back to the first lab. Then add the full path to our newly
 created layer to the list of layers.
 
-Validate the integration of the \code{meta-felabs} layer with:
+Validate the integration of the \code{meta-bootlinlabs} layer with:
 \begin{verbatim}
 bitbake-layers show-layers
 \end{verbatim}
 
+and make sure you don't have any warning from bitbake.
+
 \section{Add a recipe to the layer}
 
 In the previous lab we introduced a recipe for the nInvaders game. We included
 it to the existing \code{meta} layer. While this approach give a working result,
 the Yocto logic is not respected. You should instead always \textbf{use a custom layer}
 to add recipes or to customize the existing ones. To illustrate this we will
-move our previously created nInvaders recipe into the \code{meta-felabs} layer.
+move our previously created nInvaders recipe into the \code{meta-bootlinlabs} layer.
 
 You can check the nInvaders recipe is part of the \code{meta} layer first:
 \begin{verbatim}
@@ -70,5 +69,5 @@ bitbake-layers show-recipes ninvaders
 \end{verbatim}
 
 Then move the nInvaders recipe to the layer created below. You can check that
-the nInvaders recipe is now part of the \code{meta-felabs} layer with the
+the nInvaders recipe is now part of the \code{meta-bootlinlabs} layer with the
 \code{bitbake-layers} command.
diff --git a/labs/yocto-sdk/yocto-sdk.tex b/labs/yocto-sdk/yocto-sdk.tex
index 2f9f439..0864563 100644
--- a/labs/yocto-sdk/yocto-sdk.tex
+++ b/labs/yocto-sdk/yocto-sdk.tex
@@ -15,7 +15,7 @@ Two SDKs are available, one only embedding a toolchain and the
 other one allowing for application development. We will use the latter one
 here.
 
-First, build an SDK for the \code{felabs-image-minimal} image, with
+First, build an SDK for the \code{bootlinlabs-image-minimal} image, with
 the \code{populate_sdk} task.
 
 Once the SDK is generated, a script will be available at
@@ -31,7 +31,7 @@ generated at the previous step.
 
 {\footnotesize
 \begin{verbatim}
-$BUILDDIR/tmp/deploy/sdk/poky-glibc-x86_64-felabs-image-minimal-cortexa8hf-neon-toolchain-2.3.sh
+$BUILDDIR/tmp/deploy/sdk/poky-glibc-x86_64-bootlinlabs-image-minimal-cortexa8hf-neon-toolchain-2.3.sh
 \end{verbatim}
 }