[FE training-materials-updates] Tinysystem lab: minor font improvement

Michael Opdenacker michael.opdenacker at free-electrons.com
Thu Nov 21 10:33:21 CET 2013

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

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


commit 728d37667ffc95a126858084258c4386c783289d
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Thu Nov 21 10:32:41 2013 +0100

    Tinysystem lab: minor font improvement
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


 labs/sysdev-buildroot/sysdev-buildroot.tex   |   23 +++++++++++++----------
 labs/sysdev-tinysystem/sysdev-tinysystem.tex |    2 +-
 2 files changed, 14 insertions(+), 11 deletions(-)

diff --git a/labs/sysdev-buildroot/sysdev-buildroot.tex b/labs/sysdev-buildroot/sysdev-buildroot.tex
index 6cfde87..5f20dcf 100644
--- a/labs/sysdev-buildroot/sysdev-buildroot.tex
+++ b/labs/sysdev-buildroot/sysdev-buildroot.tex
@@ -211,29 +211,32 @@ Here's what you can do:
 \code{nfsroot} directory. Make your board boot on this directory. 
 \item In the root filesystem, you may need to edit \code{etc/inittab}
   uncomment the line with \code{ttyS0}, and replace all the occurrences
-  of \code{ttyS0} by \code{ttyO2}
+  of \code{tty1} by \code{tty0} (Caution: this is a {\em zero} character
+  this time.
 \item Connect your board to an DVI-D or HDMI display
 \item Rebuild your kernel with the below configuration settings
 (successfully tested with Linux 3.2):
-CONFIG_PANEL_PICODLP=y (if you use the TI Pico Projector)
+##CONFIG_PANEL_PICODLP=y (if you use the TI Pico Projector)
 Note that the USB settings are only needed if you want to connect a USB
diff --git a/labs/sysdev-tinysystem/sysdev-tinysystem.tex b/labs/sysdev-tinysystem/sysdev-tinysystem.tex
index 9582f66..53d031c 100644
--- a/labs/sysdev-tinysystem/sysdev-tinysystem.tex
+++ b/labs/sysdev-tinysystem/sysdev-tinysystem.tex
@@ -204,7 +204,7 @@ Take the \code{hello.c} program supplied in the lab \code{data}
 directory. Cross-compile it for ARM, dynamically-linked with the
 libraries, and run it on the target.
-You will first encounter a not found error caused by the absence of
+You will first encounter a \code{not found} error caused by the absence of
 the \code{ld-uClibc.so.0} executable, which is the dynamic linker
 required to execute any program compiled with shared libraries. Using
 the find command (see examples in your command memento sheet), look

More information about the training-materials-updates mailing list