[FE training-materials-updates] Flash labs and slides: misc improvements

[Michael Opdenacker]

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

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

commit dfc82c6db97b44fc41411ce19c648d98aa196e62
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Wed Nov 4 22:37:34 2015 +0100

    Flash labs and slides: misc improvements
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


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

dfc82c6db97b44fc41411ce19c648d98aa196e62
 .../sysdev-flash-filesystems.tex                   |  5 +--
 .../sysdev-flash-filesystems.tex                   | 42 +++++++++++-----------
 2 files changed, 25 insertions(+), 22 deletions(-)

diff --git a/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex b/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
index 726f3d6..1c97ff2 100644
--- a/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
+++ b/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
@@ -39,7 +39,8 @@ Which gives the following layout:
 \section{Enabling NAND flash and filesystems}
 
 First, make sure your kernel has support for UBI and UBIFS, and also
-the option allowing us to pass the partition table through the cmdline:
+the option allowing us to pass the partition table through the command
+line:
 (\code{CONFIG_MTD_CMDLINE_PARTS}).
 
 Recompile your kernel if needed. We will update your kernel image on flash
@@ -177,7 +178,7 @@ Set the \code{bootargs} variable so that:
 
 \begin{itemize}
 \item The \code{mtdparts} environment variable contents are passed to
-  the kernel through \code{cmdline}\footnote{Remember you can tweak your
+  the kernel through its command line\footnote{Remember you can tweak your
   \code{bootargs} using U-Boot environment variables before booting the kernel.
   To achieve that, create a \code{bootargs_base} variable where you
   will store all the kernel parameters except the \code{mtdparts}
diff --git a/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex b/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
index 97f7999..de2e69f 100644
--- a/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
+++ b/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
@@ -158,24 +158,26 @@
 
 \begin{frame}
   \frametitle{U-Boot: manipulating NAND devices}
-  \begin{itemize}
-  \item U-Boot provides a set of commands to manipulate NAND devices
-  \item Grouped under the \code{nand} command
-    \begin{itemize}
-    \item \code{nand info}: show available NAND devices and their
-      characteristics
-    \item \code{nand device [dev]}: select or display the active NAND
-      device
-    \item \code{nand read[.option] <addr> <offset|part> <size>} read
-      data from the NAND
-    \item \code{nand write[.option] <addr> <offset|part> <size>} write
-      data on the NAND
-    \item Use \code{nand write.trimffs} to avoid writing empty pages
+  U-Boot provides a set of commands to manipulate NAND devices,
+  grouped under the \code{nand} command
+  \begin{itemize}
+  \item \code{nand info}\\
+    Show available NAND devices and characteristics
+  \item \code{nand device [dev]}\\
+    Select or display the active NAND device
+  \item \code{nand read[.option] <addr> <offset|partname> <size>}\\
+    Read data from NAND
+  \item \code{nand write[.option] <addr> <offset|partname> <size>}\\
+    Write data on NAND
+    \begin{itemize}
+      \item Use \code{nand write.trimffs} to avoid writing empty pages
       (those filled with \code{0xff})
-    \item \code{nand erase <offset> <size>} erase a NAND region
-    \item \code{nand erase.part <part>} erase a NAND partition
-    \item More commands for debugging purpose
     \end{itemize}
+  \item \code{nand erase <offset> <size>}\\
+    Erase a NAND region
+  \item \code{nand erase.part <partname>}\\
+    Erase a NAND partition
+  \item More commands for debugging purposes
   \end{itemize}
 \end{frame}
 
@@ -337,7 +339,7 @@ setenv mtdparts mtdparts=omap2-nand.0:512k(X-Loader)ro,1536k(U-Boot)ro,512k(Env)
   \item U-Boot and Linux are using the same syntax to describe the MTD
     partitions
   \item Directly pass the \code{mtdparts} environment variable defined in
-    U-Boot to the kernel cmdline
+    U-Boot to the kernel command line
   \item Be careful: when modifying the partition layout you might impact
     MTD users which have already stored data on existing partitions: e.g.
     a file system might complain about data corruption if you change
@@ -368,7 +370,7 @@ setenv mtdparts mtdparts=omap2-nand.0:512k(X-Loader)ro,1536k(U-Boot)ro,512k(Env)
 \begin{frame}
   \frametitle{Flash wear leveling (1)}
   \begin{itemize}
-  \item Wear leveling consists in distributing writes over the whole
+  \item Wear leveling consists in distributing erases over the whole
     flash device to avoid quickly reaching the maximum number of erase
     cycles on blocks that are written really often
   \item Can be done in:
@@ -758,7 +760,7 @@ vol_alignment=1
   \frametitle{Linux: Using a UBIFS filesystem as a rootfs}
   \begin{itemize}
   \item You just have to pass the following information on the kernel
-    cmdline:
+    command line:
     \begin{itemize}
     \item \code{ubi.mtd=1}: attach \code{/dev/mtd1} to the UBI layer and
       create \code{ubi0}
@@ -815,7 +817,7 @@ vol_alignment=1
   \item The user specifies which static volumes (s)he would like to attach
     to \code{ubiblock}
     \begin{itemize}
-    \item Through the \code{cmdline}: by passing
+    \item Through the kernel command line: by passing
       \code{ubi.block=<ubi-dev-id>,<volume-name>}
     \item Using the \code{ubiblock} utility provided by \code{mtd-utils}:
       \code{ubiblock --create <ubi-volume-dev-file>}