[bootlin/training-materials updates] master: Kernel slides: minor improvements (bf739380)
Michael Opdenacker
michael.opdenacker at bootlin.com
Tue Sep 3 11:53:22 CEST 2019
Repository : https://github.com/bootlin/training-materials
On branch : master
Link : https://github.com/bootlin/training-materials/commit/bf7393804ae9983cf5c3f9a812a9c69434aeaa66
>---------------------------------------------------------------
commit bf7393804ae9983cf5c3f9a812a9c69434aeaa66
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date: Tue Sep 3 11:53:22 2019 +0200
Kernel slides: minor improvements
Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>
>---------------------------------------------------------------
bf7393804ae9983cf5c3f9a812a9c69434aeaa66
.../kernel-driver-development-debugging.tex | 3 ++-
slides/kernel-frameworks2/kernel-frameworks2.tex | 4 ++--
slides/kernel-porting-content/kernel-porting-content.tex | 2 +-
3 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex b/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex
index 464ec1f0..ad81d00c 100644
--- a/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex
+++ b/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex
@@ -87,8 +87,9 @@ dev_info(&pdev->dev, "in probe\n");
their priority and the configuration of
\begin{itemize}
\item The \code{loglevel} kernel parameter, which defines the
- priority above which messages are displayed on the console.
+ priority number below which messages are displayed on the console.
Details in \kerneldochtml{admin-guide/kernel-parameters}.
+ \newline Examples: \code{loglevel=0}: no message, \code{loglevel=8}: all messages
\item The value of \code{/proc/sys/kernel/printk}, which allows to
change at runtime the priority above which messages are
displayed on the console. Details in
diff --git a/slides/kernel-frameworks2/kernel-frameworks2.tex b/slides/kernel-frameworks2/kernel-frameworks2.tex
index f41f9dbf..6ff9385e 100644
--- a/slides/kernel-frameworks2/kernel-frameworks2.tex
+++ b/slides/kernel-frameworks2/kernel-frameworks2.tex
@@ -28,7 +28,7 @@
\frametitle{File operations}
\begin{itemize}
\item Here are the most important operations for a character
- driver. All of them are optional.
+ driver. Many more exist. All of them are optional.
\end{itemize}
\begin{minted}[fontsize=\footnotesize]{c}
#include <linux/fs.h>
@@ -538,7 +538,7 @@ struct rtl8150 {
\begin{frame}
\frametitle{Links between structures 1/4}
\begin{itemize}
- \item The framework typically contains a \kstruct{device} \code{*}
+ \item The framework structure typically contains a \kstruct{device} \code{*}
pointer that the driver must point to the corresponding
\kstruct{device}
\begin{itemize}
diff --git a/slides/kernel-porting-content/kernel-porting-content.tex b/slides/kernel-porting-content/kernel-porting-content.tex
index ebe70f05..6d7a1a02 100644
--- a/slides/kernel-porting-content/kernel-porting-content.tex
+++ b/slides/kernel-porting-content/kernel-porting-content.tex
@@ -360,7 +360,7 @@ dtb-$(CONFIG_ARCH_MXS) += imx28-cfa10036.dtb \
370/XP.
\item For this platform, the core of the SoC support is located in
\kdir{arch/arm/mach-mvebu}
- \item The \code{board-v7.c} file (see code on the next slide)
+ \item The \kfile{arch/arm/mach-mvebu/board-v7.c} file (see code on the next slide)
contains the "{\em entry point}" of the SoC definition, the
\code{DT_MACHINE_START} .. \code{MACHINE_END} definition:
\begin{itemize}
More information about the training-materials-updates
mailing list