[FE training-materials-updates] Mention how Android gets the platform name

[Maxime Ripard]

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

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

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

commit 0a6331a19f655f8967d1fc760a4698ca72a66ddc
Author: Maxime Ripard <maxime.ripard at free-electrons.com>
Date:   Mon Oct 1 15:31:18 2012 +0200

    Mention how Android gets the platform name
    
    Signed-off-by: Maxime Ripard <maxime.ripard at free-electrons.com>


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

0a6331a19f655f8967d1fc760a4698ca72a66ddc
 .../android-native-layer-init.tex                  |    3 +++
 1 file changed, 3 insertions(+)

diff --git a/slides/android-native-layer-init/android-native-layer-init.tex b/slides/android-native-layer-init/android-native-layer-init.tex
index 860da9b..1c237d7 100644
--- a/slides/android-native-layer-init/android-native-layer-init.tex
+++ b/slides/android-native-layer-init/android-native-layer-init.tex
@@ -55,6 +55,9 @@
   \item While \code{init.rc} is always taken into account,
     \code{init.<platform_name>.rc} is only interpreted if the platform
     currently running the system reports the same name
+  \item This name is either obtained by reading the file
+    \code{/proc/cpuinfo} or from the \code{androidboot.hardware}
+    kernel parameter
   \item Most of the customizations should therefore go to the
     platform-specific configuration file rather than to the generic
     one