[FE training-materials-updates] kernel-module-env: Fix wrapping

[Maxime Ripard]

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

On branch  : kernel-bbb
Link       : http://git.free-electrons.com/training-materials/commit/?id=b9e449dc939302af5ace1ca6fd9424673cf80f17

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

commit b9e449dc939302af5ace1ca6fd9424673cf80f17
Author: Maxime Ripard <maxime.ripard at free-electrons.com>
Date:   Fri Sep 6 12:17:59 2013 +0200

    kernel-module-env: Fix wrapping
    
    Signed-off-by: Maxime Ripard <maxime.ripard at free-electrons.com>


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

b9e449dc939302af5ace1ca6fd9424673cf80f17
 .../kernel-module-environment.tex                  |   35 ++++++++++----------
 1 file changed, 18 insertions(+), 17 deletions(-)

diff --git a/labs/kernel-module-environment/kernel-module-environment.tex b/labs/kernel-module-environment/kernel-module-environment.tex
index 8ddb374..cd9e8a0 100644
--- a/labs/kernel-module-environment/kernel-module-environment.tex
+++ b/labs/kernel-module-environment/kernel-module-environment.tex
@@ -140,7 +140,8 @@ Once the USB <-> Serial connector plugged in, a new serial ports
 should appear: \code{/dev/ttyUSB0}.  You can also see this device
 appear by looking at the output of \code{dmesg}.
 
-To communicate with the board through the serial port, install a serial communication program, such as \code{picocom}:
+To communicate with the board through the serial port, install a
+serial communication program, such as \code{picocom}:
 
 \begin{verbatim}
 sudo apt-get install picocom
@@ -253,22 +254,21 @@ saveenv
 If you changed \code{ethaddr}, also power off your board, and power it
 on again (pressing the \code{reset} button is not enough).
 
-You can then test the TFTP connection
-\footnote{Note for Ubuntu 12.04 users: the \code{tftp-hpa}
-server may not work the first time you use it after booting your 
-workstation. You may need to restart it after plugging in your board: 
-\code{sudo /etc/init.d/tftpd-hpa restart}}.
-First, put a small text file in
-the directory exported through TFTP on your development
+You can then test the TFTP connection \footnote{Note for Ubuntu 12.04
+  users: the \code{tftp-hpa} server may not work the first time you
+  use it after booting your workstation. You may need to restart it
+  after plugging in your board:
+  \code{sudo /etc/init.d/tftpd-hpa restart}}.  First, put a small text
+file in the directory exported through TFTP on your development
 workstation. Then, from U-Boot, do:
 
 \begin{verbatim}
 tftp 0x81000000 textfile.txt
 \end{verbatim}
 
-{\bf Caution: known issue in Ubuntu 12.04 and later}:
-if this command doesn't work, you may have you have to stop the server
-and start it again every time you boot your workstation:  
+{\bf Caution: known issue in Ubuntu 12.04 and later}: if this command
+doesn't work, you may have you have to stop the server and start it
+again every time you boot your workstation:
 
 \begin{verbatim}
 /etc/init.d/tftpd-hpa restart
@@ -286,9 +286,9 @@ md 0x81000000
 
 \section{Boot the system}
 
-First, boot the board to the U-Boot prompt.  Before booting the
-kernel, we need to tell it that the root filesystem should be mounted
-over NFS, by setting some kernel parameters.  Use the following U-Boot
+First, boot the board to the U-Boot prompt. Before booting the kernel,
+we need to tell it that the root filesystem should be mounted over
+NFS, by setting some kernel parameters. Use the following U-Boot
 command to do so (in just 1 line):
 
 \begin{verbatim}
@@ -297,8 +297,8 @@ setenv bootargs root=/dev/nfs ip=192.168.0.100 console=ttyO0
 \end{verbatim}
 
 Of course, you need to adapt the IP addresses to your exact network
-setup. Save the environment variables (with \code{saveenv}).  Now, download
-the kernel image through \code{tftp}:
+setup. Save the environment variables (with \code{saveenv}). Now,
+download the kernel image through \code{tftp}:
 
 \begin{verbatim}
 tftp 0x81000000 uImage
@@ -341,4 +341,5 @@ We could also copy the \code{uImage} file to the eMMC flash and avoid
 downloading it over and over again. However, handling flash is outside
 of the scope of this course. See our
 \href{http://free-electrons.com/training/embedded-linux/}{Embedded
-Linux system development course} and its on-line materials for details.
+  Linux system development course} and its on-line materials for
+details.