[FE training-materials-updates] We need the udev instructions for fastboot too

[Maxime Ripard]

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

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

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

commit 2edb00da54638cc46aa64653f7f7971d0af0529a
Author: Maxime Ripard <maxime.ripard at free-electrons.com>
Date:   Mon May 19 11:42:54 2014 +0200

    We need the udev instructions for fastboot too
    
    Signed-off-by: Maxime Ripard <maxime.ripard at free-electrons.com>


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

2edb00da54638cc46aa64653f7f7971d0af0529a
 labs/android-adb/android-adb.tex             |   32 +++-----------------------
 labs/android-new-board/android-new-board.tex |   28 ++++++++++++++++++++++
 2 files changed, 31 insertions(+), 29 deletions(-)

diff --git a/labs/android-adb/android-adb.tex b/labs/android-adb/android-adb.tex
index 9dab7c8..326d72b 100644
--- a/labs/android-adb/android-adb.tex
+++ b/labs/android-adb/android-adb.tex
@@ -30,41 +30,15 @@ However, the Android source code also has an embedded SDK, so you
 already have the \code{adb} binary in the
 \code{out/host/linux-x86/bin/}.
 
-To add this directory to your \code{PATH} after the Linaro build
-during the previous lab, you can go through the same environment setup
-steps as earlier:
+To add this directory to your \code{PATH} after the build done in the
+previous lab, you can go through the same environment setup steps as
+earlier:
 
 \begin{verbatim}
 source build/envsetup.sh
 lunch beagleboneblack-eng
 \end{verbatim}
 
-\section{Configure USB access on your machine}
-
-Your instructor will now give you a USB to mini-USB cable. Connect
-the mini-USB connector to your board, and the other connector to your
-computer.
-
-We will use this connection to access the device through ADB.
-
-If you execute any command right now, you are very likely to have a
-permission denied error. This is because the USB device associated to
-the BeagleBone doesn't have the right permissions to let you open it.
-
-We need to make sure that \code{udev} sets the right permissions so
-that we can access it as a user. To do so, create the file
-\code{/etc/udev/rules.d/51-android.rules} and copy the following line:
-
-\code{SUBSYSTEM=="usb", ATTR{idVendor}=="<VendorId>", ATTR{idProduct}=="<ProductID>", MODE="0600", OWNER="<username>"}
-
-You can retrieve the vendor and product IDs to use when by using the
-\code{lsusb} command, and looking at the line with \code{Google
-  Inc.}. You should see on this line the IDs to use, with the format
-\code{ID <VendorID>:<ProductID>}.
-
-Now, unplug the USB cable and plug it again. You should now be able to
-use \code{adb} from your user account.
-
 \section{Get logs from the device}
 
 ADB provides many useful features to work with an existing Android
diff --git a/labs/android-new-board/android-new-board.tex b/labs/android-new-board/android-new-board.tex
index 4227aa2..5d91fc8 100644
--- a/labs/android-new-board/android-new-board.tex
+++ b/labs/android-new-board/android-new-board.tex
@@ -168,6 +168,34 @@ you wish to exit \code{picocom}, press \code{[Ctrl][a]} followed by
 
 You should then be able to access the serial console.
 
+\section{Configure USB access on your machine}
+
+Your instructor will now give you a USB to mini-USB cable. Connect
+the mini-USB connector to your board, and the other connector to your
+computer.
+
+We will use this connection for fastboot and, later on, adb.
+
+If you execute any command right now, you are very likely to have an
+error, because fastboot can't even detect the device. This is because
+the USB device associated to the BeagleBone doesn't have the right
+permissions to let you open it.
+
+We need to make sure that \code{udev} sets the right permissions so
+that we can access it as a user. To do so, create the file
+\code{/etc/udev/rules.d/51-android.rules} and copy the following line:
+
+\code{SUBSYSTEM=="usb", ATTR{idVendor}=="<VendorId>", ATTR{idProduct}=="<ProductID>", MODE="0600", OWNER="<username>"}
+
+You can retrieve the vendor and product IDs to use when by using the
+\code{lsusb} command, and looking at the line with \code{Google
+  Inc.}. You should see on this line the IDs to use, with the format
+\code{ID <VendorID>:<ProductID>}.
+
+Now, unplug the USB cable and plug it again. You should now be able to
+use \code{fastboot} from your user account, with the command
+\code{fastboot devices} showing the board properly.
+
 \section{Flashing and Booting the Images}
 
 To flash the images we previously generated, we will use