[FE training-materials-updates] slides/buildroot-introduction: add more contents

[Thomas Petazzoni]

Repository : git://git.free-electrons.com/training-materials.git

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

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

commit 43a0e902838ae373b7c4a309c184d433e8e77d02
Author: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
Date:   Thu May 7 14:38:20 2015 +0200

    slides/buildroot-introduction: add more contents
    
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>


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

43a0e902838ae373b7c4a309c184d433e8e77d02
 .../buildroot-introduction.tex                     | 102 ++++++++++++++++++++-
 slides/buildroot-introduction/menuconfig.png       | Bin 0 -> 85136 bytes
 2 files changed, 99 insertions(+), 3 deletions(-)

diff --git a/slides/buildroot-introduction/buildroot-introduction.tex b/slides/buildroot-introduction/buildroot-introduction.tex
index f1cd5d4..0755655 100644
--- a/slides/buildroot-introduction/buildroot-introduction.tex
+++ b/slides/buildroot-introduction/buildroot-introduction.tex
@@ -140,12 +140,108 @@
   \end{columns}
 \end{frame}
 
+\begin{frame}{Getting Buildroot}
+  \begin{itemize}
+  \item Stable Buildroot releases are published every three months.
+  \item Tarballs are available for each stable release
+    \begin{itemize}
+    \item \url{http://buildroot.org/downloads/}
+    \end{itemize}
+  \item However, it is generally more convenient to clone the Git
+    repository
+    \begin{itemize}
+    \item Allows to clearly identify the changes made to the Buildroot
+      source code
+    \item Simplifies the upstreaming of the Buildroot changes
+    \item \code{git clone git://git.busybox.net/buildroot}
+    \item Git tags available for every stable release.
+    \end{itemize}
+  \end{itemize}
+\end{frame}
+
+\begin{frame}{Using Buildroot}
+  \begin{itemize}
+  \item Implemented in \code{make}
+    \begin{itemize}
+    \item With a few helper shell scripts
+    \end{itemize}
+  \item Interaction always with the main \code{Makefile} in the main
+    Buildroot sources directory.
+    \begin{block}{}
+\begin{verbatim}
+$ cd buildroot/
+$ make help
+\end{verbatim}
+    \end{block}
+  \item No need to run as \code{root}, Buildroot is designed to work
+    executed with normal user priviledges.
+    \begin{itemize}
+    \item Running as root is even strongly discouraged!
+    \end{itemize}
+  \end{itemize}
+\end{frame}
+
+\begin{frame}{Configuring Buildroot}
+  \begin{itemize}
+  \item Like the Linux kernel, uses {\em kconfig}
+  \item A choice of configuration interfaces:
+    \begin{itemize}
+    \item \code{make menuconfig}
+    \item \code{make nconfig}
+    \item \code{make xconfig}
+    \item \code{make gconfig}
+    \end{itemize}
+  \item Make sure to install the relevant libraries in your system
+    ({\em ncurses} for menuconfig/nconfig, {\em Qt} for xconfig, {\em
+      Gtk} for gconfig)
+  \end{itemize}
+\end{frame}
+
+\begin{frame}{Main {\tt menuconfig} menu}
+  \begin{center}
+    \includegraphics[width=\textwidth]{slides/buildroot-introduction/menuconfig.png}
+  \end{center}
+\end{frame}
+
+\begin{frame}{Running the build}
+  \begin{itemize}
+  \item As simple as:
+    \begin{block}{}
+\begin{verbatim}
+$ make
+\end{verbatim}
+    \end{block}
+  \item Often useful to keep a log of the build output, for analysis
+    or investigation:
+    \begin{block}{}
+\begin{verbatim}
+$ make 2>&1 | tee build.log
+\end{verbatim}
+    \end{block}
+  \end{itemize}
+\end{frame}
+
+\begin{frame}{Build results}
+  \begin{itemize}
+  \item The build results are located in \code{output/images}
+  \item Depending on the configuration, this directory will contain:
+    \begin{itemize}
+    \item One or several root filesystem images, in various formats
+    \item One kernel image, possibly one or several Device Tree blobs
+    \item One or several bootloader images
+    \end{itemize}
+  \end{itemize}
+\end{frame}
+
 \setuplabframe
 {Basic Buildroot usage}
 {
   \begin{itemize}
-  \item Getting and setting up Buildroot
-  \item Configuring and building a basic system with Buildroot
-  \item Running the system on a hardware platform and in QEMU
+  \item Get Buildroot
+  \item Configure a minimal system with Buildroot for the BeagleBone
+    Black
+  \item Do the build
+  \item Prepare the BeagleBone Black for usage
+  \item Flash and test the generated system
   \end{itemize}
 }
diff --git a/slides/buildroot-introduction/menuconfig.png b/slides/buildroot-introduction/menuconfig.png
new file mode 100644
index 0000000..353927a
Binary files /dev/null and b/slides/buildroot-introduction/menuconfig.png differ