7 files changed, 195 insertions, 526 deletions

diff --git a/doc/book-enea-nfv-access-release-info/doc/about_release.xml b/doc/book-enea-nfv-access-release-info/doc/about_release.xml
index 203637c..a470845 100644
--- a/doc/book-enea-nfv-access-release-info/doc/about_release.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/about_release.xml
@@ -4,8 +4,8 @@
 <chapter id="relinfo-about-release">
   <title>About This Release</title>
 
-  <para>This release of Enea NFV Access <xi:include href="eltf_params_updated.xml"
-  xmlns:xi="http://www.w3.org/2001/XInclude"
+  <para>This release of Enea NFV Access <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 NFV Access distribution for a selected set of targets. This release is
   generated from the yocto <xi:include href="eltf_params_updated.xml"
@@ -22,146 +22,101 @@
   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 id="release-content">
+    <title>NFV Access Release content</title>
+
+    <para>The NFV Access 1.0 Release contains along with other items,
+    documentation, pre-built kernels and images, a bootloader and a
+    SDK.</para>
+
+    <para>The directories structure is detailed below:</para>
+
+    <programlisting>-- documentation/
+   /* NFV Access documentation */
+-- inteld1521/
+   /* artifacts for the host side */
+        -- deb/
+           /* deb packages */
+        -- images/
+            -- enea-image-virtualization-host
+               /* precompiled artifacts for the Host release image */
+                -- various artifacts
+            -- enea-image-virtualization-host-sdk
+               /* precompiled artifacts for the Host SDK image.
+               The SDK image contains userspace tools and kernel
+               configurations necessary for developing, debugging
+               and profiling applications and kernel modules */
+                -- various artifacts
+        -- sdk
+           /* NFV Access SDK for the host */
+                -- enea-glibc-x86_64-enea-image-virtualization-host-sdk /
+                   -corei7-64-toolchain-7.0.sh
+                   /* self-extracting archive installing
+                   cross-compilation toolchain for the host */
+-- qemux86-64
+   /* artifacts for the guest side */
+        -- deb/
+           /* deb packages */
+        -- images/
+            -- enea-image-virtualization-guest
+               /* precompiled artifacts for the Guest image */
+                -- various artifacts
+        -- sdk
+           /* NFV Access SDK for the guest */
+                -- enea-glibc-x86_64-enea-image-virtualization-guest-sdk /
+                   -core2-64-toolchain-7.0.sh
+                   /* self-extracting archive installing cross-compilation
+                   toolchain for the guest (QEMU x86-64) */
+</programlisting>
+
+    <para>For each combination of image and target, the following set of
+    artifacts is available:</para>
+
+    <programlisting>-- bzImage
+   /* kernel image */
+-- bzImage-&lt;target&gt;.bin
+   /* kernel image, same as above */
+-- config-&lt;target&gt;.config
+   /* kernel configuration file */
+-- core-image-minimal-initramfs-&lt;target&gt;.cpio.gz
+   /* cpio archive of the initramfs */
+-- core-image-minimal-initramfs-&lt;target&gt;.qemuboot.conf
+   /* qemu config file for the initramfs image */
+-- &lt;image-name&gt;-&lt;target&gt;.ext4
+   /* EXT4 image of the rootfs */
+-- &lt;image-name&gt;-&lt;target&gt;.hddimg
+   /* msdos filesystem containing syslinux, kernel, initrd and rootfs image */
+-- &lt;image-name&gt;-&lt;target&gt;.iso
+   /* CD .iso image */
+-- &lt;image-name&gt;-&lt;target&gt;.qemuboot.conf
+   /* qemu config file for the image */
+-- &lt;image-name&gt;-&lt;target&gt;.tar.gz
+   /* tar archive of the image */
+-- &lt;image-name&gt;-&lt;target&gt;.wic
+   /* Wic image */
+-- microcode.cpio
+   /* kernel microcode data */
+-- modules-&lt;target&gt;.tgz
+   /* external kernel modules */
+-- ovmf.*.qcow2
+   /* ovmf firmware for uefi support in qemu */
+-- rmc.db
+   /* Central RMC Database */
+-- systemd-bootx64.efi
+   /* systemd-boot EFI file */
+-- grub-efi-bootx64.efi
+   /* GRUB EFI file */</programlisting>
   </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="../../s_doceneacommon/doc/supported_host_environment.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
 
   <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 NFV Access</entry>
-
-              <entry><para>See the <olink
-              targetdoc="book_enea_linux_open_source"
-              targetptr="book_enea_linux_open_source"><trademark
-              class="registered">Enea</trademark> NFV Access Open Source
-              Report</olink></para></entry>
-            </row>
-
-          </tbody>
-        </tgroup>
-      </informaltable></para>
-  </section>
-
-  <section id="relinfo-provided-sdk">
-    <title>Provided Toolchain/s (SDK)</title>
+  <section condition="hidden" 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
@@ -175,120 +130,42 @@
   <section id="relinfo-documentation">
     <title>Provided Documentation</title>
 
-    <para>The following Enea NFV Access manuals are available:</para>
+    <para>Enea NFV Access is provided with the following set of
+    documents:</para>
 
     <itemizedlist spacing="compact">
       <listitem>
-        <para><trademark class="registered">Enea</trademark> NFV Access 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> NFV Access 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> NFV Access Application Development
-        Guide</olink></para>
+        <para><olink targetdoc="book_enea_nfv_access_guide"
+        targetptr="book_enea_nfv_access_guide">Enea NFV Access Guide</olink>
+        &ndash; A document describing how to use ENFV Access, as well as use
+        cases and benchmark results.</para>
       </listitem>
 
       <listitem>
-        <para><trademark class="registered">Enea</trademark> NFV Access Networking
-        Profile Guide</para>
+        <para>Enea NFV Access Release Information &ndash; This document,
+        describing the Enea NFV Access release content</para>
       </listitem>
 
       <listitem>
-        <para><olink targetdoc="book_enea_linux_open_source"
-        targetptr="book_enea_linux_open_source"><trademark
-        class="registered">Enea</trademark> NFV Access Open Source
-        Report</olink></para>
+        <para><olink targetdoc="book_enea_nfv_access_open_source"
+        targetptr="book_enea_nfv_access_open_source">Enea NFV Access Open
+        Source Report</olink> &ndash; A document containing the open source
+        and license information pertaining to packages provided with Enea NFV
+        Access 1.0.</para>
       </listitem>
 
       <listitem>
-        <para><olink targetdoc="book_enea_linux_eclipse_open_source"
-        targetptr="book_enea_linux_eclipse_open_source"><trademark
-        class="registered">Enea</trademark> NFV Access Eclipse Open Source
-        Report</olink></para>
+        <para>Enea NFV Access Test Report &ndash; The document that summarizes
+        the test results for the Enea NFV Access release.</para>
       </listitem>
 
       <listitem>
-        <para><trademark class="registered">Enea</trademark> NFV Access Test
-        Report</para>
-      </listitem>
-
-      <listitem>
-        <para><trademark class="registered">Enea</trademark> NFV Access Real-Time
-        Guide can be read at <ulink
-        url="http://linuxrealtime.org">http://linuxrealtime.org</ulink>.</para>
+        <para>Enea NFV Access Security Report &ndash; The document that lists
+        all security fixes included in the Enea NFV Access 1.0 release.</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 NFV Access</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 NFV Access 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>
+  <xi:include href="../../s_doceneacommon/doc/security_fixes.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
 </chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-release-info/doc/book.xml b/doc/book-enea-nfv-access-release-info/doc/book.xml
index 9c96184..ea37252 100644
--- a/doc/book-enea-nfv-access-release-info/doc/book.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/book.xml
@@ -1,18 +1,35 @@
 <?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" [
-]>
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
 <book id="book_enea_nfv_access_release_info">
-  <title><trademark class="registered">Enea</trademark> NFV Access 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_nfv_access.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>
+  <title><trademark class="registered">Enea</trademark> NFV Access Release
+  Information</title>
+
+  <subtitle>Release Version <xi:include href="eltf_params_updated.xml"
+  xmlns:xi="http://www.w3.org/2001/XInclude"
+  xpointer="element(EneaLinux_REL_VER/1)" /></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="system_requirements_prerequisites.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+  <xi:include href="getting_enea_nfv_access.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>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-release-info/doc/eltf_params_updated.xml b/doc/book-enea-nfv-access-release-info/doc/eltf_params_updated.xml
index 627e923..f6bd068 100644
--- a/doc/book-enea-nfv-access-release-info/doc/eltf_params_updated.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/eltf_params_updated.xml
@@ -89,10 +89,10 @@ repo sync</programlisting></para>
   </section>
 
   <section id="eltf-target-tables-section">
-    <title>Supported Targets with Parameters</title>
+    <title>Supported Reference Boards with Parameters</title>
 
-    <para>The tables below describes the target(s) supported in this Enea
-    NFV Access release.</para>
+    <para>The tables below describes the target(s) supported in this Enea NFV
+    Access release.</para>
 
     <section id="eltf-target-table-p2041rdb">
       <title>MACHINE p2041rdb - Information</title>
diff --git a/doc/book-enea-nfv-access-release-info/doc/getting_enea_nfv_access.xml b/doc/book-enea-nfv-access-release-info/doc/getting_enea_nfv_access.xml
index 9436fab..664766d 100644
--- a/doc/book-enea-nfv-access-release-info/doc/getting_enea_nfv_access.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/getting_enea_nfv_access.xml
@@ -4,16 +4,17 @@
 <chapter id="relinfo-getting-enea-nfv-access">
   <title>Getting Enea NFV Access</title>
 
-  <para>Enea NFV Access is available as both pre-built binary images and source
-  code. Both serve a specific purpose and each have their advantages. However,
-  using the pre-built binary images allows for getting up and running faster.
-  Please refer to the sections below for details on how to get Enea NFV Access as
-  pre-built binary images or source code.</para>
+  <para>Enea NFV Access is available as both pre-built binary images and
+  source code. Both serve a specific purpose and each have their advantages.
+  However, using the pre-built binary images allows for getting up and running
+  faster. Please refer to the sections below for details on how to get Enea
+  NFV Access as pre-built binary images or source code.</para>
 
   <section id="relinfo-getting-pre-built-images">
     <title>Getting Pre-built Binaries</title>
 
-    <para>Enea NFV Access pre-built binaries are available for download on <ulink
+    <para>Enea NFV Access pre-built binaries are available for download on
+    <ulink
     url="https://portal.enea.com/login/?redirect_to=https%3A%2F%2Fportal.enea.com%2F">Enea
     Download Portal</ulink>. Log in using the credentials provided. Using the
     menu, browse to the <emphasis role="bold">Linux</emphasis> section. You
@@ -21,19 +22,19 @@
     and the <emphasis role="bold">Online Documentation</emphasis>
     section.</para>
 
-    <para>The Files section lists each Enea NFV Access distribution, one for each
-    version and profile, as a separate download package. Clicking on the name
-    of the distribution will open a new page, which presents further details
-    about the content of the release and a list of downloadable archives, one
-    for each hardware target included in the release. Each archive provides
-    the following content:</para>
+    <para>The Files section lists each Enea NFV Access distribution, one for
+    each version and profile, as a separate download package. Clicking on the
+    name of the distribution will open a new page, which presents further
+    details about the content of the release and a list of downloadable
+    archives, one for each hardware target included in the release. Each
+    archive provides the following content:</para>
 
     <itemizedlist>
       <listitem>
         <para><emphasis>images</emphasis> directory &ndash; this directory
         includes the binary image files needed to boot the target with Enea
-        NFV Access. This includes the kernel, the root file system, device tree,
-        etc.</para>
+        NFV Access. This includes the kernel, the root file system, device
+        tree, etc.</para>
       </listitem>
 
       <listitem>
@@ -57,28 +58,28 @@
     <itemizedlist>
       <listitem>
         <para><emphasis role="bold">Enea NFV Access Developer&rsquo;s
-        Guide</emphasis> -intended for Enea NFV Access developers, who
-        want to configure and build customized NFV Access kernel images for
-        embedded system targets, using the Yocto configuration and build
-        system.</para>
+        Guide</emphasis> -intended for Enea NFV Access developers, who want to
+        configure and build customized NFV Access kernel images for embedded
+        system targets, using the Yocto configuration and build system.</para>
       </listitem>
 
       <listitem>
         <para><emphasis role="bold">Enea NFV Access Application Developer's
-        Guide</emphasis> - dedicated to Enea NFV Access application developers, who
-        want to build and run applications.</para>
+        Guide</emphasis> - dedicated to Enea NFV Access application
+        developers, who want to build and run applications.</para>
       </listitem>
 
       <listitem>
-        <para><emphasis role="bold">Enea NFV Access Guide</emphasis>
-        - provides further information meant to get the most out of the
+        <para><emphasis role="bold">Enea NFV Access Guide</emphasis> -
+        provides further information meant to get the most out of the
         virtualization features.</para>
       </listitem>
 
       <listitem>
-        <para><emphasis role="bold">Enea NFV Access Open Source Report</emphasis> -
-        contains the open source and license information pertaining to
-        packages provided with this release of Enea NFV Access.</para>
+        <para><emphasis role="bold">Enea NFV Access Open Source
+        Report</emphasis> - contains the open source and license information
+        pertaining to packages provided with this release of Enea NFV
+        Access.</para>
       </listitem>
 
       <listitem>
@@ -102,8 +103,8 @@
 
     <para>Enea NFV Access sources are available for cloning from a set of Git
     repositories on <ulink url="https://git.enea.com">git.enea.com</ulink>.
-    Since Enea NFV Access requires multiple repositories, Google Repo tool is used
-    in order to manage configurations and make the cloning step simpler.
+    Since Enea NFV Access requires multiple repositories, Google Repo tool is
+    used in order to manage configurations and make the cloning step simpler.
     Google Repo tool uses files, known as manifests, which store a list of
     tuples (repository URL, version). The Repo tool is then used to traverse
     the list of tuples in the manifest file and clone the specified versions
@@ -147,8 +148,8 @@ id_rsa.pub</programlisting>
     <section id="getting-source-code-step-two">
       <title>Get Sources</title>
 
-      <para>To use the Repo tool to download the sources for Enea NFV Access, do
-      the following:</para>
+      <para>To use the Repo tool to download the sources for Enea NFV Access,
+      do the following:</para>
 
       <orderedlist>
         <listitem condition="hidden">
diff --git a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
index 44c76e1..e3f068a 100644
--- a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
@@ -6,221 +6,16 @@
 
   <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 NFV Access regardless of when
-  they will be included by the open source project. Remaining issues are
+  upstream, and the corrections are included in Enea NFV Access 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
- NFV Access 1.0" and needs to be adapted when a release info for another ENFV Access version
-  changes.</remark></para>
+  NFV Access 1.0" and needs to be adapted when a release info for another ENFV
+  Access 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>
+  <section id="release-specific-limitations">
+    <title>Release-Specific Limitations</title>
 
     <itemizedlist spacing="compact">
       <listitem>
@@ -234,28 +29,7 @@
       </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>
+        <para></para>
       </listitem>
     </itemizedlist>
   </section>
diff --git a/doc/book-enea-nfv-access-release-info/doc/main_changes.xml b/doc/book-enea-nfv-access-release-info/doc/main_changes.xml
index 18bb93f..ebe69c6 100644
--- a/doc/book-enea-nfv-access-release-info/doc/main_changes.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/main_changes.xml
@@ -6,18 +6,18 @@
 
   <para>N/A.</para>
 
-  <para>This is the first release of Enea NFV Access, Networking profile.</para>
+  <para>This is the first release of Enea NFV Access, Networking
+  profile.</para>
 
   <section condition="hidden" id="relinfo-changes-other">
-    <title>New Functionality/Enhancements</title>
+    <title>New Features</title>
 
     <remark>Based in the Jira query: 'project = CPDX and fixVersion = "Enea
     NFV Access 1.0"'</remark>
 
     <itemizedlist spacing="compact">
       <listitem>
-        <para>New Yocto version (<xi:include
-        href="eltf_params_updated.xml"
+        <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>
@@ -34,20 +34,20 @@
     on repos and the manifest.</para>
   </section>
 
-  <section condition="hidden" id="relinfo-fixed">
-    <title>Problems Fixed in this Release</title>
+  <section id="packages">
+    <title>Provided Packages</title>
 
-    <para>TBD <remark>FIXME or set condition hidden</remark></para>
+    <para></para>
   </section>
 
-  <section condition="hidden" id="relinfo-added-drivers">
-    <title>Added Drivers</title>
+  <section id="relinfo-backward-compat">
+    <title>Compatibility</title>
 
-    <para>TBD <remark>FIXME or set condition hidden</remark></para>
+    <para></para>
   </section>
 
   <!--
   <xi:include href="pkgdiff_generated.xml"
               xmlns:xi="http://www.w3.org/2001/XInclude" />
   -->
-</chapter>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-release-info/doc/prerequisites.xml b/doc/book-enea-nfv-access-release-info/doc/system_requirements_prerequisites.xml
index 7ae2eb6..f598693 100644
--- a/doc/book-enea-nfv-access-release-info/doc/prerequisites.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/system_requirements_prerequisites.xml
@@ -1,10 +1,10 @@
 <?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>
+<chapter id="sys-req-prerequisites">
+  <title>System Requirements and Prerequisites</title>
 
-  <para>Building Enea NFV Access or compiling applications requires that your git
+  <para>Using Enea NFV Access or compiling applications requires that your git
   environment be setup properly and for certain packages to be installed on
   your NFV Access development host.</para>