[bootlin/training-materials updates] master: Fix typos (fdeaada9)
Michael Opdenacker
michael.opdenacker at bootlin.com
Fri May 24 09:14:26 CEST 2019
Repository : https://github.com/bootlin/training-materials
On branch : master
Link : https://github.com/bootlin/training-materials/commit/fdeaada947421ef9de1c012ad6c9c392e8d9890f
>---------------------------------------------------------------
commit fdeaada947421ef9de1c012ad6c9c392e8d9890f
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date: Fri May 24 09:14:26 2019 +0200
Fix typos
Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>
>---------------------------------------------------------------
fdeaada947421ef9de1c012ad6c9c392e8d9890f
labs/boot-time-application/boot-time-application.tex | 4 ++--
labs/boot-time-board-setup/boot-time-board-setup.tex | 4 ++--
labs/boot-time-bootloader/boot-time-bootloader.tex | 4 ++--
labs/boot-time-build-bootloader/boot-time-build-bootloader.tex | 4 ++--
.../boot-time-build-kernel-and-start-system.tex | 2 +-
.../boot-time-filesystem-optimizations.tex | 2 +-
labs/boot-time-init-scripts/boot-time-init-scripts.tex | 4 ++--
labs/boot-time-kernel/boot-time-kernel.tex | 2 +-
.../boot-time-software-measurement/boot-time-software-measurement.tex | 4 ++--
labs/boot-time-sources-download/boot-time-sources-download.tex | 2 +-
labs/boot-time-toolchain/boot-time-toolchain.tex | 2 +-
labs/kernel-board-setup/kernel-board-setup.tex | 4 ++--
.../kernel-compiling-and-nfs-booting.tex | 2 +-
labs/kernel-i2c-communication/kernel-i2c-communication.tex | 2 +-
slides/boot-time-toolchain2/using-time-command.svg | 2 +-
slides/sysdev-kernel-building/sysdev-kernel-building.tex | 4 ++--
slides/sysdev-realtime/sysdev-realtime.tex | 4 ++--
.../sysdev-root-filesystem-principles.tex | 2 +-
18 files changed, 27 insertions(+), 27 deletions(-)
diff --git a/labs/boot-time-application/boot-time-application.tex b/labs/boot-time-application/boot-time-application.tex
index 6b130add..627274f9 100644
--- a/labs/boot-time-application/boot-time-application.tex
+++ b/labs/boot-time-application/boot-time-application.tex
@@ -256,7 +256,7 @@ Notes:
\begin{itemize}
\item It seems you can not run an empty \code{while} loop with Busybox
\code{sh}. That's why I had to put a real command (not a comment)
- inside the looop.
+ inside the loop.
\item Fortunately, the \code{sleep} command supports subsecond waiting.
Did you know?
\item When we optimize the kernel, we will try to address this camera
@@ -264,7 +264,7 @@ Notes:
something on the screen to make the user wait.
\end{itemize}
-Update and reboot your system through \code{grabeserial}. Fill the below table
+Update and reboot your system through \code{grabserial}. Fill the below table
with updated figures (we don't expect earlier parts of system bootup to
be impacted... scripts may run faster after being recompiled in
\code{Thumb2})
diff --git a/labs/boot-time-board-setup/boot-time-board-setup.tex b/labs/boot-time-board-setup/boot-time-board-setup.tex
index 5acbdff1..f1d5ea2e 100644
--- a/labs/boot-time-board-setup/boot-time-board-setup.tex
+++ b/labs/boot-time-board-setup/boot-time-board-setup.tex
@@ -38,13 +38,13 @@ during the practical labs.
\section{Setting up serial communication with the board}
The Beaglebone serial connector is exported on the 6 pins close to one
-of the 48 pins headers. Using your special USB to Serial adaptor provided
+of the 48 pins headers. Using your special USB to Serial adapter provided
by your instructor, connect the ground wire (blue) to the pin closest
to the power supply connector (let's call it pin 1), and the \code{TX} (red)
and \code{RX} (green) wires to the pins 4 (board \code{RX}) and
5 (board \code{TX})\footnote{See
\url{https://www.olimex.com/Products/Components/Cables/USB-Serial-Cable/USB-Serial-Cable-F/}
-for details about the USB to Serial adaptor that we are using.}.
+for details about the USB to Serial adapter that we are using.}.
You always should make sure that you connect the \code{TX} pin of the cable
to the \code{RX} pin of the board, and vice versa, whatever the board and
diff --git a/labs/boot-time-bootloader/boot-time-bootloader.tex b/labs/boot-time-bootloader/boot-time-bootloader.tex
index 454b2726..e9ad1f7f 100644
--- a/labs/boot-time-bootloader/boot-time-bootloader.tex
+++ b/labs/boot-time-bootloader/boot-time-bootloader.tex
@@ -1,4 +1,4 @@
-\subchapter{Bootloader optimizations}{Reuce bootloader execution time}
+\subchapter{Bootloader optimizations}{Reduce bootloader execution time}
In this lab, we will run the final stage of boot time reduction:
\begin{itemize}
@@ -22,7 +22,7 @@ It's now time to eliminate useless features in U-Boot. Go to
\code{~/boot-time-labs/bootloader/u-boot/} and run \code{make
menuconfig} to unselect features that we don't need in our system.
-For the moment, don't touch the \code{SPL / TPL} optipns, as we will try
+For the moment, don't touch the \code{SPL / TPL} options, as we will try
to use U-Boot's Falcon mode at the end.
In the same way you did when you reduced the kernel configuration,
diff --git a/labs/boot-time-build-bootloader/boot-time-build-bootloader.tex b/labs/boot-time-build-bootloader/boot-time-build-bootloader.tex
index 5783500a..186085c3 100644
--- a/labs/boot-time-build-bootloader/boot-time-build-bootloader.tex
+++ b/labs/boot-time-build-bootloader/boot-time-build-bootloader.tex
@@ -79,7 +79,7 @@ On a board in a normal state, there should be a bootloader on the on-board MMC
external SD card (unless you hold the \code{USER} button while powering
up your board, which is just suitable for exceptional needs).
-Therefore, to override this behaviour and use the external SD card,
+Therefore, to override this behavior and use the external SD card,
instead, let's wipe out the \code{MLO} file on the eMMC.
Power up or reset your board, and in the U-Boot prompt, run:
@@ -103,7 +103,7 @@ on
\url{https://raw.githubusercontent.com/bootlin/training-materials/master/lab-data/common/bootloader/beaglebone-black/README.txt}.
Now, copy your newly compiled \code{MLO} and \code{u-boot.img} files to
-the SD card's \code{boot} partition, and after cleanly umounting this
+the SD card's \code{boot} partition, and after cleanly unmounting this
partition, insert the SD card into the board and reset it.
You should now see your board booting with your own \code{MLO} and U-Boot
diff --git a/labs/boot-time-build-kernel-and-start-system/boot-time-build-kernel-and-start-system.tex b/labs/boot-time-build-kernel-and-start-system/boot-time-build-kernel-and-start-system.tex
index de9f0520..ad229c46 100644
--- a/labs/boot-time-build-kernel-and-start-system/boot-time-build-kernel-and-start-system.tex
+++ b/labs/boot-time-build-kernel-and-start-system/boot-time-build-kernel-and-start-system.tex
@@ -34,7 +34,7 @@ Open \code{Makefile} again and make sure you now have a 5.1.y version.
You need the same \code{PATH} and \code{CROSS_COMPILE} environment
variables as when you compiled U-Boot, plus the \code{ARCH} one that
-corresponds to the target archicture.
+corresponds to the target architecture.
So, add the below line at the end of your \code{~/.bashrc} file:
diff --git a/labs/boot-time-filesystem-optimizations/boot-time-filesystem-optimizations.tex b/labs/boot-time-filesystem-optimizations/boot-time-filesystem-optimizations.tex
index e5355cf6..83ea264d 100644
--- a/labs/boot-time-filesystem-optimizations/boot-time-filesystem-optimizations.tex
+++ b/labs/boot-time-filesystem-optimizations/boot-time-filesystem-optimizations.tex
@@ -143,7 +143,7 @@ echo "Starting ffmpeg" > /dev/console
ffmpeg -t 10 -f video4linux2 -video_size 544x288 -input_format mjpeg -i /dev/video0 -pix_fmt rgb565le -f fbdev /dev/fb0 2> /dev/console
\end{verbatim}
-Now, you should be able to extrat the measures and write them down in
+Now, you should be able to extract the measures and write them down in
the table above. If your tests run the same way ours did, the
initramfs approach should win by a few tens of milliseconds.
diff --git a/labs/boot-time-init-scripts/boot-time-init-scripts.tex b/labs/boot-time-init-scripts/boot-time-init-scripts.tex
index a3f8b857..ebbcb393 100644
--- a/labs/boot-time-init-scripts/boot-time-init-scripts.tex
+++ b/labs/boot-time-init-scripts/boot-time-init-scripts.tex
@@ -1,4 +1,4 @@
-\subchapter{Init script optimizations}{Analysing and optimizing init
+\subchapter{Init script optimizations}{Analyzing and optimizing init
scripts}
\section{Measuring}
@@ -51,7 +51,7 @@ halt
Remove the SD card and copy that file to \code{~/boot-time-labs/rootfs/} on your host.
-\subsection{Analyse bootchart data on your workstation}
+\subsection{Analyze bootchart data on your workstation}
To compile and use \code{bootchart} on your workstation, you first need to
install a few Java packages:
diff --git a/labs/boot-time-kernel/boot-time-kernel.tex b/labs/boot-time-kernel/boot-time-kernel.tex
index 6bd3fb01..24eeeaba 100644
--- a/labs/boot-time-kernel/boot-time-kernel.tex
+++ b/labs/boot-time-kernel/boot-time-kernel.tex
@@ -57,7 +57,7 @@ inkscape boot.svg
\includegraphics[width=\textwidth]{labs/boot-time-kernel/boot.pdf}
\end{center}
-Now review the longuest initcalls in detail. Each label is the name of
+Now review the longest initcalls in detail. Each label is the name of
a function in the kernel sources. Try to find out in which source file
each function is defined\footnote{You can do it with utilities such as
\code{cscope}, which your instructor will be happy to demonstrate,
diff --git a/labs/boot-time-software-measurement/boot-time-software-measurement.tex b/labs/boot-time-software-measurement/boot-time-software-measurement.tex
index b4e1df96..044c9a0d 100644
--- a/labs/boot-time-software-measurement/boot-time-software-measurement.tex
+++ b/labs/boot-time-software-measurement/boot-time-software-measurement.tex
@@ -35,7 +35,7 @@ grabserial -d /dev/ttyUSB0 -t -e 30
\begin{itemize}
\item \code{-t} Displays the time when the first character of each line
was received.
-\item \code{-e} Specifies the {\bf e}end time when \code{grabserial}
+\item \code{-e} Specifies the {\bf e}nd time when \code{grabserial}
will exit.
\end{itemize}
@@ -77,7 +77,7 @@ mkdir -p board/beaglecam/patches/ffmpeg/
cp ../data/0001-ffmpeg-*.patch board/beaglecam/patches/ffmpeg/
\end{verbatim}
-Then, tell Builldroot to look for patches in this directory, by adding
+Then, tell Buildroot to look for patches in this directory, by adding
\code{board/beaglecam/patches} to the
\code{BR2_GLOBAL_PATCH_DIR} configuration setting (through \code{make
menuconfig} or by directly editing the \code{.config} file.
diff --git a/labs/boot-time-sources-download/boot-time-sources-download.tex b/labs/boot-time-sources-download/boot-time-sources-download.tex
index 319babd7..5686c5e6 100644
--- a/labs/boot-time-sources-download/boot-time-sources-download.tex
+++ b/labs/boot-time-sources-download/boot-time-sources-download.tex
@@ -82,7 +82,7 @@ needed.
Go to the \code{$HOME/boot-time-labs/kernel} directory.
-This represents the biggest amout of sources to download, actually more
+This represents the biggest amount of sources to download, actually more
than 1 GB of data! Again, you can use a pre-downloaded archive if that
turns out to be to much for your actual connection.
diff --git a/labs/boot-time-toolchain/boot-time-toolchain.tex b/labs/boot-time-toolchain/boot-time-toolchain.tex
index 2347fd44..0b57bfd5 100644
--- a/labs/boot-time-toolchain/boot-time-toolchain.tex
+++ b/labs/boot-time-toolchain/boot-time-toolchain.tex
@@ -134,7 +134,7 @@ start working on the next lab.
When the build is over:
\begin{itemize}
-\item Measure the new rootfilesystem archive and \code{ffmpeg}
+\item Measure the new root filesystem archive and \code{ffmpeg}
executable size, write it down in the table, and compute the difference
percentages vs. the ARM code.
\item Update the SD card with the new filesystem, run the same time
diff --git a/labs/kernel-board-setup/kernel-board-setup.tex b/labs/kernel-board-setup/kernel-board-setup.tex
index 4ab95504..37ece214 100644
--- a/labs/kernel-board-setup/kernel-board-setup.tex
+++ b/labs/kernel-board-setup/kernel-board-setup.tex
@@ -49,13 +49,13 @@ too during the practical labs.
\section{Setting up serial communication with the board}
The Beaglebone serial connector is exported on the 6 pins close to one
-of the 48 pins headers. Using your special USB to Serial adaptor provided
+of the 48 pins headers. Using your special USB to Serial adapter provided
by your instructor, connect the ground wire (blue) to the pin closest
to the power supply connector (let's call it pin 1), and the \code{TX} (red)
and \code{RX} (green) wires to the pins 4 (board \code{RX}) and
5 (board \code{TX})\footnote{See
\url{https://www.olimex.com/Products/Components/Cables/USB-Serial-Cable/USB-Serial-Cable-F/}
-for details about the USB to Serial adaptor that we are using.}.
+for details about the USB to Serial adapter that we are using.}.
You always should make sure that you connect the \code{TX} pin of the cable
to the \code{RX} pin of the board, and vice versa, whatever the board and
diff --git a/labs/kernel-compiling-and-nfs-booting/kernel-compiling-and-nfs-booting.tex b/labs/kernel-compiling-and-nfs-booting/kernel-compiling-and-nfs-booting.tex
index cd172236..4b369f25 100644
--- a/labs/kernel-compiling-and-nfs-booting/kernel-compiling-and-nfs-booting.tex
+++ b/labs/kernel-compiling-and-nfs-booting/kernel-compiling-and-nfs-booting.tex
@@ -191,7 +191,7 @@ By mistake, you could have booted a kernel previously stored in flash
(typically through a default boot command in U-Boot), or forgotten to
update the kernel image in \code{/var/lib/tftpboot}.
-This could explain some unexpected behaviour.
+This could explain some unexpected behavior.
There are two ways of checking your kernel version:
\begin{itemize}
diff --git a/labs/kernel-i2c-communication/kernel-i2c-communication.tex b/labs/kernel-i2c-communication/kernel-i2c-communication.tex
index 217ebdc3..b3eab639 100644
--- a/labs/kernel-i2c-communication/kernel-i2c-communication.tex
+++ b/labs/kernel-i2c-communication/kernel-i2c-communication.tex
@@ -209,7 +209,7 @@ errors.
\section{Read nunchuk registers}
-The nunchuk exhibits a rather weird behaviour: it seems that it updates
+The nunchuk exhibits a rather weird behavior: it seems that it updates
the state of its internal registers only when they have been read.
As a consequence, we will need to read the registers twice!
diff --git a/slides/boot-time-toolchain2/using-time-command.svg b/slides/boot-time-toolchain2/using-time-command.svg
index c01147c6..df1437d4 100644
--- a/slides/boot-time-toolchain2/using-time-command.svg
+++ b/slides/boot-time-toolchain2/using-time-command.svg
@@ -267,7 +267,7 @@
id="tspan839-4"
x="12.817226"
y="95.986916"
- style="fill:#000000;fill-opacity:1;stroke-width:0.26458332px">Second run (program and librairies already in file cache)</tspan></text>
+ style="fill:#000000;fill-opacity:1;stroke-width:0.26458332px">Second run (program and libraries already in file cache)</tspan></text>
<text
xml:space="preserve"
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:8.8194437px;line-height:125%;font-family:Sans;-inkscape-font-specification:'Sans, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-feature-settings:normal;text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;stroke-width:0.26458332px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
diff --git a/slides/sysdev-kernel-building/sysdev-kernel-building.tex b/slides/sysdev-kernel-building/sysdev-kernel-building.tex
index a91e28eb..e95ef6ea 100644
--- a/slides/sysdev-kernel-building/sysdev-kernel-building.tex
+++ b/slides/sysdev-kernel-building/sysdev-kernel-building.tex
@@ -445,7 +445,7 @@ tools (\code{gcc}, \code{as}, \code{ld}, \code{objcopy}, \code{strip}...).
\item Therefore making the kernel image available to the target is
usually manual or done through scripts in build systems.
\item It is however possible to customize the \code{make install}
- behaviour in \code{arch/<arch>/boot/install.sh}
+ behavior in \code{arch/<arch>/boot/install.sh}
\end{itemize}
\end{frame}
@@ -594,7 +594,7 @@ tools (\code{gcc}, \code{as}, \code{ld}, \code{objcopy}, \code{strip}...).
\frametitle{Kernel command line}
\begin{itemize}
\item In addition to the compile time configuration, the kernel
- behaviour can be adjusted with no recompilation using the {\bf
+ behavior can be adjusted with no recompilation using the {\bf
kernel command line}
\item The kernel command line is a string that defines various
arguments to the kernel
diff --git a/slides/sysdev-realtime/sysdev-realtime.tex b/slides/sysdev-realtime/sysdev-realtime.tex
index d7d540ff..65c84d29 100644
--- a/slides/sysdev-realtime/sysdev-realtime.tex
+++ b/slides/sysdev-realtime/sysdev-realtime.tex
@@ -54,7 +54,7 @@
\item {\bf Approach 2}
\begin{itemize}
\item Add a layer below the Linux kernel that will handle all the
- real-time requirements, so that the behaviour of Linux doesn't
+ real-time requirements, so that the behavior of Linux doesn't
affect real-time tasks.
\item Approach taken by RTLinux, RTAI and {\bf Xenomai}
\end{itemize}
@@ -826,7 +826,7 @@ timer_delete(timer_t timerid)
\code{sigtimedwait()} or \code{sigwaitinfo()} functions. Usually
better.
\end{itemize}
- \item Signal behaviour can be configured using \code{sigaction()}
+ \item Signal behavior can be configured using \code{sigaction()}
\item The mask of blocked signals can be changed with
\code{pthread_sigmask()}
\item Delivery of a signal using \code{pthread_kill()} or
diff --git a/slides/sysdev-root-filesystem-principles/sysdev-root-filesystem-principles.tex b/slides/sysdev-root-filesystem-principles/sysdev-root-filesystem-principles.tex
index 7c569538..207a5da6 100644
--- a/slides/sysdev-root-filesystem-principles/sysdev-root-filesystem-principles.tex
+++ b/slides/sysdev-root-filesystem-principles/sysdev-root-filesystem-principles.tex
@@ -106,7 +106,7 @@ Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block(0,0)
\item etc.
\end{itemize}
\item It is up to the system designer to choose the configuration
- for the system, and configure the kernel behaviour with
+ for the system, and configure the kernel behavior with
\code{root=}
\end{itemize}
\end{frame}
More information about the training-materials-updates
mailing list