meta-ewaol repository provides three layers compatible with the Yocto
Project, in the following sub-directories:
Yocto distribution layer providing top-level and general policies for the EWAOL distribution images.
Yocto software layer with recipes that include run-time tests to validate EWAOL functionalities.
Yocto BSP layer with target platform specific extensions for particular EWAOL distribution images.
For the N1SDP hardware target platform, this layer currently extends the
n1sdpmachine definition from the
meta-arm-bsplayer for EWAOL virtualization distribution images.. The
meta-ewaol-bsplayer contains an additional grub configuration file with Xen boot entry and a custom kickstart
ewaol-virtualization-n1sdp-efidisk.wks.infile. There is also a
xen-devicetree.bbrecipe, to generate a devicetree with extra modules nodes required by Xen to start the Control VM (Dom0). In addition, the Xen devicetree together with a Xen efi binary are included into the final wic image in the
For the AVA hardware target platform, this layer provides additional
systemdconfiguration for ethernet interfaces based on the
i40eas used on the AVA Developer Platform.
Layer Dependency Overview
The following diagram illustrates the layers which are integrated by the EWAOL
project, which are further expanded on below. The layer revisions are related to the EWAOL
EWAOL depends on the following layer dependency sources:
URL: https://git.yoctoproject.org/git/poky layers: meta, meta-poky branch: kirkstone revision: HEAD URL: https://git.openembedded.org/meta-openembedded layers: meta-filesystems, meta-networking, meta-oe, meta-python branch: kirkstone revision: HEAD URL: https://git.yoctoproject.org/git/meta-virtualization layers: meta-virtualization branch: kirkstone revision: HEAD
Additional layer dependency sources may be conditionally required, depending on the specific EWAOL distribution image being built.
The first additional layer dependency source is the
which provides three Yocto layers:
URL: https://git.yoctoproject.org/git/meta-arm layers: meta-arm, meta-arm-bsp, meta-arm-toolchain branch: kirkstone revision: HEAD
The layers required from
meta-arm depend on the EWAOL distribution image:
EWAOL SDK distribution images require
meta-arm-toolchain, as the
gator-daemonpackage is installed on the rootfs.
An EWAOL virtualization distribution image requires
meta-arm-toolchain, as by default a bundled Guest VM image based on the
An EWAOL distribution image built for the N1SDP hardware target platform requires
These layers are described as follows:
Clean separation between Firmware and OS.
The canonical source for SystemReady firmware.
Board specific components for Arm target platforms.
Provides toolchain for Arm target platforms
The second additional layer dependency source is the
repository, which provides a single Yocto layer:
URL: https://github.com/ADLINK/meta-adlink-ampere.git layers: meta-adlink-ampere branch: kirkstone revision: HEAD
This Yocto layer provides BSP components required when building an EWAOL distribution image for the AVA hardware target platform.