[FE training-materials-updates] " :" replaced by ":"
michael.opdenacker at free-electrons.com
michael.opdenacker at free-electrons.com
Wed Feb 29 15:49:58 CET 2012
- Log -----------------------------------------------------------------
http://git.free-electrons.com/training-materials/commit/?id=0c5621047a088c46c80233f62581777747a28633
commit 0c5621047a088c46c80233f62581777747a28633
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date: Wed Feb 29 15:49:00 2012 +0100
" :" replaced by ":"
English punctuation rule
diff --git a/labs/kernel-debugging/kernel-debugging.tex b/labs/kernel-debugging/kernel-debugging.tex
index 290ead7..6849747 100644
--- a/labs/kernel-debugging/kernel-debugging.tex
+++ b/labs/kernel-debugging/kernel-debugging.tex
@@ -16,7 +16,7 @@ that you added ? Your kernel probably has neither \code{CONFIG_DEBUG} nor
Now, recompile your kernel with \code{CONFIG_DYNAMIC_DEBUG} and reboot. The
dynamic debug feature can be configured using debugfs, so you'll have
to mount the debugfs filesystem first. Then, after reading the dynamic
-debug documentation in the kernel sources, do the following things :
+debug documentation in the kernel sources, do the following things:
\begin{itemize}
@@ -38,7 +38,7 @@ drivers and be able to selectively enable only some of them.
Since you have enabled debugfs to control the dynamic debug feature,
we will also use it to add a new debugfs entry. Modify your driver to
-add :
+add:
\begin{itemize}
diff --git a/labs/kernel-power-management/kernel-power-management.tex b/labs/kernel-power-management/kernel-power-management.tex
index c25efbc..5328b6d 100644
--- a/labs/kernel-power-management/kernel-power-management.tex
+++ b/labs/kernel-power-management/kernel-power-management.tex
@@ -45,7 +45,7 @@ in \code{/home/<user>/felabs/powermgt/usage/nfsroot/}.
\section{Suspend and resume}
-To suspend to RAM the Calao board, run :
+To suspend to RAM the Calao board, run:
\begin{verbatim}
echo mem > /sys/power/state
diff --git a/labs/sysdev-application-development/sysdev-application-development.tex b/labs/sysdev-application-development/sysdev-application-development.tex
index 8fcd9cc..341dd47 100644
--- a/labs/sysdev-application-development/sysdev-application-development.tex
+++ b/labs/sysdev-application-development/sysdev-application-development.tex
@@ -38,7 +38,7 @@ since those wrappers pass some mandatory flags (especially the
\code{--sysroot} gcc flag, which tells gcc where to look for the
headers and libraries).
-Let's add this directory to our PATH :
+Let's add this directory to our PATH:
\begin{verbatim}
export PATH=/home/<user>/felabs/sysdev/buildroot/output/host/usr/bin:$PATH
\end{verbatim}
diff --git a/labs/sysdev-block-filesystems/sysdev-block-filesystems.tex b/labs/sysdev-block-filesystems/sysdev-block-filesystems.tex
index 9b6fc59..18b4a28 100644
--- a/labs/sysdev-block-filesystems/sysdev-block-filesystems.tex
+++ b/labs/sysdev-block-filesystems/sysdev-block-filesystems.tex
@@ -31,7 +31,7 @@ used in this previous lab.\footnote{If you didn't do or complete the
Using fdisk, add two additional partitions to the MMC card (in
addition to the existing \code{boot} partition created in the
-bootloaders lab) :
+bootloaders lab):
\begin{itemize}
diff --git a/labs/sysdev-buildroot/sysdev-buildroot.tex b/labs/sysdev-buildroot/sysdev-buildroot.tex
index f2bf730..00a6623 100644
--- a/labs/sysdev-buildroot/sysdev-buildroot.tex
+++ b/labs/sysdev-buildroot/sysdev-buildroot.tex
@@ -128,7 +128,7 @@ toolchain, then download, extract, configure, compile and install each
component of the embedded system.
All the compilation has taken place in the \code{output/} subdirectory. Let's
-explore its contents :
+explore its contents:
\begin{itemize}
diff --git a/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex b/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
index 5e63769..adc5ee3 100644
--- a/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
+++ b/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
@@ -20,7 +20,7 @@ make our system use its internal flash storage.
The root filesystem will still be in a read-only filesystem, put on an
MTD partition. Read/write data will be stored in a JFFS2 filesystem
in another MTD partition. The layout of the internal OneNAND flash
-will be :
+will be:
\begin{itemize}
\item From 0 to 0x80000, X-Loader (512 KB)
@@ -71,7 +71,7 @@ board dependent. Nevertheless, during device development, it can be
useful to define partitions at boot time, on the kernel command line.
Enter the U-Boot shell and erase the NAND flash, from offset
-0x00280000, up to the end of the NAND flash (Erase size : 0x1FD80000
+0x00280000, up to the end of the NAND flash (Erase size: 0x1FD80000
bytes)
Using the \code{tftp} command, download and flash the kernel image at
@@ -89,7 +89,7 @@ procedures. This is very handy to avoid mistakes when typing commands!
Look at the way MTD partitions are defined in the kernel sources
(\code{arch/arm/mach-omap2/board-igep-0020.c})
-Set the \code{bootargs} variable so that :
+Set the \code{bootargs} variable so that:
\begin{itemize}
\item you define the 6 MTD partitions, as detailed previously
diff --git a/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex b/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex
index 6a9ddf0..a46bda6 100644
--- a/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex
+++ b/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex
@@ -106,7 +106,7 @@ saveenv
\section{Load and boot the kernel using U-Boot}
-We will use TFTP to load the kernel image to the IGEP board :
+We will use TFTP to load the kernel image to the IGEP board:
\begin{itemize}
@@ -122,7 +122,7 @@ We will use TFTP to load the kernel image to the IGEP board :
\end{itemize}
-You should see Linux boot and finally hang with the following message :
+You should see Linux boot and finally hang with the following message:
\begin{verbatim}
Waiting for root device /dev/mmcblk0p2...
@@ -132,7 +132,7 @@ This is expected: we haven't provided a working root filesystem for
our device yet.
You can automate now all this every time the board is booted or
-reset. Reset the board, and specify a different \code{bootcmd} :
+reset. Reset the board, and specify a different \code{bootcmd}:
\begin{verbatim}
setenv bootcmd 'tftp 80000000 uImage;bootm 80000000'
diff --git a/labs/sysdev-real-time/sysdev-real-time.tex b/labs/sysdev-real-time/sysdev-real-time.tex
index 1caa335..2b417b7 100644
--- a/labs/sysdev-real-time/sysdev-real-time.tex
+++ b/labs/sysdev-real-time/sysdev-real-time.tex
@@ -103,7 +103,7 @@ the results.
Get Xenomai from its download area at
\url{http://download.gna.org/xenomai/stable/} and untar Xenomai.
-Prepare the kernel for Xenomai compilation :
+Prepare the kernel for Xenomai compilation:
\begin{verbatim}
./scripts/prepare-kernel.sh --arch=arm --linux=/path/to/linux-2.6.35.9
\end{verbatim}
@@ -135,7 +135,7 @@ arm-none-linux-gnueabi-gcc $CFL -o rttest rttest.c $LDF
Now boot the board with the new kernel.
-Run the following commands on the board :
+Run the following commands on the board:
\begin{verbatim}
echo 0 > /proc/xenomai/latency
-----------------------------------------------------------------------
Summary of changes:
labs/kernel-debugging/kernel-debugging.tex | 4 ++--
.../kernel-power-management.tex | 2 +-
.../sysdev-application-development.tex | 2 +-
.../sysdev-block-filesystems.tex | 2 +-
labs/sysdev-buildroot/sysdev-buildroot.tex | 2 +-
.../sysdev-flash-filesystems.tex | 6 +++---
.../sysdev-kernel-cross-compiling.tex | 6 +++---
labs/sysdev-real-time/sysdev-real-time.tex | 4 ++--
8 files changed, 14 insertions(+), 14 deletions(-)
More information about the training-materials-updates
mailing list