7 files changed, 392 insertions, 204 deletions

diff --git a/doc/book-enea-linux-user-guide/doc/application_development.xml b/doc/book-enea-linux-user-guide/doc/application_development.xml
index 3458d39..0e2edf4 100644
--- a/doc/book-enea-linux-user-guide/doc/application_development.xml
+++ b/doc/book-enea-linux-user-guide/doc/application_development.xml
@@ -146,7 +146,7 @@ MODULE_LICENSE("GPL");</programlisting>
     environment. For this, see <xref linkend="install_el_sdk" />.</para>
 
     <para>The following section, <ulink
-    url="http://www.yoctoproject.org/docs/2.3/sdk-manual/sdk-manual.html#sdk-use-devtool-to-add-an-application">Use
+    url="http://www.yoctoproject.org/docs/2.5/sdk-manual/sdk-manual.html#sdk-use-devtool-to-add-an-application">Use
     devtool add to Add an Application</ulink>, in Yocto Project Software
     Development Kit (SDK) Developer's Guide, explains how to use devtool to
     generate recipes from existing application code, edit and build recipes,
@@ -279,4 +279,4 @@ NOTE: Your packages are in &lt;SDK_dir&gt;/tmp/deploy/deb</programlisting>
       </listitem>
     </orderedlist>
   </section>
-</chapter>
\ No newline at end of file
+</chapter>
diff --git a/doc/book-enea-linux-user-guide/doc/eltf_params_updated.xml b/doc/book-enea-linux-user-guide/doc/eltf_params_updated.xml
index 0543f86..0efa6af 100644
--- a/doc/book-enea-linux-user-guide/doc/eltf_params_updated.xml
+++ b/doc/book-enea-linux-user-guide/doc/eltf_params_updated.xml
@@ -42,17 +42,17 @@ export PATH=~/bin:$PATH</programlisting></para>
     correct also compared to the "previous" REL VER in pardoc-distro.xml
     "prev_baseline".</bridgehead>
 
-    <para id="EneaLinux_REL_VER"><phrase>7</phrase></para>
+    <para id="EneaLinux_REL_VER"><phrase>8</phrase></para>
 
-    <para id="Yocto_VER"><phrase>2.3</phrase></para>
+    <para id="Yocto_VER"><phrase>2.5</phrase></para>
 
-    <para id="Yocto_NAME"><phrase>pyro</phrase></para>
+    <para id="Yocto_NAME"><phrase>sumo</phrase></para>
 
     <para id="ULINK_YOCTO_PROJECT_DOWNLOAD"><ulink
-    url="http://www.yoctoproject.org/downloads/core/pyro23">http://www.yoctoproject.org/downloads/core/pyro23</ulink></para>
+    url="http://www.yoctoproject.org/downloads/core/pyro23">http://www.yoctoproject.org/downloads</ulink></para>
 
     <para id="ULINK_ENEA_LINUX_URL"><ulink
-    url="http://linux.enea.com/EneaLinux7.0">http://linux.enea.com/EneaLinux7.0</ulink></para>
+    url="http://linux.enea.com/EneaLinux8.0">http://linux.enea.com/EneaLinux8.0</ulink></para>
 
     <bridgehead>A programlisting, ID "eltf-repo-cloning-enea-linux". Use
     $MACHINE/default.xml as parameter, where MACHINE is one of the target
@@ -61,7 +61,7 @@ export PATH=~/bin:$PATH</programlisting></para>
     <para id="eltf-repo-cloning-enea-linux"><programlisting>mkdir enea-linux
 cd enea-linux
 repo init -u git@git.enea.com:linux/manifests/el_manifests-standard.git \
-    -b refs/tags/Enea_Linux_7.0_RC4 -m $MACHINE/default.xml
+    -b refs/tags/Enea_Linux_8.0 -m intel-corei7-64/default.xml
 repo sync</programlisting></para>
 
     <bridgehead>A table with ONE row, only the row with ID
@@ -87,78 +87,227 @@ repo sync</programlisting></para>
     target parameters in each target subsection table.</bridgehead>
   </section>
 
-  <section id="eltf-target-tables-section">
+  <section id="eltf-machine-tables-section">
     <title>Supported Targets with Parameters</title>
 
     <para>The section(s) below describe the target(s) supported in this Enea
     Linux release.</para>
 
-    <section id="eltf-target-table-rpi">
-      <title>MACHINE raspberry pi 3 - Information</title>
+    <section id="eltf-target-tables-section">
+      <title>MACHINE Information</title>
 
-      <para><informaltable>
-          <tgroup cols="2">
-            <colspec colwidth="6*" />
+      <para>The table(s) below describes the target(s) supported in this Enea
+      Linux release.</para>
 
-            <colspec colwidth="9*" />
+      <table>
+        <title>MACHINE Information Intel Xeon D</title>
 
-            <tbody>
-              <row>
-                <entry>Target official name</entry>
+        <tgroup cols="2">
+          <colspec align="center" />
 
-                <entry>Raspberry Pi 3</entry>
-              </row>
+          <thead>
+            <row>
+              <entry align="center">Component</entry>
 
-              <row>
-                <entry>Architecture and Description</entry>
+              <entry align="center">Description</entry>
+            </row>
+          </thead>
 
-                <entry>ARM Cortex-A53 (ARMv8)</entry>
-              </row>
+          <tbody>
+            <row>
+              <entry align="left">Target official name</entry>
 
-              <row>
-                <entry>Link to target datasheet</entry>
+              <entry>Intel Xeon D</entry>
+            </row>
 
-                <entry>See <ulink
-                url="https://www.raspberrypi.org/documentation/hardware/raspberrypi/bcm2837/README.md">link
-                to Raspberry Pi's datasheet</ulink></entry>
-              </row>
+            <row>
+              <entry align="left">Architecture and Description</entry>
 
-              <row>
-                <entry>Poky version</entry>
+              <entry>x86-64</entry>
+            </row>
 
-                <entry>Git-commit-id:
-                2021e95bcd986e5bcfe457da5c3e16d60241d050</entry>
-              </row>
+            <row>
+              <entry align="left">Link to target datasheet</entry>
 
-              <row>
-                <entry>GCC version</entry>
+              <entry><ulink
+              url="https://www.intel.com/content/www/us/en/processors/xeon/xeon-d-1500-datasheet-vol-1.html">Intel
+              Xeon D datasheet</ulink></entry>
+            </row>
 
-                <entry>6.3</entry>
-              </row>
+            <row>
+              <entry align="left">Poky version</entry>
 
-              <row>
-                <entry>Linux Kernel Version</entry>
+              <entry>Git-commit-id: TBD</entry>
+            </row>
 
-                <entry>4.9</entry>
-              </row>
+            <row>
+              <entry align="left">GCC version</entry>
 
-              <row>
-                <entry>Supported Drivers</entry>
+              <entry>7.3</entry>
+            </row>
 
-                <entry>Ethernet, I2C, SPI, PCM/I2S, UART, USB,
-                SD/SDHC/SDXC</entry>
-              </row>
+            <row>
+              <entry align="left">Linux Kernel Version</entry>
 
-              <row>
-                <entry>Enea deb folder for downloading DEB packages for this
-                target</entry>
+              <entry>4.14</entry>
+            </row>
 
-                <entry><ulink
-                url="http://linux.enea.com/EneaLinux7.0/deb">http://linux.enea.com/EneaLinux7.0/deb</ulink></entry>
-              </row>
-            </tbody>
-          </tgroup>
-        </informaltable></para>
+            <row condition="hidden">
+              <entry align="left">Supported Drivers</entry>
+
+              <entry>Ethernet, RTC, UART</entry>
+            </row>
+
+            <row>
+              <entry>Enea deb folder for downloading DEB packages for this
+              target</entry>
+
+              <entry><ulink
+              url="http://linux.enea.com/EneaLinux8.0/deb">http://linux.enea.com/EneaLinux8.0/deb</ulink></entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+
+      <table>
+        <title>MACHINE Information Intel Atom C3000</title>
+
+        <tgroup cols="2">
+          <colspec align="center" />
+
+          <thead>
+            <row>
+              <entry align="center">Component</entry>
+
+              <entry align="center">Description</entry>
+            </row>
+          </thead>
+
+          <tbody>
+            <row>
+              <entry align="left">Target official name</entry>
+
+              <entry>Intel Atom C3000</entry>
+            </row>
+
+            <row>
+              <entry align="left">Architecture and Description</entry>
+
+              <entry>x86-64</entry>
+            </row>
+
+            <row>
+              <entry align="left">Link to target datasheet</entry>
+
+              <entry><ulink
+              url="https://www.intel.com/content/www/us/en/products/docs/processors/atom/c-series/c3000-family-datasheet.html">Intel
+              Atom datasheet</ulink></entry>
+            </row>
+
+            <row>
+              <entry align="left">Poky version</entry>
+
+              <entry>Git-commit-id: TBD</entry>
+            </row>
+
+            <row>
+              <entry align="left">GCC version</entry>
+
+              <entry>7.3</entry>
+            </row>
+
+            <row>
+              <entry align="left">Linux Kernel Version</entry>
+
+              <entry>4.14</entry>
+            </row>
+
+            <row condition="hidden">
+              <entry align="left">Supported Drivers</entry>
+
+              <entry>Ethernet, RTC, UART</entry>
+            </row>
+
+            <row>
+              <entry>Enea deb folder for downloading DEB packages for this
+              target</entry>
+
+              <entry><ulink
+              url="http://linux.enea.com/EneaLinux8.0/deb">http://linux.enea.com/EneaLinux8.0/deb</ulink></entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+
+      <table>
+        <title>MACHINE Information Intel NUC Kaby Lake</title>
+
+        <tgroup cols="2">
+          <colspec align="center" />
+
+          <thead>
+            <row>
+              <entry align="center">Component</entry>
+
+              <entry align="center">Description</entry>
+            </row>
+          </thead>
+
+          <tbody>
+            <row>
+              <entry align="left">Target official name</entry>
+
+              <entry>Intel NUC Kaby Lake</entry>
+            </row>
+
+            <row>
+              <entry align="left">Architecture and Description</entry>
+
+              <entry>x86-64</entry>
+            </row>
+
+            <row>
+              <entry align="left">Link to target datasheet</entry>
+
+              <entry><ulink
+              url="https://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/nuc-kit-nuc7i5bnh-nuc7i5bnk-brief.pdf">Intel
+              NUC Kaby Lake datasheet</ulink></entry>
+            </row>
+
+            <row>
+              <entry align="left">Poky version</entry>
+
+              <entry>Git-commit-id: TBD</entry>
+            </row>
+
+            <row>
+              <entry align="left">GCC version</entry>
+
+              <entry>7.3</entry>
+            </row>
+
+            <row>
+              <entry align="left">Linux Kernel Version</entry>
+
+              <entry>4.14</entry>
+            </row>
+
+            <row condition="hidden">
+              <entry align="left">Supported Drivers</entry>
+
+              <entry>Ethernet, RTC, UART</entry>
+            </row>
+
+            <row>
+              <entry>Enea deb folder for downloading DEB packages for this
+              target</entry>
+
+              <entry><ulink
+              url="http://linux.enea.com/EneaLinux8.0/deb">http://linux.enea.com/EneaLinux8.0/deb</ulink></entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
     </section>
   </section>
-</section>
\ No newline at end of file
+</section>
diff --git a/doc/book-enea-linux-user-guide/doc/getting_enea_linux.xml b/doc/book-enea-linux-user-guide/doc/getting_enea_linux.xml
index 350c966..21d0cb9 100644
--- a/doc/book-enea-linux-user-guide/doc/getting_enea_linux.xml
+++ b/doc/book-enea-linux-user-guide/doc/getting_enea_linux.xml
@@ -12,7 +12,7 @@
     <title>Getting Pre-Built Binaries</title>
 
     <para>Enea Linux pre-built binaries are available for download on <ulink
-    url="https://portal.enea.com/login/?redirect_to=https%3A%2F%2Fportal.enea.com%2F">Enea
+    url="https://portal.enea.com/login">Enea
     Download Portal</ulink>. Log in using the credentials provided. Using the
     menu, browse to the <emphasis role="bold">Linux</emphasis> section. You
     will now have access to the <emphasis role="bold">Files</emphasis> section
@@ -34,8 +34,8 @@
       </listitem>
 
       <listitem>
-        <para><emphasis>sdk</emphasis> directory - this directory includes the
-        installer for the SDK.</para>
+        <para><emphasis>esdk</emphasis> directory - this directory includes the
+        installer for the Extensible SDK.</para>
       </listitem>
 
       <listitem>
@@ -118,17 +118,6 @@ id_rsa.pub</programlisting>
         </listitem>
 
         <listitem>
-          <para>Define the <filename>MACHINE</filename> from one of the
-          targets 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><itemizedlist>
-              <listitem>
-                <para>raspberrypi3-64</para>
-              </listitem>
-            </itemizedlist></para>
-        </listitem>
-
-        <listitem>
           <para>Then use the repo command below:</para>
 
           <xi:include href="../../book-enea-linux-release-info/doc/eltf_params_updated.xml"
@@ -153,4 +142,4 @@ id_rsa.pub</programlisting>
       etc. When this is done a reference from here should be added.</remark>
     </section>
   </section>
-</chapter>
\ No newline at end of file
+</chapter>
diff --git a/doc/book-enea-linux-user-guide/doc/preface.xml b/doc/book-enea-linux-user-guide/doc/preface.xml
index b1de43c..ff06753 100644
--- a/doc/book-enea-linux-user-guide/doc/preface.xml
+++ b/doc/book-enea-linux-user-guide/doc/preface.xml
@@ -3,7 +3,7 @@
   <title>Preface</title>
 
   <section id="guide_purpose">
-    <title>The Purpose of This Guide</title>
+    <title>The Purpose of this Guide</title>
 
     <para>This guide is intended for all Enea Linux developers who want to
     configure and build customized Linux kernel images for embedded system
@@ -103,6 +103,17 @@
             <entry>The release specific document listing the CVEs affecting
             this distribuition.</entry>
           </row>
+
+          <row>
+            <entry><ulink type=""
+            url="https://linux.enea.com/4.0/documentation/html/book-enea-linux-realtime-guide/">Enea
+            Linux Real Time documentation</ulink> and <ulink
+            url="https://rt.wiki.kernel.org/index.php/Main_Page">Real-Time
+            Linux Wiki</ulink></entry>
+
+            <entry>Enea Linux Real-Time Guide and Real-Time Linux Wiki
+            page.</entry>
+          </row>
         </tbody>
       </tgroup>
     </table>
@@ -154,4 +165,4 @@
       </listitem>
     </itemizedlist>
   </section>
-</chapter>
\ No newline at end of file
+</chapter>
diff --git a/doc/book-enea-linux-user-guide/doc/prerequisites_and_requirements.xml b/doc/book-enea-linux-user-guide/doc/prerequisites_and_requirements.xml
index 9642722..2215ba8 100644
--- a/doc/book-enea-linux-user-guide/doc/prerequisites_and_requirements.xml
+++ b/doc/book-enea-linux-user-guide/doc/prerequisites_and_requirements.xml
@@ -63,7 +63,7 @@ $ git config --global user.email johndoe@example.com</programlisting>
       <para>Building Enea Linux requires a set of packages to be installed on
       your Linux development host. The list of required packages is described
       in the <ulink
-      url="https://www.yoctoproject.org/docs/2.3/ref-manual/ref-manual.html#required-packages-for-the-host-development-system">Yocto
+      url="https://www.yoctoproject.org/docs/2.5/ref-manual/ref-manual.html#required-packages-for-the-host-development-system">Yocto
       Project reference manual</ulink>.</para>
     </section>
   </section>
@@ -98,4 +98,4 @@ Use dash as the default system shell (/bin/sh)? No</programlisting>
       </listitem>
     </itemizedlist>
   </section>
-</chapter>
\ No newline at end of file
+</chapter>
diff --git a/doc/book-enea-linux-user-guide/doc/using_eclipse.xml b/doc/book-enea-linux-user-guide/doc/using_eclipse.xml
index 9918ca2..8e560f5 100644
--- a/doc/book-enea-linux-user-guide/doc/using_eclipse.xml
+++ b/doc/book-enea-linux-user-guide/doc/using_eclipse.xml
@@ -7,7 +7,7 @@
 
     <para>For instructions on how to install Eclipse Oxygen, please refer to
     the <ulink
-    url="http://www.yoctoproject.org/docs/2.3.2/sdk-manual/sdk-manual.html#adt-eclipse">Yocto
+    url="http://www.yoctoproject.org/docs/2.5/sdk-manual/sdk-manual.html#adt-eclipse">Yocto
     Project Software Development Kit (SDK) Developer's Guide</ulink>, chapter
     4.3.2.1. Although the instructions listed there currently, refer to the
     Neon release of Eclipse, the same steps still apply to the Oxygen release,
@@ -47,7 +47,7 @@
 
     <para>To install the Yocto Plugins in Eclipse, follow the instructions in
     <ulink
-    url="http://www.yoctoproject.org/docs/2.3.2/sdk-manual/sdk-manual.html#adt-eclipse">chapter
+    url="http://www.yoctoproject.org/docs/2.5/sdk-manual/sdk-manual.html#adt-eclipse">chapter
     4.3.2.1.3.2</ulink>. of the Yocto Manual, starting with <emphasis
     role="bold">step 8</emphasis>. In <emphasis role="bold">step 12</emphasis>
     use the local archive that you downloaded previously.</para>
@@ -60,10 +60,14 @@
     Installed?</emphasis> link, as seen below.</para>
 
     <mediaobject>
-      <imageobject>
-        <imagedata align="center" contentwidth="650"
+      <imageobject role="fo">
+        <imagedata align="center" contentwidth="600"
                    fileref="images/install_new_sw.svg" />
       </imageobject>
+
+      <imageobject role="html">
+        <imagedata align="center" fileref="images/install_new_sw.png" />
+      </imageobject>
     </mediaobject>
   </section>
 
@@ -193,7 +197,7 @@ root 329 0.0 0.2 1864824 2600 ? Ssl 12:47 0:08 /usr/sbin/tcf-agent -d -L- -l0</p
           <para>For the <emphasis role="bold">Sysroot Location</emphasis>
           option, specify the path to the target sysroot directory inside the
           toolchain root location e.g.
-          <literal>&lt;extsdkdir&gt;/tmp/sysroots/aarch64-enea-linux/raspberrypi3-64</literal></para>
+          <literal>&lt;extsdkdir&gt;/tmp/sysroots/corei7-64-enea-linux/</literal></para>
         </listitem>
 
         <listitem>
@@ -217,9 +221,9 @@ root 329 0.0 0.2 1864824 2600 ? Ssl 12:47 0:08 /usr/sbin/tcf-agent -d -L- -l0</p
       <tip>
         <para>More details on how to configure the cross-compiler can be found
         in the <ulink
-        url="http://www.yoctoproject.org/docs/2.3/sdk-manual/sdk-manual.html"><emphasis>Yocto
+        url="http://www.yoctoproject.org/docs/2.5/sdk-manual/sdk-manual.html"><emphasis>Yocto
         Project Software Development Kit (SDK) Developer's Guide
-        2.3</emphasis></ulink>. Change the Yocto version in the link if
+        2.5</emphasis></ulink>. Change the Yocto version in the link if
         needed.</para>
 
         <para>There is also a good cheat sheet available in Eclipse, under
@@ -873,7 +877,7 @@ root 329 0.0 0.2 1864824 2600 ? Ssl 12:47 0:08 /usr/sbin/tcf-agent -d -L- -l0</p
                 <para>Under the <emphasis role="bold">Debugger</emphasis> tab,
                 fill in the <literal>GDB Debugger</literal> field with the
                 path to the GDB binary from the SDK. Example path:
-                <filename>&lt;extsdkdir&gt;/tmp/sysroots/x86_64-linux/usr/bin/&lt;arch&gt;-enea-linux/&lt;arch&gt;-enea-linux-gdb</filename></para>
+                <filename>&lt;extsdkdir&gt;/tmp/sysroots/x86_64/usr/bin/&lt;arch&gt;-enea-linux/&lt;arch&gt;-enea-linux-gdb</filename></para>
               </listitem>
 
               <listitem>
@@ -896,7 +900,7 @@ root 329 0.0 0.2 1864824 2600 ? Ssl 12:47 0:08 /usr/sbin/tcf-agent -d -L- -l0</p
     <para>In this section you learn to set up Eclipse for KGDB<indexterm>
         <primary>KGDB</primary>
       </indexterm> kernel debugging over the serial port, with examples for
-    the <literal>raspberrypi3</literal> target. This is only given as an
+    the <literal>intel-corei7-64</literal> target. This is only given as an
     example, your Enea Linux distribution may contain other targets. The
     corresponding instruction for debugging outside Eclipse is available in
     Debugging the Linux Kernel (KGDB) from Command Line.<remark>LATER: Merge
@@ -930,7 +934,7 @@ root 329 0.0 0.2 1864824 2600 ? Ssl 12:47 0:08 /usr/sbin/tcf-agent -d -L- -l0</p
         you can find it in the rootfs under the <literal>/boot</literal>
         folder. If you build your own kernel using bitbake, it should be
         available in your build folder. Located in, for example:
-        <filename><filename>tmp/work/raspberrypi3_64-enea-linux/linux-raspberrypi/1_4.9.59+gitAUTOINC+meta_machine-r0/image/boot/vmlinux-4.9.59</filename></filename></para>
+        <filename><filename>tmp/work/corei7-64-intel-common-enea-linux/linux-intel/4.14.66+gitAUTOINC+d64aec9793_dd6a8b48d4-r0/linux-corei7-64-intel-common-standard-build/vmlinux</filename></filename></para>
       </listitem>
 
       <listitem>
diff --git a/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml b/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml
index 3997038..a68f7da 100644
--- a/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml
+++ b/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml
@@ -5,9 +5,9 @@
   <section id="build_enealinux">
     <title>Building Enea Linux</title>
 
-    <para>Enea Linux is made available as sources as well. This allows
-    building various Enea Linux artifacts and this is detailed in the
-    following sections:</para>
+    <para>Enea Linux is made available as sources, this allows for of building
+    various Enea Linux artifacts and is detailed in the following
+    sections:</para>
 
     <section id="build_images">
       <title>Building the images</title>
@@ -16,15 +16,18 @@
 
       <procedure>
         <step>
+          <para>Set the $MACHINE/&lt;machine&gt; variable to the target you
+          need, e.g. <literal>intel-corei7-64</literal>.</para>
+        </step>
+
+        <step>
           <para>Clone Enea Linux sources using Repo tool. Please refer to
-          chapter 3.2 in the current documebt for more details on how to do
-          this.</para>
+          <xref linkend="getting_sources" /> for more details.</para>
 
           <programlisting>$ mkdir enea-linux
 $ cd enea-linux
-$ export MACHINE=&lt;machine&gt;
 $ repo init -u git@git.enea.com:linux/manifests/el_manifests-standard.git \
-    -b refs/tags/Enea_Linux_7.0 -m $MACHINE/default.xml
+    -b refs/tags/Enea_Linux_8.0 -m $MACHINE/default.xml
 $ repo sync</programlisting>
         </step>
 
@@ -35,13 +38,10 @@ $ repo sync</programlisting>
 $ TEMPLATECONF=meta-el-standard/conf/template.&lt;machine&gt; \
 . ./oe-init-build-env &lt;build_dir&gt;</programlisting>
 
-          <note>
-            <para>Sourcing the build environment is needed everytime a new
-            shell is used. However, sourcing using the
-            <literal>TEMPLATECONF</literal> is only needed the first time
-            around. Afterwards it is enough to source the build directory
-            created before.</para>
-          </note>
+          <para>Sourcing the build environment is needed everytime a new shell
+          is used. However, sourcing using the <literal>TEMPLATECONF</literal>
+          is only needed the first time around. After the first time, it is
+          enough to source the build directory created before.</para>
 
           <note>
             <para>The build directory may reside on an NFS mount, but the
@@ -105,9 +105,8 @@ $ cd &lt;build_dir&gt;/tmp/deploy/images/&lt;target&gt;/  # Here are the build b
 
           <programlisting>$ mkdir enea-linux
 $ cd enea-linux
-$ export MACHINE=&lt;machine&gt;
 $ repo init -u git@git.enea.com:linux/manifests/el_manifests-standard.git \
-    -b refs/tags/Enea_Linux_7.0 -m $MACHINE/default.xml
+    -b refs/tags/Enea_Linux_8.0 -m $MACHINE/default.xml
 $ repo sync</programlisting>
         </step>
 
@@ -118,13 +117,10 @@ $ repo sync</programlisting>
 $ TEMPLATECONF=meta-el-standard/conf/template.&lt;machine&gt; \
 . ./oe-init-build-env &lt;build_dir&gt;</programlisting>
 
-          <note>
-            <para>Sourcing the build environment is needed everytime a new
-            shell is used. However, sourcing using the
-            <literal>TEMPLATECONF</literal> is only needed the first time
-            around. Afterwards it is enough to source the build directory
-            created before.</para>
-          </note>
+          <para>Sourcing the build environment is needed everytime a new shell
+          is used. However, sourcing using the <literal>TEMPLATECONF</literal>
+          is only needed the first time around. Afterwards it is enough to
+          source the build directory created before.</para>
 
           <note>
             <para>The build directory may reside on an NFS mount, but the
@@ -177,109 +173,140 @@ $ cd &lt;build_dir&gt;/tmp/deploy/sdk/  # Here is the SDK installer script</prog
     <para>Enea Linux supports multiple booting methods so those will be
     described in the following sections.</para>
 
-    <section id="boot_from_arm">
-      <title>Boot from RAM</title>
-
-      <para>This example requires that a TFTP server is set up at IP address
-      <literal>&lt;tftp_server_ip&gt;</literal>, and that the server stores
-      the Enea Linux image files, kernel image, device tree blob and root
-      filesystem, in <literal>/tftpboot/&lt;download_directory&gt;.</literal>
-      Please refer to <xref linkend="prebuiltprereq" /> for more details on
-      how to install and configure the TFTP server.</para>
+    <section id="enea-linux-x86-pxe">
+      <title>Booting via PXE</title>
 
-      <para>Once you have that in place, run the following commands on the
-      target:</para>
+      <para>Below you find an example of how to boot Enea Linux in a target
+      supporting PXE. The PXE boot is handled by the target BIOS.</para>
 
-      <programlisting>## set tftp server IP
-U-Boot&gt; setenv serverip &lt;tftp_server_ip&gt;
+      <para>This requires the setup of DHCP, TFTP and NFS servers on the host.
+      The DHCP server contains a configuration for the target, found via the
+      target MAC address, and refers to the TFTP server for the boot image and
+      to the NFS server for the root file system.</para>
 
-## tftp the image files on the target machine
-U-Boot&gt; tftpboot 0x01000000 Image  
-U-Boot&gt; tftpboot 0x02000000 Image-bcm2837-rpi-3-b.dtb 
-U-Boot&gt; tftpboot 0x03000000 enea-image-standard-raspberrypi3-64.ext2.gz.u-boot
+      <para>For the DHCP server, in addition to the general configuration, the
+      DHCPD configuration should contain an entry for the target with the
+      following information:</para>
 
-## add any other bootargs values if necessary 
-U-Boot&gt; setenv bootargs "8250.nr_uarts=1 root=/dev/ram rw ramdisk_size=500000 ip=dhcp \
-console=ttyS0,115200"
+      <itemizedlist spacing="compact">
+        <listitem>
+          <para>Host name</para>
+        </listitem>
 
-## Start boot sequence
-U-Boot&gt; booti 0x01000000 0x03000000 0x02000000</programlisting>
-    </section>
+        <listitem>
+          <para>MAC hardware ethernet address (also available in the TFTP
+          configuration)</para>
+        </listitem>
 
-    <section id="boot_from_sd">
-      <title>Boot from SD card</title>
+        <listitem>
+          <para>IP address, (assuming a fixed IP address is used)</para>
+        </listitem>
 
-      <para>Copy the
-      <filename>enea-image-standard-raspberrypi3-64.rpi-sdimg</filename> image
-      to the SD card using the Linux dd tool or Win32DiskImager in Windows,
-      and insert it into the RPi. The Raspberry Pi will not start without a
-      properly formatted SD Card, containing the bootloader, kernel image and
-      rootfs.</para>
+        <listitem>
+          <para>The TFTP server shall be defined as
+          <literal>next-server</literal></para>
+        </listitem>
 
-      <para>Below you can find two methods of how to format an SD Card:</para>
+        <listitem>
+          <para>The relative path in the TFTP server to the PXE file
+          <filename><literal>pxelinux.0</literal></filename></para>
+        </listitem>
 
-      <itemizedlist>
         <listitem>
-          <para><emphasis role="bold">Format and copy images to the SD card
-          using the Linux dd command line</emphasis></para>
+          <para>The NFS server IP address and the path to the rootfs on the
+          NFS server, defined as <literal>option root-path</literal></para>
+        </listitem>
+      </itemizedlist>
 
-          <para>The <command>dd</command> command copies a file, converting
-          the format of the data in the process, according to the operands
-          specified:</para>
+      <para>Example of a DHCP server configuration:</para>
 
-          <programlisting>sudo dd bs=4M if=enea-image-standard-sdk-raspberrypi3-64.rpi-sdimg of=/dev/sdg</programlisting>
+      <programlisting>host intel-corei7-64_host {
+    hardware ethernet 01:00:25:90:c8:c5:98;
+    fixed-address     192.168.1.38;
+    next-server       192.168.2.10;
+    filename          "intel-corei7-64_tftp/pxelinux.0";
+    option root-path  "192.168.2.20:/export/intel-corei7-64_rootfs";
+}</programlisting>
 
-          <note>
-            <para>Use <command>dd</command> cautiously - improper usage or
-            entering the wrong values could inadvertently wipe, destroy, or
-            overwrite the data on your hard drive.</para>
-          </note>
-        </listitem>
+      <para>For the TFTP server, the TFTP path to the target's pxelinux.0 file
+      is given in the DHCP Configuration. Examples of files included in the
+      TFTP subdirectory indicated by the DHCP configuration are:</para>
 
-        <listitem>
-          <para><emphasis role="bold">Format the SD card using the
-          Win32DiskImager program</emphasis></para>
+      <programlisting>pxelinux.0
+vesamenu.c32
+boot/device01/bzImage                          (bootable image file)
+pxelinux.cfg/01-00-25-90-c8-c5-98              (Configuration file)</programlisting>
 
-          <orderedlist>
-            <listitem>
-              <para>Download and unzip <ulink
-              url="https://sourceforge.net/projects/win32diskimager/">Win32DiskImager</ulink></para>
-            </listitem>
+      <para>One configuration file has the same name as the target's MAC
+      address (but with hyphens instead of a colon). This configuration file
+      contains a pointer to the bootable image and also a list of command line
+      arguments to append when the image is started. The same NFS path to the
+      root file system is both in the DHCP and the TFTP configuration.</para>
 
-            <listitem>
-              <para>Run <filename>Win32DiskImager.exe</filename></para>
-            </listitem>
+      <para>Example of a configuration file:</para>
 
-            <listitem>
-              <para>Select the drive of your SD card</para>
-            </listitem>
+      <programlisting>default vesamenu.c32
+prompt 0
+timeout 100
 
-            <listitem>
-              <para>Select the image
-              <filename><filename>enea-image-standard-raspberrypi3-64.rpi-sdimg</filename></filename></para>
-            </listitem>
+label device01
+  menu label ^EneaLinuxNFS
+  menu default
+  kernel boot/device01/bzImage
+  <emphasis role="bold">append</emphasis> root=/dev/nfs nfsmount=192.168.2.20:/export/intel-corei7-64_rootfs ip=dhcp
+                                                            console=ttyS0,115200</programlisting>
 
-            <listitem>
-              <para>Click "Write" and wait for the write to complete</para>
-            </listitem>
+      <para><emphasis role="bold">NFS server</emphasis>: The NFS server shall
+      contain an unpacked root file system in the path indicated both in the
+      DHCP and in the TFTP configuration.</para>
 
-            <listitem>
-              <para>Exit the imager and eject the SD Card</para>
-            </listitem>
+      <para>After configuring the servers, copy files from the build directory
+      into the correctly configured paths:</para>
 
-            <listitem>
-              <para>Plug the card into your Raspberry Pi</para>
-            </listitem>
-          </orderedlist>
+      <orderedlist spacing="compact">
+        <listitem>
+          <para>Ensure the target is not already running an OS, otherwise the
+          target might attempt to change files on the root file system while
+          it is populated with new files.</para>
+        </listitem>
 
-          <note>
-            <para>Be careful to select the correct drive. If you choose the
-            wrong one you may destroy your HDD data. If you are using an SD
-            Card slot and can't see the drive in the Win32DiskImager window,
-            try using an affordable external adapter in a USB slot.</para>
-          </note>
+        <listitem>
+          <para>Copy <filename>pxelinux.0</filename> and
+          <filename>vesamenu.c32</filename> from the build directory, e.g.
+          from
+          <filename>&lt;build_dir&gt;tmp/work/corei7-64-enea-linux/syslinux/6.03-r0/image/usr/share/syslinux/</filename>.</para>
         </listitem>
-      </itemizedlist>
+
+        <listitem>
+          <para>Copy <filename>bzImage</filename> from
+          <filename>&lt;build_dir&gt;/tmp/deploy/images/&lt;target&gt;/</filename>.</para>
+        </listitem>
+
+        <listitem>
+          <para>Populate the root file system in the NFS directory by
+          unpacking
+          <filename>enea-image-standard-intel-corei7-64.tar.gz</filename>
+          found at
+          <filename>&lt;build_dir&gt;/tmp/deploy/images/&lt;target&gt;/</filename>.</para>
+        </listitem>
+      </orderedlist>
+
+      <para>Boot the target by:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Use the BIOS or boot setup to select PXE boot, if not already
+          selected.</para>
+        </listitem>
+
+        <listitem>
+          <para>Reboot the target.</para>
+        </listitem>
+      </orderedlist>
+
+      <para>The boot setup menu is usually launched by pressing F12 or ESC
+      during BIOS power up tests. Look up the manufacturer's documentation for
+      your board model to find the appropriate key.</para>
     </section>
   </section>
 
@@ -342,8 +369,7 @@ BBLAYERS ?= " \
   /path/to/poky/meta-el-common \
   /path/to/poky/meta-el-standard \
   /path/to/poky/meta-enea-bsp-common \
-  /path/to/poky/meta-enea-bsp-&lt;arch&gt; \
-  /path/to/poky/meta-fsl-&lt;arch&gt; \
+  /path/to/poky/meta-enea-bsp-x86 \
   /path/to/poky/meta-openembedded/meta-oe \
   /path/to/poky/meta-openembedded/meta-networking \
   /path/to/poky/meta-openembedded/meta-filesystems \
@@ -386,8 +412,8 @@ BBLAYERS ?= " \
       <para>As a result, <filename>BBLAYERS</filename> shall be extended with
       the bsp-layer/s layer for your target and any other additional layer/s.
       For details on how to do this, see the <ulink
-      url="http://www.yoctoproject.org/docs/2.3/dev-manual/dev-manual.html#understanding-and-creating-layers">Yocto
-      2.3 Dev Manual, section "Understanding and Creating Layers"</ulink> . If
+      url="http://www.yoctoproject.org/docs/2.5/dev-manual/dev-manual.html#understanding-and-creating-layers">Yocto
+      2.5 Dev Manual, section "Understanding and Creating Layers".</ulink> If
       needed replace the Yocto version.</para>
 
       <para>Layers can be added when you initialize the build environment. The
@@ -414,11 +440,10 @@ BBLAYERS ?= " \
       <title>Adding a Recipe</title>
 
       <para>Study the <ulink
-      url="https://www.yoctoproject.org/docs/2.3/dev-manual/dev-manual.html#new-recipe-single-c-file-package-hello-world"><ulink
-      url="https://www.yoctoproject.org/docs/2.3/dev-manual/dev-manual.html#new-recipe-single-c-file-package-hello-world">Hello
-      World recipe</ulink></ulink> in the Yocto Project Development Manual. If
-      needed replace the example version (2.3) with the Yocto version in your
-      Enea Linux distribution.</para>
+      url="https://www.yoctoproject.org/docs/2.5/dev-manual/dev-manual.html#new-recipe-single-c-file-package-hello-world">Hello
+      World recipe</ulink> in the Yocto Project Development Manual. If needed
+      replace the example version (2.5) with the Yocto version in your Enea
+      Linux distribution.</para>
     </section>
 
     <section id="config_pkg_recipes">
@@ -650,7 +675,7 @@ $ ./enea-*-toolchain-&lt;version&gt;.sh</programlisting>
 
         <para>Example:</para>
 
-        <programlisting>$ . /opt/enea/environment-setup-aarch64-enea-linux</programlisting>
+        <programlisting>$ . /opt/enea/environment-setup-corei7-64-enea-linux</programlisting>
       </listitem>
     </orderedlist>
 
@@ -658,6 +683,16 @@ $ ./enea-*-toolchain-&lt;version&gt;.sh</programlisting>
     set up, you can proceed with Cross-Compiling Applications from Command
     Line (4.1) or, if Eclipse is installed, Cross-Compiling from Eclipse
     (5.4.1).</para>
+
+    <section id="boot_qemux86">
+      <title>Building and booting Enea Linux on QEMU x86</title>
+
+      <para>Build an Enea Linux image from the SDK to run on QEMU x86:</para>
+
+      <programlisting>$ cd &lt;sdkdir&gt;/workspace
+$ devtool build-image enea-image-standard 
+$ devtool runqemu kvm enea-image-standard nographic slirp  </programlisting>
+    </section>
   </section>
 
   <section id="pkg_mg">
@@ -667,8 +702,8 @@ $ ./enea-*-toolchain-&lt;version&gt;.sh</programlisting>
     image in a consistent way, e.g. to install, upgrade, or delete packages
     considering the dependencies. The package management systems supported by
     Enea Linux are described in this section. More information about PMS can
-    be found in the Yocto 2.3 document <ulink
-    url="http://www.yoctoproject.org/docs/2.3/mega-manual/mega-manual.html">Yocto
+    be found in the Yocto 2.5 document <ulink
+    url="http://www.yoctoproject.org/docs/2.5/mega-manual/mega-manual.html">Yocto
     Project Mega Manual</ulink>. If needed replace the Yocto version in the
     link.</para>
 
@@ -676,7 +711,7 @@ $ ./enea-*-toolchain-&lt;version&gt;.sh</programlisting>
       <title>APT Package Management (DEB Packages)</title>
 
       <para>Enea Linux provides DEB packages on <ulink
-      url="http://linux.enea.com/EneaLinux7.0/">linux.enea.com</ulink> site,
+      url="http://linux.enea.com/EneaLinux8.0/">linux.enea.com</ulink> site,
       in directory
       <literal><literal>&lt;release&gt;/&lt;target&gt;/deb</literal>/</literal>.</para>
 
@@ -777,4 +812,4 @@ ptest-runner-dev - A C program to run all installed ptests - Development files</
       </section>
     </section>
   </section>
-</chapter>
\ No newline at end of file
+</chapter>