[FE training-materials-updates] Buildroot lab clarifications and updates

[Michael Opdenacker]

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

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

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

commit f4ac938f4189ef25f0e4b843e25f9c071aa86cbb
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Thu Nov 21 05:32:26 2013 +0100

    Buildroot lab clarifications and updates
    
    - According to version 2013.08.x
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


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

f4ac938f4189ef25f0e4b843e25f9c071aa86cbb
 labs/sysdev-buildroot/sysdev-buildroot.tex |   54 +++++++++++++++-------------
 1 file changed, 29 insertions(+), 25 deletions(-)

diff --git a/labs/sysdev-buildroot/sysdev-buildroot.tex b/labs/sysdev-buildroot/sysdev-buildroot.tex
index 9fe8d25..6cfde87 100644
--- a/labs/sysdev-buildroot/sysdev-buildroot.tex
+++ b/labs/sysdev-buildroot/sysdev-buildroot.tex
@@ -67,41 +67,45 @@ make menuconfig
 Set the following options:
 
 \begin{itemize}
-\item Target Architecture: \code{ARM (little endian)}
-\item Target Architecture Variant: \code{arm926t}.
-\item Toolchain
+\item \code{Target Architecture}: \code{ARM (little endian)}
+\item \code{Target Architecture Variant}: \code{arm926t} (we will start booting
+      the generated filesystem on an emulated arm9 based system,
+      instead of the IGEPv2 board)
+\item \code{Toolchain}
   \begin{itemize}
-  \item Toolchain type: \code{External toolchain}
-  \item Toolchain: \code{Custom toolchain}
-  \item Toolchain path: use the toolchain you built:
+  \item \code{Toolchain type}: \code{External toolchain}
+  \item \code{Toolchain}: \code{Custom toolchain}
+  \item \code{Toolchain path}: use the toolchain you built:
     \code{/usr/local/xtools/arm-unknown-linux-uclibcgnueabi}
-  \item External toolchain C library: \code{uClibc}
+  \item \code{External toolchain C library}: \code{uClibc}
   \item We must tell Buildroot about our toolchain configuration, so:
-    enable Toolchain has large file support, Toolchain has RPC support
-    and Toolchain has C++ support. Buildroot will check these
-    parameters anyway.
+    enable \code{Toolchain has large file support?}, \code{Toolchain has
+    RPC support?}, and \code{Toolchain has C++ support?}.
+    Buildroot will check these parameters anyway.
   \end{itemize}
-\item System configuration
+\item \code{System configuration}
   \begin{itemize}
-  \item Port to run a getty (login prompt) on, change \code{ttyS0} to \code{tty1}
+  \item \code{Port to run a getty (login prompt) on}: change \code{ttyS0} to \code{tty1}
   \end{itemize}
-\item Package selection for the target
+\item \code{Target packages}
   \begin{itemize}
-  \item Keep Busybox (default version) and keep the Busybox
+  \item Keep \code{BusyBox} (default version) and keep the Busybox
     configuration proposed by Buildroot;
-  \item In Graphics libraries and applications (graphic/text)
+  \item \code{In Graphic libraries and applications (graphic/text)}
     \begin{itemize}
-    \item Select directfb. Buildroot will automatically select the
+    \item Select \code{directfb}. Buildroot will automatically select the
       necessary dependencies.
-    \item Remove touchscreen support from DirectFB
-    \item Select directfb examples
-    \item Select all the DirectFB examples
+    \begin{itemize}
+         \item Remove \code{enable touchscreen support}
+         \item Select \code{directfb examples}
+         \item Select all the DirectFB examples
+     \end{itemize}
     \end{itemize}
   \end{itemize}
-\item Filesystem images
+\item \code{Filesystem images}
   \begin{itemize}
-  \item Select ext2 root filesystem
-  \item Select tar the root filesystem
+  \item Select \code{ext2/3/4 root filesystem}
+  \item Select \code{tar the root filesystem}
   \end{itemize}
 \end{itemize}
 
@@ -178,10 +182,10 @@ support, allowing to test graphical applications relying on the
 DirectFB library. Later, we will be able move to a real board if your
 hardware also has a graphical display.
 
-The \code{run_qemu} script contains what's needed to boot the system
-in QEMU.
+Execute the \code{run_qemu} script, which contains what's needed
+to boot the system in QEMU.
 
-Log in (\code{root} account, no password), run demo programs:
+Log in (\code{root} account, no password), and run demo programs:
 
 \begin{verbatim}
 df_andi