[meta-intel] [master][PATCH 1/3] meta-crystalforest: relocate meta-crystalforest layer into meta-isg layer
chia.chuan.wu at intel.com
chia.chuan.wu at intel.com
Fri Oct 2 04:28:37 PDT 2015
From: Wu Chia Chuan <chia.chuan.wu at intel.com>
This is in support of BSP consolidation of all Intel platforms in to meta-isg common layer.
The "MAINTAINERS file" and "meta-isg/MAINTAINERS file" are updated to reflect the changed.
Signed-off-by: Wu Chia Chuan <chia.chuan.wu at intel.com>
---
MAINTAINERS | 4 -
meta-crystalforest/COPYING.MIT | 17 --
meta-crystalforest/README | 240 --------------------
meta-crystalforest/README.sources | 17 --
meta-crystalforest/conf/layer.conf | 12 -
meta-crystalforest/conf/machine/crystalforest.conf | 40 ----
.../formfactor/crystalforest-gladden/machconfig | 3 -
.../formfactor/crystalforest-server/machconfig | 3 -
.../recipes-bsp/formfactor/formfactor_0.0.bbappend | 1 -
meta-isg/MAINTAINERS | 4 +
meta-isg/meta-crystalforest/COPYING.MIT | 17 ++
meta-isg/meta-crystalforest/README | 240 ++++++++++++++++++++
meta-isg/meta-crystalforest/README.sources | 17 ++
meta-isg/meta-crystalforest/conf/layer.conf | 12 +
.../conf/machine/crystalforest.conf | 40 ++++
.../formfactor/crystalforest-gladden/machconfig | 3 +
.../formfactor/crystalforest-server/machconfig | 3 +
.../recipes-bsp/formfactor/formfactor_0.0.bbappend | 1 +
18 files changed, 337 insertions(+), 337 deletions(-)
delete mode 100644 meta-crystalforest/COPYING.MIT
delete mode 100644 meta-crystalforest/README
delete mode 100644 meta-crystalforest/README.sources
delete mode 100644 meta-crystalforest/binary/.gitignore
delete mode 100644 meta-crystalforest/conf/layer.conf
delete mode 100644 meta-crystalforest/conf/machine/crystalforest.conf
delete mode 100644 meta-crystalforest/recipes-bsp/formfactor/formfactor/crystalforest-gladden/machconfig
delete mode 100644 meta-crystalforest/recipes-bsp/formfactor/formfactor/crystalforest-server/machconfig
delete mode 100644 meta-crystalforest/recipes-bsp/formfactor/formfactor_0.0.bbappend
create mode 100644 meta-isg/meta-crystalforest/COPYING.MIT
create mode 100644 meta-isg/meta-crystalforest/README
create mode 100644 meta-isg/meta-crystalforest/README.sources
create mode 100644 meta-isg/meta-crystalforest/binary/.gitignore
create mode 100644 meta-isg/meta-crystalforest/conf/layer.conf
create mode 100644 meta-isg/meta-crystalforest/conf/machine/crystalforest.conf
create mode 100644 meta-isg/meta-crystalforest/recipes-bsp/formfactor/formfactor/crystalforest-gladden/machconfig
create mode 100644 meta-isg/meta-crystalforest/recipes-bsp/formfactor/formfactor/crystalforest-server/machconfig
create mode 100644 meta-isg/meta-crystalforest/recipes-bsp/formfactor/formfactor_0.0.bbappend
diff --git a/MAINTAINERS b/MAINTAINERS
index 79a021d..443041d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -31,10 +31,6 @@ COMMON
M: Saul Wold <sgw at linux.intel.com>
F: common/
-CRYSTALFOREST
-M: Wu Chia Chuan <chia.chuan.wu at intel.com>
-F: meta-crystalforest/
-
TLK
M: Saul Wold <sgw at linux.intel.com>
F: meta-tlk/
diff --git a/meta-crystalforest/COPYING.MIT b/meta-crystalforest/COPYING.MIT
deleted file mode 100644
index fb950dc..0000000
--- a/meta-crystalforest/COPYING.MIT
+++ /dev/null
@@ -1,17 +0,0 @@
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
diff --git a/meta-crystalforest/README b/meta-crystalforest/README
deleted file mode 100644
index f549f90..0000000
--- a/meta-crystalforest/README
+++ /dev/null
@@ -1,240 +0,0 @@
-This README file contains information on building the meta-crystalforest
-BSP layer, and booting the images contained in the /binary directory.
-Please see the corresponding sections below for details.
-
-Overview of Intel Communication Product Offering
-------------------------------------------------
-
-The following platforms are supported on meta-intel dizzy branch ONLY:
-
-Crystal Forest/Server - Shumway reference platform configurations:
-processor: Intel Xeon E5-2600/E5-2400 (Sandy Bridge-based) or
- Intel Xeon E5-2600v2/E5-2400v2 (Ivy Bridge-based)
-chipset: Intel Communication Chipset 8900-8920 Series (Cave Creek)
-url: http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-e5-89xx/overview
-
-Crystal Forest/Gladden - Stargo reference platform configurations:
-processor: Intel Xeon E3-1125C/E3-1105C (Sandy Bridge-based) or
- Intel Xeon E3-1125v2/E3-1105v2 (Ivy Bridge-based)
-chipset: Intel Communication Chipset 8900-8920 Series (Cave Creek)
-url: http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-core-pentium-celeron-89xx/overview
-
-Highland Forest (Crystal Forest/Server Refresh) - Shumway reference platform configurations:
-processor: Intel Xeon E5-2600v2/E5-2400v2 (Ivy Bridge-based)
-chipset: Intel Communication Chipset 8925-8955 Series (Coleto Creek)
-url: https://www-ssl.intel.com/content/www/us/en/intelligent-systems/crystal-forest-server/xeon-e5-v2-89xx-chipset-ibd.html
-
-The following platform is supported on meta-intel fido branch and beyond.
-
-River Forest - Long Brook reference platform configurations:
-processor: Intel Xeon E5-2600v3/E5-2400v3 (Haswell EP-based)
-chipset: Intel Communication Chipset 8925-8955 Series (Coleto Creek)
-url: https://www-ssl.intel.com/content/www/my/en/embedded/products/river-forest/overview.html?wapkw=coleto
-
-All above four platforms use PCIe-based Matrox graphics card for display.
-
-More Information on all Intel® embedded platforms can be found here:
-
- http://www.intel.com/p/en_US/embedded/hwsw/hardware
-
-
-Yocto Project Compatible
-========================
-
-This BSP is compatible with the Yocto Project as per the requirements
-listed here:
-
- https://www.yoctoproject.org/webform/yocto-project-compatible-registration
-
-Dependencies
-============
-
-This layer depends on:
-
- URI: git://git.openembedded.org/bitbake
- branch: master
-
- URI: git://git.openembedded.org/openembedded-core
- layers: meta
- branch: master
-
- URI: git://git.yoctoproject.org/meta-intel
- layers: intel
- branch: master
-
-
-Patches
-=======
-
-Please submit any patches against this BSP to the meta-intel mailing
-list (meta-intel at yoctoproject.org) and cc: the maintainer:
-
-Maintainer: Wu Chia Chuan <chia.chuan.wu at intel.com>
-
-Please see the meta-intel/MAINTAINERS file for more details.
-
-
-Table of Contents
-=================
-
- I. Building the meta-crystalforest BSP layer
- II. Booting the images in /binary
-III. Device Notes
- a. Boot Loader
- b. I/O drivers
-IV. Enabling Intel DPDK and QuickAssist Technology
-
-I. Building the meta-crystalforest BSP layer
-=======================================
-
-In order to build an image with BSP support for a given release, you
-need to download the corresponding BSP tarball from the 'Board Support
-Package (BSP) Downloads' page of the Yocto Project website.
-
-Having done that, and assuming you extracted the BSP tarball contents
-at the top-level of your yocto build tree, you can build a crystalforest
-image by adding the location of the meta-crystalforest layer to
-bblayers.conf, along with the meta-intel layer itself (to access
-common metadata shared between BSPs) e.g.:
-
- yocto/meta-intel \
- yocto/meta-intel/meta-crystalforest \
-
-Crystal Forest layer is meant for building both Crystal Forest Gladden
-and Crystal Forest Server platforms. By enabling Crystal Forest layer,
-the image you build is able to boot on both supported platforms.
-
-To enable the Crystal Forest layer, add the Crystal Forest MACHINE to
-build/local.conf:
-
- MACHINE ?= "crystalforest"
-
-You should then be able to build a crystalforest image as such:
-
- $ source oe-init-build-env
- $ bitbake core-image-sato
-
-At the end of a successful build, you should have a live image that
-you can boot from a USB flash drive (see instructions on how to do
-that below, in the section 'Booting the images from /binary').
-
-The live image is located within build/tmp/deploy/images/<machine> folder.
-
-As an alternative to downloading the BSP tarball, you can also work
-directly from the meta-intel git repository. For each BSP in the
-'meta-intel' repository, there are multiple branches, one
-corresponding to each major release starting with 'laverne' (0.90), in
-addition to the latest code which tracks the current master (note that
-not all BSPs are present in every release). Instead of extracting a
-BSP tarball at the top level of your yocto build tree, you can
-equivalently check out the appropriate branch from the meta-intel
-repository at the same location.
-
-
-II. Booting the images in /binary
-=================================
-
-This BSP contains bootable live images, which can be used to directly
-boot Yocto off of a USB flash drive.
-
-You can deploy the hddimg image to a USB or SATA device. You will
-need to know the device name on your host as well as the device name on
-the target. Be careful with this step as using the wrong host device can
-result in overwriting data on your host machine.
-
-Under Linux, USB and SATA devices typically appears as /dev/sdb,
-/dev/sdc, etc. Watching your system messages as you connect the device
-will tell you exactly which device name is assigned to the device.
-On the Valley Island platform, assuming only one storage device is
-attached at boot, a USB or SATA device will be /dev/sda.
-
-After inserting the boot media into your host machine and determining
-your host and target device, create the image using the mkefidisk.sh
-script, provided by poky under scripts/contrib/. Note that root
-privileges are required. For example, using an USB device which appears
-as /dev/sdc on the host:
-
-$ sudo ./mkefidisk.sh /dev/sdc core-image-sato-<machine>.hddimg /dev/sda
-
-Follow the prompts on the screen to confirm the action.
-
-This should give you a bootable USB flash device. Insert the device
-into a bootable USB socket on the target, and power on. This should
-result in a system booted to the Sato graphical desktop.
-
-If you want a terminal, use the arrows at the top of the UI to move to
-different pages of available applications, one of which is named
-'Terminal'. Clicking that should give you a root terminal.
-
-If you want to ssh into the system, you can use the root terminal to
-ifconfig the IP address and use that to ssh in. The root password is
-empty, so to log in type 'root' for the user name and hit 'Enter' at
-the Password prompt: and you should be in.
-
-III. Device Notes
-=================
-
-a. Boot Loader
---------------
-- Support BIOS version at Shumway board (HighlandForest/CrystalForest-server):
- CCFRCLC0.019
-
-- Support BIOS version at Stargo board ( CrystalForest-Gladden ):
- CIVGCCK1.86C.0003.P00
-
-- Support BIOS version at Long Brook board (RiverForest)
- GRNDCRB1.86B.0022.R01.i02.1405151000
-
-b. I/O drivers
---------------
--Support Matrox graphic card.
--Support SATA, USB Host v2.0
--Supported I/O devices (APIC, RTC, SPI, UART, I2C, LPS, SMBus i801,
- WDT, and HPET)
-
-
-IV. Enabling Intel DPDK and QuickAssist Technology
-===================================================
-
-DPDK recipe: meta-intel/meta-isg/common/recipes-extended/dpdk
-QAT recipe: meta-crystalforest/recipes-extended/qat
-QAT-enable zlib recipe: meta-crystalforest/recipes-extended/zlib-qat
-
-Note:
-qat16 recipe is meant for platform with Coleto Creek chipset.
-qat15 recipe is meant for platform with Cave Creek chipset.
-
-conf/machine/crystalforest.conf is the common machine configuration
-to support Crystal Forest/server, Crystal Forest/gladden, Highland Forest and
-River Forest. In order to generate the right binary for these platforms which
-have different QAT technology, user could change the default config accordingly
-within crystalforest.conf as below:
-
-For Coleto Creek chipset:
-PREFERRED_PROVIDER_virtual/qat ?= "qat16"
-
-For Cave Creek chipset:
-PREFERRED_PROVIDER_virtual/qat ?= "qat15"
-
-Another option and preferred approach for above setting is to override
-configuration under build/conf/local.conf as follow:
-
-For Coleto Creek chipset:
-PREFERRED_PROVIDER_virtual/qat = "qat16"
-
-For Cave Creek chipset:
-PREFERRED_PROVIDER_virtual/qat = "qat15"
-
-By default, the machine configuration does not assume that the above
-ingredients are pre-installed onto the BSP. Developers are required
-to either use smart tool to install those software packages or
-configure IMAGE_INSTALL under build/conf/local.conf, for example.
-
-For Coleto Creek chipset:
-IMAGE_INSTALL += "dpdk qat16 zlib-qat"
-
-For Cavecreek Creek chipset:
-IMAGE_INSTALL += "dpdk qat15 zlib-qat"
-
-The list of packages can be searched under tmp/deploy/<package-type>
-folder.
diff --git a/meta-crystalforest/README.sources b/meta-crystalforest/README.sources
deleted file mode 100644
index 0d4d849..0000000
--- a/meta-crystalforest/README.sources
+++ /dev/null
@@ -1,17 +0,0 @@
-The sources for the packages comprising the images shipped with this
-BSP can be found at the following location:
-
-http://downloads.yoctoproject.org/mirror/sources/
-
-The metadata used to generate the images shipped with this BSP, in
-addition to the code contained in this BSP, can be found at the
-following location:
-
-http://downloads.yoctoproject.org/releases/yocto/yocto-1.3/poky-danny-8.0.tar.bz2
-
-The metadata used to generate the images shipped with this BSP, in
-addition to the code contained in this BSP, can also be found at the
-following locations:
-
-git://git.yoctoproject.org/poky.git
-git://git.yoctoproject.org/meta-intel
diff --git a/meta-crystalforest/binary/.gitignore b/meta-crystalforest/binary/.gitignore
deleted file mode 100644
index e69de29..0000000
diff --git a/meta-crystalforest/conf/layer.conf b/meta-crystalforest/conf/layer.conf
deleted file mode 100644
index daa2ba7..0000000
--- a/meta-crystalforest/conf/layer.conf
+++ /dev/null
@@ -1,12 +0,0 @@
-# We have a conf and classes directory, add to BBPATH
-BBPATH .= ":${LAYERDIR}"
-
-# We have a recipes directory, add to BBFILES
-BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
- ${LAYERDIR}/recipes-*/*/*.bbappend"
-
-BBFILE_COLLECTIONS += "crystalforest"
-BBFILE_PATTERN_crystalforest := "^${LAYERDIR}/"
-BBFILE_PRIORITY_crystalforest = "6"
-
-LAYERDEPENDS_crystalforest = "intel"
diff --git a/meta-crystalforest/conf/machine/crystalforest.conf b/meta-crystalforest/conf/machine/crystalforest.conf
deleted file mode 100644
index 7716e56..0000000
--- a/meta-crystalforest/conf/machine/crystalforest.conf
+++ /dev/null
@@ -1,40 +0,0 @@
-#@TYPE: Machine
-#@NAME: crystalforest
-
-#@WEBTITLE: Intel Xeon E3-1125C/E3-1105C (Formerly Sandy Bridge-Gladden)
-#Processors with Intel Communication Chipset 89xx (Crystal Forest Gladden Platform)
-
-#@DESCRIPTION: Machine configuration for Crystal Forest Gladden systems
-#for Smaller Form Factor Communication Infrastructure
-# i.e. Xeon E3-1125C/E3-1105C + Intel 89xx communication Chipset
-
-#@WEBTITLE: Intel Xeon E5-2600 and E5-2400 (Formerly Sandy Bridge-EP/EN)
-#Processors with Intel Communication Chipset 89xx (Crystal Forest Server Platform)
-
-#@DESCRIPTION: Machine configuration for Crystal Forest Server systems
-#for Large-Scale Communications Infrastructure
-# i.e. Xeon E5-2600 and E5-2400 + Intel 89xx Communication Chipsets
-
-PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
-PREFERRED_VERSION_linux-yocto ?= "3.14%"
-
-require conf/machine/include/intel-corei7-64-common.inc
-require conf/machine/include/intel-common-pkgarch.inc
-require conf/machine/include/meta-intel.inc
-
-XSERVER ?= "${XSERVER_X86_BASE} \
- ${XSERVER_X86_EXT} \
- ${XSERVER_X86_MATROX_MGA} \
- "
-MACHINE_EXTRA_RRECOMMENDS += "calgary-corpus \
- canterbury-corpus \
- "
-#This Kernel Option is required for Intel Quick Assist Technology Software.
-APPEND += "acpi_enforce_resources=lax"
-
-#Uncomment the below Kernel Option if Virtualization is not needed.
-#APPEND += "intel_iommu=off"
-
-SYSLINUX_OPTS = "serial 0 115200"
-SERIAL_CONSOLE = "115200 ttyS0"
-APPEND += "console=ttyS0,115200 console=tty0"
diff --git a/meta-crystalforest/recipes-bsp/formfactor/formfactor/crystalforest-gladden/machconfig b/meta-crystalforest/recipes-bsp/formfactor/formfactor/crystalforest-gladden/machconfig
deleted file mode 100644
index ffce012..0000000
--- a/meta-crystalforest/recipes-bsp/formfactor/formfactor/crystalforest-gladden/machconfig
+++ /dev/null
@@ -1,3 +0,0 @@
-# Assume a USB mouse and keyboard are connected
-HAVE_TOUCHSCREEN=0
-HAVE_KEYBOARD=1
diff --git a/meta-crystalforest/recipes-bsp/formfactor/formfactor/crystalforest-server/machconfig b/meta-crystalforest/recipes-bsp/formfactor/formfactor/crystalforest-server/machconfig
deleted file mode 100644
index ffce012..0000000
--- a/meta-crystalforest/recipes-bsp/formfactor/formfactor/crystalforest-server/machconfig
+++ /dev/null
@@ -1,3 +0,0 @@
-# Assume a USB mouse and keyboard are connected
-HAVE_TOUCHSCREEN=0
-HAVE_KEYBOARD=1
diff --git a/meta-crystalforest/recipes-bsp/formfactor/formfactor_0.0.bbappend b/meta-crystalforest/recipes-bsp/formfactor/formfactor_0.0.bbappend
deleted file mode 100644
index 72d991c..0000000
--- a/meta-crystalforest/recipes-bsp/formfactor/formfactor_0.0.bbappend
+++ /dev/null
@@ -1 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
diff --git a/meta-isg/MAINTAINERS b/meta-isg/MAINTAINERS
index 98b8a5e..36cef64 100644
--- a/meta-isg/MAINTAINERS
+++ b/meta-isg/MAINTAINERS
@@ -49,3 +49,7 @@ F: meta-mohonpeak/
VALLEYISLAND
M: Chang Rebecca Swee Fun <rebecca.swee.fun.chang at intel.com>
F: meta-valleyisland/
+
+CRYSTALFOREST
+M: Wu Chia Chuan <chia.chuan.wu at intel.com>
+F: meta-crystalforest/
diff --git a/meta-isg/meta-crystalforest/COPYING.MIT b/meta-isg/meta-crystalforest/COPYING.MIT
new file mode 100644
index 0000000..fb950dc
--- /dev/null
+++ b/meta-isg/meta-crystalforest/COPYING.MIT
@@ -0,0 +1,17 @@
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
diff --git a/meta-isg/meta-crystalforest/README b/meta-isg/meta-crystalforest/README
new file mode 100644
index 0000000..4878105
--- /dev/null
+++ b/meta-isg/meta-crystalforest/README
@@ -0,0 +1,240 @@
+This README file contains information on building the meta-crystalforest
+BSP layer, and booting the images contained in the /binary directory.
+Please see the corresponding sections below for details.
+
+Overview of Intel Communication Product Offering
+------------------------------------------------
+
+The following platforms are supported on meta-intel dizzy branch ONLY:
+
+Crystal Forest/Server - Shumway reference platform configurations:
+processor: Intel Xeon E5-2600/E5-2400 (Sandy Bridge-based) or
+ Intel Xeon E5-2600v2/E5-2400v2 (Ivy Bridge-based)
+chipset: Intel Communication Chipset 8900-8920 Series (Cave Creek)
+url: http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-e5-89xx/overview
+
+Crystal Forest/Gladden - Stargo reference platform configurations:
+processor: Intel Xeon E3-1125C/E3-1105C (Sandy Bridge-based) or
+ Intel Xeon E3-1125v2/E3-1105v2 (Ivy Bridge-based)
+chipset: Intel Communication Chipset 8900-8920 Series (Cave Creek)
+url: http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-core-pentium-celeron-89xx/overview
+
+Highland Forest (Crystal Forest/Server Refresh) - Shumway reference platform configurations:
+processor: Intel Xeon E5-2600v2/E5-2400v2 (Ivy Bridge-based)
+chipset: Intel Communication Chipset 8925-8955 Series (Coleto Creek)
+url: https://www-ssl.intel.com/content/www/us/en/intelligent-systems/crystal-forest-server/xeon-e5-v2-89xx-chipset-ibd.html
+
+The following platform is supported on meta-intel fido branch and beyond.
+
+River Forest - Long Brook reference platform configurations:
+processor: Intel Xeon E5-2600v3/E5-2400v3 (Haswell EP-based)
+chipset: Intel Communication Chipset 8925-8955 Series (Coleto Creek)
+url: https://www-ssl.intel.com/content/www/my/en/embedded/products/river-forest/overview.html?wapkw=coleto
+
+All above four platforms use PCIe-based Matrox graphics card for display.
+
+More Information on all Intel® embedded platforms can be found here:
+
+ http://www.intel.com/p/en_US/embedded/hwsw/hardware
+
+
+Yocto Project Compatible
+========================
+
+This BSP is compatible with the Yocto Project as per the requirements
+listed here:
+
+ https://www.yoctoproject.org/webform/yocto-project-compatible-registration
+
+Dependencies
+============
+
+This layer depends on:
+
+ URI: git://git.openembedded.org/bitbake
+ branch: master
+
+ URI: git://git.openembedded.org/openembedded-core
+ layers: meta
+ branch: master
+
+ URI: git://git.yoctoproject.org/meta-intel
+ layers: intel
+ branch: master
+
+
+Patches
+=======
+
+Please submit any patches against this BSP to the meta-intel mailing
+list (meta-intel at yoctoproject.org) and cc: the maintainer:
+
+Maintainer: Wu Chia Chuan <chia.chuan.wu at intel.com>
+
+Please see the meta-isg/MAINTAINERS file for more details.
+
+
+Table of Contents
+=================
+
+ I. Building the meta-crystalforest BSP layer
+ II. Booting the images in /binary
+III. Device Notes
+ a. Boot Loader
+ b. I/O drivers
+IV. Enabling Intel DPDK and QuickAssist Technology
+
+I. Building the meta-crystalforest BSP layer
+=======================================
+
+In order to build an image with BSP support for a given release, you
+need to download the corresponding BSP tarball from the 'Board Support
+Package (BSP) Downloads' page of the Yocto Project website.
+
+Having done that, and assuming you extracted the BSP tarball contents
+at the top-level of your yocto build tree, you can build a crystalforest
+image by adding the location of the meta-crystalforest layer to
+bblayers.conf, along with the meta-intel layer itself (to access
+common metadata shared between BSPs) e.g.:
+
+ yocto/meta-intel \
+ yocto/meta-intel/meta-isg/meta-crystalforest \
+
+Crystal Forest layer is meant for building both Crystal Forest Gladden
+and Crystal Forest Server platforms. By enabling Crystal Forest layer,
+the image you build is able to boot on both supported platforms.
+
+To enable the Crystal Forest layer, add the Crystal Forest MACHINE to
+build/local.conf:
+
+ MACHINE ?= "crystalforest"
+
+You should then be able to build a crystalforest image as such:
+
+ $ source oe-init-build-env
+ $ bitbake core-image-sato
+
+At the end of a successful build, you should have a live image that
+you can boot from a USB flash drive (see instructions on how to do
+that below, in the section 'Booting the images from /binary').
+
+The live image is located within build/tmp/deploy/images/<machine> folder.
+
+As an alternative to downloading the BSP tarball, you can also work
+directly from the meta-intel git repository. For each BSP in the
+'meta-intel' repository, there are multiple branches, one
+corresponding to each major release starting with 'laverne' (0.90), in
+addition to the latest code which tracks the current master (note that
+not all BSPs are present in every release). Instead of extracting a
+BSP tarball at the top level of your yocto build tree, you can
+equivalently check out the appropriate branch from the meta-intel
+repository at the same location.
+
+
+II. Booting the images in /binary
+=================================
+
+This BSP contains bootable live images, which can be used to directly
+boot Yocto off of a USB flash drive.
+
+You can deploy the hddimg image to a USB or SATA device. You will
+need to know the device name on your host as well as the device name on
+the target. Be careful with this step as using the wrong host device can
+result in overwriting data on your host machine.
+
+Under Linux, USB and SATA devices typically appears as /dev/sdb,
+/dev/sdc, etc. Watching your system messages as you connect the device
+will tell you exactly which device name is assigned to the device.
+On the Valley Island platform, assuming only one storage device is
+attached at boot, a USB or SATA device will be /dev/sda.
+
+After inserting the boot media into your host machine and determining
+your host and target device, create the image using the mkefidisk.sh
+script, provided by poky under scripts/contrib/. Note that root
+privileges are required. For example, using an USB device which appears
+as /dev/sdc on the host:
+
+$ sudo ./mkefidisk.sh /dev/sdc core-image-sato-<machine>.hddimg /dev/sda
+
+Follow the prompts on the screen to confirm the action.
+
+This should give you a bootable USB flash device. Insert the device
+into a bootable USB socket on the target, and power on. This should
+result in a system booted to the Sato graphical desktop.
+
+If you want a terminal, use the arrows at the top of the UI to move to
+different pages of available applications, one of which is named
+'Terminal'. Clicking that should give you a root terminal.
+
+If you want to ssh into the system, you can use the root terminal to
+ifconfig the IP address and use that to ssh in. The root password is
+empty, so to log in type 'root' for the user name and hit 'Enter' at
+the Password prompt: and you should be in.
+
+III. Device Notes
+=================
+
+a. Boot Loader
+--------------
+- Support BIOS version at Shumway board (HighlandForest/CrystalForest-server):
+ CCFRCLC0.019
+
+- Support BIOS version at Stargo board ( CrystalForest-Gladden ):
+ CIVGCCK1.86C.0003.P00
+
+- Support BIOS version at Long Brook board (RiverForest)
+ GRNDCRB1.86B.0022.R01.i02.1405151000
+
+b. I/O drivers
+--------------
+-Support Matrox graphic card.
+-Support SATA, USB Host v2.0
+-Supported I/O devices (APIC, RTC, SPI, UART, I2C, LPS, SMBus i801,
+ WDT, and HPET)
+
+
+IV. Enabling Intel DPDK and QuickAssist Technology
+===================================================
+
+DPDK recipe: meta-intel/meta-isg/common/recipes-extended/dpdk
+QAT recipe: meta-intel/meta-isg/common/recipes-extended/qat
+QAT-enable zlib recipe: meta-intel/meta-isg/common/recipes-extended/zlib-qat
+
+Note:
+qat16 recipe is meant for platform with Coleto Creek chipset.
+qat15 recipe is meant for platform with Cave Creek chipset.
+
+conf/machine/crystalforest.conf is the common machine configuration
+to support Crystal Forest/server, Crystal Forest/gladden, Highland Forest and
+River Forest. In order to generate the right binary for these platforms which
+have different QAT technology, user could change the default config accordingly
+within crystalforest.conf as below:
+
+For Coleto Creek chipset:
+PREFERRED_PROVIDER_virtual/qat ?= "qat16"
+
+For Cave Creek chipset:
+PREFERRED_PROVIDER_virtual/qat ?= "qat15"
+
+Another option and preferred approach for above setting is to override
+configuration under build/conf/local.conf as follow:
+
+For Coleto Creek chipset:
+PREFERRED_PROVIDER_virtual/qat = "qat16"
+
+For Cave Creek chipset:
+PREFERRED_PROVIDER_virtual/qat = "qat15"
+
+By default, the machine configuration does not assume that the above
+ingredients are pre-installed onto the BSP. Developers are required
+to either use smart tool to install those software packages or
+configure IMAGE_INSTALL under build/conf/local.conf, for example.
+
+For Coleto Creek chipset:
+IMAGE_INSTALL += "dpdk qat16 zlib-qat"
+
+For Cavecreek Creek chipset:
+IMAGE_INSTALL += "dpdk qat15 zlib-qat"
+
+The list of packages can be searched under tmp/deploy/<package-type>
+folder.
diff --git a/meta-isg/meta-crystalforest/README.sources b/meta-isg/meta-crystalforest/README.sources
new file mode 100644
index 0000000..0d4d849
--- /dev/null
+++ b/meta-isg/meta-crystalforest/README.sources
@@ -0,0 +1,17 @@
+The sources for the packages comprising the images shipped with this
+BSP can be found at the following location:
+
+http://downloads.yoctoproject.org/mirror/sources/
+
+The metadata used to generate the images shipped with this BSP, in
+addition to the code contained in this BSP, can be found at the
+following location:
+
+http://downloads.yoctoproject.org/releases/yocto/yocto-1.3/poky-danny-8.0.tar.bz2
+
+The metadata used to generate the images shipped with this BSP, in
+addition to the code contained in this BSP, can also be found at the
+following locations:
+
+git://git.yoctoproject.org/poky.git
+git://git.yoctoproject.org/meta-intel
diff --git a/meta-isg/meta-crystalforest/binary/.gitignore b/meta-isg/meta-crystalforest/binary/.gitignore
new file mode 100644
index 0000000..e69de29
diff --git a/meta-isg/meta-crystalforest/conf/layer.conf b/meta-isg/meta-crystalforest/conf/layer.conf
new file mode 100644
index 0000000..daa2ba7
--- /dev/null
+++ b/meta-isg/meta-crystalforest/conf/layer.conf
@@ -0,0 +1,12 @@
+# We have a conf and classes directory, add to BBPATH
+BBPATH .= ":${LAYERDIR}"
+
+# We have a recipes directory, add to BBFILES
+BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
+ ${LAYERDIR}/recipes-*/*/*.bbappend"
+
+BBFILE_COLLECTIONS += "crystalforest"
+BBFILE_PATTERN_crystalforest := "^${LAYERDIR}/"
+BBFILE_PRIORITY_crystalforest = "6"
+
+LAYERDEPENDS_crystalforest = "intel"
diff --git a/meta-isg/meta-crystalforest/conf/machine/crystalforest.conf b/meta-isg/meta-crystalforest/conf/machine/crystalforest.conf
new file mode 100644
index 0000000..7716e56
--- /dev/null
+++ b/meta-isg/meta-crystalforest/conf/machine/crystalforest.conf
@@ -0,0 +1,40 @@
+#@TYPE: Machine
+#@NAME: crystalforest
+
+#@WEBTITLE: Intel Xeon E3-1125C/E3-1105C (Formerly Sandy Bridge-Gladden)
+#Processors with Intel Communication Chipset 89xx (Crystal Forest Gladden Platform)
+
+#@DESCRIPTION: Machine configuration for Crystal Forest Gladden systems
+#for Smaller Form Factor Communication Infrastructure
+# i.e. Xeon E3-1125C/E3-1105C + Intel 89xx communication Chipset
+
+#@WEBTITLE: Intel Xeon E5-2600 and E5-2400 (Formerly Sandy Bridge-EP/EN)
+#Processors with Intel Communication Chipset 89xx (Crystal Forest Server Platform)
+
+#@DESCRIPTION: Machine configuration for Crystal Forest Server systems
+#for Large-Scale Communications Infrastructure
+# i.e. Xeon E5-2600 and E5-2400 + Intel 89xx Communication Chipsets
+
+PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
+PREFERRED_VERSION_linux-yocto ?= "3.14%"
+
+require conf/machine/include/intel-corei7-64-common.inc
+require conf/machine/include/intel-common-pkgarch.inc
+require conf/machine/include/meta-intel.inc
+
+XSERVER ?= "${XSERVER_X86_BASE} \
+ ${XSERVER_X86_EXT} \
+ ${XSERVER_X86_MATROX_MGA} \
+ "
+MACHINE_EXTRA_RRECOMMENDS += "calgary-corpus \
+ canterbury-corpus \
+ "
+#This Kernel Option is required for Intel Quick Assist Technology Software.
+APPEND += "acpi_enforce_resources=lax"
+
+#Uncomment the below Kernel Option if Virtualization is not needed.
+#APPEND += "intel_iommu=off"
+
+SYSLINUX_OPTS = "serial 0 115200"
+SERIAL_CONSOLE = "115200 ttyS0"
+APPEND += "console=ttyS0,115200 console=tty0"
diff --git a/meta-isg/meta-crystalforest/recipes-bsp/formfactor/formfactor/crystalforest-gladden/machconfig b/meta-isg/meta-crystalforest/recipes-bsp/formfactor/formfactor/crystalforest-gladden/machconfig
new file mode 100644
index 0000000..ffce012
--- /dev/null
+++ b/meta-isg/meta-crystalforest/recipes-bsp/formfactor/formfactor/crystalforest-gladden/machconfig
@@ -0,0 +1,3 @@
+# Assume a USB mouse and keyboard are connected
+HAVE_TOUCHSCREEN=0
+HAVE_KEYBOARD=1
diff --git a/meta-isg/meta-crystalforest/recipes-bsp/formfactor/formfactor/crystalforest-server/machconfig b/meta-isg/meta-crystalforest/recipes-bsp/formfactor/formfactor/crystalforest-server/machconfig
new file mode 100644
index 0000000..ffce012
--- /dev/null
+++ b/meta-isg/meta-crystalforest/recipes-bsp/formfactor/formfactor/crystalforest-server/machconfig
@@ -0,0 +1,3 @@
+# Assume a USB mouse and keyboard are connected
+HAVE_TOUCHSCREEN=0
+HAVE_KEYBOARD=1
diff --git a/meta-isg/meta-crystalforest/recipes-bsp/formfactor/formfactor_0.0.bbappend b/meta-isg/meta-crystalforest/recipes-bsp/formfactor/formfactor_0.0.bbappend
new file mode 100644
index 0000000..72d991c
--- /dev/null
+++ b/meta-isg/meta-crystalforest/recipes-bsp/formfactor/formfactor_0.0.bbappend
@@ -0,0 +1 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
--
1.7.9.5
More information about the meta-intel
mailing list