[FE training-materials-updates] Embedded Linux: remove slides about commercial toolsets

Michael Opdenacker michael.opdenacker at free-electrons.com
Thu Nov 5 19:16:08 CET 2015


Repository : git://git.free-electrons.com/training-materials.git
On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=88a6e2b37a37d27708121df03d0ff70567fd53ca

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

commit 88a6e2b37a37d27708121df03d0ff70567fd53ca
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Thu Nov 5 19:16:08 2015 +0100

    Embedded Linux: remove slides about commercial toolsets
    
    - Not properly covered, not much added value anyway
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


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

88a6e2b37a37d27708121df03d0ff70567fd53ca
 .../sysdev-embedded-linux.tex                      | 72 ----------------------
 1 file changed, 72 deletions(-)

diff --git a/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex b/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex
index fdbf795..f03b20e 100644
--- a/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex
+++ b/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex
@@ -15,7 +15,6 @@
     \item Web browsers
     \end{itemize}
   \item System building
-  \item Commercial tool sets and distributions
   \end{itemize}
 \end{frame}
 
@@ -1519,74 +1518,3 @@ $(eval $(autotools-package))
   \end{itemize}
 }
 
-\subsection{Commercial embedded Linux solutions}
-
-\begin{frame}
-  \frametitle{Commercial embedded Linux solutions}
-  Caution: {\em commercial} doesn't mean {\em proprietary!}
-  \begin{itemize}
-  \item Vendors play fair with the GPL and do make their source code
-    available to their users, and most of the time, eventually to the
-    community.
-    \begin{itemize}
-    \item As long as they distribute the sources to their users, the
-      GPL doesn't require vendors to share their sources with any
-      third party.
-    \end{itemize}
-  \item Graphical toolkits developed by the vendors are usually
-    proprietary, trying to make it easier to create and embedded Linux
-    systems.
-  \item Major players: Wind River, Montavista, TimeSys
-  \end{itemize}
-\end{frame}
-
-\begin{frame}
-  \frametitle{Commercial solution strengths}
-  \fontsize{10}{10}\selectfont
-  \begin{columns}
-    \column{0.5\textwidth}
-    \begin{itemize}
-    \item Technical advantages
-      \begin{itemize}
-      \item Well tested and supported kernel and tool versions
-      \item Often supporting patches not supported by the
-        mainline kernel yet (example: real-time patches)
-      \end{itemize}
-    \item Complete development tool sets: kernels, toolchains,
-      utilities, binaries for impressive lists of target platforms
-    \item Integrated utilities for automatic kernel image, initramfs
-      and filesystem generation.
-    \end{itemize}
-    \column{0.5\textwidth}
-    \begin{itemize}
-    \item Graphical developments tools
-    \item Development tools available on multiple platforms: GNU /
-      Linux, Solaris, Windows...
-    \item Support services
-      \begin{itemize}
-      \item Useful if you don't have your own support resources
-      \item Long term support commitment, even for versions considered
-        as obsolete by the community, but not by your users!
-      \end{itemize}
-    \end{itemize}
-  \end{columns}
-\end{frame}
-
-\begin{frame}
-  \frametitle{Commercial or community solutions?}
-  {\bf Commercial distributions and tool sets}
-  \begin{itemize}
-  \item Best if you don't have your own support resources and have a
-    sufficient budget
-  \item Help focusing on your primary job: making an embedded device.
-  \item You can even subcontract driver development to the vendor
-  \end{itemize}
-  {\bf Community distributions and tools}
-  \begin{itemize}
-  \item Best if you are on a tight budget
-  \item Best if you are willing to build your own embedded Linux
-    expertise, investigate issues by yourselves, and train your own
-    support resources.
-  \end{itemize}
-  In any case, your products are based on Free Software!
-\end{frame}




More information about the training-materials-updates mailing list