[FE training-materials-updates] IGEP framebuffer instructions

[Michael Opdenacker]

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

On branch  : igep-framebuffer
Link       : http://git.free-electrons.com/training-materials/commit/?id=e4aee40f4e981e2a38d477ce0e2afd705b3cfe2c

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

commit e4aee40f4e981e2a38d477ce0e2afd705b3cfe2c
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Thu Nov 21 21:18:10 2013 +0100

    IGEP framebuffer instructions
    
    - Expected to work in 3.13... waiting
      Thanks to patches submitted in November
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


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

e4aee40f4e981e2a38d477ce0e2afd705b3cfe2c
 labs/sysdev-buildroot/sysdev-buildroot.tex |   54 ++++++++++++++++++++++++++++
 1 file changed, 54 insertions(+)

diff --git a/labs/sysdev-buildroot/sysdev-buildroot.tex b/labs/sysdev-buildroot/sysdev-buildroot.tex
index fcc0cd7..d966a05 100644
--- a/labs/sysdev-buildroot/sysdev-buildroot.tex
+++ b/labs/sysdev-buildroot/sysdev-buildroot.tex
@@ -194,6 +194,60 @@ df_fire
 ...
 \end{verbatim}
 
+\section{Tests on the IGEPv2 board}
+
+If you have graphical displays to connect your IGEPv2 board to (LCD
+display with DVI-D or HDMI input, TI Pico Projector...), and the
+corresponding cables (HDMI to DVI-D or HDMI to HDMI), you can test
+your root filesystem on the board.
+
+You can skip to the next section if you don't have a display.
+
+Here's what you can do:
+
+\begin{itemize}
+\item Continue to use the same kernel as in the previous labs
+\item Extract the tar file for the generated root filesystem in a
+\code{nfsroot} directory. Make your board boot on this directory. 
+\item In the root filesystem, you may need to edit \code{etc/inittab},
+  and add a new line similar to the one running a \code{getty} in
+  \code{ttyO2}, but on \code{tty0} instead (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
+(Currently broken but expect to work in 3.13)
+\begin{verbatim}
+CONFIG_OMAP2_DSS=y
+CONFIG_FB_OMAP2=y
+CONFIG_DISPLAY_PANEL_DPI=y
+CONFIG_DISPLAY_CONNECTOR_DVI=y
+CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
+CONFIG_LOGO=y
+CONFIG_USB_EHCI_HCD=y
+CONFIG_USB_EHCI_TT_NEWSCHED=y
+CONFIG_USB_EHCI_HCD_OMAP=y
+CONFIG_USB_OHCI_HCD=y
+CONFIG_USB_OHCI_HCD_OMAP3=y
+\end{verbatim}
+
+Note that the USB settings are only needed if you want to connect a USB
+mouse and keyboard (behind a USB 2.0 hub), to interact with the
+framebuffer console and with the DirectFB programs.
+
+To make your life simpler, we also included a complete Linux
+configuration file in the \code{data} folder in the lab directory.
+
+\item Add the following settings to the boot arguments:
+  \begin{itemize}
+  \item \code{console=tty0}\\(allows you to have both a framebuffer
+    and serial console)
+  \item \code{vram=12M}\\(video RAM)
+  \item \code{omapfb.mode=dvi:640x480MR-16 at 60}\\(example for the
+    Pico Projector. You may first try to do without this parameter,
+    and then specify a mode that your monitor supports).
+  \end{itemize}
+\end{itemize}
+
 \section{Going further}
 
 \begin{itemize}