12 files changed, 1612 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..01679f8
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/about_release.xml
@@ -0,0 +1,294 @@
+<?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 <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>. 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>
+
+    <informaltable>
+      <tgroup cols="1">
+        <thead>
+          <row>
+            <entry>Item</entry>
+          </row>
+        </thead>
+
+        <tbody>
+          <row>
+            <entry><para>Source code, recipes and scripts for building the
+            distribution and SDKs. See <xref
+            linkend="relinfo-getting-enea-linux" />.</para></entry>
+          </row>
+
+          <row>
+            <entry><para>Documentation. See <xref
+            linkend="relinfo-documentation" />.</para></entry>
+          </row>
+
+          <row>
+            <entry>Pre-built binaries (kernel image, dtb &amp; rootfs)</entry>
+          </row>
+
+          <row>
+            <entry>Pre-built packages (RPM). See links for each
+            target.<remark>INFO Below is an Eclipse row from
+            eltf_params_updated.xml. MANUALLY if eclipse is not included, set
+            condition hidden on the row element BOTH in template.xml and in
+            updated.xml.</remark></entry>
+          </row>
+
+          <xi:include href="eltf_params_updated.xml"
+                      xmlns:xi="http://www.w3.org/2001/XInclude"
+                      xpointer="element(eltf-eclipse-version-row)" />
+        </tbody>
+      </tgroup>
+    </informaltable>
+  </section>
+
+  <section id="relinfo-supported-targets">
+    <title>Supported Targets</title>
+
+    <informaltable>
+      <tgroup cols="3">
+        <colspec align="left" colname="c1" colwidth="1*" />
+
+        <colspec align="left" colname="c2" colwidth="1*" />
+
+        <colspec align="left" colname="c3" colwidth="1*" />
+
+        <thead valign="bottom">
+          <row>
+            <entry>Target</entry>
+
+            <entry>Architecture</entry>
+
+            <entry>Specification</entry>
+          </row>
+        </thead>
+
+        <tbody>
+          <row>
+            <entry>P2041RDB</entry>
+
+            <entry><para>Power, e500mc</para></entry>
+
+            <entry>See <ulink
+            url="http://www.nxp.com/products/microcontrollers-and-processors/power-architecture-processors/qoriq-power-architecture-processors/p2041-qoriq-reference-design-board:RDP2041BOARD">link
+            to NXP's datasheet</ulink></entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </informaltable>
+
+    <para><remark>FIXME should autocreate a list of targets, hopefully from
+    the generated README file, by using MAKEFILE to update pardoc-distro
+    AND/OR also auto-create an XML file to include here with description text
+    for each target etc..</remark></para>
+  </section>
+
+  <section id="relinfo-supported-host-environment">
+    <title>Supported Host Environment</title>
+
+    <itemizedlist>
+      <listitem>
+        <para>Ubuntu 14.04 LTS, 64-bit<remark>Hardcoded now in this XML file.
+        Might be moved to the parameter file later.</remark><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>
+      </listitem>
+    </itemizedlist>
+  </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"
+              targetptr="book_enea_linux_open_source"><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 Toolchain/s (SDK)</title>
+
+    <para>The SDK contains toolchains supporting cross-compilation of
+    applications for the targets on an x86_64 host. See the <olink
+    targetdoc="book_enea_linux_app_dev_guide"
+    targetptr="book_enea_linux_app_dev_guide"><trademark
+    class="registered">Enea</trademark> Linux Application Development
+    Guide</olink> for information on how to build and install a
+    toolchain.</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_platforms_dev_guide"
+        targetptr="book_enea_linux_platforms_dev_guide"><trademark
+        class="registered">Enea</trademark> Linux Platforms Development
+        Guide</olink></para>
+      </listitem>
+
+      <listitem>
+        <para><olink targetdoc="book_enea_linux_app_dev_guide"
+        targetptr="book_enea_linux_app_dev_guide"><trademark
+        class="registered">Enea</trademark> Linux Application Development
+        Guide</olink></para>
+      </listitem>
+
+      <listitem>
+        <para><trademark class="registered">Enea</trademark> Linux Networking
+        Profile Guide</para>
+      </listitem>
+
+      <listitem>
+        <para><olink targetdoc="book_enea_linux_open_source"
+        targetptr="book_enea_linux_open_source"><trademark
+        class="registered">Enea</trademark> Linux Open Source
+        Report</olink></para>
+      </listitem>
+
+      <listitem>
+        <para><olink targetdoc="book_enea_linux_eclipse_open_source"
+        targetptr="book_enea_linux_eclipse_open_source"><trademark
+        class="registered">Enea</trademark> Linux Eclipse 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 Real-Time
+        Guide can be read at <ulink
+        url="http://linuxrealtime.org">http://linuxrealtime.org</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>On target T4240RDB:</para>
+
+        <itemizedlist spacing="compact">
+          <listitem>
+            <para>SRIO support in user space (NWRITE, NREAD, msg,
+            doorbell)</para>
+          </listitem>
+
+          <listitem>
+            <para>USDPAA</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>Smart Package Management</para>
+      </listitem>
+    </itemizedlist>
+  </section>
+
+  <section id="relinfo-security-fixes">
+    <title>Security Fixes</title>
+
+    <para>See <ulink
+    url="http://www.enea.com/solutions/Enea-Linux/Security/CVEs-list">List of
+    CVEs addressed in Enea Linux</ulink> and <ulink
+    url="http://www.enea.com/solutions/Enea-Linux/Security#how-to-get-security-updates">How
+    to Get Security Updates</ulink>.</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>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>
\ No newline at end of file
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..91af443
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/book.xml
@@ -0,0 +1,18 @@
+<?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" [
+]>
+<book id="book_enea_linux_release_info">
+  <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>
+  <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..2200997
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/build_boot_template.xml
@@ -0,0 +1,28 @@
+<?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 these build/boot instruction have been extracted
+  into the following sections.</para>
+
+  <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..a55234f
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/eltf_params_updated.xml
@@ -0,0 +1,165 @@
+<?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 14.04.5 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>6</phrase></para>
+
+    <para id="Yocto_VER"><phrase>2.1</phrase></para>
+
+    <para id="Yocto_NAME"><phrase>krogoth</phrase></para>
+
+    <para id="ULINK_YOCTO_PROJECT_DOWNLOAD"><ulink
+    url="http://www.yoctoproject.org/downloads/core/krogoth/21">http://www.yoctoproject.org/downloads/core/krogoth/21</ulink></para>
+
+    <para id="ULINK_ENEA_LINUX_URL"><ulink
+    url="https://linux.enea.com/6">https://linux.enea.com/6</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/el_manifests-networking.git \
+    -b refs/tags/EL6 -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. Do this both in
+    template.xml and updated.xml.</bridgehead>
+
+    <informaltable>
+      <tgroup cols="1">
+        <tbody>
+          <row condition="hidden" id="eltf-eclipse-version-row">
+            <entry>Eclipse version 4.3 (Mars) 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-p2041rdb">
+      <title>MACHINE p2041rdb - Information</title>
+
+      <para><informaltable>
+          <tgroup cols="2">
+            <colspec colwidth="6*" />
+
+            <colspec colwidth="9*" />
+
+            <tbody>
+              <row>
+                <entry>Target official name</entry>
+
+                <entry>P2041RDB</entry>
+              </row>
+
+              <row>
+                <entry>Architecture and Description</entry>
+
+                <entry>Power, e500mc</entry>
+              </row>
+
+              <row>
+                <entry>Link to target datasheet</entry>
+
+                <entry>See <ulink
+                url="http://www.nxp.com/products/microcontrollers-and-processors/power-architecture-processors/qoriq-power-architecture-processors/p2041-qoriq-reference-design-board:RDP2041BOARD">link
+                to NXP's datasheet</ulink></entry>
+              </row>
+
+              <row>
+                <entry>Poky version</entry>
+
+                <entry>Git-commit-id:
+                75ca53211488a3e268037a44ee2a7ac5c7181bd2</entry>
+              </row>
+
+              <row>
+                <entry>GCC version</entry>
+
+                <entry>5.3</entry>
+              </row>
+
+              <row>
+                <entry>Linux Kernel Version</entry>
+
+                <entry>3.12</entry>
+              </row>
+
+              <row>
+                <entry>Supported Drivers</entry>
+
+                <entry>Ethernet, I2C, SPI, PCI Express, USB, Flash,
+                SD/SDHC/SDXC, RTC</entry>
+              </row>
+
+              <row>
+                <entry>Enea rpm folder for downloading RPM packages for this
+                target</entry>
+
+                <entry><ulink
+                url="https://linux.enea.com/6/p2041rgb/rpm">https://linux.enea.com/6/p2041rgb/rpm</ulink></entry>
+              </row>
+            </tbody>
+          </tgroup>
+        </informaltable></para>
+    </section>
+  </section>
+</section>
\ No newline at end of file
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..7f1d3cb
--- /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.1
+
+_____________________________________________________________________________
+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:
+krogoth
+
+_____________________________________________________________________________
+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/core/krogoth/21
+
+_____________________________________________________________________________
+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/6
+
+_____________________________________________________________________________
+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/el_manifests-standard.git \
+    -b refs/tags/EL6 -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..055be15
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/getting_enea_linux.xml
@@ -0,0 +1,84 @@
+<?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>
+
+  <section id="relinfo-getting-pre-built-images">
+    <title>Getting Pre-built Binaries</title>
+
+    <para>Application developers will download pre-complied images from the
+    Enea Portal or will receive prebuilt images from the platform developers.
+    For further information on this see <olink
+    targetdoc="book_enea_linux_app_dev_guide"
+    targetptr="book_enea_linux_app_dev_guide">Enea Linux Application
+    Development Guide</olink>.</para>
+  </section>
+
+  <section id="relinfo-getting-source">
+    <title>Getting the Source</title>
+
+    <para>The source for this Enea Linux release is available for cloning from
+    a set of Git repositories. To manage the different repositories, Google's
+    repo tool is used. The basic idea is to store a list with (repo-URL,
+    version) tuples in a separate file, known as the manifest. The repo tool
+    is then used to traverse the list and clone the specified versions of the
+    repositories. See <ulink
+    url="https://code.google.com/p/git-repo/">https://code.google.com/p/git-repo/</ulink>
+    for more info.</para>
+
+    <para>To use repo tool to download the source for Enea Linux, follow the
+    steps below:</para>
+
+    <orderedlist>
+      <listitem>
+        <para>Make sure that the repo tool is installed. If not, follow the
+        instructions below. The instruction assumes a suitable place in your
+        PATH to use. You might change that.<remark>INFO: 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>Use the repo tool to download the source: Please define MACHINE
+        to your target, uncomment and use one of the MACHINE lines 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)" />
+
+        <para>and use the repo command below:<remark> Below is include of ID
+        "eltf-repo-cloning-enea-linux" from eltf_params_updated.xml. Here the
+        $MACHINE shall be given!</remark></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>The source code is now downloaded. Current directory will contain a
+    README file with instructions on how to build the distro and boot the
+    target. For convenience, 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, e.g. to get a list of the repositories, use the following
+    command:</para>
+
+    <programlisting>$ repo manifest</programlisting>
+
+    <remark>The UG should be updated with instructions on how to add
+    customisations. That section should also contain some more info about the
+    manifest: The manifest templates, using a branch instead of the tag EL6,
+    ... When this is done a reference from here should be added.</remark>
+  </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..7282d0f
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/jiraissues_override.xml
@@ -0,0 +1,36 @@
+<?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>Release-Specific Problems</title>
+
+  <informaltable>
+    <tgroup cols="2">
+      <colspec colwidth="6*" colname="c1"/>
+
+      <colspec align="center" colwidth="1*" colname="c2"/>
+
+      <thead>
+        <row>
+          <entry align="center">Summary</entry>
+
+          <entry>Enea Ref</entry>
+        </row>
+      </thead>
+
+      <tbody>
+        <row>
+          <entry>Eclipse Plug-Ins for Perf and Latencytop are not functioning properly on P2041RDB target.</entry>
+
+          <entry>LXCR-6936</entry>
+        </row>
+
+        <row>
+          <entry><para>LTTng kernel tracing from Eclipse does not work due to RSE connectivity problems.</para><para>As a workaround, traces can be collected on target and visualized on Eclipse, after copying the files on the host system.</para></entry>
+
+          <entry>LXCR-7166</entry>
+        </row>
+      </tbody>
+    </tgroup>
+  </informaltable>
+</section>
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..173046b
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml
@@ -0,0 +1,267 @@
+<?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>The open source projects are continuously working on correcting
+  reported problems. Corrections to bugs detected by Enea are submitted
+  upstream, and the corrections are included in Enea Linux regardless of when
+  they will be included by the open source project. Remaining issues 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</title>
+
+    <para>The Yocto Project community uses a Bugzilla database to track
+    information on reported bugs and other issues: <ulink
+    url="https://bugzilla.yoctoproject.org">
+    https://bugzilla.yoctoproject.org</ulink>.</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-package-manager">
+    <title>Smart Package Manager</title>
+
+    <para>Installation of some packages might currently fail when installing
+    using the Smart Package Manager. An example is the qemu package. Errors
+    can e.g. be reported by smart about conflicts with files from other
+    packages.<remark>INFO It is possible to hide this setting condition hidden
+    on the section element</remark></para>
+
+    <para>The recommended solution to this problem is to install the failing
+    package using rpm, already available in enea-image-base. In order to
+    install it using rpm, first install rpm using the command <command>smart
+    install rpm</command>, then download the package to the target, and
+    finally on the target use <command>rpm -i
+    &lt;packagename&gt;.rpm</command>. If not installed, several dependencies
+    can be reported as "Failed dependencies" with lines "x is needed by y". In
+    that case, install the required packages "x" found by dependencies by
+    using the smart package manager. Add a channel to an accessible directory
+    containing all missing rpm packages. Add packages detected to be missing,
+    until all dependencies are resolved.<remark>FIXME It would be nice to add
+    also a PowerPC example with qemu failing, the example below is for
+    ARM.</remark></para>
+
+    <section>
+      <title>Example with Failing QEMU Package</title>
+
+      <para>As an example, the qemu installation can show the following
+      error.<remark>INFO It is possible to hide this setting condition hidden
+      on the section element</remark></para>
+
+      <note>
+        <para>The example below is for ARM, including the RPM names. For
+        PowerPC similar errors can occur and other packages are needed.</para>
+      </note>
+
+      <para><emphasis role="bold">error: file /var/run from install of
+      qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 conflicts with file from package
+      base-files-3.0.14-r89.0.hierofalcon</emphasis></para>
+
+      <para>A solution to this problem is to install the above qemu package
+      using rpm, already available in enea-image-base. In order to install it
+      using rpm, first install rpm using the command <command>smart install
+      rpm</command>, then download the above package from
+      &lt;build_dir&gt;/tmp/deploy/rpm/aarch64. On target, use <command>rpm -i
+      qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64.rpm</command>. If not installed,
+      several dependencies can be seen, e.g.:</para>
+
+      <programlisting>error: Failed dependencies:
+        libpixman-1-0 &gt;= 0.32.6 is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64
+        libpixman-1.so.0()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64
+        libglib-2.0.so.0()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64
+        libcap2 &gt;= 2.22 is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64
+        libglib-2.0-0 &gt;= 2.40.0 is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64
+        bluez4 &gt;= 4.101 is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64
+        libbluetooth.so.3()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64
+        libcap.so.2()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64</programlisting>
+
+      <para>Install the required packages found by dependencies by using the
+      smart package manager, as specified in the User's Guide, by adding a
+      channel to an accessible directory containing all of the above rpm
+      packages. Suggestion for installing required packages, as in the
+      following example for qemu and ARM:</para>
+
+      <programlisting>smart install bash
+        smart install libcap
+        smart install bluez4
+        smart install libpixman-1-0
+        rpm -i qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64.rpm</programlisting>
+
+      <para>Add packages detected to be missing until all dependencies are
+      resolved.</para>
+    </section>
+  </section>
+
+  <section condition="hidden" id="bugs-limitations-target-side-tools">
+    <title>Target-Side Tools</title>
+
+    <itemizedlist spacing="compact">
+      <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">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>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><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..115acb5
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/main_changes.xml
@@ -0,0 +1,53 @@
+<?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>N/A.</para>
+
+  <para>This is the first release of Enea Linux, Networking profile.</para>
+
+  <section condition="hidden" id="relinfo-changes-other">
+    <title>New Functionality/Enhancements</title>
+
+    <remark>Based in the Jira query: 'project = CPDX and fixVersion = "Enea
+    Linux 6"'</remark>
+
+    <itemizedlist spacing="compact">
+      <listitem>
+        <para>New Yocto version (<xi:include
+        href="eltf_params_updated.xml"
+        xmlns:xi="http://www.w3.org/2001/XInclude"
+        xpointer="element(Yocto_VER/1)" />). See <ulink
+        url="https://www.yoctoproject.org/downloads/core/krogoth21">https://www.yoctoproject.org/downloads/core/krogoth21</ulink>.</para>
+      </listitem>
+
+      <listitem>
+        <para>Introduction of the repo tool to manage the Git
+        repositories.</para>
+      </listitem>
+    </itemizedlist>
+
+    <para>For details, see the Git logs for the repositories specified in the
+    manifest files. See <xref linkend="relinfo-getting-source" /> for more inf
+    on repos and the manifest.</para>
+  </section>
+
+  <section condition="hidden" id="relinfo-fixed">
+    <title>Problems Fixed in this Release</title>
+
+    <para>TBD <remark>FIXME or set condition hidden</remark></para>
+  </section>
+
+  <section condition="hidden" id="relinfo-added-drivers">
+    <title>Added Drivers</title>
+
+    <para>TBD <remark>FIXME or set condition hidden</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..9c5aa95
--- /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="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..e94d012
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/system_requirements.xml
@@ -0,0 +1,162 @@
+<?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.1 documents:
+  Yocto Project Start <ulink
+  url="http://www.yoctoproject.org/docs/2.1/yocto-project-qs/yocto-project-qs.html#yp-resources">
+  http://www.yoctoproject.org/docs/2.1/yocto-project-qs/yocto-project-qs.html#yp-resources</ulink>
+  and the Yocto Project Reference Manual <ulink
+  url="http://www.yoctoproject.org/docs/2.1/ref-manual/ref-manual.html#intro-requirements">
+  http://www.yoctoproject.org/docs/2.1/ref-manual/ref-manual.html#intro-requirements</ulink>.
+  If needed, replace the Yocto version in the link(s) 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, as specified in the <emphasis
+          role="bold">Enea Linux Release Information</emphasis>.</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. Currenly, Eclipse
+          generally recommends at least Java 6 JRE/JDK. More information
+          regarding operating environments for Eclipse, is provided in the
+          <emphasis>Eclipse Project Release Notes</emphasis> for the version
+          used. This can usually be found via
+          http://www.eclipse.org/eclipse/development/readme_eclipse_version.
+          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 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