[FE training-materials-updates] Update device tree location

[Alexandre Belloni]

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

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

commit 159fc0b6b3ff81c311ffb2d342decb108744098b
Author: Alexandre Belloni <alexandre.belloni at free-electrons.com>
Date:   Tue Mar 8 20:18:12 2016 +0100

    Update device tree location
    
    Signed-off-by: Alexandre Belloni <alexandre.belloni at free-electrons.com>


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

159fc0b6b3ff81c311ffb2d342decb108744098b
 labs/kernel-i2c-device-model/kernel-i2c-device-model.tex | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/labs/kernel-i2c-device-model/kernel-i2c-device-model.tex b/labs/kernel-i2c-device-model/kernel-i2c-device-model.tex
index e9f9b20..26d1d50 100644
--- a/labs/kernel-i2c-device-model/kernel-i2c-device-model.tex
+++ b/labs/kernel-i2c-device-model/kernel-i2c-device-model.tex
@@ -114,7 +114,7 @@ Now, copy the new DTB to the tftp server home directory, change the DTB
 file name in the U-Boot configuration\footnote{Tip: you just need to run
 \code{editenv bootargs} and \code{saveenv}.}, and boot the board.
 
-Through the \code{/proc/device-tree} directory, it is possible to check
+Through the \code{/sys/firmware/devicetree} directory, it is possible to check
 the Device Tree settings that your system has loaded. That's useful when
 you are not sure exactly which settings were actually loaded.
 
@@ -122,8 +122,8 @@ For example, you can check the presence of a new \code{nunchuk} node in
 your device tree:
 
 \begin{verbatim}
-# find /proc/device-tree -name "*nunchuk*"
-/proc/device-tree/ocp/i2c at 4802a000/nunchuk at 52
+# find /sys/firmware/devicetree -name "*nunchuk*"
+/sys/firmware/devicetree/base/ocp/i2c at 4802a000/nunchuk at 52
 \end{verbatim}
 
 Using the Device Tree Compiler (\code{dtc}, which we put in the root
@@ -132,7 +132,7 @@ better than checking the source files and includes in the source
 directory!
 
 \begin{verbatim}
-# dtc -I fs /proc/device-tree/
+# dtc -I fs /sys/firmware/devicetree/base/
 \end{verbatim}
 
 Look for \code{i2c1} and \code{nunchuk} in the output of this command,