[FE training-materials-updates] kernel: add subsection in very large chapters

Thomas Petazzoni thomas.petazzoni at free-electrons.com
Tue Oct 1 16:32:36 CEST 2013


Repository : git://git.free-electrons.com/training-materials.git

On branch  : kernel-ng
Link       : http://git.free-electrons.com/training-materials/commit/?id=9b6f10fad2c51bc558cc3e321514a75a27c0c21f

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

commit 9b6f10fad2c51bc558cc3e321514a75a27c0c21f
Author: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
Date:   Tue Oct 1 16:32:08 2013 +0200

    kernel: add subsection in very large chapters
    
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>


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

9b6f10fad2c51bc558cc3e321514a75a27c0c21f
 slides/kernel-device-model/kernel-device-model.tex |   46 +++++++++++---------
 slides/kernel-frameworks/kernel-frameworks.tex     |    8 ++++
 2 files changed, 34 insertions(+), 20 deletions(-)

diff --git a/slides/kernel-device-model/kernel-device-model.tex b/slides/kernel-device-model/kernel-device-model.tex
index 48b42be..7bc6561 100644
--- a/slides/kernel-device-model/kernel-device-model.tex
+++ b/slides/kernel-device-model/kernel-device-model.tex
@@ -1,5 +1,7 @@
 \section{Linux device and driver model}
 
+\subsection{Introduction}
+
 \begin{frame}{The need for a device model?}
   \begin{itemize}
   \item The Linux kernel runs on a wide range of architectures and
@@ -83,6 +85,8 @@
   \end{itemize}
 \end{frame}
 
+\subsection{Example of the USB bus}
+
 \begin{frame}
 \frametitle{Example: USB Bus 1/2}
   \begin{center}
@@ -277,26 +281,7 @@ static int rtl8150_probe(struct usb_interface *intf,
   \end{center}
 \end{frame}
 
-\begin{frame}
-  \frametitle{sysfs}
-  \begin{itemize}
-  \item The bus, device, drivers, etc. structures are internal to the
-    kernel
-  \item The \code{sysfs} virtual filesystem offers a mechanism to
-    export such information to userspace
-  \item Used for example by \code{udev} to provide automatic module loading,
-    firmware loading, device file creation, etc.
-  \item \code{sysfs} is usually mounted in \code{/sys}
-    \begin{itemize}
-    \item \code{/sys/bus/} contains the list of buses
-    \item \code{/sys/devices/} contains the list of devices
-    \item \code{/sys/class} enumerates devices by class (\code{net},
-      \code{input}, \code{block}...), whatever the bus they are connected
-      to. Very useful!
-    \end{itemize}
-  \item Take your time to explore \code{/sys} on your workstation.
-  \end{itemize}
-\end{frame}
+\subsection{Platform drivers}
 
 \begin{frame}{Non-discoverable busses}
   \begin{itemize}
@@ -658,6 +643,27 @@ static struct platform_driver serial_omap_driver = {
 \end{frame}
 
 \begin{frame}
+  \frametitle{sysfs}
+  \begin{itemize}
+  \item The bus, device, drivers, etc. structures are internal to the
+    kernel
+  \item The \code{sysfs} virtual filesystem offers a mechanism to
+    export such information to userspace
+  \item Used for example by \code{udev} to provide automatic module loading,
+    firmware loading, device file creation, etc.
+  \item \code{sysfs} is usually mounted in \code{/sys}
+    \begin{itemize}
+    \item \code{/sys/bus/} contains the list of buses
+    \item \code{/sys/devices/} contains the list of devices
+    \item \code{/sys/class} enumerates devices by class (\code{net},
+      \code{input}, \code{block}...), whatever the bus they are connected
+      to. Very useful!
+    \end{itemize}
+  \item Take your time to explore \code{/sys} on your workstation.
+  \end{itemize}
+\end{frame}
+
+\begin{frame}
   \frametitle{References}
   \begin{itemize}
   \item Kernel documentation
diff --git a/slides/kernel-frameworks/kernel-frameworks.tex b/slides/kernel-frameworks/kernel-frameworks.tex
index e0ec663..08828a7 100644
--- a/slides/kernel-frameworks/kernel-frameworks.tex
+++ b/slides/kernel-frameworks/kernel-frameworks.tex
@@ -18,6 +18,8 @@
   \end{columns}
 \end{frame}
 
+\subsection{Userspace vision of devices}
+
 \begin{frame}
   \frametitle{Types of devices} Under Linux, there is essentially
   three types of devices:
@@ -120,6 +122,8 @@ close(fd);
   \end{itemize}
 \end{frame}
 
+\subsection{Character drivers}
+
 \begin{frame}
   \frametitle{A character driver in the kernel}
   \begin{itemize}
@@ -370,6 +374,8 @@ int main(void)
 \end{minted}
 \end{frame}
 
+\subsection{The concept of kernel frameworks}
+
 \begin{frame}
   \frametitle{Beyond character drivers: kernel frameworks}
   \begin{itemize}
@@ -396,6 +402,8 @@ int main(void)
   \end{center}
 \end{frame}
 
+\subsection{Example of the framebuffer framework}
+
 \begin{frame}
   \frametitle{Example: Framebuffer Framework}
   \begin{itemize}



More information about the training-materials-updates mailing list