[FE training-materials-updates] labs: yocto-lab2: Update it to krogoth

[Antoine Ténart]

Repository : git://git.free-electrons.com/training-materials.git
On branch  : dev_mylene/yocto_update/krogoth
Link       : http://git.free-electrons.com/training-materials/commit/?id=636eef3bdbec73fd3df6d4789048dcc9081381d5

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

commit 636eef3bdbec73fd3df6d4789048dcc9081381d5
Author: Mylène Josserand <mylene.josserand at free-electrons.com>
Date:   Fri Jun 17 14:58:17 2016 +0200

    labs: yocto-lab2: Update it to krogoth
    
    Modifications/differences:
       - The kernel provided by default is now the on from Yocto
       "linux-yocto" and not "linux-ti-staging".
       - Filesystem image is bz2
    
    Signed-off-by: Mylène Josserand <mylene.josserand at free-electrons.com>


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

636eef3bdbec73fd3df6d4789048dcc9081381d5
 .../yocto-advanced-configuration/yocto-advanced-configuration.tex | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/labs/yocto-advanced-configuration/yocto-advanced-configuration.tex b/labs/yocto-advanced-configuration/yocto-advanced-configuration.tex
index 7b6c671..5e28c36 100644
--- a/labs/yocto-advanced-configuration/yocto-advanced-configuration.tex
+++ b/labs/yocto-advanced-configuration/yocto-advanced-configuration.tex
@@ -139,17 +139,17 @@ To see which kernel is used, dry-run BitBake:
 bitbake -vn virtual/kernel
 \end{verbatim}
 
-In our case, we can see the \code{linux-ti-staging} provides the
+In our case, we can see the \code{linux-yocto} provides the
 \code{virtual/kernel} functionality:
 \small
 \begin{verbatim}
-NOTE: selecting linux-ti-staging to satisfy virtual/kernel due to PREFERRED_PROVIDER
+NOTE: selecting linux-yocto to satisfy virtual/kernel due to PREFERRED_PROVIDERS
 \end{verbatim}
 \normalsize
 
 We can force Yocto to select another \code{kernel} by explicitly
 defining which one to use in our local configuration. Try switching
-from \code{linux-ti-staging} to \code{linux-dummy} only using the
+from \code{linux-yocto} to \code{linux-dummy} only using the
 local configuration.
 
 Then check the previous step worked by dry-running again BitBake.
@@ -173,7 +173,7 @@ accessible by NFS clients. Simply uncompress the archived output image in the
 previously created \code{/nfs} directory:
 \begin{verbatim}
 sudo tar xpf $BUILDDIR/tmp/deploy/images/beaglebone/\
-  core-image-minimal-beaglebone.tar.gz -C /nfs
+  core-image-minimal-beaglebone.tar.bz2 -C /nfs
 \end{verbatim}
 
 Then boot the board.