1 files changed, 105 insertions, 0 deletions

diff --git a/intel-corei7-64/README b/intel-corei7-64/README
index c45f2b1..1897d99 100644
--- a/intel-corei7-64/README
+++ b/intel-corei7-64/README
@@ -1,7 +1,112 @@
 This file contains build and boot instructions for Enea Linux on
 intel-corei7-64, standard profile.
 
+Build instructions
+------------------
+$ mkdir enea-linux
+$ cd enea-linux
+$ repo init -u git@git.enea.com:linux/manifests/el_manifests-standard.git \
+    -b refs/tags/Enea_Linux_8.1 -m intel-corei7-64/default.xml
+$ repo sync
+$ cd poky
+$ TEMPLATECONF=meta-el-standard/conf/template.intel-corei7-64 . \
+    ./oe-init-build-env <build_dir>
+$ bitbake enea-image-standard / enea-image-standard-sdk
 
 
+Booting via PXE
+---------------
+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.
 
+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.
+
+For the DHCP server, in addition to the general configuration, the DHCPD
+configuration should contain an entry for the target with the following
+information:
+
+    - Host name
+
+    - MAC hardware ethernet address (also available in the TFTP configuration)
+
+    - IP address, (assuming a fixed IP address is used)
+
+    - The TFTP server shall be defined as next-server
+
+    - The relative path in the TFTP server to the PXE file pxelinux.0
+
+    - The NFS server IP address and the path to the rootfs on the NFS server,
+      defined as option root-path
+
+Example of a DHCP server configuration:
+
+    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";
+    }
+
+=== 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:
+
+    pxelinux.0
+    vesamenu.c32
+    boot/device01/bzImage                          (bootable image file)
+    pxelinux.cfg/01-00-25-90-c8-c5-98              (Configuration file)
+
+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.
+
+Example of a configuration file:
+
+    default vesamenu.c32
+    prompt 0
+    timeout 100
+
+    label device01
+      menu label ^EneaLinuxNFS
+      menu default
+      kernel boot/device01/bzImage
+      append root=/dev/nfs nfsmount=192.168.2.20:/export/intel-corei7-64_rootfs
+             ip=dhcp console=ttyS0,115200
+
+=== NFS server ===
+    The NFS server shall contain an unpacked root file system in the
+path indicated both in the DHCP and in the TFTP configuration.
+
+After configuring the servers, copy files from the build directory into the
+correctly configured paths:
+
+    1. 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.
+
+    2. Copy pxelinux.0 and vesamenu.c32 from the build directory, e.g. from
+       <build_dir>tmp/work/corei7-64-enea-linux/syslinux/6.04-pre2-r0/image/usr/share/syslinux/.
+
+    3. Copy bzImage from <build_dir>/tmp/deploy/images/<target>/.
+
+    4. Populate the root file system in the NFS directory by unpacking
+       enea-image-jjv-intel-corei7-64.tar.gz found at 
+       <build_dir>/tmp/deploy/images/<target>/.
+
+Boot the target by:
+
+    1. Use the BIOS or boot setup to select PXE boot, if not already selected.
+
+    2. Reboot the target.
+
+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.