meta-isg: meta-haswell-wc: BSP layer retirement

The meta-haswell-wc BSP layer is retired in future YP releases.The
plan is to consolidate all Intel SoC BSP into intel common BSP.

Since the features provided by meta-haswell-wc can be obtained
from Intel Common BSP with newer kernel version, this layer can
be retired from master.

Signed-off-by: Ong Chun Weng <chun.weng.ong@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>

7 files changed, 0 insertions, 251 deletions

diff --git a/meta-isg/meta-haswell-wc/COPYING.MIT b/meta-isg/meta-haswell-wc/COPYING.MIT
deleted file mode 100644
index 89de3547..00000000
--- a/meta-isg/meta-haswell-wc/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-isg/meta-haswell-wc/README b/meta-isg/meta-haswell-wc/README
deleted file mode 100644
index 2b7f2753..00000000
--- a/meta-isg/meta-haswell-wc/README
+++ /dev/null
@@ -1,172 +0,0 @@
-This README file contains information on building the meta-haswell-wc
-BSP layer, and booting the images contained in the /binary directory.
-Please see the corresponding sections below for details.
-
-The BSP is made specifically for 4th Gen Intel Core Processor (Haswell)
-Development Kit with Mobile Intel QM87 & HM86 Chipset (formerly known as
-Shark Bay). This BSP assumes that integrated graphics are being used.
-The "haswell-wc" BSP is meant to support "Walnut Canyon" Shark Bay
-development kit.
-
-Further information about the Haswell Platforms supported by this BSP can be
-found here:
-
-  http://www.intel.com/content/www/us/en/intelligent-systems/shark-bay/4th-generation-core-qm87-hm86-chipsets.html
-
-Information on all Intel® embedded platforms can be found here:
-
-  http://www.intel.com/p/en_US/embedded/hwsw/hardware
-
-
-Compliance
-==========
-
-This BSP is compliant 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 Yocto mailing list
-(meta-intel@yoctoproject.org) and cc: the maintainer:
-
-Maintainer: Ng Wei Tee <wei.tee.ng@intel.com>
-
-Please see the meta-intel/MAINTAINERS file for more details.
-
-
-Table of Contents
-=================
-
-  I. Building the meta-haswell-wc BSP layer
- II. Booting the images in /binary
-III. Device Notes
-     a. Boot Loader
-     b. I/O drivers
-
-
-I. Building the meta-haswell-wc 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 haswell-wc
-image by adding the location of the meta-haswell-wc 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-haswell-wc \
-
-To enable the haswell-wc layer, add the haswell-wc MACHINE to local.conf:
-
-  MACHINE ?= "haswell-wc"
-
-You should then be able to build a haswell-wc 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').
-
-NOTE: The 'haswell-wc' machine will include support for hardware video
-acceleration via gstreamer if and only if the "commercial" string is
-added to the the LICENSE_FLAGS_WHITELIST variable in your local.conf.
-
-For example:
-
-  LICENSE_FLAGS_WHITELIST = "commercial"
-
-The reason this is needed is to prevent the image from including
-anything that might violate the license terms of the packages used to
-implement the the video acceleration feature, such as gst-ffmpeg and
-ffmpeg.  As always, please consult the licenses included in the
-specific packages for details if you use packages that require
-particular LICENSE_FLAGS.
-
-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.
-
-Under Linux, insert a USB flash drive.  Assuming the USB flash drive
-takes device /dev/sdf, use dd to copy the live image to it.  For
-example:
-
-# dd if=core-image-sato-haswell-wc.hddimg of=/dev/sdf
-# sync
-# eject /dev/sdf
-
-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.
-
-----
-
-If you find you're getting corrupt images on the USB (it doesn't show
-the syslinux boot: prompt, or the boot: prompt contains strange
-characters), try doing this first:
-
-# dd if=/dev/zero of=/dev/sdf bs=1M count=512
-
-
-III. Device Notes
-=================
-
-a. Boot Loader
---------------
-BIOS:   HSWLPTU1.86C.0131.R05.1308140140
-
-b. I/O drivers
---------------
-Support integrated graphics driver (i965)
-
-Support SATA, USB Host v2.0
-
-Supported I/O devices (APIC, RTC, SPI, UART, I2C, LPS, SMBus i801,
-WDT, and HPET)
diff --git a/meta-isg/meta-haswell-wc/README.sources b/meta-isg/meta-haswell-wc/README.sources
deleted file mode 100644
index 8cde68e8..00000000
--- a/meta-isg/meta-haswell-wc/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.4/poky-dylan-9.0.2.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-haswell-wc/conf/layer.conf b/meta-isg/meta-haswell-wc/conf/layer.conf
deleted file mode 100644
index bfd1f823..00000000
--- a/meta-isg/meta-haswell-wc/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 += "haswell-wc"
-BBFILE_PATTERN_haswell-wc := "^${LAYERDIR}/"
-BBFILE_PRIORITY_haswell-wc = "6"
-
-LAYERDEPENDS_haswell-wc = "intel"
diff --git a/meta-isg/meta-haswell-wc/conf/machine/haswell-wc.conf b/meta-isg/meta-haswell-wc/conf/machine/haswell-wc.conf
deleted file mode 100644
index d6e62169..00000000
--- a/meta-isg/meta-haswell-wc/conf/machine/haswell-wc.conf
+++ /dev/null
@@ -1,29 +0,0 @@
-#@TYPE: Machine
-#@NAME: haswell-wc
-
-#@WEBTITLE: 4th Generation Intel Core Processors with Mobile
-# Intel QM87 and HM86 Chipsets (Formerly Shark Bay)
-
-#@DESCRIPTION: Machine configuration for "Walnut Canyon",
-# a Shark Bay development kit.
-
-PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
-PREFERRED_VERSION_linux-yocto ?= "3.19%"
-
-MACHINE_FEATURES += "pcbios efi va-impl-intel"
-
-require conf/machine/include/intel-corei7-64-common.inc
-require conf/machine/include/intel-common-pkgarch.inc
-require conf/machine/include/meta-intel.inc
-
-MACHINE_HWCODECS ?= "va-intel gstreamer-vaapi-1.0"
-
-XSERVER ?= "${XSERVER_X86_BASE} \
-            ${XSERVER_X86_EXT} \
-            ${XSERVER_X86_I965} \
-           "
-
-#Since intel-common-standard.scc turn on CONFIG_FB_EFI
-#This Kernel Option is required in order to disable FB-EFI
-#If not the SATO image will be freezed.
-APPEND += "video=efifb:off"
diff --git a/meta-isg/meta-haswell-wc/recipes-bsp/formfactor/formfactor/haswell-wc/machconfig b/meta-isg/meta-haswell-wc/recipes-bsp/formfactor/formfactor/haswell-wc/machconfig
deleted file mode 100644
index ffce0122..00000000
--- a/meta-isg/meta-haswell-wc/recipes-bsp/formfactor/formfactor/haswell-wc/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-isg/meta-haswell-wc/recipes-bsp/formfactor/formfactor_0.0.bbappend b/meta-isg/meta-haswell-wc/recipes-bsp/formfactor/formfactor_0.0.bbappend
deleted file mode 100644
index 72d991c7..00000000
--- a/meta-isg/meta-haswell-wc/recipes-bsp/formfactor/formfactor_0.0.bbappend
+++ /dev/null
@@ -1 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"