[bootlin/training-materials updates] master: Boot time: improve slide order (3c4f1639)

Michael Opdenacker michael.opdenacker at bootlin.com
Thu May 23 23:33:15 CEST 2019


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

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

commit 3c4f16397b1e25fc2c896d3c234d9e21d5d988aa
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Thu May 23 23:33:15 2019 +0200

    Boot time: improve slide order
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


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

3c4f16397b1e25fc2c896d3c234d9e21d5d988aa
 .../boot-time-init-scripts.tex                     | 56 ++++++++++++++++++++++
 .../boot-time-init-scripts3.tex                    | 55 ---------------------
 2 files changed, 56 insertions(+), 55 deletions(-)

diff --git a/slides/boot-time-init-scripts/boot-time-init-scripts.tex b/slides/boot-time-init-scripts/boot-time-init-scripts.tex
index 5a012f99..548e7b80 100644
--- a/slides/boot-time-init-scripts/boot-time-init-scripts.tex
+++ b/slides/boot-time-init-scripts/boot-time-init-scripts.tex
@@ -189,6 +189,62 @@ You may try \code{mklibs}, available at \url{http://packages.debian.org/sid/mkli
 \end{itemize}
 \end{frame}
 
+\begin{frame}
+\frametitle{Quick splashscreen display (1)}
+Often the first sign of life that you are showing!
+\begin{itemize}
+\item You could use the \code{fbv} program
+      (\url{http://freecode.com/projects/fbv})\\
+      to display your splashscreen.
+\item On \code{armel}, you can just use our statically compiled
+      binary: {\tiny
+\url{https://github.com/bootlin/static-binaries/tree/master/fbv/}}
+\item However, this is slow:\\
+      878 ms on an Microchip AT91SAM9263 system!
+\end{itemize}
+\end{frame}
+
+\begin{frame}[fragile]
+\frametitle{Quick splashscreen display (2)}
+\begin{itemize}
+\item To do it faster, you can dump the framebuffer contents:\\
+      \begin{verbatim}
+fbv -d 1 /root/logo.bmp
+cp /dev/fb0 /root/logo.fb
+lzop -9 /root/logo.fb
+      \end{verbatim}
+\item And then copy it back as early as possible in an initramfs:
+      \begin{verbatim}
+lzopcat /root/logo.fb.lzo > /dev/fb0
+      \end{verbatim}
+\end{itemize}
+Results on an Microchip AT91SAM9263 system: \\
+\begin{tabular}{| l || c | c | c | }
+\hline
+& \code{fbv} & plain copy (\code{dd}) & \code{lzopcat} \\
+\hline
+Time & 878 ms & 54 ms & 52.5 ms\\
+\hline
+\end{tabular}
+\vfill
+\footnotesize
+\url{https://bootlin.com/blog/super-fast-linux-splashscreen/}
+\end{frame}
+
+\begin{frame}
+\frametitle{Animated splashscreen}
+Still slow to read and write entire screens. Just draw useful pixels
+and even create an animation!
+\begin{itemize}
+\item Create a simple C program that just animates pixels and simple
+      geometric shapes on the framebuffer!
+\item Example: {\small \url{https://bootlin.com/pub/code/fb/anim.c}}.
+      On a 400 MHz ARM9 system: starts drawing in 10 ms \\
+      Size: 24 KB, compiled statically.
+\end{itemize}
+\end{frame}
+
+
 \setuplabframe
 {Reducing time in init-scripts}
 {
diff --git a/slides/boot-time-init-scripts3/boot-time-init-scripts3.tex b/slides/boot-time-init-scripts3/boot-time-init-scripts3.tex
index e8d96ab6..db046bce 100644
--- a/slides/boot-time-init-scripts3/boot-time-init-scripts3.tex
+++ b/slides/boot-time-init-scripts3/boot-time-init-scripts3.tex
@@ -75,58 +75,3 @@ Initramfs compression & 3016928 & 4.1050 s & 1.760 s  & 8.813 s & + 18 ms \\
 \hline
 \end{tabular}
 \end{frame}
-
-\begin{frame}
-\frametitle{Quick splashscreen display (1)}
-Often the first sign of life that you are showing!
-\begin{itemize}
-\item You could use the \code{fbv} program
-      (\url{http://freecode.com/projects/fbv})\\
-      to display your splashscreen.
-\item On \code{armel}, you can just use our statically compiled
-      binary: {\tiny
-\url{https://github.com/bootlin/static-binaries/tree/master/fbv/}}
-\item However, this is slow:\\
-      878 ms on an Microchip AT91SAM9263 system!
-\end{itemize}
-\end{frame}
-
-\begin{frame}[fragile]
-\frametitle{Quick splashscreen display (2)}
-\begin{itemize}
-\item To do it faster, you can dump the framebuffer contents:\\
-      \begin{verbatim}
-fbv -d 1 /root/logo.bmp
-cp /dev/fb0 /root/logo.fb
-lzop -9 /root/logo.fb
-      \end{verbatim}
-\item And then copy it back as early as possible in an initramfs:
-      \begin{verbatim}
-lzopcat /root/logo.fb.lzo > /dev/fb0
-      \end{verbatim}
-\end{itemize}
-Results on an Microchip AT91SAM9263 system: \\
-\begin{tabular}{| l || c | c | c | }
-\hline
-& \code{fbv} & plain copy (\code{dd}) & \code{lzopcat} \\
-\hline
-Time & 878 ms & 54 ms & 52.5 ms\\
-\hline
-\end{tabular}
-\vfill
-\footnotesize
-\url{https://bootlin.com/blog/super-fast-linux-splashscreen/}
-\end{frame}
-
-\begin{frame}
-\frametitle{Animated splashscreen}
-Still slow to read and write entire screens. Just draw useful pixels
-and even create an animation!
-\begin{itemize}
-\item Create a simple C program that just animates pixels and simple
-      geometric shapes on the framebuffer!
-\item Example: {\small \url{https://bootlin.com/pub/code/fb/anim.c}}.
-      On a 400 MHz ARM9 system: starts drawing in 10 ms \\
-      Size: 24 KB, compiled statically.
-\end{itemize}
-\end{frame}




More information about the training-materials-updates mailing list