[BL training-materials-updates] labs: yocto-*: it's 2018, use https wherever possible

[Quentin Schulz]

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

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

commit d86a7c0f8a3033357ca245a7de0e817ce04ffc5d
Author: Quentin Schulz <quentin.schulz at bootlin.com>
Date:   Sat Aug 18 17:29:21 2018 +0200

    labs: yocto-*: it's 2018, use https wherever possible
    
    Signed-off-by: Quentin Schulz <quentin.schulz at bootlin.com>


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

d86a7c0f8a3033357ca245a7de0e817ce04ffc5d
 labs/yocto-custom-image/yocto-custom-image.tex   | 2 +-
 labs/yocto-extend-recipe/yocto-extend-recipe.tex | 4 ++--
 labs/yocto-sdk/yocto-sdk.tex                     | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/labs/yocto-custom-image/yocto-custom-image.tex b/labs/yocto-custom-image/yocto-custom-image.tex
index b815cc8..d0ef905 100644
--- a/labs/yocto-custom-image/yocto-custom-image.tex
+++ b/labs/yocto-custom-image/yocto-custom-image.tex
@@ -20,7 +20,7 @@ and show how to link the two of them to avoid configuration duplication.
 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/2.5/dev-manual/dev-manual.html}. There
+\url{https://www.yoctoproject.org/docs/2.5/dev-manual/dev-manual.html}. There
 are different ways to customize an image, we here want to create a full recipe,
 using a custom \code{.bb} file.
 
diff --git a/labs/yocto-extend-recipe/yocto-extend-recipe.tex b/labs/yocto-extend-recipe/yocto-extend-recipe.tex
index 0019428..f5527fb 100644
--- a/labs/yocto-extend-recipe/yocto-extend-recipe.tex
+++ b/labs/yocto-extend-recipe/yocto-extend-recipe.tex
@@ -19,7 +19,7 @@ extend some configuration variables of the original recipe.
 
 Try to create an appended recipe with the help of the online Yocto
 Project development documentation. You can find it at
-\url{http://www.yoctoproject.org/docs/2.5/dev-manual/dev-manual.html}. We here
+\url{https://www.yoctoproject.org/docs/2.5/dev-manual/dev-manual.html}. We here
 aim to extend the \code{linux-ti-staging} kernel recipe.
 
 You can see available \code{bbappend} files and the recipe they apply to by
@@ -43,7 +43,7 @@ a joystick input. We can add this by applying patches during the
 find them under \code{~/yocto-labs/bootlin-lab-data/nunchuk/linux}. For more
 details about how to write the driver handling the Nunchuk, have a look at our
 embedded Linux kernel and driver development training course at
-\url{http://bootlin.com/training/kernel/}.
+\url{https://bootlin.com/training/kernel/}.
 
 Applying a patch is a common task in the daily Yocto process. Many recipes,
 appended or not, apply a specific patch on top of a mainline project. It's why
diff --git a/labs/yocto-sdk/yocto-sdk.tex b/labs/yocto-sdk/yocto-sdk.tex
index bea2cc6..8c87180 100644
--- a/labs/yocto-sdk/yocto-sdk.tex
+++ b/labs/yocto-sdk/yocto-sdk.tex
@@ -51,7 +51,7 @@ env
 \section{Compile an application in the SDK}
 
 Download the essential \code{Ctris} sources at
-\url{http://download.mobatek.net/sources/ctris-0.42-1-src.tar.bz2}
+\url{https://download.mobatek.net/sources/ctris-0.42-1-src.tar.bz2}
 
 Extract the source in the SDK:
 \begin{verbatim}