[FE training-materials-updates] labs/kernel-marvell-armada: take into account the linux -> kernel rename

Thomas Petazzoni thomas.petazzoni at free-electrons.com
Wed Jul 23 14:03:12 CEST 2014

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

On branch  : marvell-armada
Link       : http://git.free-electrons.com/training-materials/commit/?id=6fcf379bf17ad2f63c55a0a7ace6e04389034598


commit 6fcf379bf17ad2f63c55a0a7ace6e04389034598
Author: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
Date:   Wed Jul 23 14:02:34 2014 +0200

    labs/kernel-marvell-armada: take into account the linux -> kernel rename
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>


 .../kernel-marvell-armada.tex                      |   19 +++++++++----------
 1 file changed, 9 insertions(+), 10 deletions(-)

diff --git a/labs/kernel-marvell-armada/kernel-marvell-armada.tex b/labs/kernel-marvell-armada/kernel-marvell-armada.tex
index 19c3804..d8d4f0c 100644
--- a/labs/kernel-marvell-armada/kernel-marvell-armada.tex
+++ b/labs/kernel-marvell-armada/kernel-marvell-armada.tex
@@ -15,7 +15,7 @@ the latest release candidate of the kernel. If there is a newer one,
 you can also try it.
 Apply the \code{scu-fix.patch} patch available from the labs data
-directory (\code{$HOME/felabs/linux/marvell-armada}). It works around
+directory (\code{$HOME/felabs/kernel/marvell-armada}). It works around
 a problem in the Marvell U-Boot bootloader, which has been fixed in
 more recent versions of U-Boot (maybe it is even already fixed on the
 board you're using).
@@ -27,7 +27,7 @@ we'll use out of tree build. This means we'll have one source tree,
 and two separate build trees. Start by creating a build directory:
-mkdir $HOME/felabs/linux/mvebu-le
+mkdir $HOME/felabs/kernel/mvebu-le
 And move to this directory.
@@ -37,11 +37,11 @@ configuration for ARMv7 Marvell EBU platforms in the kernel (i.e
 Armada 370, XP, 375, 38x and Dove) :
-make -C $HOME/felabs/linux/src O=$(pwd) ARCH=arm mvebu_v7_defconfig
+make -C $HOME/felabs/kernel/src O=$(pwd) ARCH=arm mvebu_v7_defconfig
 This command tells \code{make} to use the Makefile in
-\code{$HOME/felabs/linux/src}, but also tells the kernel that the
+\code{$HOME/felabs/kernel/src}, but also tells the kernel that the
 current directory (passed through \code{O=}) should be used as the
 build tree. After this command has been executed, a small {\em
   wrapper} Makefile has been generated in the build directory, so we
@@ -60,7 +60,7 @@ We will have to:
     and RAM disk (initramfs/initrd) support} $\rightarrow$ {\em
     Initramfs source file(s)}, set the path to the pre-built {\em
     initramfs} we are providing. It is available in
-  \code{$HOME/felabs/linux/marvell-armada/rootfs.cpio.le}.
+  \code{$HOME/felabs/kernel/marvell-armada/rootfs.cpio.le}.
 \item In {\em System Type}, explore the options available under {\em
     Marvell Engineering Business Unit (MVEBU) SoCs}
 \item In {\em Boot Options}, make sure {\em Use appended device tree
@@ -187,20 +187,20 @@ endian one in terms of generated code, we'll use a separate build
 tree. Let's create it first:
-mkdir $HOME/felabs/linux/mvebu-be
+mkdir $HOME/felabs/kernel/mvebu-be
 Go in this directory, and then copy the configuration file we have
 created for the little endian build:
-cp $HOME/felabs/linux/mvebu-le/.config .config
+cp $HOME/felabs/kernel/mvebu-le/.config .config
 Now, we'll adjust the configuration:
-make -C $HOME/felabs/linux/src O=$(pwd) ARCH=arm menuconfig
+make -C $HOME/felabs/kernel/src O=$(pwd) ARCH=arm menuconfig
 Note that since it's the first time we run a \code{make} command from
@@ -211,7 +211,7 @@ In the configuration, adjust the following items:
 \item Adjust the path of the {\em initramfs}, to point to
-  \code{$HOME/felabs/linux/marvell-armada/rootfs.cpio.be}, which
+  \code{$HOME/felabs/kernel/marvell-armada/rootfs.cpio.be}, which
   contains a big endian userspace.
 \item In {\em System type}, enable the {\em Build big-endian kernel}
@@ -221,4 +221,3 @@ Start the build of your kernel, generate the appended zImage, then the
 uImage, and boot your kernel. You can verify with \code{uname} that
 you are indeed running a \code{armv7b} system, i.e a big-endian ARM

More information about the training-materials-updates mailing list