[FE training-materials-updates] Merge branch 'ubuntu1204'

michael.opdenacker at free-electrons.com michael.opdenacker at free-electrons.com
Mon Jun 25 22:43:26 CEST 2012

- Log -----------------------------------------------------------------

commit 99763ceebad0f688b3d8d4c3320d219d75ecbe12
Merge: aac9b83 61f4575
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Mon Jun 25 22:41:40 2012 +0200

    Merge branch 'ubuntu1204'


commit aac9b8387a72ad9c359046264cb6cfa862e32e14
Merge: c632470 b664487
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Mon Jun 25 14:51:23 2012 +0200

    Merge branch 'master' of git.free-electrons.com:training-materials


commit c632470c940635eeeaa23cf7588620f6aff3d58d
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Thu Jun 21 15:00:31 2012 +0200

    Mostly font updates

diff --git a/slides/sysdev-busybox/sysdev-busybox.tex b/slides/sysdev-busybox/sysdev-busybox.tex
index 468c5ee..4ca01f4 100644
--- a/slides/sysdev-busybox/sysdev-busybox.tex
+++ b/slides/sysdev-busybox/sysdev-busybox.tex
@@ -78,12 +78,12 @@
   \frametitle{Applet highlight - BusyBox vi}
-  \item If you are using BusyBox, adding vi supports only adds
+  \item If you are using BusyBox, adding \code{vi} support only adds
     20K. (built with shared libraries, using uClibc).
   \item You can select which exact features to compile in.
-  \item Users hardly realize that they are using a lightweight vi
+  \item Users hardly realize that they are using a lightweight \code{vi}
-  \item Tip: you can learn vi on the desktop, by running the vimtutor
+  \item Tip: you can learn \code{vi} on the desktop, by running the \code{vimtutor}
@@ -100,7 +100,7 @@
     \item \code{make allnoconfig}\\
       Unselects all options. Good to configure only what you need.
-  \item \code{make xconfig} (graphical, needs the libqt3-mt-dev package)\\
+  \item \code{make xconfig} (graphical, needs the \code{libqt3-mt-dev} package)\\
     or \code{make menuconfig} (text)\\
     Same configuration interfaces as the ones used by the Linux kernel
     (though older versions are used).
diff --git a/slides/sysdev-root-filesystem-device-files/sysdev-root-filesystem-device-files.tex b/slides/sysdev-root-filesystem-device-files/sysdev-root-filesystem-device-files.tex
index 08917e7..a32a120 100644
--- a/slides/sysdev-root-filesystem-device-files/sysdev-root-filesystem-device-files.tex
+++ b/slides/sysdev-root-filesystem-device-files/sysdev-root-filesystem-device-files.tex
@@ -91,7 +91,7 @@ close(fd);
   \frametitle{Creating device files}
     \item On a basic Linux system, the device files have to be created
-    manually using the mknod command
+    manually using the \code{mknod} command
     \item \code{mknod /dev/<device> [c|b] major minor}
     \item Needs root privileges
diff --git a/slides/sysdev-root-filesystem-virtual-fs/sysdev-root-filesystem-virtual-fs.tex b/slides/sysdev-root-filesystem-virtual-fs/sysdev-root-filesystem-virtual-fs.tex
index 8b464f8..a902d94 100644
--- a/slides/sysdev-root-filesystem-virtual-fs/sysdev-root-filesystem-virtual-fs.tex
+++ b/slides/sysdev-root-filesystem-virtual-fs/sysdev-root-filesystem-virtual-fs.tex
@@ -12,7 +12,7 @@
       about process management, memory management, etc.
   \item The \code{proc} filesystem is used by many standard userspace
-    applications, and they expect it to be mounted in /proc
+    applications, and they expect it to be mounted in \code{/proc}
   \item Applications such as \code{ps} or \code{top} would not work
     without the \code{proc} filesystem
   \item Command to mount \code{/proc}:\\


commit fd409694636d1a983731c0ef6bc4e922931d043d
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Thu Jun 21 14:59:18 2012 +0200

    onenand erase: reaches the end with no argument
    - No need to give the erase size

diff --git a/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex b/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
index f28c060..8a66ba4 100644
--- a/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
+++ b/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
@@ -64,8 +64,9 @@ board dependent. Nevertheless, during device development, it can be
 useful to define partitions at boot time, on the kernel command line.
 Enter the U-Boot shell and erase the NAND flash, from offset
-0x00280000, up to the end of the NAND flash (Erase size: 0x1FD80000
+0x00280000, up to the end of the NAND flash (tip: if you don't
+specify the number of bytes to erase, \code{onenand erase} will
+continue until it reaches the end).
 Using the \code{tftp} command, download and flash the kernel image at
 the correct location.


commit 3a59ce27a8eb3a005e974d25eb343ec354ada44a
Merge: 71bbb21 5027b59
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Thu Jun 21 14:46:40 2012 +0200

    Merge branch 'master' of git.free-electrons.com:training-materials


commit 71bbb21e8c4018c60208c1a904b782bf3578503a
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Wed Jun 20 15:18:16 2012 +0200

    Improve nand booting instructions

diff --git a/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex b/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex
index a1bd941..5d2d832 100644
--- a/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex
+++ b/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex
@@ -176,7 +176,8 @@ nand write 0x80000000 0x280000 0x400000
            (RAM addr)   (NAND addr) (size)
-Then, we should be able to boot the kernel from the NAND using:
+Power your board off and on, to clear RAM contents. We should now be able to load
+the kernel image from NAND and boot it using:
 nand read 0x80000000  0x280000    0x400000


commit 4ef1d4459049d969f1e3f62aa202852940a6dd14
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Wed Jun 20 14:38:56 2012 +0200

    Highlight the O in ttyO2 earlier

diff --git a/labs/sysdev-tinysystem/sysdev-tinysystem.tex b/labs/sysdev-tinysystem/sysdev-tinysystem.tex
index 821a2fd..fa3d106 100644
--- a/labs/sysdev-tinysystem/sysdev-tinysystem.tex
+++ b/labs/sysdev-tinysystem/sysdev-tinysystem.tex
@@ -76,7 +76,9 @@ First, boot the board to the U-Boot prompt. Before booting the kernel,
 we need to tell it that the root filesystem should be mounted over
 NFS, by setting some kernel parameters.
-Use the following U-Boot command to do so (in just 1 line):
+Use the following U-Boot command to do so, in just 1 line
+(Caution: in \code{ttyO2} below, it's the capital letter \code{O}, like in
+{\bf O}MAP and not the number zero):
@@ -85,9 +87,6 @@ setenv bootargs console=ttyO2,115200 root=/dev/nfs ip= \
-Caution: in \code{ttyO2} it's the capital letter \code{O} (like in
-{\bf O}MAP) and not the number zero.
 Of course, you need to adapt the IP addresses to your exact network
 setup. Save the environment variables (with \code{saveenv}).


Summary of changes:
 ...board-onenand-init-visible-to-board-code.patch} |    0
 .../{busybox-1.19.config => busybox-1.20.config}   |   31 ++--
 .../sysdev-block-filesystems.tex                   |    5 +-
 .../sysdev-flash-filesystems.tex                   |    5 +-
 .../sysdev-kernel-cross-compiling.tex              |    9 +-
 labs/sysdev-tinysystem/sysdev-tinysystem.tex       |   24 ++-
 labs/sysdev-toolchain/sysdev-toolchain.tex         |   34 ++--
 labs/sysdev-u-boot/sysdev-u-boot.tex               |  169 +++++---------------
 slides/sysdev-busybox/sysdev-busybox.tex           |    8 +-
 slides/sysdev-intro/sysdev-intro.tex               |    2 +-
 .../sysdev-linux-intro-configuration.tex           |    2 +-
 slides/sysdev-realtime/sysdev-realtime.tex         |    2 +-
 .../sysdev-root-filesystem-device-files.tex        |    2 +-
 .../sysdev-root-filesystem-virtual-fs.tex          |    2 +-
 14 files changed, 114 insertions(+), 181 deletions(-)
 rename lab-data/sysdev/kernel/{omap2-make-board-onenand-init-visible-to-board-code.patch => linux-3.2-omap2-make-board-onenand-init-visible-to-board-code.patch} (100%)
 rename lab-data/sysdev/tinysystem/data/{busybox-1.19.config => busybox-1.20.config} (98%)

More information about the training-materials-updates mailing list