[FE training-materials-updates] Misc line return and font size improvements
Michael Opdenacker
michael.opdenacker at free-electrons.com
Thu Nov 5 19:45:53 CET 2015
Repository : git://git.free-electrons.com/training-materials.git
On branch : master
Link : http://git.free-electrons.com/training-materials/commit/?id=787c3c800f0be421a74110f48c808102ba9ae743
>---------------------------------------------------------------
commit 787c3c800f0be421a74110f48c808102ba9ae743
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date: Thu Nov 5 19:45:53 2015 +0100
Misc line return and font size improvements
Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>
>---------------------------------------------------------------
787c3c800f0be421a74110f48c808102ba9ae743
.../sysdev-embedded-linux.tex | 34 ++++---
.../sysdev-flash-filesystems.tex | 104 +++++++++++----------
2 files changed, 73 insertions(+), 65 deletions(-)
diff --git a/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex b/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex
index a9ab2c4..9c57a01 100644
--- a/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex
+++ b/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex
@@ -65,25 +65,23 @@
\begin{frame}
\frametitle{Choosing components}
+ Not all free software components are necessarily good to
+ re-use. One must pay attention to:
\begin{itemize}
- \item Not all free software components are necessarily good to
- re-use. One must pay attention to:
- \begin{itemize}
- \item {\bf Vitality} of the developer and user communities. This
- vitality ensures long-term maintenance of the component, and
- relatively good support. It can be measured by looking at the
- mailing-list traffic and the version control system activity.
- \item {\bf Quality} of the component. Typically, if a component is
- already available through embedded build systems, and has a
- dynamic user community, it probably means that the quality is
- relatively good.
- \item {\bf License}. The license of the component must match your
- licensing constraints. For example, GPL libraries cannot be used
- in proprietary applications.
- \item {\bf Technical requirements}. Of course, the component must
- match your technical requirements. But don't forget that you can
- improve the existing components if a feature is missing!
- \end{itemize}
+ \item {\bf Vitality} of the developer and user communities. This
+ vitality ensures long-term maintenance of the component, and
+ relatively good support. It can be measured by looking at the
+ mailing-list traffic and the version control system activity.
+ \item {\bf Quality} of the component. Typically, if a component is
+ already available through embedded build systems, and has a
+ dynamic user community, it probably means that the quality is
+ relatively good.
+ \item {\bf License}. The license of the component must match your
+ licensing constraints. For example, GPL libraries cannot be used
+ in proprietary applications.
+ \item {\bf Technical requirements}. Of course, the component must
+ match your technical requirements. But don't forget that you can
+ improve the existing components if a feature is missing!
\end{itemize}
\end{frame}
diff --git a/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex b/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
index 59e8148..0cf45dd 100644
--- a/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
+++ b/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
@@ -289,16 +289,19 @@ setenv mtdparts mtdparts=omap2-nand.0:512k(X-Loader)ro,1536k(U-Boot)ro,512k(Env)
\item U-Boot provides a set of commands to manipulate NOR devices
\item Memory mapped NOR devices
\begin{itemize}
- \item \code{flinfo [devid]} display information of all NOR devices
+ \item \code{flinfo [devid]}\\
+ Display information of all NOR devices
or a specific one if \code{devid} is provided
- \item \code{cp.[bwl] <src> <target> <count>} read/write data frm/to
- the NOR device
- \item \code{erase <start> <end>} or \code{erase <start> +<len>}
- erase a memory region
- \item \code{erase bank <bankid>} erase a memory bank
- \item \code{erase all} erase all banks
- \item \code{protect on|off <range-description>} protect a memory
- range
+ \item \code{cp.[bwl] <src> <target> <count>}\\
+ Read/write data from/to the NOR device
+ \item \code{erase <start> <end>} or \code{erase <start> +<len>}\\
+ Erase a memory region
+ \item \code{erase bank <bankid>}\\
+ Erase a memory bank
+ \item \code{erase all}\\
+ Erase all banks
+ \item \code{protect on|off <range-description>}\\
+ Protect a memory range
\end{itemize}
\end{itemize}
\end{frame}
@@ -309,11 +312,14 @@ setenv mtdparts mtdparts=omap2-nand.0:512k(X-Loader)ro,1536k(U-Boot)ro,512k(Env)
\item SPI NOR devices
\begin{itemize}
\item Grouped under the \code{sf} command
- \item \code{sf probre [[bus:]cs] [hz] [mode]} probe a NOR device on
- \item \code{sf read|write <addr> <offset> <len>} read/write data
- from/to a SPI NOR
- \item \code{sf erase <offset> +<len>} erase a memory region
- \item \code{sf update <addr> <offset> <len>} erase + write operation
+ \item \code{sf probe [[bus:]cs] [hz] [mode]}\\
+ Probe a NOR device on
+ \item \code{sf read|write <addr> <offset> <len>}\\
+ Read/write data from/to a SPI NOR
+ \item \code{sf erase <offset> +<len>}\\
+ Erase a memory region
+ \item \code{sf update <addr> <offset> <len>}\\
+ Erase + write operation
\end{itemize}
\end{itemize}
\end{frame}
@@ -553,13 +559,15 @@ setenv mtdparts mtdparts=omap2-nand.0:512k(X-Loader)ro,1536k(U-Boot)ro,512k(Env)
\item Creates a UBI image to be flashed on an MTD partition
\item Takes the following arguments:
\begin{itemize}
- \item \code{-o <output-file-path>} path to the output image file
- \item \code{-p <peb-size>} the PEB size (MTD erase block size)
- \item \code{-m <min-io-size>} the minimum write unit size (e.g.
- MTD write size)
- \item \code{-s <subpage-size>} subpage size, only needed if both
- your flash and your flash controller are supporting subpage
- writes
+ \item \code{-o <output-file-path>}\\
+ Path to the output image file
+ \item \code{-p <peb-size>}\\
+ The PEB size (MTD erase block size)
+ \item \code{-m <min-io-size>}\\
+ The minimum write unit size (e.g. MTD write size)
+ \item \code{-s <subpage-size>}\\
+ Subpage size, only needed if both your flash and your
+ flash controller are supporting subpage writes
\item The last argument is a path to a UBI image description file
\end{itemize}
\item Example: \code{ubinize -o ubi.img -p 16KiB -m 512 -s 256 cfg.ini}
@@ -613,13 +621,15 @@ vol_flags=autoresize
\frametitle{U-Boot: UBI tools}
Grouped under the \code{ubi} command
\begin{itemize}
- \item \code{ubi part <part-name>} attach an MTD partition to the UBI
- layer
- \item \code{ubi info [layout]} display UBI device information (or
- volume information if the \code{layout} string is passed
- \item \code{ubi check <vol-name>} check if a volume exists
- \item \code{ubi readvol <dest-addr> <vol-name> [<size>]} read volume
- contents
+ \item \code{ubi part <part-name>}\\
+ Attach an MTD partition to the UBI layer
+ \item \code{ubi info [layout]}\\
+ Display UBI device information\\
+ (or volume information if the \code{layout} string is passed
+ \item \code{ubi check <vol-name>}\\
+ Check if a volume exists
+ \item \code{ubi readvol <dest-addr> <vol-name> [<size>]}\\
+ Read volume contents
\item U-Boot also provides tools to update the UBI device contents
\item Using them is highly discouraged (the U-Boot UBI implementation
is not entirely stable, and using commands that do not touch the UBI
@@ -639,13 +649,13 @@ vol_flags=autoresize
UBI elements
\item UBI device management:
\begin{itemize}
- \item \code{ubiformat <MTD-device-id>} format an MTD partition and
- preserve Erase Counter information if any
- \item \code{ubiattach -m <MTD-device-id> /dev/ubi_ctrl} attach an
- MTD partition/device to the UBI layer, and create a UBI device
- \item \code{ubidetach -m <MTD-device-id> /dev/ubi_ctrl} detach an
- MTD partition/device from the UBI layer, and remove this associated
- UBI device
+ \item \code{ubiformat <MTD-device-id>}\\
+ Format an MTD partition and preserve Erase Counter information if any
+ \item \code{ubiattach -m <MTD-device-id> /dev/ubi_ctrl}\\
+ Attach an MTD partition/device to the UBI layer, and create a UBI device
+ \item \code{ubidetach -m <MTD-device-id> /dev/ubi_ctrl}\\
+ Detach an MTD partition/device from the UBI layer, and remove
+ the associated UBI device
\end{itemize}
\end{itemize}
\end{frame}
@@ -654,17 +664,17 @@ vol_flags=autoresize
\frametitle{Linux: UBI target tools (2)}
UBI volume management:
\begin{itemize}
- \item \code{ubimkvol /dev/ubi<UBI-device-id> -N <name> -s <size>} create
- a new volume. Use \code{-m} in place of \code{-s <size>} if you want
- to assign all the remaining to this volume
- \item \code{ubirmvol /dev/ubi<UBI-device-id> -N <name>} delete an UBI
- volume
- \item \code{ubiupdatevol /dev/ubi<UBI-device-id>_<UBI-vol-id> [-s <size>] <vol-image-file>}
- update volume contents
- \item \code{ubirsvol /dev/ubi<UBI-device-id> -N <name> -s <size>}
- resize an UBI volume
- \item \code{ubirename /dev/ubi<UBI-device-id>_<UBI-vol-id> <old-name> <new-size>}
- rename a UBI volume
+ \item {\small \code{ubimkvol /dev/ubi<UBI-device-id> -N <name> -s <size>}}\\
+ Create a new volume. Use \code{-m} in place of \code{-s <size>}
+ if you want to assign all the remaining space to this volume.
+ \item {\small \code{ubirmvol /dev/ubi<UBI-device-id> -N <name>}}\\
+ Delete a UBI volume
+ \item {\small \code{ubiupdatevol /dev/ubi<UBI-device-id>_<UBI-vol-id> [-s <size>] <vol-image-file>}}\\
+ Update volume contents
+ \item {\small \code{ubirsvol /dev/ubi<UBI-device-id> -N <name> -s <size>}}\\
+ Resize a UBI volume
+ \item {\small \code{ubirename /dev/ubi<UBI-device-id>_<UBI-vol-id> <old-name> <new-size>}}\\
+ Rename a UBI volume
\end{itemize}
\end{frame}
@@ -694,7 +704,7 @@ vol_flags=autoresize
\code{ubiattach})
\item \code{-c 1000}, maximum number of logical erase
blocks. Details:
- {\tiny\url{http://linux-mtd.infradead.org/faq/ubifs.html\#L_max_leb_cnt}}
+ {\scriptsize\url{http://linux-mtd.infradead.org/faq/ubifs.html\#L_max_leb_cnt}}
\end{itemize}
\item Once created
\begin{itemize}
More information about the training-materials-updates
mailing list