[bootlin/training-materials updates] master: Boot time slides: detail OMAP booting process (9d66a34e)

[Michael Opdenacker]

Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/9d66a34e3bc989f3013f847079e2ed7c15950a55

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

commit 9d66a34e3bc989f3013f847079e2ed7c15950a55
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Thu May 23 17:32:35 2019 +0200

    Boot time slides: detail OMAP booting process
    
    - Sharing the slide with the embedded linux course
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


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

9d66a34e3bc989f3013f847079e2ed7c15950a55
 common/booting-process-omap.tex                    | 26 ++++++++++++++++++++++
 .../boot-time-principles/boot-time-principles.tex  |  2 ++
 .../sysdev-bootloaders-sequence.tex                | 26 +---------------------
 3 files changed, 29 insertions(+), 25 deletions(-)

diff --git a/common/booting-process-omap.tex b/common/booting-process-omap.tex
new file mode 100644
index 00000000..db1683e3
--- /dev/null
+++ b/common/booting-process-omap.tex
@@ -0,0 +1,26 @@
+\begin{frame}
+\frametitle{Booting on ARM TI OMAP2+ / AM33xx}
+  \begin{columns}
+    \column{0.3\textwidth}
+    \includegraphics[height=0.8\textheight]{slides/sysdev-bootloaders-sequence/omap-boot.pdf}
+    \column{0.7\textwidth}
+    \footnotesize
+    \begin{itemize}
+    \item {\bf ROM Code}: tries to find a valid bootstrap image from
+      various storage sources, and load it into SRAM or RAM (RAM can
+      be initialized by ROM code through a configuration header). Size
+      limited to \textless 64 KB. No user interaction possible.
+    \item {\bf X-Loader} or {\bf U-Boot SPL}: runs from SRAM. Initializes
+      the DRAM, the NAND or MMC controller, and loads the secondary
+      bootloader into RAM and starts it. No user interaction
+      possible. File called \code{MLO}.
+    \item {\bf U-Boot}: runs from RAM. Initializes some other hardware
+      devices (network, USB, etc.).  Loads the kernel image from
+      storage or network to RAM and starts it. Shell with commands
+      provided. File called \code{u-boot.bin} or \code{u-boot.img}.
+    \item {\bf Linux Kernel}: runs from RAM. Takes over the system
+      completely (bootloaders no longer exists).
+    \end{itemize}
+  \end{columns}
+\end{frame}
+
diff --git a/slides/boot-time-principles/boot-time-principles.tex b/slides/boot-time-principles/boot-time-principles.tex
index 3225a544..ebc6a082 100644
--- a/slides/boot-time-principles/boot-time-principles.tex
+++ b/slides/boot-time-principles/boot-time-principles.tex
@@ -40,6 +40,8 @@ We are focusing on reducing {\em cold} boot time, from power on to the
 critical application.
 \end{frame}
 
+\input{../common/booting-process-omap.tex}
+
 \begin{frame}
 \frametitle{What to optimize first}
 Start by optimizing the {\bf last steps} of the boot process!
diff --git a/slides/sysdev-bootloaders-sequence/sysdev-bootloaders-sequence.tex b/slides/sysdev-bootloaders-sequence/sysdev-bootloaders-sequence.tex
index 5d2b0088..343c76d0 100644
--- a/slides/sysdev-bootloaders-sequence/sysdev-bootloaders-sequence.tex
+++ b/slides/sysdev-bootloaders-sequence/sysdev-bootloaders-sequence.tex
@@ -129,31 +129,7 @@
   \end{columns}
 \end{frame}
 
-\begin{frame}
-\frametitle{Booting on ARM TI OMAP3}
-  \begin{columns}
-    \column{0.3\textwidth}
-    \includegraphics[height=0.8\textheight]{slides/sysdev-bootloaders-sequence/omap-boot.pdf}
-    \column{0.7\textwidth}
-    \footnotesize
-    \begin{itemize}
-    \item {\bf ROM Code}: tries to find a valid bootstrap image from
-      various storage sources, and load it into SRAM or RAM (RAM can
-      be initialized by ROM code through a configuration header). Size
-      limited to \textless 64 KB. No user interaction possible.
-    \item {\bf X-Loader} or {\bf U-Boot}: runs from SRAM. Initializes
-      the DRAM, the NAND or MMC controller, and loads the secondary
-      bootloader into RAM and starts it. No user interaction
-      possible. File called \code{MLO}.
-    \item {\bf U-Boot}: runs from RAM. Initializes some other hardware
-      devices (network, USB, etc.).  Loads the kernel image from
-      storage or network to RAM and starts it. Shell with commands
-      provided. File called \code{u-boot.bin} or \code{u-boot.img}.
-    \item {\bf Linux Kernel}: runs from RAM. Takes over the system
-      completely (bootloaders no longer exists).
-    \end{itemize}
-  \end{columns}
-\end{frame}
+\input{../common/booting-process-omap.tex}
 
 \begin{frame}
   \frametitle{Booting on Marvell SoCs}