[FE training-materials-updates] Give a bit more clue to get the file we need to edit

Maxime Ripard maxime.ripard at free-electrons.com
Mon Nov 19 14:50:16 CET 2012


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

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

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

commit f85dc0d78bb59c84bfeb6c1963cff533413853de
Author: Maxime Ripard <maxime.ripard at free-electrons.com>
Date:   Mon Nov 19 14:49:51 2012 +0100

    Give a bit more clue to get the file we need to edit
    
    Signed-off-by: Maxime Ripard <maxime.ripard at free-electrons.com>


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

f85dc0d78bb59c84bfeb6c1963cff533413853de
 labs/android-new-board/android-new-board.tex |    6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/labs/android-new-board/android-new-board.tex b/labs/android-new-board/android-new-board.tex
index 2475880..5278137 100644
--- a/labs/android-new-board/android-new-board.tex
+++ b/labs/android-new-board/android-new-board.tex
@@ -224,7 +224,8 @@ script.
 However, the build system can help us here. Use the
 \code{BOARD_KERNEL_CMDLINE} variable to set these new value. It will
 be processed by the build system and then used when it generates the
-boot image.
+boot image. Since this variable is related to the hardware, this
+variable should be in \code{BoardConfig.mk}
 
 You can also add \code{no_console_suspend} to the bootargs as Android
 by default suspends the shell on the serial line after a minute or so,
@@ -240,7 +241,8 @@ Button mapping is done in two steps. First, in the kernel, the board
 should define the available buttons. In this case, we will use the
 small black buttons right next to the screen on the DevKit8000. These
 buttons are handled by the \code{gpio-keys} driver, and defined in the
-devkit8000 board file in the kernel.
+devkit8000 board file in the kernel, in the \code{arch/arm/mach-omap2}
+folder.
 
 If you look into that file, you will see that only one button is
 defined, the one corresponding to the button labeled \code{user key}



More information about the training-materials-updates mailing list