[FE training-materials-updates] kernel debugging: remove ref to the LDD book

[Michael Opdenacker]

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

On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=6c3d62f07606f65341dd09f9bd89fa5ba5648809

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

commit 6c3d62f07606f65341dd09f9bd89fa5ba5648809
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Thu Oct 11 15:18:42 2012 +0200

    kernel debugging: remove ref to the LDD book
    
    The "debugging" chapter of the Linux Device Drivers book
    is now too old to be mentioned. It doesn't know about debugfs,
    for example, and recommends obsolete debugging techniques.


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

6c3d62f07606f65341dd09f9bd89fa5ba5648809
 .../kernel-driver-development-debugging.tex        |   24 ++++++++------------
 1 file changed, 10 insertions(+), 14 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 6043345..03c7819 100644
--- a/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex
+++ b/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex
@@ -189,9 +189,9 @@
   \item Details available in the kernel documentation:
     \kerneldoc{DocBook/kgdb/}
   \item Recommended to turn on \code{CONFIG_FRAME_POINTER} to aid in
-    producing more reliable stack backtraces in gdb.
-  \item You must include a kgdb I/O driver. One of them is kgdb over
-    serial console (\code{kgdboc}: kgdb over console, enabled by
+    producing more reliable stack backtraces in \code{gdb}.
+  \item You must include a kgdb I/O driver. One of them is \code{kgdb} over
+    serial console (\code{kgdboc}: \code{kgdb} over console, enabled by
     \code{CONFIG_KGDB_SERIAL_CONSOLE})
   \item Configure \code{kgdboc} at boot time by passing to the kernel:
     \begin{itemize}
@@ -204,11 +204,11 @@
 \begin{frame}
   \frametitle{Using kgdb 2/2}
   \begin{itemize}
-  \item Then also pass \code{kgdbwait} to the kernel: it makes kgdb
-    wait for a debugger connection.
+  \item Then also pass \code{kgdbwait} to the kernel: it makes
+    \code{kgdb} wait for a debugger connection.
   \item Boot your kernel, and when the console is initialized,
     interrupt the kernel with \code{Alt} + \code{SyrRq} + \code{g}.
-  \item On your workstation, start gdb as follows:
+  \item On your workstation, start \code{gdb} as follows:
     \begin{itemize}
     \item \code{gdb ./vmlinux}
     \item \code{(gdb) set remotebaud 115200}
@@ -224,9 +224,9 @@
   \begin{itemize}
   \item Two types of JTAG dongles
     \begin{itemize}
-    \item Those offering a gdb compatible interface, over a serial
-      port or an Ethernet connexion. Gdb can directly connect to them.
-    \item Those not offering a gdb compatible interface are generally
+    \item Those offering a \code{gdb} compatible interface, over a
+      serial port or an Ethernet connexion. \code{gdb} can directly
+      connect to them. \item Those not offering a gdb compatible interface are generally
       supported by OpenOCD (Open On Chip Debugger):
       \url{http://openocd.sourceforge.net/}
       \begin{itemize}
@@ -239,7 +239,7 @@
       \end{itemize}
     \end{itemize}
   \item See very useful details on using Eclipse / gcc / gdb / OpenOCD
-    on Windows:
+    on Windows (similar usage):
     \begin{itemize}
     \item \url{http://www2.amontec.com/sdk4arm/ext/jlynch-tutorial-20061124.pdf}
     \item \url{http://www.yagarto.de/howto/yagarto2/}
@@ -264,10 +264,6 @@
     \begin{itemize}
     \item \url{http://kerneltrap.org/node/3648}
     \end{itemize}
-  \item More about kernel debugging in the free Linux Device Drivers book
-    \begin{itemize}
-    \item \url{http://lwn.net/images/pdf/LDD3/ch04.pdf}
-    \end{itemize}
   \end{itemize}
 \end{frame}