Initial commit

7 files changed, 1168 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..15d676c
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/about_release.xml
@@ -0,0 +1,469 @@
+<?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="../../s_docsrc_common/pardoc-distro.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 distribution using the branch <xi:include
+  href="../../s_docsrc_common/pardoc-distro.xml"
+  xmlns:xi="http://www.w3.org/2001/XInclude"
+  xpointer="element(Yocto_NAME/1)" />.<remark>INFO Yocto distro autopicked
+  from poky.ent as DISTRO_NAME_NO_CAP</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, scripts, etc for building the
+            distro 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)</entry>
+          </row>
+
+          <row>
+            <entry>Eclipse executable plus development tools for command line
+            and Eclipse</entry>
+          </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>was
+        EneaLinux_HOST_VER</remark></para>
+      </listitem>
+    </itemizedlist>
+  </section>
+
+  <section id="relinfo-supported-versions">
+    <title>Supported Versions</title>
+
+    <informaltable>
+      <tgroup cols="2">
+        <thead valign="bottom">
+          <row>
+            <entry>Item</entry>
+
+            <entry>Version</entry>
+          </row>
+        </thead>
+
+        <tbody>
+          <row>
+            <entry><para>Yocto</para></entry>
+
+            <entry><xi:include href="../../s_docsrc_common/pardoc-distro.xml"
+            xmlns:xi="http://www.w3.org/2001/XInclude"
+            xpointer="element(Yocto_VER/1)" /> (<xi:include
+            href="../../s_docsrc_common/pardoc-distro.xml"
+            xmlns:xi="http://www.w3.org/2001/XInclude"
+            xpointer="element(Yocto_NAME/1)" />)<remark>INFO: Auto-fetched
+            from poky.ent via pardoc-distro.xml</remark></entry>
+          </row>
+
+          <row>
+            <entry>Poky source</entry>
+
+            <entry><xi:include href="../../s_docsrc_common/pardoc-distro.xml"
+            xmlns:xi="http://www.w3.org/2001/XInclude"
+            xpointer="element(Poky_VER/1)" /><remark>INFO: Auto-fetched from
+            poky.ent via pardoc-distro.xml</remark></entry>
+          </row>
+
+          <row>
+            <entry>GCC version</entry>
+
+            <entry>5.3<remark>was EneaLinux_GCC_VER Not in poky.ent
+            </remark></entry>
+          </row>
+
+          <row>
+            <entry>Linux kernel version<remark>was EneaLinux_KERNEL_VER Not in
+            poky.ent</remark></entry>
+
+            <entry><para>3.12 (P2041RDB &amp; LS1021a-IoT)</para><para>4.4
+            (QEmu targets)</para></entry>
+          </row>
+
+          <row>
+            <entry>Eclipse</entry>
+
+            <entry>4.5 (Mars)<remark>was Eclipse_VER and was Eclipse_NAME Not
+            in poky.ent</remark></entry>
+          </row>
+
+          <row>
+            <entry>Packages</entry>
+
+            <entry>See <xref linkend="relinfo-packages" /></entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </informaltable>
+  </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 and Provider</entry>
+
+              <entry>Reference</entry>
+            </row>
+          </thead>
+
+          <tbody>
+            <row>
+              <entry>Packages in Enea Linux images</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>
+
+            <row>
+              <entry>Tools in the Eclipse tarball provided with Enea
+              Linux</entry>
+
+              <entry><para>See the <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></entry>
+            </row>
+
+            <row>
+              <entry>Packages provided by Yocto</entry>
+
+              <entry><para>See the Yocto "Release Notes" <xi:include
+              href="../../docsrc_common/pardoc-distro.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude"
+              xpointer="element(ULINK_YOCTO_RELEASE_NOTES/1)" /></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-provided-drivers">
+    <title>Supported Drivers</title>
+
+    <informaltable>
+      <tgroup cols="2">
+        <colspec align="left" colwidth="3*" />
+
+        <colspec align="center" colwidth="2*" />
+
+        <thead>
+          <row>
+            <entry>Driver</entry>
+
+            <entry>P2041RDB</entry>
+          </row>
+        </thead>
+
+        <tbody>
+          <row>
+            <entry>Ethernet</entry>
+
+            <entry>X</entry>
+          </row>
+
+          <row>
+            <entry>I2C</entry>
+
+            <entry>X</entry>
+          </row>
+
+          <row>
+            <entry>SPI</entry>
+
+            <entry>X</entry>
+          </row>
+
+          <row>
+            <entry>PCI Express</entry>
+
+            <entry>X</entry>
+          </row>
+
+          <row>
+            <entry>USB</entry>
+
+            <entry>X</entry>
+          </row>
+
+          <row>
+            <entry>Flash</entry>
+
+            <entry>X</entry>
+          </row>
+
+          <row>
+            <entry>SD/SDHC/SDXC</entry>
+
+            <entry>X</entry>
+          </row>
+
+          <row>
+            <entry>RTC</entry>
+
+            <entry>X</entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </informaltable>
+  </section>
+
+  <section id="relinfo-documentation">
+    <title>Provided Documentation</title>
+
+    <para>The following Enea Linux manuals are available:</para>
+
+    <itemizedlist spacing="compact">
+      <listitem>
+        <para>README.htm - top page of the documentation<remark>FIXME Needs to
+        be fixed (= created and added to make dist). OR remove this
+        line?</remark></para>
+      </listitem>
+
+      <listitem>
+        <para>README - text files describing various details like build- and
+        boot-commands - the commands are also seen in <xref
+        linkend="relinfo-build-boot" />.</para>
+      </listitem>
+
+      <listitem>
+        <para><trademark class="registered">Enea</trademark> Linux Release
+        Information (this document)</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><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> - Generic version included in this distribution</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> - Generic version included in this distribution</para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold"><trademark
+        class="registered">Enea</trademark> Linux Real-Time Guide</emphasis>
+        can be read at <ulink
+        url="http://linuxrealtime.org">http://linuxrealtime.org</ulink>.</para>
+      </listitem>
+    </itemizedlist>
+
+    <para>In addition to the local versions of the generic guides reached via
+    the above links, you can also read the latest versions via the direct
+    online links below. When accessing them via the links below, you need to
+    logon to the portal.enea.com. These online versions may be
+    updated/improved asynchronously with the releases.<remark>INFO: Should be
+    accessable to all customer's with Enea Linux 6 or later</remark>
+    <remark>INFO: On portal, generic guides can NOT link TO the distro
+    specific guides, but the distro specific guides can link to the generic -
+    HOWEVER these links (found above) will go to the versions inside the
+    delivery, instead of to the latest versions.</remark></para>
+
+    <itemizedlist spacing="compact">
+      <listitem>
+        <para><ulink
+        url="https://portal.enea.com/wp-content/uploads/_mediavault/book-enea-linux-application-dev-guide.pdf">Enea
+        Linux Application Development Guide</ulink> - Latest generic version
+        online</para>
+      </listitem>
+
+      <listitem>
+        <para><ulink
+        url="https://portal.enea.com/wp-content/uploads/_mediavault/book-enea-linux-platforms-dev-guide.pdf">Enea
+        Linux Platforms Development Guide</ulink> - Latest generic version
+        online</para>
+      </listitem>
+    </itemizedlist>
+
+    <para>How to use Eclipse is described inside the Enea Linux user's guides.
+    Eclipse's own documentation is available in directory
+    <filename>eclipse/readme</filename>.</para>
+  </section>
+
+  <section 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:</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>
+
+      <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 <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 id="relinfo-excluded">
+    <title>Intentional Limitations</title>
+
+    <para>The following functionality supported in other Enea Linux releases
+    has been excluded in this release:<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>
\ 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..d1226b9
--- /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="../../s_docsrc_common/pardoc-distro.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..653f943
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/build_boot_template.xml
@@ -0,0 +1,26 @@
+<?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 FILE! A new build_boot.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/getting_enea_linux.xml b/doc/book-enea-linux-release-info/doc/getting_enea_linux.xml
new file mode 100644
index 0000000..f25c1a5
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/getting_enea_linux.xml
@@ -0,0 +1,103 @@
+<?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:</para>
+
+        <para><programlisting>$ curl https://storage.googleapis.com/git-repo-downloads/repo &gt; ~/bin/repo
+$ chmod a+x ~/bin/repo</programlisting>The instruction assumes that ~/bin
+        exists and is included in the PATH variable.</para>
+      </listitem>
+
+      <listitem>
+        <para>Use the repo tool to download the source:<remark>FIXME: Before
+        final release the tag for the manifest must be set in Makefile as
+        MANIFESTHASH, typically something like refs/tags/EL6. Before that, a
+        generic branch name is used instead, e.g. krogoth in
+        Makefile</remark></para>
+
+        <para><programlisting>$ mkdir enea-linux
+$ cd enea-linux
+$ repo init -u  <xi:include href="../../s_docsrc_common/pardoc-distro.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude"
+              xpointer="element(EneaLinux_MANIFESTURL/1)" /> \
+            -b <xi:include href="../../s_docsrc_common/pardoc-distro.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude"
+              xpointer="element(EneaLinux_MANIFESTHASH/1)" /> \
+            -m &lt;manifest file&gt;
+$ repo sync</programlisting></para>
+
+        <para>The parameter &lt;manifest file&gt; depends on the target. See
+        the following table:</para>
+
+        <informaltable>
+          <tgroup cols="2">
+            <thead>
+              <row>
+                <entry align="center">Target</entry>
+
+                <entry align="center">Manifest file</entry>
+              </row>
+            </thead>
+
+            <tbody>
+              <row>
+                <entry>P2041RDB</entry>
+
+                <entry><para>p2041rdb/default.xml</para></entry>
+              </row>
+            </tbody>
+          </tgroup>
+        </informaltable>
+      </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/known_bugs_and_limitations.xml b/doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml
new file mode 100644
index 0000000..5058404
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml
@@ -0,0 +1,453 @@
+<?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 have been
+  upstreamed, and the corrections been included in Enea Linux regardless of
+  when they will be included by the open source project. Remaining issues are
+  listed below, and workarounds to some of the problems are described in
+  chapter <emphasis>Troubleshooting</emphasis> in the <olink
+  targetdoc="book_enea_linux_users_guide"
+  targetptr="book_enea_linux_users_guide"><trademark
+  class="registered">Enea</trademark> Linux User's Guide</olink>.</para>
+
+  <section id="bugs-limitations-yocto">
+    <title>Yocto</title>
+
+    <para>Open source projects often use bug databases for much more than
+    tracking bugs. The Yocto Project's Bugzilla database also functions as a
+    feature tracking program, both for the current release and for future
+    releases, and a way to track non-software issues, like documentation
+    changes.</para>
+
+    <para>The following page shows a sampling of the database: <ulink
+    url="https://www.yoctoproject.org/tools-resources/bugs">https://www.yoctoproject.org/tools-resources/bugs</ulink>.</para>
+
+    <para>For the full database, visit <ulink
+    url="https://bugzilla.yoctoproject.org">https://bugzilla.yoctoproject.org</ulink>.</para>
+  </section>
+
+  <section 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.</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 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.</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.</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 id="bugs-limitations-eclipse">
+    <title>Eclipse Tools</title>
+
+    <para>The Eclipse tools provided together with Enea Linux are part of the
+    Yocto 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:</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 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 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:</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 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 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 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..da302c1
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/main_changes.xml
@@ -0,0 +1,50 @@
+<?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 in the Enea
+  Linux release compared to the previous release (Enea Linux 5.0-ppc).</para>
+
+  <section 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="../../s_docsrc_common/pardoc-distro.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 id="relinfo-fixed">
+    <title>Problems Fixed in this Release</title>
+
+    <para>TBD <remark>FIXME or set condition hidden</remark></para>
+  </section>
+
+  <section 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>
\ No newline at end of file
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..587b812
--- /dev/null
+++ b/doc/book-enea-linux-release-info/doc/prerequisites.xml
@@ -0,0 +1,49 @@
+<?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 some packages
+  to be installed on your Linux development host. See the list of Required
+  Packages for Host Development System, found in the Yocto 2.1 document:
+  <ulink
+  url="https://www.yoctoproject.org/docs/2.1/ref-manual/ref-manual.html#required-packages-for-the-host-development-system">https://www.yoctoproject.org/docs/2.1/ref-manual/ref-manual.html#required-packages-for-the-host-development-system</ulink>.
+  If needed, replace 2.1 with the actual Yocto version in your Enea Linux
+  distribution.<remark>Sorry by the list in the Yocto document do not seem to
+  be enough at all at least for platform building! Therefore we need to add a
+  complete list here, and we actually have a bigger list than we needed, but
+  it's better to have more and not be needed than to lack
+  information.</remark></para>
+
+  <para>Install Host Packages</para>
+
+  <note>
+    <para>The list below is generic and might contain packages that are not
+    necessary. Additional packages might be required to build for some
+    targets. See the Enea Linux Release Information if more packages are
+    needed and which hosts have been tested by Enea for this Enea Linux
+    release.<remark>QUEST: Are the lists below ok? The lists below try to
+    cover ALL normal use cases for both ApplGuide and PlatfGuide, incl.
+    Eclipse, instead of limiting to some use case. Easier to keep
+    updated.</remark></para>
+  </note>
+
+  <section id="inst-host-packages-ubuntu-debian">
+    <title>Ubuntu 14.04 LTS, 64-bit</title>
+
+    <para>Ensure the system is up-to-date:</para>
+
+    <programlisting>$ sudo apt-get update</programlisting>
+
+    <para>For a supported <emphasis role="bold">Ubuntu</emphasis><indexterm>
+        <primary>Ubuntu</primary>
+      </indexterm> distribution you need the following packages:</para>
+
+    <programlisting># 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</programlisting>
+  </section>
+</chapter>
\ No newline at end of file