[FE training-materials-updates] Font fixes + correct way to set ARCH and CROSS_COMPILE

[Michael Opdenacker]

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

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

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

commit 464e846159711146596ff537ac9135c231db768c
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Wed Oct 3 06:18:27 2012 +0200

    Font fixes + correct way to set ARCH and CROSS_COMPILE
    
    No longer suggest to modify ARCH and CROSS_COMPILE
    in the Makefile


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

464e846159711146596ff537ac9135c231db768c
 .../kernel-module-environment.tex                  |   33 ++++++++++----------
 1 file changed, 16 insertions(+), 17 deletions(-)

diff --git a/labs/kernel-module-environment/kernel-module-environment.tex b/labs/kernel-module-environment/kernel-module-environment.tex
index 83c2ad0..7fb0209 100644
--- a/labs/kernel-module-environment/kernel-module-environment.tex
+++ b/labs/kernel-module-environment/kernel-module-environment.tex
@@ -52,8 +52,8 @@ is needed to build the \code{uImage} file for U-boot (\code{mkimage} utility).
 
 We are going to install a cross-compiling toolchain from
 Linaro\footnote{Note that Linaro toolchains by default generate code
-for the {\em armv7} instruction set, while our AT91 CPU only supports
-{\em armv5}. This is not a problem, as the kernel \code{Makefile} will
+for the \code{armv7} instruction set, while our AT91 CPU only supports
+\code{armv5}. This is not a problem, as the kernel \code{Makefile} will
 invoke the cross-compiler with the right instruction set settings.}, a
 very popular source for ARM toolchains (amongst other useful resources
 for Linux on ARM).
@@ -70,9 +70,8 @@ dpkg -L gcc-arm-linux-gnueabi
 
 \section{Kernel configuration}
 
-Set the \code{ARCH} and \code{CROSS_COMPILE} settings for the arm
-platform and to use your cross-compiler, either by modifying the
-kernel \code{Makefile} or by setting environment variables.
+Set the \code{ARCH} and \code{CROSS_COMPILE} definitions for the \code{arm}
+platform and to use your cross-compiler.
 
 Configure this kernel with the ready-made configuration for boards
 with the AT91SAM9263 CPU.
@@ -80,11 +79,11 @@ with the AT91SAM9263 CPU.
 Make sure that this configuration has \code{CONFIG_ROOT_NFS=y} (support
 booting on an NFS exported root directory).
 
-Compile your kernel and generate the uImage kernel image that U-boot
-needs (the U-boot bootloader needs the kernel zImage file to be
-encapsulated in a special container and the kernel Makefile can
+Compile your kernel and generate the \code{uImage} kernel image that U-boot
+needs (the U-boot bootloader needs the kernel \code{zImage} file to be
+encapsulated in a special container and the kernel \code{Makefile} can
 generate this container for you by running the mkimage tool found in
-the uboot-mkimage package):
+the \code{uboot-mkimage} package):
 
 \begin{verbatim}
 make uImage
@@ -92,7 +91,7 @@ make uImage
 
 \section{Setting up the NFS server}
 
-Install the NFS server by installing the nfs-kernel-server
+Install the NFS server by installing the \code{nfs-kernel-server}
 package. Once installed, edit the \code{/etc/exports} file as
 \code{root} to add the following lines, assuming that the IP address
 of your board will be \code{192.168.0.100}:
@@ -127,8 +126,8 @@ sudo apt-get install picocom
 \end{verbatim}
 
 Run \code{picocom -b 115200 /dev/ttyUSB1}, to start a serial
-communication on \code{/dev/ttyUSB1}, with a baudrate of 115200. If
-you wish to exit picocom, press \code{[Ctrl][a]} followed by
+communication on \code{/dev/ttyUSB1}, with a baudrate of \code{115200}. If
+you wish to exit \code{picocom}, press \code{[Ctrl][a]} followed by
 \code{[Ctrl][x]}.
 
 You should now see the U-Boot prompt:
@@ -162,8 +161,8 @@ adapter. A new network interface, probably \code{eth1} or \code{eth2},
 should appear on your Linux system.
 
 To configure your network interface on the workstation side, click on
-the {\em Network Manager} tasklet on your desktop, and select {\em
-Edit Connections}.
+the \code{Network Manager} tasklet on your desktop, and select
+\code{Edit Connections}.
 
 \begin{center}
 \includegraphics[width=8cm]{labs/kernel-module-environment/network-config-1.png}
@@ -175,7 +174,7 @@ Select the new wired network connection:
 \includegraphics[width=8cm]{labs/kernel-module-environment/network-config-2.png}
 \end{center}
 
-In the {\em IPv4 Settings} tab, make the interface use a static IP
+In the \code{IPv4 Settings} tab, make the interface use a static IP
 address, like 192.168.0.1 (of course, make sure that this address
 belongs to a separate network segment from the one of the main company
 network):
@@ -238,8 +237,8 @@ setenv bootargs root=/dev/nfs ip=192.168.0.100
 \normalsize
 
 Of course, you need to adapt the IP addresses to your exact network
-setup. Save the environment variables (with saveenv).  Now, download
-the kernel image through tftp:
+setup. Save the environment variables (with \code{saveenv}).  Now, download
+the kernel image through \code{tftp}:
 
 \begin{verbatim}
 tftp 0x21000000 uImage