[FE training-materials-updates] Buildroot lab: temporarily remove the igep experiments

[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=fbc27b03c821d80fe83f9a358acd9f2385326306

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

commit fbc27b03c821d80fe83f9a358acd9f2385326306
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Thu Nov 21 21:15:55 2013 +0100

    Buildroot lab: temporarily remove the igep experiments
    
    - Currently broken
    - Will keep the intructions in a separate branch
      to be merged later.
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


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

fbc27b03c821d80fe83f9a358acd9f2385326306
 labs/sysdev-buildroot/sysdev-buildroot.tex |   63 ----------------------------
 1 file changed, 63 deletions(-)

diff --git a/labs/sysdev-buildroot/sysdev-buildroot.tex b/labs/sysdev-buildroot/sysdev-buildroot.tex
index 5f20dcf..fcc0cd7 100644
--- a/labs/sysdev-buildroot/sysdev-buildroot.tex
+++ b/labs/sysdev-buildroot/sysdev-buildroot.tex
@@ -194,69 +194,6 @@ 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}
-  uncomment the line with \code{ttyS0}, and replace all the occurrences
-  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):
-\begin{verbatim}
-CONFIG_OMAP2_DSS=y
-CONFIG_FB_OMAP2=y
-#CONFIG_FB_CFB_FILLRECT=y
-#CONFIG_FB_CFB_COPYAREA=y
-#CONFIG_FB_CFB_IMAGEBLIT=y
-#CONFIG_PANEL_GENERIC_DPI=y
-CONFIG_DISPLAY_PANEL_DPI=y
-CONFIG_DISPLAY_CONNECTOR_DVI=y
-#CONFIG_PANEL_DVI=y
-##CONFIG_PANEL_PICODLP=y (if you use the TI Pico Projector)
-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_OMAP1=y
-CONFIG_USB_OHCI_HCD_OMAP3=y
-#CONFIG_USB_OHCI_LITTLE_ENDIAN=y
-#CONFIG_USB_OTG_UTILS=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}