[FE training-materials-updates] Explain the interest of statically compiled drivers

[Michael Opdenacker]

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

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

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

commit 69d98be3bbbed0fd5cb91ac811dae708defa68e6
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Fri Oct 5 06:15:56 2012 +0200

    Explain the interest of statically compiled drivers


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

69d98be3bbbed0fd5cb91ac811dae708defa68e6
 .../kernel-source-code-drivers.tex                 |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/slides/kernel-source-code-drivers/kernel-source-code-drivers.tex b/slides/kernel-source-code-drivers/kernel-source-code-drivers.tex
index e2587ef..a60debd 100644
--- a/slides/kernel-source-code-drivers/kernel-source-code-drivers.tex
+++ b/slides/kernel-source-code-drivers/kernel-source-code-drivers.tex
@@ -221,7 +221,8 @@
     kernel version and patch version (closed source drivers).
   \item Drivers have all privileges. You need the sources to make sure
     that a driver is not a security risk.
-  \item Your drivers can be statically compiled into the kernel.
+  \item Your drivers can be statically compiled into the kernel
+    (useful to have a kernel image with all drivers needed at boot time)
   \end{itemize}
 \end{frame}