[bootlin/training-materials updates] master: Embedded linux labs: upgrade kernel (19194fd2)

[Michael Opdenacker]

Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/19194fd2d14bd9177fd681aee3f078b28ac7a683

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

commit 19194fd2d14bd9177fd681aee3f078b28ac7a683
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Sat May 2 07:54:53 2020 +0200

    Embedded linux labs: upgrade kernel
    
    - At least on the Xplained board
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


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

19194fd2d14bd9177fd681aee3f078b28ac7a683
 .../sysdev-kernel-fetch-and-patch.tex              | 23 ++++++++++++++++++----
 1 file changed, 19 insertions(+), 4 deletions(-)

diff --git a/labs/sysdev-kernel-fetch-and-patch/sysdev-kernel-fetch-and-patch.tex b/labs/sysdev-kernel-fetch-and-patch/sysdev-kernel-fetch-and-patch.tex
index b787936d..43628edd 100644
--- a/labs/sysdev-kernel-fetch-and-patch/sysdev-kernel-fetch-and-patch.tex
+++ b/labs/sysdev-kernel-fetch-and-patch/sysdev-kernel-fetch-and-patch.tex
@@ -19,11 +19,21 @@ identify the latest stable version.
 Just to make sure you know how to do it, check the version of the
 Linux kernel running on your machine.
 
+\ifdefstring{\labboard}{discovery}{
 We will use \code{linux-4.19.x}, which this lab was tested with.
 
 To practice with the \code{patch} command later, download the full 4.18
 sources. Unpack the archive, which creates a \code{linux-4.18}
-directory. Remember that you can use \code{wget <URL>} on the command
+directory.
+}{
+We will use \code{linux-5.6.x}, which this lab was tested with.
+
+To practice with the \code{patch} command later, download the full 5.5
+sources. Unpack the archive, which creates a \code{linux-5.5}
+directory.
+}
+
+Remember that you can use \code{wget <URL>} on the command
 line to download files.
 
 \section{Apply patches}
@@ -36,9 +46,9 @@ a second patch to move from 4.19 to 4.19.9.
 We need to use 4.19.9 precisely, because we will apply another patch
 on top of that to add support for the STM32 platform.
 }{
-Download the patch files corresponding to the latest 4.19 stable
-release: a first patch to move from 4.18 to 4.19 and if one exists,
-a second patch to move from 4.19 to 4.19.x.
+Download the patch files corresponding to the latest 5.6 stable
+release: a first patch to move from 5.5 to 5.6 and if one exists,
+a second patch to move from 5.6 to 5.6.x.
 }
 
 Without uncompressing them to a separate file, apply the patches to the Linux
@@ -56,4 +66,9 @@ View one of the patch files with \code{vi} or \code{gvim}
 (if you prefer a graphical editor), to understand the information carried
 by such a file. How are described added or removed files?
 
+\ifdefstring{\labboard}{discovery}{
 Rename the \code{linux-4.18} directory to \code{linux-4.19.<x>}.
+}{
+Rename the \code{linux-5.5} directory to \code{linux-5.6.<x>}.
+}
+