First draft of doc copied from standard profile

-updated rel-info
-updated UG
-added new chapterdoc for RT: Real-Time in Enea Linux

Change-Id: If8cec0e29d1d6aa4a09507881d815af13dd68ee2
Signed-off-by: Sona Sarmadi <sona.sarmadi@enea.com>

12 files changed, 1885 insertions, 0 deletions

diff --git a/doc/book-enea-linux-release-info/doc/about_release.xml b/doc/book-enea-linux-release-info/doc/about_release.xml
new file mode 100644
index 0000000..cb75bc1
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/about_release.xml
@@ -0,0 +1,235 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="relinfo-about-release">
+  <title>About This Release</title>
+
+  <para>This release of Enea Linux <xi:include href="eltf_params_updated.xml"
+  xmlns:xi="http://www.w3.org/2001/XInclude"
+  xpointer="element(EneaLinux_REL_VER/1)" /> provides a publicly available
+  Enea Linux distribution for a selected set of targets. This release is
+  generated from the Yocto Project <xi:include href="eltf_params_updated.xml"
+  xmlns:xi="http://www.w3.org/2001/XInclude"
+  xpointer="element(Yocto_VER/1)" /> distribution using the branch <xi:include
+  href="eltf_params_updated.xml" xmlns:xi="http://www.w3.org/2001/XInclude"
+  xpointer="element(Yocto_NAME/1)" />.<remark>INFO <emphasis
+  role="bold">eltf_params_updated.xml</emphasis> contains many parameters in
+  the book, also in the open source books, and MUST be created FROM <emphasis
+  role="bold">eltf_params_template.xml</emphasis>. </remark></para>
+
+  <para><remark>The parameters are automatically used in the books, via
+  xi:include statements, similar to how parameters from pardoc-distro.xml are
+  included in the book. Read the file <emphasis
+  role="bold">eltf_params_updated_template_how_to_use.txt</emphasis> for
+  important details about formats and how to do! The idea is that ELTF will
+  auto-create/update it.</remark></para>
+
+  <section id="relinfo-provided-contents">
+    <title>Provided Contents</title>
+
+    <para>The current release contains documentation, prebuilt kernels and
+    images, a bootloader and an SDK. The directories structure is detailed
+    below:</para>
+
+    <programlisting>-- Documentation/
+   /* Enea Linux 8 documentation */
+   -- intel-corei7-64/
+        /* artifacts for the reference machine */
+             -- deb/
+                /* deb packages */
+             -- images/
+                -- enea-image-rt
+                   /* precompiled artifacts for the platform release image */
+                    -- various artifacts (rootfs, kernel, config, dtb etc.)
+                -- enea-image-rt-sdk
+                   /* precompiled artifacts for the development process. The image
+                      contains userspace tools and kernel configurations necessary
+                      for developing, debugging and profiling applications and \
+                      kernel modules */
+                    -- various artifacts
+             -- sdk
+                /* SDK related artifacts including SDK installer and manifests  */
+                      /* self-extracting archive installing cross-compilation
+                      toolchain for the platform */
+                   -- x86_64-buildtools-nativesdk-standalone-8.0.sh
+                      /* self-extracting archive installing additional tools
+                         for the host machine */</programlisting>
+
+    <para>The following set of artifacts is available:</para>
+
+    <programlisting>-- Image
+   /* kernel image */
+-- Image-target.bin
+   /* kernel image, same as above */
+-- Image-target.dtb
+   /* the device tree blob */
+-- config-target.config
+   /* kernel configuration file */
+-- image-name-target.ext3
+   /* compressed EXT3 image of the rootfs */
+-- image-name-target.tar.bz2
+   /* tar archive of the image */
+-- modules-&lt;target&gt;.tgz
+   /* external kernel modules */</programlisting>
+  </section>
+
+  <section id="relinfo-supported-host-environment">
+    <title>Supported Host Environment</title>
+
+    <para>The following environments have been validated as host environments
+    for this release of Enea Linux: <emphasis role="bold">Ubuntu 16.04 LTS,
+    64-bit</emphasis>.</para>
+
+    <para><remark>INFO Below is a complete section with ID
+    "eltf-target-tables-section" included from elft_params_updated.xml. It
+    contains a variable number of target tables and the section title should
+    be "Supported Targets with Parameters". It has have a short sentence about
+    what it is in the beginning. The subtitles shall have the directory name
+    of the target in the manifest.</remark></para>
+  </section>
+
+  <xi:include href="eltf_params_updated.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude"
+              xpointer="element(eltf-target-tables-section)" />
+
+  <section id="relinfo-packages">
+    <title>Provided Packages</title>
+
+    <para><informaltable>
+        <tgroup cols="2">
+          <colspec align="left" colname="c1" colwidth="3*" />
+
+          <colspec align="left" colname="c2" colwidth="6*" />
+
+          <thead valign="bottom">
+            <row>
+              <entry>Type of Packages</entry>
+
+              <entry>Reference</entry>
+            </row>
+          </thead>
+
+          <tbody>
+            <row>
+              <entry>Packages in Enea Linux</entry>
+
+              <entry><para>See the <olink
+              targetdoc="book_enea_linux_open_source_rt"
+              targetptr="book_enea_linux_open_source_rt"><trademark
+              class="registered">Enea</trademark> Linux Open Source
+              Report</olink></para></entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </informaltable></para>
+  </section>
+
+  <section id="relinfo-provided-sdk">
+    <title>Provided Toolchains (SDK)</title>
+
+    <para>The SDK contains toolchains supporting cross-compilation of
+    applications for the targets on an aarch64 host. For information on how to
+    build and install a toolchain, see the chapter <olink
+    targetdoc="book_enea_linux_user_guide_rt"
+    targetptr="using_enealinux">Using Enea Linux, in the <xi:include
+    href="../../s_docbuild/olinkdb/pardoc-names.xml"
+    xmlns:xi="http://www.w3.org/2001/XInclude"
+    xpointer="element(book_enea_linux_user_guide_standard/1)" /></olink>.</para>
+  </section>
+
+  <section id="relinfo-documentation">
+    <title>Provided Documentation</title>
+
+    <para>The following Enea Linux manuals are available:</para>
+
+    <itemizedlist spacing="compact">
+      <listitem>
+        <para><trademark class="registered">Enea</trademark> Linux Release
+        Information (this document)</para>
+      </listitem>
+
+      <listitem>
+        <para><olink targetdoc="book_enea_linux_user_guide_rt"
+        targetptr="book_enea_linux_user_guide_rt"><trademark
+        class="registered">Enea</trademark> Linux User's Guide</olink></para>
+      </listitem>
+
+      <listitem>
+        <para><olink targetdoc="book_enea_linux_open_source_rt"
+        targetptr="book_enea_linux_open_source_rt"><trademark
+        class="registered">Enea</trademark> Linux Open Source
+        Report</olink></para>
+      </listitem>
+
+      <listitem>
+        <para><trademark class="registered">Enea</trademark> Linux Test
+        Report</para>
+      </listitem>
+
+      <listitem>
+        <para><trademark class="registered">Enea</trademark> Linux Security
+        Report</para>
+      </listitem>
+
+      <listitem>
+        <para><trademark class="registered">Enea</trademark><ulink
+        url="http://linuxrealtime.org"> Linux Real-Time Guide</ulink></para>
+      </listitem>
+    </itemizedlist>
+  </section>
+
+  <section condition="hidden" id="relinfo-provided-other">
+    <title>Other Provided Functionality</title>
+
+    <para>The functionality in a distribution depends on included packages in
+    the default image. In addition to the supported features, the following
+    functionality is also available, among other:<remark>INFO: This section
+    might be hidden by setting condition hidden on the section, MANUALLY in
+    this file</remark></para>
+
+    <itemizedlist spacing="compact">
+      <listitem>
+        <para>APT Package Management</para>
+      </listitem>
+
+      <listitem>
+        <para>Eclipse ADT (excl. QEMU) and plug-ins for application
+        development: LTTng, Perf, LatencyTOP, PowerTOP, SystemTap</para>
+      </listitem>
+    </itemizedlist>
+  </section>
+
+  <section id="relinfo-security-fixes">
+    <title>Security Fixes</title>
+
+    <para>See the <ulink
+    url="https://www.enea.com/products/security/security-updates/">List of
+    CVEs addressed in Enea Linux</ulink> for details.</para>
+  </section>
+
+  <section condition="hidden" id="relinfo-excluded">
+    <title>Intentional Limitations</title>
+
+    <para>The following functionality supported in other Enea Linux releases
+    has been excluded in this release:<remark>INFO: This section might be
+    hidden by setting condition hidden on the section, MANUALLY in this
+    file.</remark><itemizedlist spacing="compact">
+        <listitem>
+          <para>Eclipse plug-ins for image creation (HOB)</para>
+        </listitem>
+
+        <listitem>
+          <para>Networking features: DPDK vSwitch, DPDK</para>
+        </listitem>
+
+        <listitem>
+          <para>Real-time features: Fully Preemptible Kernel (FPK) from the
+          PREEMPT_RT patch</para>
+        </listitem>
+
+        <listitem>
+          <para>Memory features: NUMA</para>
+        </listitem>
+      </itemizedlist></para>
+  </section>
+</chapter>
diff --git a/doc/book-enea-linux-release-info/doc/book.xml b/doc/book-enea-linux-release-info/doc/book.xml
new file mode 100644
index 0000000..13aff10
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/book.xml
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
+<!ENTITY % local.common.attrib "xml:base CDATA #IMPLIED">
+]>
+<book id="book_enea_linux_release_info_rt">
+  <title><trademark class="registered">Enea</trademark> Linux Release Information</title>
+  <subtitle>Release Version
+         <xi:include href="eltf_params_updated.xml" xpointer="element(EneaLinux_REL_VER/1)"
+         xmlns:xi="http://www.w3.org/2001/XInclude" /></subtitle>
+  <!-- OLINKDBPATH_USED_BY_XMLMIND ../../s_docbuild/olinkdb  -->
+  <xi:include href="../../s_docbuild/template/docsrc_common/bookinfo_userdoc.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+  <xi:include href="about_release.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+  <!--
+  <xi:include href="prerequisites.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+  <xi:include href="getting_enea_linux.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+  <xi:include href="build_boot_generated.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+  -->
+  <xi:include href="main_changes.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+  <xi:include href="known_bugs_and_limitations.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+  <xi:include href="../../s_docbuild/template/docsrc_common/contacting_enea_enea_linux.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</book>
diff --git a/doc/book-enea-linux-release-info/doc/build_boot_template.xml b/doc/book-enea-linux-release-info/doc/build_boot_template.xml
new file mode 100644
index 0000000..e39dd81
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/build_boot_template.xml
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="relinfo-build-boot">
+  <title>Target Specific Instructions</title>
+
+  <para>If the source has been fetched (<xref
+  linkend="relinfo-getting-source" />), there will be a target specific README
+  file containing the build and boot instructions. To make it easier for the
+  reader, the contents of this file(s) have been extracted into the following
+  sections.</para>
+
+  <note>
+    <para>The build process duration may vary and be longer than expected in
+    some cases, depending on the individual build resources and parameters of
+    each target/machine supported in this release.</para>
+  </note>
+
+  <para><remark>NOTE: Only EDIT THE TEMPLATE build_boot_template.xml file here
+  and also only edit the manifest template ".README" (name starting by a dot)!
+  A new build_boot_generated.xml file is created from the template and
+  sections are added below automatically from the README files for each target
+  when building the book! Only in the template file you see a line below with
+  SCRIPT_...._HERE and the text telling that this is a template
+  file.</remark></para>
+
+  <para>SCRIPT_INCLUDES_BUILD_BOOT_SECTIONS_HERE</para>
+
+  <para><emphasis role="bold">This is a template file which you can edit. When
+  the book is built, a new XML chapter file is created where the above part of
+  this file is copied to the new XML file and all from the line above is
+  replaced automatically by build and boot sections from the README
+  files!</emphasis></para>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-linux-release-info/doc/eltf_params_template.xml b/doc/book-enea-linux-release-info/doc/eltf_params_template.xml
new file mode 100644
index 0000000..278ad71
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/eltf_params_template.xml
@@ -0,0 +1,151 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<section id="eltf_created_params">
+  <title>File with Parameters in the Book Auto-updated by ELFT</title>
+
+  <note>
+    <para>See the <emphasis
+    role="bold">eltf_params_updated_template_howto_use.txt</emphasis> text
+    file for description of how to create the final <emphasis
+    role="bold">eltf_params_updated.xml</emphasis> from this template and for
+    all <emphasis role="bold">REQUIREMENTS</emphasis>. Use the command
+    "<emphasis role="bold">make eltf</emphasis>" to extract a full list of all
+    ELTF variables, which always begins with ELTF_ and don't only rely on the
+    howto text file list! The plan is that ELTF will auto-update this when
+    needed.</para>
+  </note>
+
+  <section id="host_prereq">
+    <title>Common Parameters</title>
+
+    <bridgehead>A programlisting, ID
+    "eltf-prereq-apt-get-commands-host"</bridgehead>
+
+    <para id="eltf-prereq-apt-get-commands-host"><programlisting>ELTF_PL_HOST_PREREQ</programlisting></para>
+
+    <bridgehead>A programlisting, ID
+    "eltf-getting-repo-install-command"</bridgehead>
+
+    <para id="eltf-getting-repo-install-command"><programlisting>ELTF_PL_GET_REPO</programlisting></para>
+
+    <bridgehead>Several phrase elements, various IDs. Ensure EL_REL_VER is
+    correct also compared to the "previous" REL VER in pardoc-distro.xml
+    "prev_baseline".</bridgehead>
+
+    <para id="EneaLinux_REL_VER"><phrase>ELTF_EL_REL_VER</phrase></para>
+
+    <para id="Yocto_VER"><phrase>ELTF_YOCTO_VER</phrase></para>
+
+    <para id="Yocto_NAME"><phrase>ELTF_YOCTO_NAME</phrase></para>
+
+    <para id="ULINK_YOCTO_PROJECT_DOWNLOAD"><ulink
+    url="ELTF_YOCTO_PROJ_DOWNLOAD_URL">ELTF_YOCTO_PROJ_DOWNLOAD_TXTURL</ulink></para>
+
+    <para id="ULINK_ENEA_LINUX_URL"><ulink
+    url="ELTF_EL_DOWNLOAD_URL">ELTF_EL_DOWNLOAD_TXTURL</ulink></para>
+
+    <bridgehead>A programlisting, ID "eltf-repo-cloning-enea-linux". Use
+    $MACHINE/default.xml as parameter, where MACHINE is one of the target
+    directory names in the manifest.</bridgehead>
+
+    <para id="eltf-repo-cloning-enea-linux"><programlisting>ELTF_PL_CLONE_W_REPO</programlisting></para>
+
+    <bridgehead>A table with ONE row, only the row with ID
+    "eltf-eclipse-version-row" is included in the book. MANUALLY BOTH in the
+    template.xml and in the updated.xml, set condition hidden on the
+    &lt;row&gt;, if eclipse is not in the release.</bridgehead>
+
+    <informaltable>
+      <tgroup cols="1">
+        <tbody>
+          <row id="eltf-eclipse-version-row">
+            <entry>Eclipse version ELTF_ECLIPSE_VERSION plus command line
+            development tools are included in this Enea Linux release.</entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </informaltable>
+
+    <bridgehead>Below is one big section with title "Supported Targets with
+    Parameters". The entire section is included completely in the book via ID
+    "eltf-target-tables-section" and shall be LAST in the template. The
+    template contains ONE target subsection. COPY/APPEND it, if multiple
+    targets exist in the release and optionally add rows with additional
+    target parameters in each target subsection table.</bridgehead>
+  </section>
+
+  <section id="eltf-target-tables-section">
+    <title>Supported Targets with Parameters</title>
+
+    <para>The tables below describes the target(s) supported in this Enea
+    Linux release.</para>
+
+    <section id="eltf-target-table-ELTF_T_MANIFEST_DIR">
+      <title>MACHINE ELTF_T_MANIFEST_DIR - Information</title>
+
+      <para><informaltable>
+          <tgroup cols="2">
+            <colspec colwidth="6*" />
+
+            <colspec colwidth="9*" />
+
+            <tbody>
+              <row>
+                <entry>Target official name</entry>
+
+                <entry>ELTF_T_NAME</entry>
+              </row>
+
+              <row>
+                <entry>Architecture and Description</entry>
+
+                <entry>ELTF_T_ARC_DESC</entry>
+              </row>
+
+              <row>
+                <entry>Link to target datasheet</entry>
+
+                <entry>See <ulink
+                url="ELTF_T_DS_URL">ELTF_T_DS_TXTURL</ulink></entry>
+              </row>
+
+              <row>
+                <entry>Poky version</entry>
+
+                <entry>ELTF_T_POKY_VER</entry>
+              </row>
+
+              <row>
+                <entry>GCC version</entry>
+
+                <entry>ELTF_T_GCC_VER</entry>
+              </row>
+
+              <row>
+                <entry>Linux Kernel Version</entry>
+
+                <entry>ELTF_T_KERN_VER</entry>
+              </row>
+
+              <row>
+                <entry>Supported Drivers</entry>
+
+                <entry>ELTF_T_DRIVERS</entry>
+              </row>
+
+              <row>
+                <entry>Enea rpm folder for downloading RPM packages for this
+                target</entry>
+
+                <entry><ulink
+                url="ELTF_T_EL_RPM_URL">ELTF_T_EL_RPM_TXTURL</ulink></entry>
+              </row>
+            </tbody>
+          </tgroup>
+        </informaltable></para>
+    </section>
+
+    <!-- ELTFADD_MORE_TARGET_SECTIONS_BELOW_IF_NEEDED -->
+  </section>
+</section>
\ No newline at end of file
diff --git a/doc/book-enea-linux-release-info/doc/eltf_params_updated.xml b/doc/book-enea-linux-release-info/doc/eltf_params_updated.xml
new file mode 100644
index 0000000..dfcee4a
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/eltf_params_updated.xml
@@ -0,0 +1,282 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<section id="eltf_created_params">
+  <title>File with Parameters in the Book Auto-updated by ELFT</title>
+
+  <note>
+    <para>See the <emphasis
+    role="bold">eltf_params_updated_template_howto_use.txt</emphasis> text
+    file for description of how to create the final <emphasis
+    role="bold">eltf_params_updated.xml</emphasis> from this template and for
+    all <emphasis role="bold">REQUIREMENTS</emphasis>. Use the command
+    "<emphasis role="bold">make eltf</emphasis>" to extract a full list of all
+    ELTF variables, which always begins with ELTF_ and don't only rely on the
+    howto text file list! The plan is that ELTF will auto-update this when
+    needed.</para>
+  </note>
+
+  <section id="host_prereq">
+    <title>Common Parameters</title>
+
+    <bridgehead>A programlisting, ID
+    "eltf-prereq-apt-get-commands-host"</bridgehead>
+
+    <para id="eltf-prereq-apt-get-commands-host"><programlisting># Host Ubuntu 16.04.2 LTS 64bit
+sudo apt-get -y update
+sudo apt-get -y install sed wget subversion git-core coreutils unzip texi2html \
+   texinfo libsdl1.2-dev docbook-utils fop gawk python-pysqlite2 diffstat \
+   make gcc build-essential xsltproc g++ desktop-file-utils chrpath  \
+   libgl1-mesa-dev libglu1-mesa-dev autoconf automake groff libtool xterm \
+   libxml-parser-perl</programlisting></para>
+
+    <bridgehead>A programlisting, ID
+    "eltf-getting-repo-install-command"</bridgehead>
+
+    <para id="eltf-getting-repo-install-command"><programlisting>mkdir -p ~/bin
+curl https://storage.googleapis.com/git-repo-downloads/repo &gt; ~/bin/repo
+chmod a+x ~/bin/repo
+export PATH=~/bin:$PATH</programlisting></para>
+
+    <bridgehead>Several phrase elements, various IDs. Ensure EL_REL_VER is
+    correct also compared to the "previous" REL VER in pardoc-distro.xml
+    "prev_baseline".</bridgehead>
+
+    <para id="EneaLinux_REL_VER"><phrase>8</phrase></para>
+
+    <para id="Yocto_VER"><phrase>2.5</phrase></para>
+
+    <para id="Yocto_NAME"><phrase>sumo</phrase></para>
+
+    <para id="ULINK_YOCTO_PROJECT_DOWNLOAD"><ulink
+    url="http://www.yoctoproject.org/downloads">http://www.yoctoproject.org/downloads</ulink></para>
+
+    <para id="ULINK_ENEA_LINUX_URL"><ulink
+    url="http://linux.enea.com/EneaLinux7.0">http://linux.enea.com/EneaLinux8.0</ulink></para>
+
+    <bridgehead>A programlisting, ID "eltf-repo-cloning-enea-linux". Use
+    $MACHINE/default.xml as parameter, where MACHINE is one of the target
+    directory names in the manifest.</bridgehead>
+
+    <para id="eltf-repo-cloning-enea-linux"><programlisting>mkdir enea-linux
+cd enea-linux
+repo init -u git@git.enea.com:linux/manifests/el_manifests-rt.git \
+    -b refs/tags/Enea_Linux_8.0 -m $MACHINE/default.xml
+repo sync</programlisting></para>
+
+    <bridgehead>A table with ONE row, only the row with ID
+    "eltf-eclipse-version-row" is included in the book. MANUALLY in book, set
+    condition hidden if eclipse is not in the release.</bridgehead>
+
+    <informaltable>
+      <tgroup cols="1">
+        <tbody>
+          <row id="eltf-eclipse-version-row">
+            <entry>Eclipse version 4.7 (Oxygen) plus command line development
+            tools are included in this Enea Linux release.</entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </informaltable>
+
+    <bridgehead>Below is one big section with title "Supported Targets with
+    Parameters". The entire section is included completely in the book via ID
+    "eltf-target-tables-section" and shall be LAST in the template. The
+    template contains ONE target subsection. COPY/APPEND it, if multiple
+    targets exist in the release and optionally add rows with additional
+    target parameters in each target subsection table.</bridgehead>
+  </section>
+
+  <section id="eltf-target-tables-section">
+    <title>Supported Reference Boards with Parameters</title>
+
+    <para>The table(s) below describes the target(s) supported in this Enea
+    Linux release.</para>
+
+    <table>
+      <title>MACHINE Information Intel Xeon D</title>
+
+      <tgroup cols="2">
+        <colspec align="center" />
+
+        <thead>
+          <row>
+            <entry align="center">Component</entry>
+
+            <entry align="center">Description</entry>
+          </row>
+        </thead>
+
+        <tbody>
+          <row>
+            <entry align="left">Target official name</entry>
+
+            <entry>Intel Xeon D</entry>
+          </row>
+
+          <row>
+            <entry align="left">Architecture and Description</entry>
+
+            <entry>x86-64</entry>
+          </row>
+
+          <row>
+            <entry align="left">Link to target datasheet</entry>
+
+            <entry><ulink
+            url="https://www.intel.com/content/www/us/en/processors/xeon/xeon-d-1500-datasheet-vol-1.html">Intel
+            Xeon D datasheet</ulink></entry>
+          </row>
+
+          <row>
+            <entry align="left">Poky version</entry>
+
+            <entry>Git-commit-id: TBD</entry>
+          </row>
+
+          <row>
+            <entry align="left">GCC version</entry>
+
+            <entry>7.3</entry>
+          </row>
+
+          <row>
+            <entry align="left">Linux Kernel Version</entry>
+
+            <entry>4.14</entry>
+          </row>
+
+          <row condition="hidden">
+            <entry align="left">Supported Drivers</entry>
+
+            <entry>Ethernet, RTC, UART</entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
+
+    <table>
+      <title>MACHINE Information Intel Atom C3000</title>
+
+      <tgroup cols="2">
+        <colspec align="center" />
+
+        <thead>
+          <row>
+            <entry align="center">Component</entry>
+
+            <entry align="center">Description</entry>
+          </row>
+        </thead>
+
+        <tbody>
+          <row>
+            <entry align="left">Target official name</entry>
+
+            <entry>Intel Atom C3000</entry>
+          </row>
+
+          <row>
+            <entry align="left">Architecture and Description</entry>
+
+            <entry>x86-64</entry>
+          </row>
+
+          <row>
+            <entry align="left">Link to target datasheet</entry>
+
+            <entry><ulink
+            url="https://www.intel.com/content/www/us/en/products/docs/processors/atom/c-series/c3000-family-datasheet.html">Intel
+            Atom datasheet</ulink></entry>
+          </row>
+
+          <row>
+            <entry align="left">Poky version</entry>
+
+            <entry>Git-commit-id: TBD</entry>
+          </row>
+
+          <row>
+            <entry align="left">GCC version</entry>
+
+            <entry>7.3</entry>
+          </row>
+
+          <row>
+            <entry align="left">Linux Kernel Version</entry>
+
+            <entry>4.14</entry>
+          </row>
+
+          <row condition="hidden">
+            <entry align="left">Supported Drivers</entry>
+
+            <entry>Ethernet, RTC, UART</entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
+
+    <table>
+      <title>MACHINE Information Intel NUC Kaby Lake</title>
+
+      <tgroup cols="2">
+        <colspec align="center" />
+
+        <thead>
+          <row>
+            <entry align="center">Component</entry>
+
+            <entry align="center">Description</entry>
+          </row>
+        </thead>
+
+        <tbody>
+          <row>
+            <entry align="left">Target official name</entry>
+
+            <entry>Intel NUC Kaby Lake</entry>
+          </row>
+
+          <row>
+            <entry align="left">Architecture and Description</entry>
+
+            <entry>x86-64</entry>
+          </row>
+
+          <row>
+            <entry align="left">Link to target datasheet</entry>
+
+            <entry><ulink
+            url="https://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/nuc-kit-nuc7i5bnh-nuc7i5bnk-brief.pdf">Intel
+            NUC Kaby Lake datasheet</ulink></entry>
+          </row>
+
+          <row>
+            <entry align="left">Poky version</entry>
+
+            <entry>Git-commit-id: TBD</entry>
+          </row>
+
+          <row>
+            <entry align="left">GCC version</entry>
+
+            <entry>7.3</entry>
+          </row>
+
+          <row>
+            <entry align="left">Linux Kernel Version</entry>
+
+            <entry>4.14</entry>
+          </row>
+
+          <row condition="hidden">
+            <entry align="left">Supported Drivers</entry>
+
+            <entry>Ethernet, RTC, UART</entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
+  </section>
+</section>
diff --git a/doc/book-enea-linux-release-info/doc/eltf_params_updated_template_how_to_use.txt b/doc/book-enea-linux-release-info/doc/eltf_params_updated_template_how_to_use.txt
new file mode 100644
index 0000000..6e1358f
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/eltf_params_updated_template_how_to_use.txt
@@ -0,0 +1,320 @@
+eltf_params_template_updated_howto_use.txt
+
+This is a way to collect all parameters for an Enea Linux release
+in one parameter file, easy to automatically update by ELTF regularly.
+
+NOTE: Both the release info AND the open source books use parameters from
+      here, but the XML file is inside the release info book directory.
+
+NOTE: The manifest_conf.mk, or overridden by the environment variable
+      MANIFESTHASH, contains the full tag (or hashvalue) for downloading
+      the manifest when the books are built. The list of target
+      directories are fetched from the manifest into the book.
+      The eltf_params_updates.xml can all the time contain
+      the final next complete tag e.g. refs/tags/EL6 or similar
+      in the ELTF_PL_CLONE_W_REPO parameter command lines.
+
+The ordinary book XML files use xi:include statements to include elements
+from this parameter file. The book XML files can thus be manually edited.
+Before editing, you must run "make init".
+Any other text in the template or updated.xml file, outside the parts that
+are included in the book, are not used but still all must be correct
+DocBook XML files.
+
+ELTF work:
+ template => ELTF replaces ALL ELTF_xxx variables => updated XML file
+    => push to git only if changed
+
+
+eltf_params_template.xml  (in git)
+   File used by ELTF to autocreate/update the real parameter
+   file eltf_params_updated.xml.
+
+eltf_params_updated.xml  (in git)
+   Real parameter file where ELTF has replaced all ELTF_xx variables with
+   strings, in several cases with multiline strings.
+   No spaces or linefeed allowed in beginning or end of the variable values!
+
+
+xi:include: Each parameter is xi:include'ed in various book files, using
+   the IDs existing in the parameter files.
+   In most cases the 1:st element inside an element with an ID is included
+   using a format like eltf-prereq-apt-get-commands-host/1.
+   In very few cases the element with the ID is included in the book, one
+   example is the target section which has an ID, but which contains
+   multiple subsections, one per target.
+   All IDs in a book must be unique.
+
+DocBook XML: All XML files must be correct DocBook XML files.
+
+Do NOT edit/save the real *updated.xml file with XMLmind to avoid changes
+   not done by ELTF. But it is OK to open the real file in XMLmind to
+   check that the format is correct.
+
+ELTF should autocreate a temporary "real" file but only replace
+   and push the eltf_params_updated.xml if it is changed.
+
+
+make eltf
+   This lists all ELTF_xxx variables and some rules how to treat them
+
+DocBook Format: All elements - rules:
+   Several strict generic XML rules apply for all strings:
+    1. No TABs allowed or any other control chr than "linefeed"
+    2. Only 7-bit ASCII
+    3. Any < > & must be converted to &lt; &gt; and &amp;
+       Similar for any other non-7-bit-ASCII but avoid those!
+    4. No leading spaces or linefeeds when replacing the ELTF_* variable
+    5. No trailing spaces or linefeeds when replacing the ELTF_* variable
+    6. Note: Keep existing spaces before/efter ELTF_* in a few cases.
+
+DocBook Format: <programlisting> - rules: ELTF*PL* variables
+   Several strict rules apply for the multiline string in programlisting
+   in addition to the general XML rules above:
+    7. Max line length < 80 char
+    8. Use backslash (\) to break longer lines
+    9. Use spaces (e.g. 4) to indent continuation lines in programlistings
+   10. No trailing spaces on any line
+   11. No spaces or linefeed immediately after leading <programlisting>
+   12. No spaces or linefeed before trailing </programlisting>
+
+DocBook Format: <ulink> - rules: ELTF_*URL* variables
+   13. ELTF_*URL and corresponding ELTF_*TXTURL shall be identical strings
+   14. Only if the URL is extremely long, the TXTURL can be a separate string
+
+Each target has one section with target parameters:
+       <section id="eltf-target-table-ELTF_T_MANIFEST_DIR">
+        <title>MACHINE ELTF_T_MANIFEST_DIR - Information</title>
+          ..... with many ELTF_ variables ....
+       </section>
+
+   15. If there is only one target. ELTF just replaces ELTF parameters
+
+   16. It there are multiple targets. ELTF copies the section and appends the
+       section the required number of times.
+       Each section ID will become unique: eltf-target-table-ELTF_T_MANIFEST_DIR
+       Each section title will become unique
+
+Tables with target parameters in each target section:
+   17. It is possible for ELTF to append more rows with one parameter each
+       to these tables, because the entire tables are included in the book
+
+Special - NOT YET READY DEFINED how to handle the optionally included
+   Eclipse and its version, but this is a first suggestion:
+   18. Just now ELTF can define ELFT_ECLIPSE_VERSION as a full string
+       with both version number and name,
+   19. MANUALLY if Eclipse is NOT included in the release,
+       the release manager should manually set condition="hidden" on
+       the entire section in the book XML about Eclipse
+
+
+
+BELOW WE TRY TO EXPLAIN EACH ELTF_* variable, but always check with make eltf
+if there are more new variables, missing in this description file.
+
+_____________________________________________________________________________
+ELTF_PL_HOST_PREREQ       Multiline list of host prerequisites, e.g. commands
+                          like sudo apt-get install xxxx or similar.
+                          First line = comment with the complete host name!
+                          It is possible to include multiple hosts by just
+                          adding an empty line, comment with host name, etc.
+                          xi:include eltf-prereq-apt-get-commands-host/1
+                          This is a <programlisting>...</programlisting>
+                          Example:
+# Host Ubuntu 14.04.5 LTS 64bit
+sudo apt-get update
+sudo apt-get install sed wget subversion git-core coreutils unzip texi2html \
+   texinfo libsdl1.2-dev docbook-utils fop gawk python-pysqlite2 diffstat \
+   make gcc build-essential xsltproc g++ desktop-file-utils chrpath  \
+   libgl1-mesa-dev libglu1-mesa-dev autoconf automake groff libtool xterm \
+   libxml-parser-perl
+
+_____________________________________________________________________________
+ELTF_PL_GET_REPO          Multiline commands to download the repo tool
+                          xi:include eltf-getting-repo-install-command/1
+                          This is a <programlisting>...</programlisting>
+                          Example:
+mkdir -p ~/bin
+curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
+chmod a+x ~/bin/repo
+export PATH=~/bin:$PATH
+
+_____________________________________________________________________________
+ELTF_EL_REL_VER           General parameter string: The version of this Enea
+                          Linux release. Major version and optional .Minor
+                          Typically created from MAJOR and MINOR in enea.conf
+                          MINOR in enea.conf is empty or contains a dot+minor
+                          xi_include EneaLinux_REL_VER/1
+                          This is a <phrase>X.x</phrase> used in many places.
+                          Examples:
+6
+  or
+6.1
+
+_____________________________________________________________________________
+ELTF_YOCTO_VER            General parameter string: Yocto version, created
+                          from DISTRO in poky.ent
+                          xi:include Yocto_VER/1
+                          This is a <phrase>X.x</phrase> used in many places.
+                          Example:
+2.5
+
+_____________________________________________________________________________
+ELTF_YOCTO_NAME           General parameter string: Yocto name (branch), created
+                          from DISTRO_NAME_NO_CAP in poky.ent
+                          xi:include Yocto_NAME/1
+                          This is a <phrase>X.x</phrase> used in many places.
+                          Example:
+sumo
+
+_____________________________________________________________________________
+ELTF_YOCTO_PROJ_DOWNLOAD_TXTURL  General parameters. These two are IDENTICAL
+ELTF_YOCTO_PROJ_DOWNLOAD_URL     strings with correct Yocto version string
+                                 at the end, typically without "dot".
+                          xi:include ULINK_YOCTO_PROJECT_DOWNLOAD/1
+                          This is an <ulink url="...">...</ulink>
+                          Example:
+http://www.yoctoproject.org/downloads
+
+_____________________________________________________________________________
+ELTF_EL_DOWNLOAD_TXTURL   General parameters. These two are IDENTICAL strings
+ELTF_EL_DOWNLOAD_URL      and shall be the http:/..... address where
+                          Enea Linux can be downloaded
+                          Often containing same version as in ELTF_EL_REL_VER
+                          xi:include ULINK_ENEA_LINUX_URL/1
+                          This is an <ulink url="...">...</ulink>
+                          Example:
+http://linux.enea.com/8
+
+_____________________________________________________________________________
+ELTF_PL_CLONE_W_REPO      Multiline commands to run repo to clone everything.
+                          Use the variable $MACHINE/default.xml (the text in
+                          the book will list the avaiable values of MACHINE,
+                          taken from the manifest repository)
+                          xi:include eltf-repo-cloning-enea-linux/1
+                          This is a <programlisting>...</programlisting>
+                          Example:
+mkdir enea-linux
+cd enea-linux
+repo init -u git@git.enea.com:linux/manifests/el_manifests-rt.git \
+    -b refs/tags/EL8 -m $MACHINE/default.xml
+repo sync
+
+_____________________________________________________________________________
+ELTF_ECLIPSE_VERSION      Optional general parameter string.
+                          NOT YET READY DEFINED
+                          Just now a release manage must manually set
+                          condition="hidden" on the Eclipse section,
+                          if Eclipse is not included in the release.
+                          ELTF just replaces ELTF_ECLIPSE_VERSION with a full
+                          string with "X.Y (name)"
+                          It includes the ID and can only be ONCE in the book.
+                          xi:include eltf-eclipse-version-row
+                          Example.
+4.5 (Mars)
+
+
+_____________________________________________________________________________
+ELTF_T_*                  All these are in each target (MACHINE) and ELTF
+                          must separately replace them with strings for
+                          each target
+                          NOTE: All (except the MANIFEST_DIR) are in rows
+                                in a table and ELTF can select to append
+                                more parameters by adding more rows
+
+_____________________________________________________________________________
+ELTF_T_MANIFEST_DIR       This happens to be in two places. Must be exactly
+ELTF_T_MANIFEST_DIR       the directory name in the manifest, e.g. same
+                          as the MACHINE names in $MACHINE/default.xml.
+                          In book: a) Part of section ID
+                                   b) Part of section title
+                          Examples:
+p2041rgb
+  or
+ls1021aiot
+  or
+qemuarm
+
+_____________________________________________________________________________
+ELTF_T_NAME               Target specific: "Target Official Name"
+                          NOT same as the target directory name in most cases.
+                          In book: An <entry> element in a row
+                          Examples:
+P2041RGB
+  or
+LS1021a-IoT
+  or
+qemuarm
+
+_____________________________________________________________________________
+ELTF_T_ARC_DESC           Target specific: "Architecture and Description"
+                          It can be a short identification string or
+                          it can be a longer descriptive sentence.
+                          In book: An <entry> element in a row
+                          Examples:
+Power, e500mc
+  or
+ARM Cortex-A7
+
+_____________________________________________________________________________
+ELTF_T_DS_TXTURL          Target specific: "Link to target datasheet. These
+ELTF_T_DS_URL             two usually are IDENTICAL strings with correct
+                          hyperlink to the target's official datasheet.
+                          In book: an <ulink url="...">...</ulink>
+                          Only if the link is VERY LONG, the text part shall
+                          instead be a descriptive string (see 2:nd example).
+                          NOTE: Also here no spaces or line-feeds!
+                          Examples:
+url="http://wiki.qemu.org">http://wiki.qemu.org
+or
+url="http://www.nxp.com/products/microcontrollers-and-processors/arm-processors/qoriq-arm-processors/qoriq-ls1021a-iot-gateway-reference-design:LS1021A-IoT">link to NXP's datasheet
+
+_____________________________________________________________________________
+ELTF_T_POKY_VER           Target specific: "Poky version" created either
+                          from POKYVERSION in poky.ent
+                          or using a hashvalue with a leading string, in
+                          which case it may be different per target.
+                          In book: An <entry> in a row
+                          Examples:
+15.0.0
+or
+Git commit id: 75ca53211488a3e268037a44ee2a7ac5c7181bd2
+
+_____________________________________________________________________________
+ELTF_T_GCC_VER            Target specific: "GCC Version". Should be in poky
+                          but not easy to find among various parameters.
+                          ELTF would extract it from build logs building SDK
+                          and it is possibly different per target.
+                          In book: An <entry> in a row
+                          Example:
+5.3
+
+_____________________________________________________________________________
+ELTF_T_KERN_VER           Target specific: "Linux Kernel Version". Often
+                          different per target.
+                          In book: An <entry> in a row
+                          Example:
+3.12
+
+_____________________________________________________________________________
+ELTF_T_DRIVERS            Target specific: "Supported Drivers". This is a
+                          comma-separated list of driver names.
+                          ELTF should create the list in same order for each
+                          target, e.g. alphabetic migth be OK.
+                          In book: An <entry> in a row
+                          Example:
+Ethernet, I2C, SPI, PCI, USB, SD/SDHC/SDXC
+
+
+_____________________________________________________________________________
+ELTF_T_EL_RPM_TXTURL      Target specific: "Enea rpm folder for downloading
+ELTF_T_EL_RPM_URL         RPM packages for this target". These two are
+                          INDENTICAL strings with hyperlink to the web site
+                          at Enea where the customer can download RPMs
+                          Note: Often the ELFT_EL_REL_VER value and
+                                the ELTF_T_MANIFEST_DIR are used in the link.
+                          In book: an <ulink url="...">...</ulink>
+                          Example:
+url="https://linux.enea.com/6/ls1021aiot/rpm">https://linux.enea.com/6/ls1021aiot/rpm
+
+_____________________________________________________________________________
diff --git a/doc/book-enea-linux-release-info/doc/getting_enea_linux.xml b/doc/book-enea-linux-release-info/doc/getting_enea_linux.xml
new file mode 100644
index 0000000..76487ef
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/getting_enea_linux.xml
@@ -0,0 +1,185 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="relinfo-getting-enea-linux">
+  <title>Getting Enea Linux</title>
+
+  <para>Enea Linux is available as both pre-built binary images and source
+  code. Both serve a specific purpose and each have their advantages. However,
+  using the pre-built binary images allows for getting up and running faster.
+  Please refer to the sections below for details on how to get Enea Linux as
+  pre-built binary images or source code.</para>
+
+  <section id="relinfo-getting-pre-built-images">
+    <title>Getting Pre-built Binaries</title>
+
+    <para>Enea Linux pre-built binaries are available for download on <ulink
+    url="https://portal.enea.com/login/?redirect_to=https%3A%2F%2Fportal.enea.com%2F">portal.enea.com</ulink>.
+    Log in using the credentials provided by Enea for your user account. Using
+    the menu, browse to the Linux section where you will now have access to
+    the <emphasis role="bold">Files</emphasis> and <emphasis
+    role="bold">Online Documentation</emphasis> sections.</para>
+
+    <para>The Files section lists each Enea Linux distribution, one for each
+    version and profile, as a separate download package. Clicking on the name
+    of the distribution will open a new page, which presents further details
+    about the content of the release and a list of downloadable archives, one
+    for each hardware target included in the release. Each archive provides
+    the following content:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para><emphasis>images</emphasis> directory &ndash; this directory
+        includes the binary image files needed to boot the target with Enea
+        Linux. This includes the kernel, the root file system, device tree,
+        etc.</para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis>sdk</emphasis> directory &ndash; this directory
+        includes the installer for the SDK.</para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis>deb</emphasis> directory &ndash; this directory
+        contains all the packages included in the distribution in deb format,
+        which can be installed using the package manager.</para>
+      </listitem>
+    </itemizedlist>
+
+    <para>For faster downloads, each archive is mirrored in several places,
+    geographically. Choose the archive in the region closest to you.</para>
+
+    <para>The Documentation section lists all the documents delivered with the
+    release:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para><emphasis role="bold">Enea Linux User&rsquo;s Guide</emphasis> -
+        intended for Enea Linux platform developers, who want to configure and
+        build customized Linux kernel images for embedded system targets,
+        using the Yocto configuration and build system.</para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">Enea Linux Open Source Report</emphasis> -
+        contains the open source and license information pertaining to
+        packages provided with this release of Enea Linux.</para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">Enea Linux Release Info</emphasis> -
+        provides information about the current released distribution for a
+        selected set of targets, along with installation requirements and
+        procedures.</para>
+      </listitem>
+    </itemizedlist>
+  </section>
+
+  <section id="relinfo-getting-source">
+    <title>Getting the Sources</title>
+
+    <para>Enea Linux sources are available for cloning from a set of Git
+    repositories on <ulink url="https://git.enea.com">git.enea.com</ulink>.
+    Since Enea Linux requires multiple repositories, Google Repo tool is used
+    in order to manage configurations and make the cloning step simpler. The
+    Google Repo tool uses files, known as manifests, which store a list of
+    tuples (repository URL, version). The Repo tool is then used to traverse
+    the list of tuples in the manifest file and clone the specified versions
+    of each repository. See <ulink
+    url="https://code.google.com/p/git-repo/">Google Code Archive for
+    git-repo</ulink>, for more info.</para>
+
+    <section id="getting-source-code-step-one">
+      <title>Get access to git.enea.com</title>
+
+      <para>In order to get access to git.enea.com, a ssh key is required for
+      Git authentication. If you don't already have such a key, follow the
+      steps below to generate one:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Generate the ssh key pair:</para>
+
+          <programlisting>$ ssh-keygen -t rsa</programlisting>
+
+          <para>When asked for a password, just press
+          <command>Enter</command>. This will create two files in the
+          <literal>.ssh</literal> directory in your home directory.</para>
+
+          <programlisting>id_rsa
+id_rsa.pub</programlisting>
+        </listitem>
+
+        <listitem>
+          <para>Copy the public key into an authorized_keys file:</para>
+
+          <programlisting>$ cat id_rsa.pub &gt;&gt; authorized_keys</programlisting>
+        </listitem>
+      </orderedlist>
+
+      <para>Once these steps are done and you have a valid ssh key pair, send
+      the public key,
+      <emphasis><emphasis><filename>id_rsa.pub</filename></emphasis></emphasis>,
+      via email to <email>mailto:git_support@list.enea.se</email> in order to
+      get access to <ulink
+      url="https://git.enea.com">git.enea.com</ulink>.</para>
+    </section>
+
+    <section id="getting-source-code-step-two">
+      <title>Get Sources</title>
+
+      <para>To use the Repo tool to download the sources for Enea Linux, do
+      the following:</para>
+
+      <orderedlist>
+        <listitem condition="hidden">
+          <para>Make sure that the repo tool is installed. If not, do the
+          following: <remark>Below is include of ID
+          "eltf-getting-repo-install-command" from
+          eltf_params_updated.xml</remark></para>
+
+          <xi:include href="eltf_params_updated.xml"
+                      xmlns:xi="http://www.w3.org/2001/XInclude"
+                      xpointer="element(eltf-getting-repo-install-command/1)" />
+        </listitem>
+
+        <listitem>
+          <para>Define the MACHINE to the following target listed
+          here:<remark>Below is the "machine_list" programlisting in
+          machine_list_generated.xml created by the make system by extracting
+          from the manifest</remark></para>
+
+          <xi:include href="machine_list_generated.xml"
+                      xmlns:xi="http://www.w3.org/2001/XInclude"
+                      xpointer="element(machine-list/1)" />
+        </listitem>
+
+        <listitem>
+          <para>Then use the repo command below:</para>
+
+          <xi:include href="eltf_params_updated.xml"
+                      xmlns:xi="http://www.w3.org/2001/XInclude"
+                      xpointer="element(eltf-repo-cloning-enea-linux/1)" />
+        </listitem>
+      </orderedlist>
+
+      <para>Once the source code is downloaded, the current directory will
+      contain a README file with instructions on how to build the distro and
+      boot the raspberry pi machine. For ease of use, these instructions are
+      also copied into this document, see <xref
+      linkend="relinfo-build-boot" />.</para>
+
+      <para>It is not necessary to explicitly clone the manifest repository
+      since that is done automatically by the repo tool. To see the current
+      manifest, use the following command:</para>
+
+      <programlisting>$ repo manifest</programlisting>
+
+      <remark>The UG should be updated with instructions on how to add
+      customizations. That section should also contain more info about the
+      manifest: the manifest templates, using a branch instead of the tag EL6,
+      etc. When this is done a reference from here should be added.</remark>
+    </section>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-linux-release-info/doc/jiraissues_override.xml b/doc/book-enea-linux-release-info/doc/jiraissues_override.xml
new file mode 100644
index 0000000..331a5ae
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/jiraissues_override.xml
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<section id="relinfo_extracted_from_jira">
+  <title>Extracted from Jira</title>
+
+  <para>In the table below are the issue(s) that currently affect this specific release. Use the ticket reference provided for each issue, to look up further information if needed.</para>
+  
+  <informaltable>
+    <tgroup cols="2">
+      <colspec colname="c1" colwidth="6*" />
+
+      <colspec align="center" colname="c2" colwidth="1*" />
+
+      <thead>
+        <row>
+          <entry align="center">Summary</entry>
+
+          <entry>Enea Ref</entry>
+        </row>
+      </thead>
+
+      <tbody>
+        <row>
+          <entry></entry>
+
+          <entry></entry>
+        </row>
+      </tbody>
+    </tgroup>
+  </informaltable>
+</section>
\ No newline at end of file
diff --git a/doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml
new file mode 100644
index 0000000..6fafb8d
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml
@@ -0,0 +1,377 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="bugs-limitations">
+  <title>Known Problems in this Release</title>
+
+  <para>Open source projects are continuously working on correcting reported
+  problems. Fixes and workarounds to bugs detected by Enea are submitted
+  upstream, and included in Enea Linux regardless of when they will be
+  included by the open source project. Issues that still affect the current
+  release are listed below.<remark>INFO: The <emphasis
+  role="bold">Release-Specific Problems</emphasis> section further down is
+  generated from JIRA with gen_known_issues.py, but that script is HARDCODED
+  with affectedversion "Enea Linux 6" and needs to be adapted when a release
+  info for another EL version changes.</remark></para>
+
+  <section id="bugs-limitations-yocto">
+    <title>Yocto Project</title>
+
+    <para>The Yocto Project community uses a <ulink
+    url="https://bugzilla.yoctoproject.org">Bugzilla database</ulink> to track
+    information on reported bugs and other issues.</para>
+  </section>
+
+  <section condition="hidden" id="bugs-limitations-sdk">
+    <title>Toolchain / SDK</title>
+
+    <itemizedlist spacing="compact">
+      <listitem>
+        <para>Building the kernel might fail if GNU Make of version 3.82 has
+        been installed on the host. The mandatory recovery action is to revert
+        to version 3.81.<remark>INFO It is possible to hide this entire
+        subsection by setting condition hidden on the section
+        element</remark></para>
+      </listitem>
+
+      <listitem>
+        <para>Installing a second toolchain in the same directory as a
+        previous one will break the $PATH variable of the first
+        one.<remark>LXCR-3624</remark></para>
+      </listitem>
+    </itemizedlist>
+  </section>
+
+  <section condition="hidden" id="bugs-limitations-eclipse">
+    <title>Eclipse Tools</title>
+
+    <para>The Eclipse tools provided together with Enea Linux are part of the
+    Yocto Project Application Development Toolkit (ADT) and are maintained by
+    different open source projects. The list below outlines current problems
+    with the plug-ins as such, as well as kernel limitations when using a tool
+    towards the mentioned target:<remark>INFO It is possible to hide this
+    setting condition hidden on the section element</remark></para>
+
+    <itemizedlist spacing="compact">
+      <listitem>
+        <para><emphasis role="bold">HOB</emphasis> is currently not supported
+        on Red Hat.<remark>LXCR-2994, LXCR-3222</remark></para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">SystemTap</emphasis> is currently not
+        supported on Red Hat.<remark>LXCR-3274</remark></para>
+      </listitem>
+
+      <listitem>
+        <para>When running <emphasis role="bold">SystemTap</emphasis> for the
+        first time on a target, you may need to manually ssh into the target
+        beforehand, in order to add the RSA key of the host to the file
+        known_hosts. Failing to do so will result in Eclipse freezing with the
+        progress window displayed, and a terminal message <literal>The
+        authenticity of host &lt;target_ip&gt; can't be
+        established</literal>.</para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">SystemTap</emphasis> scripts sometimes
+        result crosstap error messages about inaccessible variables. This is
+        not an issue with the tool itself, but stems from the compiler
+        optimizing away some of the variables. See workaround in the User's
+        Guide.<remark>LXCR-2204</remark></para>
+      </listitem>
+
+      <listitem>
+        <para>Currently <emphasis role="bold">BitBake Commander</emphasis>
+        projects can only be created for a local connection. Due to an
+        upstream bug, selecting a remote connection causes the Eclipse GUI to
+        freeze such that it must be killed.<remark>LXCR-2801</remark></para>
+      </listitem>
+
+      <listitem>
+        <para>A limitation currently makes <emphasis
+        role="bold">Eclipse</emphasis> non-responding when running a streaming
+        script, i.e. a script that runs continuously.</para>
+      </listitem>
+
+      <listitem>
+        <para>The <emphasis role="bold">LatencyTop</emphasis> plug-in for the
+        P2041 target reports some errors due to the permissions configuration
+        on the target, but it works correctly if the
+        <literal>latencytop</literal> command is issued from the Eclipse
+        console.<remark>LXCR-6303</remark></para>
+      </listitem>
+
+      <listitem>
+        <para>Currently <emphasis role="bold">LatencyTOP</emphasis> is not
+        available for ARM kernels built with SMP support due to an ARM
+        specific limitation in the Linux kernel.</para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">PowerTOP</emphasis> sometimes freezes
+        Eclipse after displaying a progress bar with message
+        <literal>Gathering powertop data file
+        remotely</literal>.<remark>LXCR-3143</remark></para>
+      </listitem>
+
+      <listitem>
+        <para>When running <emphasis role="bold">powertop</emphasis> from the
+        Eclipse terminal towards p2020rdb targets it is necessary to specify
+        the full path in order to find the
+        command.<remark>LXCR-2265</remark></para>
+      </listitem>
+
+      <listitem>
+        <para>When running <emphasis role="bold">powertop</emphasis> from the
+        Eclipse terminal towards zynq ZC702 targets it is necessary to specify
+        the full path in order to find the
+        command.<remark>LXCR-2265</remark></para>
+      </listitem>
+
+      <listitem>
+        <para>The <emphasis role="bold">PowerTOP</emphasis> console in Eclipse
+        might display messages like <literal>Cannot load
+        /var/cache/powertop/&lt;filename&gt;</literal>. As a workaround, run
+        <emphasis role="bold">powertop --calibrate</emphasis> for a while to
+        generate the missing files. See <ulink
+        url="https://bugzilla.redhat.com/show_bug.cgi?id=698020">Bugzilla
+        #698020</ulink>.<remark>LXCR-3575</remark></para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">ssh-only</emphasis> is currently the only
+        supported connection type when running Eclipse tools towards a
+        target.<remark>LXCR-2799</remark></para>
+      </listitem>
+
+      <listitem>
+        <para>Hyphen character '-' in the name of the <emphasis
+        role="bold">Yocto Project ADT AutoTools project</emphasis> can cause
+        configuration errors.<remark>LXCR-2290</remark></para>
+      </listitem>
+
+      <listitem>
+        <para>The <emphasis role="bold">LTTng</emphasis> tool does not work on
+        <emphasis role="bold">ARM</emphasis> targets, neither from within
+        Eclipse nor when run directly on target, due to a problem with
+        lttng-modules and gcc-4.8.x. See <ulink
+        url="https://bugzilla.yoctoproject.org/show_bug.cgi?id=6015">Bugzilla
+        #6015</ulink>.<remark>LXCR-2653, LXCR-3053</remark></para>
+      </listitem>
+
+      <listitem>
+        <para>When running <emphasis role="bold">LTTng</emphasis> from
+        Eclipse, it sometimes happens that a new session created in the
+        Control View does not immediately appear under Sessions for that
+        target. However, the session is created and will appear after
+        right-clicking "Sessions" and selecting "Refresh".</para>
+      </listitem>
+
+      <listitem>
+        <para>The<emphasis role="bold"> yocto-bsp</emphasis> properties page
+        has some problems in the graphical user interface. Occasionally it is
+        not possible to resize and scroll which makes it impossible to see the
+        lower part of the properties window.<remark>LXCR-3128</remark></para>
+      </listitem>
+
+      <listitem>
+        <para>When connecting an Eclipse project configured for <emphasis
+        role="bold">KGDB</emphasis> (GDB Hardware Debugging) to a 64-bit
+        PowerPC target, GDB fails to connect unless the architecture is
+        specified in <filename>.gdbinit</filename>. See <ulink
+        url="https://bugs.eclipse.org/bugs/show_bug.cgi?id=457697">Bugzilla
+        #457697</ulink>.<remark>LXCR-3984</remark></para>
+      </listitem>
+    </itemizedlist>
+  </section>
+
+  <section condition="hidden" id="bugs-limitations-target-side-tools">
+    <title>Target-Side Tools</title>
+
+    <para>The target-side tools can be run stand-alone on target or from
+    Eclipse on host. The issues below are only observed when running the tools
+    directly on target:<remark>INFO It is possible to hide this setting
+    condition hidden on the section element</remark></para>
+
+    <itemizedlist spacing="compact">
+      <listitem>
+        <para>The <emphasis role="bold">perf report</emphasis> command hangs
+        or crashes due to segmentation fault on ARM
+        targets.<remark>LXCR-2708</remark></para>
+      </listitem>
+
+      <listitem>
+        <para>The <emphasis role="bold">perf report</emphasis> does not show
+        any output for the PandaBoard target.<remark>LXCR-2710</remark></para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">perf top</emphasis> displays for a few
+        seconds the error message <literal>Failed to open
+        /tmp/perf-388.map</literal>. Any attempt to exit the subsequent window
+        causes the system to hang.<remark>LXCR-3113</remark></para>
+      </listitem>
+
+      <listitem>
+        <para>When running the <command>perf top</command> command on the i.MX
+        6Quad SABRE Lite target, the console text may become red after running
+        for some time (~ 1 minute).<remark>LXCR-3631</remark></para>
+      </listitem>
+
+      <listitem>
+        <para>The <emphasis role="bold">LTTng</emphasis> tool does not work on
+        <emphasis role="bold">ARM</emphasis> targets, neither from within
+        Eclipse nor when run directly on target, due to a problem with
+        lttng-modules and gcc-4.8.x. See <ulink
+        url="https://bugzilla.yoctoproject.org/show_bug.cgi?id=6015">Bugzilla
+        #6015</ulink>.<remark>LXCR-2653, LXCR-3053</remark></para>
+      </listitem>
+
+      <listitem>
+        <para>The <emphasis role="bold">powertop --calibrate</emphasis>
+        command does not work on the Keystone k2hk-evm
+        target.<remark>LXCR-2660</remark></para>
+      </listitem>
+
+      <listitem>
+        <para>The <emphasis role="bold">powertop</emphasis> command run with
+        <emphasis role="bold">--calibrate</emphasis> or -<emphasis
+        role="bold">-time</emphasis> arguments may show some warnings on
+        PowerPC targets.</para>
+      </listitem>
+
+      <listitem>
+        <para>When running <emphasis role="bold">powertop</emphasis> on
+        <emphasis role="bold">ARM</emphasis> targets, the following
+        warning/error is repeated: <literal>clk_set_rate: failed to set
+        i2c0_aper rate</literal> . Then powertop stops and the statistics are
+        no longer updated. What probably happens here is that the cpufreq
+        governor tries to scale the CPU frequency, but since the I2C clock is
+        derived from the CPU frequency, the I2C driver implements some policy
+        to stay within legal frequency limits and rejects the frequency
+        changes, ending up with the warning message. A <ulink
+        url="https://github.com/Xilinx/linux-xlnx/commit/0fdd34575efae5c8eced09b6b0a1b723bff4d225">fix</ulink>
+        has been merged in the linux-xlnx kernel but is not yet propagated
+        into meta-xilinx.<remark>LXCR-3205, LXCR-3106,
+        LXCR-2660</remark></para>
+      </listitem>
+
+      <listitem>
+        <para>If you get an error message like <literal>Cannot load from file
+        /var/cache/powertop/saved_results.powertop</literal> when running
+        <emphasis role="bold">powertop</emphasis>, there is most likely not
+        enough measurement data collected yet. All you have to do is to keep
+        powertop running for a certain time.<remark>LXCR-2176, LXCR-2660,
+        LXCR-3106</remark></para>
+      </listitem>
+
+      <listitem>
+        <para>The message <literal>Model-specific registers (MSR) not found
+        (try enabling CONFIG_X86_MSR)</literal> appears when you run <emphasis
+        role="bold">powertop</emphasis> on <emphasis
+        role="bold">non-x86</emphasis> targets. powertop is mainly an x86n
+        tool, so it expects X*^_MSR config to be enabled in the kernel. For
+        non-x86 targets this config is not available in the kernel, hence,
+        powertop warns about it, but the message can be ignored on those
+        targets.<remark> LXCR-2176, LXCR-2660, LXCR-3106</remark></para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">powertop</emphasis> issues a message
+        <literal>sh: /usr/bin/xset: No such file or directory</literal> when
+        it tries to use xset to configure X display preferences but cannot
+        find the binary since the image by default contains no X system. The
+        message can simply be ignored.<remark>LXCR-2176</remark></para>
+      </listitem>
+    </itemizedlist>
+  </section>
+
+  <section condition="hidden" id="bugs-limitations-virtualization">
+    <title>Virtualization</title>
+
+    <itemizedlist spacing="compact">
+      <listitem>
+        <para><emphasis role="bold">virtualization</emphasis>: CONFIG_BRIDGE
+        is not included in the default p2020rdb
+        kernel.<remark>LXVTCR-273</remark></para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">lxc</emphasis>:</para>
+
+        <itemizedlist spacing="compact">
+          <listitem>
+            <para>User namespace is not available on PowerPC targets as it is
+            an experimental feature in the 3.8 kernel.</para>
+          </listitem>
+
+          <listitem>
+            <para>If multiple Linux containers are started from the same
+            process and share resources, destroying the containers might
+            result in a race condition with error message "Error in
+            `./lxc-test-concurrent': double free or corruption (fasttop)"
+            followed by an application
+            crash."<remark>LXVTCR-365</remark></para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">libvirt</emphasis>: Default network does
+        not start.<remark>LXVTCR-240</remark></para>
+      </listitem>
+    </itemizedlist>
+  </section>
+
+  <section condition="hidden" id="bugs-limitations-doc">
+    <title>Documentation</title>
+
+    <itemizedlist spacing="compact">
+      <listitem>
+        <para><emphasis role="bold">PDF navigation</emphasis>: When using
+        links to open other PDFs, or jump to another place in the same PDF,
+        jumping back sometimes fails. This has been observed when opening a
+        PDF in Adobe Reader, inside a browser with PDF add-on, as well as when
+        the browser is configured to open PDF files in an external PDF reader.
+        As a workaround, open the HTML version of the
+        document.<remark>LXCR-3283</remark></para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">Internet Explorer (IE) cannot display some
+        web pages</emphasis>: It is recommended to use Firefox or another
+        non-IE browser for opening external links. If you prefer reading the
+        documentation in PDF format in Adobe Reader (not in an Adobe plug-in
+        in a browser), remember to configure a non-IE browser as default
+        browser to be able to follow all links from within Adobe Reader.
+        Example of a link that does not work in IE: <ulink
+        url="https://rt.wiki.kernel.org/">https://rt.wiki.kernel.org/</ulink>.
+        <remark>LXCR-3281</remark></para>
+      </listitem>
+    </itemizedlist>
+  </section>
+
+  <section condition="hidden" id="bugs-limitations-other">
+    <title>Miscellaneous</title>
+
+    <itemizedlist spacing="compact">
+      <listitem>
+        <para>Running <emphasis role="bold">QEMU from an exported
+        rootfs</emphasis> requires sudo privileges on the host.</para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">menuconfig</emphasis> requires <emphasis
+        role="bold">Ncurses</emphasis>. If the terminal that pops up
+        immediately closes instead of showing the menuconfig interface, check
+        that the Ncurses development library is installed.</para>
+      </listitem>
+    </itemizedlist>
+  </section>
+
+  <!-- The file with a section below is autocreated by make init  -->
+
+  <!--  <xi:include href="jiraissues_generated.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-linux-release-info/doc/main_changes.xml b/doc/book-enea-linux-release-info/doc/main_changes.xml
new file mode 100644
index 0000000..c2279ee
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/main_changes.xml
@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="relinfo-changes">
+  <title>Main Changes</title>
+
+  <para>This chapter describes the major changes and additions made to this
+  release of Enea Linux.<remark>INFO Just now Hardcoded previous release
+  string in this paragraph.</remark><remark>The list of changed packages
+  further down is created from the open source book licenses.xml by the script
+  gen_pkgdiff.py by comparing with an older open source licenses.xml,
+  depending on the parameter "prev_baseline" in pardoc-distro.xml, e.g. a tag
+  like "EL5". This parameter needs to be changed to a new TAG when a release
+  info for another EL version is created. It must correspond to the release
+  string above.</remark></para>
+
+  <section id="relinfo-changes-other">
+    <title>New Functionality/Enhancements</title>
+
+    <itemizedlist spacing="compact">
+      <listitem>
+        <para><ulink
+        url="http://www.yoctoproject.org/downloads">New Yocto
+        Project version</ulink> (<xi:include href="eltf_params_updated.xml"
+        xmlns:xi="http://www.w3.org/2001/XInclude"
+        xpointer="element(Yocto_VER/1)" />)<remark>INFO Yocto_VER and
+        ULINK_YOCTO_PROJECT_DOWNLOAD in
+        eltf_params_updated.xml</remark></para>
+      </listitem>
+
+      <listitem>
+        <para>New targets: Intel Xeon D, Intel Atom C3000 and Intel NUC Kaby
+        Lake.</para>
+      </listitem>
+    </itemizedlist>
+  </section>
+
+  <section condition="hidden" id="relinfo-fixed">
+    <title>Problems Fixed in this Release</title>
+
+    <para>TBD <remark>FIXME or set condition hidden on the section
+    element</remark></para>
+  </section>
+
+  <section condition="hidden" id="relinfo-added-drivers">
+    <title>Added Drivers</title>
+
+    <para>TBD <remark>FIXME or set condition hidden on the section
+    element</remark></para>
+  </section>
+
+  <xi:include href="pkgdiff_generated.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
+</chapter>
diff --git a/doc/book-enea-linux-release-info/doc/prerequisites.xml b/doc/book-enea-linux-release-info/doc/prerequisites.xml
new file mode 100644
index 0000000..324bb57
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/prerequisites.xml
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="prerequisites">
+  <title>Prerequisites</title>
+
+  <para>Building Enea Linux or compiling applications requires that your git
+  environment be setup properly and for certain packages to be installed on
+  your Linux development host.</para>
+
+  <para>Please refer to <ulink
+  url="https://git-scm.com/book/en/v2/Getting-Started-First-Time-Git-Setup">Getting
+  Started - First-Time Git Setup</ulink>, for more details on how to set up
+  your git environment correctly, including how to set your identity using the
+  following commands:</para>
+
+  <programlisting>$ git config --global user.name "John Doe"
+$ git config --global user.email johndoe@example.com</programlisting>
+
+  <para>First ensure the system is up-to-date, then for the supported
+  distribution(s), you need the following packages:<remark>INFO: The
+  programlisting below is a parameters in eltf_params_updated.xml with ID:
+  "eltf-prereq-apt-get-command-host". If multiple hosts are supported, store
+  the commands for each host in the same programlisting with empty lines
+  between each - the comment with the FULL HOST name and version is
+  essential.</remark></para>
+
+  <xi:include href="eltf_params_updated.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude"
+              xpointer="element(eltf-prereq-apt-get-commands-host/1)" />
+
+  <xi:include href="../../s_doceneacommon/doc/system_requirements.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-linux-release-info/doc/system_requirements.xml b/doc/book-enea-linux-release-info/doc/system_requirements.xml
new file mode 100644
index 0000000..cc1248e
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/system_requirements.xml
@@ -0,0 +1,159 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<section id="enea-linux-sysreq">
+  <title>System Requirements</title>
+
+  <para>The host requirements listed below are extensive to allow for the
+  building of Linux images via the Yocto system, and not just
+  applications.</para>
+
+  <para>Please also see the system requirements in the Yocto 2.3 documents:
+  <ulink
+  url="http://www.yoctoproject.org/docs/2.3/yocto-project-qs/yocto-project-qs.html#yp-resources">Yocto
+  Project Start</ulink> and the <ulink
+  url="http://www.yoctoproject.org/docs/2.3/ref-manual/ref-manual.html#intro-requirements">Yocto
+  Project Reference Manual</ulink>. If needed, replace the Yocto version in
+  the links provided with a more recent version.</para>
+
+  <informaltable>
+    <tgroup cols="2">
+      <colspec align="left" colname="1" colwidth="1*" />
+
+      <colspec align="left" colname="2" colwidth="3*" />
+
+      <spanspec nameend="2" namest="1" spanname="onetwo" />
+
+      <tbody>
+        <row>
+          <entry spanname="onetwo"><emphasis role="bold"> Build host
+          requirements<indexterm>
+              <primary>system requirements</primary>
+            </indexterm></emphasis></entry>
+        </row>
+
+        <row>
+          <entry>Linux distribution</entry>
+
+          <entry>The downloaded code shall be built on a Linux host to
+          generate images for your target or for emulation in QEMU. For
+          information about the supported hosts and targets, see the <emphasis
+          role="bold">Enea Linux Release Information</emphasis> in your Enea
+          Linux distribution.</entry>
+        </row>
+
+        <row>
+          <entry>Internet access</entry>
+
+          <entry>Internet access must be available when building an image,
+          since bitbake downloads source files from various servers during the
+          build.</entry>
+        </row>
+
+        <row>
+          <entry>Packages</entry>
+
+          <entry>Depending on the Linux distribution and version on host, some
+          packages may be required, by bitbake for example. You will install
+          any required packages while following the installation
+          instructions.</entry>
+        </row>
+
+        <row>
+          <entry>Targets</entry>
+
+          <entry>Images can be built or downloaded for any of the targets
+          supported in this release.</entry>
+        </row>
+
+        <row>
+          <entry>Disk space</entry>
+
+          <entry><para>Your system should have at least 50 GB of free disk
+          space when bitbaking the basic enea-image-name kernel image.</para>
+          <para>For larger images and to allow for future package extensions
+          and variations in the build process, a minimum of 100 GB free disk
+          space is recommended.</para></entry>
+        </row>
+
+        <row>
+          <entry>Recommended RAM</entry>
+
+          <entry><para>Your system must have at least 4 GB available
+          RAM.</para> <para>It is recommended to have 8 GB RAM available for
+          parallel build jobs.</para></entry>
+        </row>
+
+        <row>
+          <entry>Java</entry>
+
+          <entry>Java <indexterm>
+              <primary>java</primary>
+            </indexterm>is required to run Eclipse. Currently, Eclipse
+          generally recommends at least Java 6 JRE/JDK. More information
+          regarding operating environments for Eclipse is provided in the
+          <ulink
+          url="http://www.eclipse.org/eclipse/development/readme_eclipse_version">Eclipse
+          Project Release Notes</ulink> for the Eclipse version used in this
+          release. See the <emphasis role="bold">Enea Linux Release
+          Information </emphasis>for the Eclipse Version.</entry>
+        </row>
+      </tbody>
+    </tgroup>
+  </informaltable>
+
+  <para>The build time depends on the capacity of the processor and other
+  hardware, available resources, speed of internet connection, load situation,
+  etc. E.g: on a fast 16 core machine with 16 GB RAM and SSD disks, a complete
+  build from source could take about two hours.</para>
+
+  <informaltable>
+    <tgroup cols="2">
+      <colspec align="left" colname="1" colwidth="1*" />
+
+      <colspec align="left" colname="2" colwidth="3*" />
+
+      <spanspec nameend="2" namest="1" spanname="onetwo" />
+
+      <tbody>
+        <row>
+          <entry spanname="onetwo"><emphasis role="bold">Target
+          Requirements</emphasis></entry>
+        </row>
+
+        <row>
+          <entry>External memory</entry>
+
+          <entry>To boot a CGL<indexterm>
+              <primary>CGL</primary>
+            </indexterm> image, you need at least 16 GB on a hard-disk
+          drive<indexterm>
+              <primary>HDD</primary>
+            </indexterm> on an eSATA, USB drive, or SD card.<remark>INFO:
+          (packed rootfs 4.5 GB + unpacked rootfs 1.5 GB + good
+          margins)</remark><remark>INFO: NFS does not support SELinux. In
+          order to have a security-enhanced Linux, one must take off from an
+          NFS-booted system and proceed with boot from external
+          memory.</remark></entry>
+        </row>
+      </tbody>
+    </tgroup>
+  </informaltable>
+
+  <section id="ensure-bash">
+    <title>System Shell Configuration</title>
+
+    <para>Before installing Enea Linux, ensure that bash is the default
+    shell.</para>
+
+    <para>If your system runs Ubuntu, you can use ls -l to ensure
+    <filename>/usr/bin</filename> is a symbolic link to bash. In case the link
+    points to dash, which is default in some Ubuntu versions, change it to
+    bash by running <emphasis role="bold">sudo dpkg-reconfigure
+    dash</emphasis> and answer <emphasis role="bold">No</emphasis> to the
+    question "Use dash as the default system shell (/bin/sh)?":</para>
+
+    <programlisting># ls -l /bin/sh
+        lrwxrwxrwx 1 root root 4 2012-03-02 11:53 /bin/sh -&gt; bash</programlisting>
+  </section>
+</section>
\ No newline at end of file