[FE training-materials-updates] Misc font and style improvements
michael.opdenacker at free-electrons.com
michael.opdenacker at free-electrons.com
Tue Jun 26 06:56:29 CEST 2012
- Log -----------------------------------------------------------------
http://git.free-electrons.com/training-materials/commit/?id=852a421b2b3395af5c818ae65618d3d455954863
commit 852a421b2b3395af5c818ae65618d3d455954863
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date: Tue Jun 26 06:55:07 2012 +0200
Misc font and style improvements
diff --git a/slides/sysdev-bootloaders-sequence/sysdev-bootloaders-sequence.tex b/slides/sysdev-bootloaders-sequence/sysdev-bootloaders-sequence.tex
index df6d209..4d998aa 100644
--- a/slides/sysdev-bootloaders-sequence/sysdev-bootloaders-sequence.tex
+++ b/slides/sysdev-bootloaders-sequence/sysdev-bootloaders-sequence.tex
@@ -95,7 +95,7 @@
\item This boot code is able to load a first stage bootloader from a
storage device into an internal SRAM (DRAM not initialized yet)
\begin{itemize}
- \item Storage device can typically be: MMC, NAND, SPI Flash, UART,
+ \item Storage device can typically be: MMC, NAND, SPI flash, UART,
etc.
\end{itemize}
\item The first stage bootloader is
diff --git a/slides/sysdev-bootloaders-u-boot/sysdev-bootloaders-u-boot.tex b/slides/sysdev-bootloaders-u-boot/sysdev-bootloaders-u-boot.tex
index 5a97506..e5a20b2 100644
--- a/slides/sysdev-bootloaders-u-boot/sysdev-bootloaders-u-boot.tex
+++ b/slides/sysdev-bootloaders-u-boot/sysdev-bootloaders-u-boot.tex
@@ -91,7 +91,7 @@
\begin{itemize}
\item \code{make BOARDNAME_config}
\item Where \code{BOARDNAME} is usually the name of the
- configuration file in \code{include/configs/}, without the
+ configuration file in \code{include/configs/}, without
\code{.h}
\end{itemize}
\item Make sure that the cross-compiler is available in \code{PATH}
@@ -218,9 +218,9 @@ U-Boot configuration and hardware devices)
mainly used for USB storage devices such as USB keys
\item \code{mmc}, to initialize and control the MMC subsystem, used
for SD and microSD cards
- \item \code{nand}, to erase, read and write contents to the NAND
+ \item \code{nand}, to erase, read and write contents to NAND flash
\item \code{erase}, \code{protect}, \code{cp}, to erase, modify
- protection and write to a NOR flash
+ protection and write to NOR flash
\item \code{md}, displays memory contents. Can be useful to check the
contents loaded in memory, or to look at hardware registers.
\item \code{mm}, modifies memory contents. Can be useful to modify
@@ -233,9 +233,9 @@ U-Boot configuration and hardware devices)
\begin{itemize}
\item U-Boot can be configured through environment variables, which
affect the behavior of the different commands.
- \item Environment variables are loaded from Flash to RAM at U-Boot
- startup, can be modified and saved back to Flash for persistence
- \item There is a dedicated location in Flash to store U-Boot
+ \item Environment variables are loaded from flash to RAM at U-Boot
+ startup, can be modified and saved back to flash for persistence
+ \item There is a dedicated location in flash to store U-Boot
environment, defined in the board configuration file
\item Commands to manipulate environment variables:
\begin{itemize}
@@ -243,7 +243,7 @@ U-Boot configuration and hardware devices)
\item \code{printenv <variable-name>}, shows the value of one variable
\item \code{setenv <variable-name> <variable- value>}, changes the
value of a variable, only in RAM
- \item \code{saveenv}, saves to Flash the current state of the environment
+ \item \code{saveenv}, saves the current state of the environment to flash
\end{itemize}
\end{itemize}
\end{frame}
@@ -294,7 +294,7 @@ u-boot # saveenv
several commands and test the results of commands.
\begin{itemize}
\item Useful to automate booting or upgrade processes
- \item Several command can be chained using the \code{;} operator
+ \item Several commands can be chained using the \code{;} operator
\item Tests can be done using
\code{if command ; then ... ; else ... ; fi}
\item Scripts are executed using \code{run <variable-name>}
diff --git a/slides/sysdev-dev-environment/sysdev-dev-environment.tex b/slides/sysdev-dev-environment/sysdev-dev-environment.tex
index ee717b1..d5779ff 100644
--- a/slides/sysdev-dev-environment/sysdev-dev-environment.tex
+++ b/slides/sysdev-dev-environment/sysdev-dev-environment.tex
@@ -102,7 +102,7 @@
\end{itemize}
\item Packages are stored in {\bf repositories}, usually on HTTP or
FTP servers
- \item One should only use packages from official repositories of its
+ \item You should only use packages from official repositories for your
distribution, unless strictly required.
\end{itemize}
\end{frame}
diff --git a/slides/sysdev-linux-intro-modules/sysdev-linux-intro-modules.tex b/slides/sysdev-linux-intro-modules/sysdev-linux-intro-modules.tex
index ac3d6d3..1858b67 100644
--- a/slides/sysdev-linux-intro-modules/sysdev-linux-intro-modules.tex
+++ b/slides/sysdev-linux-intro-modules/sysdev-linux-intro-modules.tex
@@ -84,7 +84,7 @@ $ dmesg
\item \code{sudo modprobe <module_name>}\\
Most common usage of \code{modprobe}: tries to load all the
modules the given module depends on, and then this module. Lots of
- other options are available. Modprobe automatically looks in
+ other options are available. \code{modprobe} automatically looks in
\code{/lib/modules/<version>/} for the object file corresponding
to the given module name.
\item \code{lsmod}\\
@@ -102,7 +102,7 @@ $ dmesg
example, no more processes opening a device file)
\item \code{sudo modprobe -r <module_name>}\\
Tries to remove the given module and all dependent modules (which
- are no longer needed after the module removal)
+ are no longer needed after removing the module)
\end{itemize}
\end{frame}
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 1cfa6a6..842b5f0 100644
--- a/slides/sysdev-root-filesystem-principles/sysdev-root-filesystem-principles.tex
+++ b/slides/sysdev-root-filesystem-principles/sysdev-root-filesystem-principles.tex
@@ -77,7 +77,7 @@
\item They are not accessible before mounting at least one filesystem.
\end{itemize}
\item As the root filesystem is the first mounted filesystem, it
- cannot be mounted with the normal mount command
+ cannot be mounted with the normal \code{mount} command
\item It is mounted directly by the kernel, according to the
\code{root=} kernel option
\item When no root filesystem is available, the kernel panics\\
@@ -97,7 +97,7 @@ Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block(0,0)
\item From the partition of a hard disk
\item From the partition of a USB key
\item From the partition of an SD card
- \item From the partition of a NAND Flash or similar type of
+ \item From the partition of a NAND flash chip or similar type of
storage device
\item From the network, using the NFS protocol
\item From memory, using a pre-loaded filesystem (by the
@@ -120,7 +120,7 @@ Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block(0,0)
\item \code{/dev/sdb2} is the second partition of the second disk
drive (either USB key or ATA hard drive)
\end{itemize}
- \item Partitions of a SD card
+ \item Partitions of an SD card
\begin{itemize}
\item \code{root=/dev/mmcblkXpY}, where \code{X} is a number
indicating the device and \code{Y} a number indicating the
@@ -128,11 +128,11 @@ Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block(0,0)
\item \code{/dev/mmcblk0p2} is the second partition of the first
device
\end{itemize}
- \item Partitions of a NAND Flash
+ \item Partitions of flash storage
\begin{itemize}
\item \code{root=/dev/mtdblockX}, where \code{X} is the partition number
- \item \code{/dev/mtdblock3} is the fourth partition of the NAND
- flash (if only one NAND flash is present)
+ \item \code{/dev/mtdblock3} is the fourth partition of a NAND
+ flash chip (if only one NAND flash chip is present)
\end{itemize}
\end{itemize}
\end{frame}
diff --git a/slides/sysdev-toolchains-options/sysdev-toolchains-options.tex b/slides/sysdev-toolchains-options/sysdev-toolchains-options.tex
index a2a7202..6ab7196 100644
--- a/slides/sysdev-toolchains-options/sysdev-toolchains-options.tex
+++ b/slides/sysdev-toolchains-options/sysdev-toolchains-options.tex
@@ -14,7 +14,7 @@
\begin{itemize}
\item Nowadays everybody uses {\em EABI}
\end{itemize}
- \item On MIPS, several ABI: {\em o32, o64, n32, n64}
+ \item On MIPS, several ABIs: {\em o32, o64, n32, n64}
\item \url{http://en.wikipedia.org/wiki/Application_Binary_Interface}
\end{itemize}
\end{frame}
http://git.free-electrons.com/training-materials/commit/?id=27ddcf4c963af1ebe915ec0e5afc5aa02cedd367
commit 27ddcf4c963af1ebe915ec0e5afc5aa02cedd367
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date: Tue Jun 26 06:46:11 2012 +0200
Fix tiny screenshot and removed vspaces
- xconfig screenshot was too small
Recreated with a bigger font size
- Removed vspace statements in
"make gconfig", "make menuconfig"
and "make nconfig", looking ugly
diff --git a/slides/sysdev-linux-intro-configuration/sysdev-linux-intro-configuration.tex b/slides/sysdev-linux-intro-configuration/sysdev-linux-intro-configuration.tex
index 2798939..28a0d60 100644
--- a/slides/sysdev-linux-intro-configuration/sysdev-linux-intro-configuration.tex
+++ b/slides/sysdev-linux-intro-configuration/sysdev-linux-intro-configuration.tex
@@ -199,13 +199,12 @@ CONFIG_NTFS_RW=y
\begin{columns}
\column{0.5\textwidth}
\code{make gconfig}
- \vspace{0.5cm}
- {\em GTK} based graphical configuration interface. Functionality
- similar to that of make \code{xconfig}.
- \vspace{0.5cm}
- Just lacking a search functionality.
- \vspace{0.5cm}
- Required Debian packages: \code{libglade2-dev}
+ \begin{itemize}
+ \item {\em GTK} based graphical configuration interface. Functionality
+ similar to that of make \code{xconfig}.
+ \item Just lacking a search functionality.
+ \item Required Debian packages: \code{libglade2-dev}
+ \end{itemize}
\column{0.5\textwidth}
\includegraphics[width=0.9\textwidth]{slides/sysdev-linux-intro-configuration/gconfig-screenshot.png}
\end{columns}
@@ -216,12 +215,11 @@ CONFIG_NTFS_RW=y
\begin{columns}
\column{0.5\textwidth}
\code{make menuconfig}
- \vspace{0.5cm}
- Useful when no graphics are available. Pretty convenient too!
- \vspace{0.5cm}
- Same interface found in other tools: BusyBox, Buildroot...
- \vspace{0.5cm}
- Required Debian packages: \code{libncurses-dev}
+ \begin{itemize}
+ \item Useful when no graphics are available. Pretty convenient too!
+ \item Same interface found in other tools: BusyBox, Buildroot...
+ \item Required Debian packages: \code{libncurses-dev}
+ \end{itemize}
\column{0.5\textwidth}
\includegraphics[width=0.9\textwidth]{slides/sysdev-linux-intro-configuration/menuconfig-screenshot.png}
\end{columns}
@@ -232,12 +230,11 @@ CONFIG_NTFS_RW=y
\begin{columns}
\column{0.5\textwidth}
\code{make nconfig}
- \vspace{0.5cm}
- A newer, similar text interface
- \vspace{0.5cm}
- More user friendly (for example, easier to access help information).
- \vspace{0.5cm}
- Required Debian packages: \code{libncurses-dev}
+ \begin{itemize}
+ \item A newer, similar text interface
+ \item More user friendly (for example, easier to access help information).
+ \item Required Debian packages: \code{libncurses-dev}
+ \end{itemize}
\column{0.5\textwidth}
\includegraphics[width=0.9\textwidth]{slides/sysdev-linux-intro-configuration/nconfig-screenshot.png}
\end{columns}
@@ -336,7 +333,7 @@ CONFIG_NTFS_RW=y
\item Enable the block layer
\begin{itemize}
\item If \code{CONFIG_EXPERT} is enabled, the block layer can be
- completely removed. Embedded systems using only Flash storage
+ completely removed. Embedded systems using only flash storage
can safely disable the block layer
\end{itemize}
\item Processor type and features (x86) or System type (ARM) or CPU selection
@@ -403,7 +400,7 @@ CONFIG_NTFS_RW=y
\begin{itemize}
\item Device drivers
\begin{itemize}
- \item MTD is the subsystem for Flash (NOR, NAND, OneNand,
+ \item MTD is the subsystem for flash (NOR, NAND, OneNand,
battery-backed memory, etc.)
\item Parallel port support
\item Block devices, a few misc block drivers such as loopback,
@@ -516,7 +513,7 @@ CONFIG_NTFS_RW=y
\item CD-ROM filesystems: ISO9660, UDF
\item DOS/Windows filesystems: FAT and NTFS
\item Pseudo filesystems: proc and sysfs
- \item Miscellaneous filesystems, with amongst other Flash
+ \item Miscellaneous filesystems, with amongst other flash
filesystems such as JFFS2, UBIFS, SquashFS, cramfs
\item Network filesystems, with mainly NFS and SMB/CIFS
\end{itemize}
diff --git a/slides/sysdev-linux-intro-configuration/xconfig-screenshot.png b/slides/sysdev-linux-intro-configuration/xconfig-screenshot.png
index 52ae808..3f5e4ad 100644
Binary files a/slides/sysdev-linux-intro-configuration/xconfig-screenshot.png and b/slides/sysdev-linux-intro-configuration/xconfig-screenshot.png differ
http://git.free-electrons.com/training-materials/commit/?id=e776da76f04ad1ae9215dbb262a8feb1e73b84c4
commit e776da76f04ad1ae9215dbb262a8feb1e73b84c4
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date: Tue Jun 26 06:16:37 2012 +0200
Update stable kernel versions info and screenshot
diff --git a/slides/sysdev-linux-intro-versioning/stable-kernels.png b/slides/sysdev-linux-intro-versioning/stable-kernels.png
index 8394e94..6435b09 100644
Binary files a/slides/sysdev-linux-intro-versioning/stable-kernels.png and b/slides/sysdev-linux-intro-versioning/stable-kernels.png differ
diff --git a/slides/sysdev-linux-intro-versioning/sysdev-linux-intro-versioning.tex b/slides/sysdev-linux-intro-versioning/sysdev-linux-intro-versioning.tex
index c3b5d4f..1b62091 100644
--- a/slides/sysdev-linux-intro-versioning/sysdev-linux-intro-versioning.tex
+++ b/slides/sysdev-linux-intro-versioning/sysdev-linux-intro-versioning.tex
@@ -78,9 +78,9 @@
Linux provider.
\item You could reuse sources for the kernel used in Ubuntu Long
Term Support releases (5 years of free security updates).
- \item You could choose one of the versions advertised as “long termâ€
- in the \url{http://kernel.org} front page. They will be maintained
- longer (2 or 3 years), unlike other versions.
+ \item The \url{http://kernel.org} front page shows which
+ versions will be supported for some time (up to 2 or 3 years),
+ and which ones won't be supported any more ("EOL: End Of Life")
\end{itemize}
\column{0.3\textwidth}
\includegraphics[width=\textwidth]{slides/sysdev-linux-intro-versioning/stable-kernels.png}
http://git.free-electrons.com/training-materials/commit/?id=758cd724e4113197b2acf7e53ba8c08e77d5f591
commit 758cd724e4113197b2acf7e53ba8c08e77d5f591
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date: Tue Jun 26 05:49:07 2012 +0200
--enable-local instead of --local in ct-ng
diff --git a/slides/sysdev-toolchains-obtaining/sysdev-toolchains-obtaining.tex b/slides/sysdev-toolchains-obtaining/sysdev-toolchains-obtaining.tex
index df9c815..51b7eed 100644
--- a/slides/sysdev-toolchains-obtaining/sysdev-toolchains-obtaining.tex
+++ b/slides/sysdev-toolchains-obtaining/sysdev-toolchains-obtaining.tex
@@ -94,7 +94,7 @@
\code{export PATH=/path/to/toolchain/bin/:$PATH}
\item Finally, compile your applications\\
\code{PREFIX-gcc -o foobar foobar.c}
- \item The \code{PREFIX} depends on the toolchain configuration, and
+ \item \code{PREFIX} depends on the toolchain configuration, and
allows to distinguish cross-compilation tools from native
compilation utilities
\end{itemize}
@@ -162,7 +162,7 @@ a cross-compiling toolchain
\item Installation of Crosstool-NG can be done system-wide, or just locally in
the source directory. For local installation:
\begin{verbatim}
-./configure --local
+./configure --enable-local
make
make install
\end{verbatim}
http://git.free-electrons.com/training-materials/commit/?id=059ac55372296d7603ac050d35d96e3e08f6f843
commit 059ac55372296d7603ac050d35d96e3e08f6f843
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date: Tue Jun 26 05:38:25 2012 +0200
Fix "- " between words
diff --git a/slides/kernel-driver-development-concurrency/kernel-driver-development-concurrency.tex b/slides/kernel-driver-development-concurrency/kernel-driver-development-concurrency.tex
index 6803c25..2329a97 100644
--- a/slides/kernel-driver-development-concurrency/kernel-driver-development-concurrency.tex
+++ b/slides/kernel-driver-development-concurrency/kernel-driver-development-concurrency.tex
@@ -4,7 +4,7 @@
\frametitle{Sources of concurrency issues}
\begin{itemize}
\item In terms of concurrency, the kernel has the same constraint
- has a multi- threaded program: all its state is global and visible
+ has a multi-threaded program: all its state is global and visible
in all executions contexts
\item Concurrency arises because of
\begin{itemize}
diff --git a/slides/kernel-resources-advice/kernel-resources-advice.tex b/slides/kernel-resources-advice/kernel-resources-advice.tex
index 1db71f6..529ddf7 100644
--- a/slides/kernel-resources-advice/kernel-resources-advice.tex
+++ b/slides/kernel-resources-advice/kernel-resources-advice.tex
@@ -22,7 +22,7 @@
\item Either contact the Linux mailing list for your architecture
(like linux-arm-kernel or linuxsh-dev...).
\item Or contact the mailing list for the subsystem you're dealing
- with (linux- usb-devel, linux-mtd...). Don't ask the maintainer
+ with (linux-usb-devel, linux-mtd...). Don't ask the maintainer
directly!
\item Most mailing lists come with a FAQ page. Make sure you read
it before contacting the mailing list.
diff --git a/slides/sysdev-application-development/sysdev-application-development.tex b/slides/sysdev-application-development/sysdev-application-development.tex
index 1d9d2e7..2725a30 100644
--- a/slides/sysdev-application-development/sysdev-application-development.tex
+++ b/slides/sysdev-application-development/sysdev-application-development.tex
@@ -79,7 +79,7 @@
relatively large set of features
\begin{itemize}
\item file and device I/O, networking, threads and
- synchronization, inter- process communication
+ synchronization, inter-process communication
\item Thoroughly described in the glibc manual, or in any {\em
Linux system programming} book
\item However, the API carries a lot of history and is not
diff --git a/slides/sysdev-bootloaders-sequence/sysdev-bootloaders-sequence.tex b/slides/sysdev-bootloaders-sequence/sysdev-bootloaders-sequence.tex
index c71a592..df6d209 100644
--- a/slides/sysdev-bootloaders-sequence/sysdev-bootloaders-sequence.tex
+++ b/slides/sysdev-bootloaders-sequence/sysdev-bootloaders-sequence.tex
@@ -29,7 +29,7 @@
non-volatile memory containing a program, the BIOS.
\item This program gets executed by the CPU after reset, and is
responsible for basic hardware initialization and loading of a
- small piece of code from non- volatile storage.
+ small piece of code from non-volatile storage.
\begin{itemize}
\item This piece of code is usually the first 512 bytes of a
storage device
diff --git a/slides/sysdev-dev-environment/sysdev-dev-environment.tex b/slides/sysdev-dev-environment/sysdev-dev-environment.tex
index 0e1373f..ee717b1 100644
--- a/slides/sysdev-dev-environment/sysdev-dev-environment.tex
+++ b/slides/sysdev-dev-environment/sysdev-dev-environment.tex
@@ -72,7 +72,7 @@
the network, creating device files, changing the system
configuration, installing or removing software
\item All {\bf other users are unprivileged}, and cannot perform
- those administrator- level operations
+ those administrator-level operations
\end{itemize}
\item On an Ubuntu system, it is not possible to log in as
\code{root}, only as a normal user.
@@ -94,7 +94,7 @@
installing, updating and removing applications and libraries:
{\bf packages}
\item Packages contains the application or library files, and
- associated meta- information, such as the version and the
+ associated meta-information, such as the version and the
dependencies
\begin{itemize}
\item \code{.deb} on Debian and Ubuntu, \code{.rpm} on Red Hat,
@@ -156,7 +156,7 @@
\end{itemize}
\item They are connected by various means: almost always a serial
line for debugging purposes, frequently an Ethernet connection,
- sometimes a JTAG for low- level debugging
+ sometimes a JTAG interface for low-level debugging
\end{itemize}
\begin{center}
\includegraphics[width=0.7\textwidth]{slides/sysdev-dev-environment/host-vs-target.pdf}
diff --git a/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex b/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex
index 056a795..a3eeaff 100644
--- a/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex
+++ b/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex
@@ -1414,7 +1414,7 @@ Contents of \code{usr/lib} after installation of {\em libpng} and {\em
toolchain.
\item They automatically download, configure, compile and install
all the components in the right order, sometimes after applying
- patches to fix cross- compiling issues.
+ patches to fix cross-compiling issues.
\item They already contain a large number of packages, that should
fit your main requirements, and are easily extensible.
\item The build becomes reproducible, which allows to easily change
diff --git a/slides/sysdev-realtime/sysdev-realtime.tex b/slides/sysdev-realtime/sysdev-realtime.tex
index cd59505..2b350af 100644
--- a/slides/sysdev-realtime/sysdev-realtime.tex
+++ b/slides/sysdev-realtime/sysdev-realtime.tex
@@ -367,7 +367,7 @@
\end{itemize}
\item In Linux, since 2.6.18, mutexes support priority inheritance
\item In userspace, priority inheritance must be explicitly enabled
- on a per- mutex basis.
+ on a per-mutex basis.
\end{itemize}
\end{frame}
@@ -423,7 +423,7 @@
\item The PREEMPT\_RT patch adds a new level of preemption, called
\code{CONFIG_PREEMPT_RT}
\item This level of preemption replaces all kernel spinlocks by
- mutexes (or so- called sleeping spinlocks)
+ mutexes (or so-called sleeping spinlocks)
\begin{itemize}
\item Instead of providing mutual exclusion by disabling
interrupts and preemption, they are just normal locks: when
@@ -521,7 +521,7 @@
\item No special library is needed, the POSIX real-time API is part
of the standard C library
\item The glibc or eglibc C libraries are recommended, as support
- for some real- time features is not available in uClibc yet
+ for some real-time features is not available in uClibc yet
\begin{itemize}
\item Priority inheritance mutexes or NPTL on some architectures,
for example
@@ -1255,7 +1255,7 @@ ret = bind(s, (struct sockaddr *)&saddr, sizeof(saddr));
\item A Xenomai specific API for developing real-time tasks
\begin{itemize}
\item Usable both in user-space and kernel space. Development of
- tasks in user- space is the preferred way.
+ tasks in user-space is the preferred way.
\item More coherent and more flexible API than the POSIX
API. Easier to learn and understand. Certainly the way to go for
new applications.
-----------------------------------------------------------------------
Summary of changes:
.../kernel-driver-development-concurrency.tex | 2 +-
.../kernel-resources-advice.tex | 2 +-
.../sysdev-application-development.tex | 2 +-
.../sysdev-bootloaders-sequence.tex | 4 +-
.../sysdev-bootloaders-u-boot.tex | 16 ++++----
.../sysdev-dev-environment.tex | 8 ++--
.../sysdev-embedded-linux.tex | 2 +-
.../sysdev-linux-intro-configuration.tex | 41 +++++++++-----------
.../xconfig-screenshot.png | Bin 101265 -> 125216 bytes
.../sysdev-linux-intro-modules.tex | 4 +-
.../stable-kernels.png | Bin 16850 -> 11770 bytes
.../sysdev-linux-intro-versioning.tex | 6 +--
slides/sysdev-realtime/sysdev-realtime.tex | 8 ++--
.../sysdev-root-filesystem-principles.tex | 12 +++---
.../sysdev-toolchains-obtaining.tex | 4 +-
.../sysdev-toolchains-options.tex | 2 +-
16 files changed, 55 insertions(+), 58 deletions(-)
More information about the training-materials-updates
mailing list