diff options
author | Ong Chun Weng <chun.weng.ong@intel.com> | 2016-08-24 14:58:52 +0800 |
---|---|---|
committer | Tom Zanussi <tom.zanussi@linux.intel.com> | 2016-08-25 11:15:10 -0500 |
commit | 99fa5a9466158e4847d7d1efd64ca1e0e002d495 (patch) | |
tree | c915f0892a206e346fd52d6110fedb2e1497ebfd | |
parent | 20c6a8ab096c01a26f6cbac93ffe0d2004619061 (diff) | |
download | meta-intel-99fa5a9466158e4847d7d1efd64ca1e0e002d495.tar.gz |
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>
-rw-r--r-- | meta-isg/meta-haswell-wc/COPYING.MIT | 17 | ||||
-rw-r--r-- | meta-isg/meta-haswell-wc/README | 172 | ||||
-rw-r--r-- | meta-isg/meta-haswell-wc/README.sources | 17 | ||||
-rw-r--r-- | meta-isg/meta-haswell-wc/conf/layer.conf | 12 | ||||
-rw-r--r-- | meta-isg/meta-haswell-wc/conf/machine/haswell-wc.conf | 29 | ||||
-rw-r--r-- | meta-isg/meta-haswell-wc/recipes-bsp/formfactor/formfactor/haswell-wc/machconfig | 3 | ||||
-rw-r--r-- | meta-isg/meta-haswell-wc/recipes-bsp/formfactor/formfactor_0.0.bbappend | 1 |
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 @@ | |||
1 | Permission is hereby granted, free of charge, to any person obtaining a copy | ||
2 | of this software and associated documentation files (the "Software"), to deal | ||
3 | in the Software without restriction, including without limitation the rights | ||
4 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | ||
5 | copies of the Software, and to permit persons to whom the Software is | ||
6 | furnished to do so, subject to the following conditions: | ||
7 | |||
8 | The above copyright notice and this permission notice shall be included in | ||
9 | all copies or substantial portions of the Software. | ||
10 | |||
11 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR | ||
12 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, | ||
13 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE | ||
14 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER | ||
15 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, | ||
16 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN | ||
17 | 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 @@ | |||
1 | This README file contains information on building the meta-haswell-wc | ||
2 | BSP layer, and booting the images contained in the /binary directory. | ||
3 | Please see the corresponding sections below for details. | ||
4 | |||
5 | The BSP is made specifically for 4th Gen Intel Core Processor (Haswell) | ||
6 | Development Kit with Mobile Intel QM87 & HM86 Chipset (formerly known as | ||
7 | Shark Bay). This BSP assumes that integrated graphics are being used. | ||
8 | The "haswell-wc" BSP is meant to support "Walnut Canyon" Shark Bay | ||
9 | development kit. | ||
10 | |||
11 | Further information about the Haswell Platforms supported by this BSP can be | ||
12 | found here: | ||
13 | |||
14 | http://www.intel.com/content/www/us/en/intelligent-systems/shark-bay/4th-generation-core-qm87-hm86-chipsets.html | ||
15 | |||
16 | Information on all IntelĀ® embedded platforms can be found here: | ||
17 | |||
18 | http://www.intel.com/p/en_US/embedded/hwsw/hardware | ||
19 | |||
20 | |||
21 | Compliance | ||
22 | ========== | ||
23 | |||
24 | This BSP is compliant with the Yocto Project as per the requirements | ||
25 | listed here: | ||
26 | |||
27 | https://www.yoctoproject.org/webform/yocto-project-compatible-registration | ||
28 | |||
29 | |||
30 | Dependencies | ||
31 | ============ | ||
32 | |||
33 | This layer depends on: | ||
34 | |||
35 | URI: git://git.openembedded.org/bitbake | ||
36 | branch: master | ||
37 | |||
38 | URI: git://git.openembedded.org/openembedded-core | ||
39 | layers: meta | ||
40 | branch: master | ||
41 | |||
42 | URI: git://git.yoctoproject.org/meta-intel | ||
43 | layers: intel | ||
44 | branch: master | ||
45 | |||
46 | Patches | ||
47 | ======= | ||
48 | |||
49 | Please submit any patches against this BSP to the Yocto mailing list | ||
50 | (meta-intel@yoctoproject.org) and cc: the maintainer: | ||
51 | |||
52 | Maintainer: Ng Wei Tee <wei.tee.ng@intel.com> | ||
53 | |||
54 | Please see the meta-intel/MAINTAINERS file for more details. | ||
55 | |||
56 | |||
57 | Table of Contents | ||
58 | ================= | ||
59 | |||
60 | I. Building the meta-haswell-wc BSP layer | ||
61 | II. Booting the images in /binary | ||
62 | III. Device Notes | ||
63 | a. Boot Loader | ||
64 | b. I/O drivers | ||
65 | |||
66 | |||
67 | I. Building the meta-haswell-wc BSP layer | ||
68 | ======================================= | ||
69 | |||
70 | In order to build an image with BSP support for a given release, you | ||
71 | need to download the corresponding BSP tarball from the 'Board Support | ||
72 | Package (BSP) Downloads' page of the Yocto Project website. | ||
73 | |||
74 | Having done that, and assuming you extracted the BSP tarball contents | ||
75 | at the top-level of your yocto build tree, you can build a haswell-wc | ||
76 | image by adding the location of the meta-haswell-wc layer to | ||
77 | bblayers.conf, along with the meta-intel layer itself (to access | ||
78 | common metadata shared between BSPs) e.g.: | ||
79 | |||
80 | yocto/meta-intel \ | ||
81 | yocto/meta-intel/meta-isg/meta-haswell-wc \ | ||
82 | |||
83 | To enable the haswell-wc layer, add the haswell-wc MACHINE to local.conf: | ||
84 | |||
85 | MACHINE ?= "haswell-wc" | ||
86 | |||
87 | You should then be able to build a haswell-wc image as such: | ||
88 | |||
89 | $ source oe-init-build-env | ||
90 | $ bitbake core-image-sato | ||
91 | |||
92 | At the end of a successful build, you should have a live image that | ||
93 | you can boot from a USB flash drive (see instructions on how to do | ||
94 | that below, in the section 'Booting the images from /binary'). | ||
95 | |||
96 | NOTE: The 'haswell-wc' machine will include support for hardware video | ||
97 | acceleration via gstreamer if and only if the "commercial" string is | ||
98 | added to the the LICENSE_FLAGS_WHITELIST variable in your local.conf. | ||
99 | |||
100 | For example: | ||
101 | |||
102 | LICENSE_FLAGS_WHITELIST = "commercial" | ||
103 | |||
104 | The reason this is needed is to prevent the image from including | ||
105 | anything that might violate the license terms of the packages used to | ||
106 | implement the the video acceleration feature, such as gst-ffmpeg and | ||
107 | ffmpeg. As always, please consult the licenses included in the | ||
108 | specific packages for details if you use packages that require | ||
109 | particular LICENSE_FLAGS. | ||
110 | |||
111 | As an alternative to downloading the BSP tarball, you can also work | ||
112 | directly from the meta-intel git repository. For each BSP in the | ||
113 | 'meta-intel' repository, there are multiple branches, one | ||
114 | corresponding to each major release starting with 'laverne' (0.90), in | ||
115 | addition to the latest code which tracks the current master (note that | ||
116 | not all BSPs are present in every release). Instead of extracting a | ||
117 | BSP tarball at the top level of your yocto build tree, you can | ||
118 | equivalently check out the appropriate branch from the meta-intel | ||
119 | repository at the same location. | ||
120 | |||
121 | |||
122 | II. Booting the images in /binary | ||
123 | ================================= | ||
124 | |||
125 | This BSP contains bootable live images, which can be used to directly | ||
126 | boot Yocto off of a USB flash drive. | ||
127 | |||
128 | Under Linux, insert a USB flash drive. Assuming the USB flash drive | ||
129 | takes device /dev/sdf, use dd to copy the live image to it. For | ||
130 | example: | ||
131 | |||
132 | # dd if=core-image-sato-haswell-wc.hddimg of=/dev/sdf | ||
133 | # sync | ||
134 | # eject /dev/sdf | ||
135 | |||
136 | This should give you a bootable USB flash device. Insert the device | ||
137 | into a bootable USB socket on the target, and power on. This should | ||
138 | result in a system booted to the Sato graphical desktop. | ||
139 | |||
140 | If you want a terminal, use the arrows at the top of the UI to move to | ||
141 | different pages of available applications, one of which is named | ||
142 | 'Terminal'. Clicking that should give you a root terminal. | ||
143 | |||
144 | If you want to ssh into the system, you can use the root terminal to | ||
145 | ifconfig the IP address and use that to ssh in. The root password is | ||
146 | empty, so to log in type 'root' for the user name and hit 'Enter' at | ||
147 | the Password prompt: and you should be in. | ||
148 | |||
149 | ---- | ||
150 | |||
151 | If you find you're getting corrupt images on the USB (it doesn't show | ||
152 | the syslinux boot: prompt, or the boot: prompt contains strange | ||
153 | characters), try doing this first: | ||
154 | |||
155 | # dd if=/dev/zero of=/dev/sdf bs=1M count=512 | ||
156 | |||
157 | |||
158 | III. Device Notes | ||
159 | ================= | ||
160 | |||
161 | a. Boot Loader | ||
162 | -------------- | ||
163 | BIOS: HSWLPTU1.86C.0131.R05.1308140140 | ||
164 | |||
165 | b. I/O drivers | ||
166 | -------------- | ||
167 | Support integrated graphics driver (i965) | ||
168 | |||
169 | Support SATA, USB Host v2.0 | ||
170 | |||
171 | Supported I/O devices (APIC, RTC, SPI, UART, I2C, LPS, SMBus i801, | ||
172 | 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 @@ | |||
1 | The sources for the packages comprising the images shipped with this | ||
2 | BSP can be found at the following location: | ||
3 | |||
4 | http://downloads.yoctoproject.org/mirror/sources/ | ||
5 | |||
6 | The metadata used to generate the images shipped with this BSP, in | ||
7 | addition to the code contained in this BSP, can be found at the | ||
8 | following location: | ||
9 | |||
10 | http://downloads.yoctoproject.org/releases/yocto/yocto-1.4/poky-dylan-9.0.2.tar.bz2 | ||
11 | |||
12 | The metadata used to generate the images shipped with this BSP, in | ||
13 | addition to the code contained in this BSP, can also be found at the | ||
14 | following locations: | ||
15 | |||
16 | git://git.yoctoproject.org/poky.git | ||
17 | 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 @@ | |||
1 | # We have a conf and classes directory, add to BBPATH | ||
2 | BBPATH .= ":${LAYERDIR}" | ||
3 | |||
4 | # We have a recipes directory, add to BBFILES | ||
5 | BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \ | ||
6 | ${LAYERDIR}/recipes-*/*/*.bbappend" | ||
7 | |||
8 | BBFILE_COLLECTIONS += "haswell-wc" | ||
9 | BBFILE_PATTERN_haswell-wc := "^${LAYERDIR}/" | ||
10 | BBFILE_PRIORITY_haswell-wc = "6" | ||
11 | |||
12 | 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 @@ | |||
1 | #@TYPE: Machine | ||
2 | #@NAME: haswell-wc | ||
3 | |||
4 | #@WEBTITLE: 4th Generation Intel Core Processors with Mobile | ||
5 | # Intel QM87 and HM86 Chipsets (Formerly Shark Bay) | ||
6 | |||
7 | #@DESCRIPTION: Machine configuration for "Walnut Canyon", | ||
8 | # a Shark Bay development kit. | ||
9 | |||
10 | PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto" | ||
11 | PREFERRED_VERSION_linux-yocto ?= "3.19%" | ||
12 | |||
13 | MACHINE_FEATURES += "pcbios efi va-impl-intel" | ||
14 | |||
15 | require conf/machine/include/intel-corei7-64-common.inc | ||
16 | require conf/machine/include/intel-common-pkgarch.inc | ||
17 | require conf/machine/include/meta-intel.inc | ||
18 | |||
19 | MACHINE_HWCODECS ?= "va-intel gstreamer-vaapi-1.0" | ||
20 | |||
21 | XSERVER ?= "${XSERVER_X86_BASE} \ | ||
22 | ${XSERVER_X86_EXT} \ | ||
23 | ${XSERVER_X86_I965} \ | ||
24 | " | ||
25 | |||
26 | #Since intel-common-standard.scc turn on CONFIG_FB_EFI | ||
27 | #This Kernel Option is required in order to disable FB-EFI | ||
28 | #If not the SATO image will be freezed. | ||
29 | 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 @@ | |||
1 | # Assume a USB mouse and keyboard are connected | ||
2 | HAVE_TOUCHSCREEN=0 | ||
3 | 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 @@ | |||
1 | FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" | ||