[FE training-materials-updates] kernel debugging slides: early printk details

[Michael Opdenacker]

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

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

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

commit f2c1a471dcbb2b04e1774351e59be23ba35d382f
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Tue Oct 15 11:15:52 2013 +0200

    kernel debugging slides: early printk details
    
    - Suggested by Jean Pihet
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


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

f2c1a471dcbb2b04e1774351e59be23ba35d382f
 .../kernel-driver-development-debugging.tex        |    6 +++---
 1 file changed, 3 insertions(+), 3 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 391739c..00c20da 100644
--- a/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex
+++ b/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex
@@ -256,9 +256,9 @@
     \item This obsoletes the \code{ksymoops} tool
     \end{itemize}
   \item If your kernel doesn't boot yet or hangs without any message,
-    you can activate the low-level debugging option
-    (\code{Kernel Hacking} section, only available on \code{arm} and
-    \code{unicore32}): \code{CONFIG_DEBUG_LL=y}
+    you can activate early debugging options (\code{CONFIG_DEBUG_LL} and
+    \code{CONFIG_EARLYPRINTK}), and add \code{earlyprintk} to the kernel
+    command line.
   \item Techniques to locate the C instruction which caused an oops:
     \url{http://j.mp/18oMRHx}
   \end{itemize}