summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat
-rw-r--r--MAINTAINERS24
-rw-r--r--conf/layer.conf2
-rw-r--r--meta-crownbay/COPYING.MIT17
-rw-r--r--meta-crownbay/README140
-rw-r--r--meta-crownbay/README.sources17
-rw-r--r--meta-crownbay/binary/.gitignore0
-rw-r--r--meta-crownbay/conf/layer.conf12
-rw-r--r--meta-crownbay/conf/machine/crownbay-noemgd.conf22
-rw-r--r--meta-crownbay/recipes-bsp/formfactor/formfactor/crownbay-noemgd/machconfig3
-rw-r--r--meta-crownbay/recipes-bsp/formfactor/formfactor_0.0.bbappend1
-rw-r--r--meta-crownbay/recipes-kernel/kmod/kmod_git.bbappend3
-rw-r--r--meta-emenlow/COPYING.MIT17
-rw-r--r--meta-emenlow/README148
-rw-r--r--meta-emenlow/README.sources17
-rw-r--r--meta-emenlow/binary/.gitignore0
-rw-r--r--meta-emenlow/conf/layer.conf12
-rw-r--r--meta-emenlow/conf/machine/emenlow-noemgd.conf20
-rw-r--r--meta-emenlow/recipes-bsp/formfactor/formfactor/emenlow-noemgd/machconfig3
-rw-r--r--meta-emenlow/recipes-bsp/formfactor/formfactor_0.0.bbappend1
-rw-r--r--meta-emenlow/recipes-graphics/xorg-xserver/xserver-xf86-config/emenlow-noemgd/xorg.conf22
-rw-r--r--meta-emenlow/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend3
-rw-r--r--meta-emenlow/recipes-kernel/linux/linux-yocto-dev.bbappend10
-rw-r--r--meta-emenlow/recipes-kernel/linux/linux-yocto_3.14.bbappend10
-rw-r--r--meta-fri2/COPYING.MIT17
-rw-r--r--meta-fri2/README339
-rw-r--r--meta-fri2/README.sources17
-rw-r--r--meta-fri2/binary/.gitignore0
-rw-r--r--meta-fri2/conf/layer.conf12
-rw-r--r--meta-fri2/conf/machine/fri2-noemgd.conf36
-rw-r--r--meta-fri2/recipes-bsp/alsa-state/alsa-state.bbappend1
-rw-r--r--meta-fri2/recipes-bsp/alsa-state/alsa-state/fri2-noemgd/asound.state411
-rw-r--r--meta-fri2/recipes-bsp/formfactor/formfactor/fri2-noemgd/machconfig3
-rw-r--r--meta-fri2/recipes-bsp/formfactor/formfactor_0.0.bbappend1
-rw-r--r--meta-fri2/recipes-bsp/grub/grub-efi_2.00.bbappend13
-rw-r--r--meta-fri2/recipes-core/init-ifupdown/files/fri2-noemgd/interfaces9
-rw-r--r--meta-fri2/recipes-core/init-ifupdown/init-ifupdown_1.0.bbappend1
-rw-r--r--meta-fri2/recipes-kernel/kmod/kmod_git.bbappend3
-rw-r--r--meta-jasperforest/COPYING.MIT17
-rw-r--r--meta-jasperforest/README137
-rw-r--r--meta-jasperforest/README.sources17
-rw-r--r--meta-jasperforest/binary/.gitignore0
-rw-r--r--meta-jasperforest/conf/layer.conf12
-rw-r--r--meta-jasperforest/conf/machine/jasperforest.conf22
-rw-r--r--meta-jasperforest/recipes-bsp/formfactor/formfactor/jasperforest/machconfig3
-rw-r--r--meta-jasperforest/recipes-bsp/formfactor/formfactor_0.0.bbappend1
-rw-r--r--meta-nuc/COPYING.MIT17
-rw-r--r--meta-nuc/README156
-rw-r--r--meta-nuc/README.sources17
-rw-r--r--meta-nuc/conf/layer.conf10
-rw-r--r--meta-nuc/conf/machine/nuc.conf27
-rw-r--r--meta-nuc/recipes-bsp/alsa-state/alsa-state.bbappend1
-rw-r--r--meta-nuc/recipes-bsp/alsa-state/alsa-state/nuc/asound.conf24
-rw-r--r--meta-nuc/recipes-bsp/formfactor/formfactor/nuc/machconfig3
-rw-r--r--meta-nuc/recipes-bsp/formfactor/formfactor_0.0.bbappend1
-rw-r--r--meta-nuc/recipes-core/initscripts/initscripts/hdmi_port_audio.sh28
-rw-r--r--meta-nuc/recipes-core/initscripts/initscripts_1.0.bbappend10
-rw-r--r--meta-sugarbay/COPYING.MIT17
-rw-r--r--meta-sugarbay/README158
-rw-r--r--meta-sugarbay/README.sources17
-rw-r--r--meta-sugarbay/binary/.gitignore0
-rw-r--r--meta-sugarbay/conf/layer.conf12
-rw-r--r--meta-sugarbay/conf/machine/sugarbay.conf26
-rw-r--r--meta-sugarbay/recipes-bsp/formfactor/formfactor/sugarbay/machconfig3
-rw-r--r--meta-sugarbay/recipes-bsp/formfactor/formfactor_0.0.bbappend1
64 files changed, 3 insertions, 2101 deletions
diff --git a/MAINTAINERS b/MAINTAINERS
index 64019636..233fa2eb 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -18,8 +18,8 @@ Descriptions of section entries:
18 M: Mail patches to: FullName <address@domain> 18 M: Mail patches to: FullName <address@domain>
19 F: Files and directories with wildcard patterns. 19 F: Files and directories with wildcard patterns.
20 A trailing slash includes all files and subdirectory files. 20 A trailing slash includes all files and subdirectory files.
21 F: meta-crownbay/ all files in and below meta-crownbay 21 F: common/ all files in and below common
22 F: meta-crownbay/* all files in meta-crownbay, but not below 22 F: common/* all files in common, but not below
23 One pattern per line. Multiple F: lines acceptable. 23 One pattern per line. Multiple F: lines acceptable.
24 24
25Please keep this list in alphabetical order. 25Please keep this list in alphabetical order.
@@ -31,34 +31,14 @@ COMMON
31M: Saul Wold <sgw@linux.intel.com> 31M: Saul Wold <sgw@linux.intel.com>
32F: common/ 32F: common/
33 33
34CROWNBAY
35M: Saul Wold <sgw@linux.intel.com>
36F: meta-crownbay/
37
38CRYSTALFOREST 34CRYSTALFOREST
39M: Wu Chia Chuan <chia.chuan.wu@intel.com> 35M: Wu Chia Chuan <chia.chuan.wu@intel.com>
40F: meta-crystalforest/ 36F: meta-crystalforest/
41 37
42EMENLOW
43M: Saul Wold <sgw@linux.intel.com>
44F: meta-emenlow/
45
46FRI2
47M: Darren Hart <dvhart@linux.intel.com>
48F: meta-fri2/
49
50JASPERFOREST
51M: Saul Wold <sgw@linux.intel.com>
52F: meta-jasperforest/
53
54ROMLEY 38ROMLEY
55M: Wu Chia Chuan <chia.chuan.wu@intel.com> 39M: Wu Chia Chuan <chia.chuan.wu@intel.com>
56F: meta-romley/ 40F: meta-romley/
57 41
58SUGARBAY
59M: Saul Wold <sgw@linux.intel.com>
60F: meta-sugarbay/
61
62TLK 42TLK
63M: Saul Wold <sgw@linux.intel.com> 43M: Saul Wold <sgw@linux.intel.com>
64F: meta-tlk/ 44F: meta-tlk/
diff --git a/conf/layer.conf b/conf/layer.conf
index 3b7de9aa..f419fe63 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -14,4 +14,4 @@ LICENSE_PATH += "${LAYERDIR}/common/custom-licenses"
14 14
15# This should only be incremented on significant changes that will 15# This should only be incremented on significant changes that will
16# cause compatibility issues with other layers 16# cause compatibility issues with other layers
17LAYERVERSION_intel = "2" 17LAYERVERSION_intel = "3"
diff --git a/meta-crownbay/COPYING.MIT b/meta-crownbay/COPYING.MIT
deleted file mode 100644
index fb950dc6..00000000
--- a/meta-crownbay/COPYING.MIT
+++ /dev/null
@@ -1,17 +0,0 @@
1Permission is hereby granted, free of charge, to any person obtaining a copy
2of this software and associated documentation files (the "Software"), to deal
3in the Software without restriction, including without limitation the rights
4to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
5copies of the Software, and to permit persons to whom the Software is
6furnished to do so, subject to the following conditions:
7
8The above copyright notice and this permission notice shall be included in
9all copies or substantial portions of the Software.
10
11THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
12IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
13FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
14AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
15LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
16OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
17THE SOFTWARE.
diff --git a/meta-crownbay/README b/meta-crownbay/README
deleted file mode 100644
index 03dafb40..00000000
--- a/meta-crownbay/README
+++ /dev/null
@@ -1,140 +0,0 @@
1This README file contains information on building the meta-crownbay
2BSP layer, and booting the images contained in the /binary directory.
3Please see the corresponding sections below for details.
4
5The Crown Bay platform consists of the Intel Atom E6xx processor,
6plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff).
7
8Further information on the platforms supported by this BSP can be
9found here:
10
11 http://www.intel.com/p/en_US/embedded/hwsw/hardware/atom-e6xx/overview
12
13And information on all Intel® embedded platforms can be found here:
14
15 http://www.intel.com/p/en_US/embedded/hwsw/hardware
16
17
18Yocto Project Compatible
19========================
20
21This BSP is compatible with the Yocto Project as per the requirements
22listed here:
23
24 https://www.yoctoproject.org/webform/yocto-project-compatible-registration
25
26
27Dependencies
28============
29
30This layer depends on:
31
32 URI: git://git.openembedded.org/bitbake
33 branch: master
34
35 URI: git://git.openembedded.org/openembedded-core
36 layers: meta
37 branch: master
38
39 URI: git://git.yoctoproject.org/meta-intel
40 layers: intel
41 branch: master
42
43
44Patches
45=======
46
47Please submit any patches against this BSP to the meta-intel mailing list
48(meta-intel@yoctoproject.org) and cc: the maintainer:
49
50Maintainer: Saul Wold <sgw@linux.intel.com>
51
52Please see the meta-intel/MAINTAINERS file for more details.
53
54
55Table of Contents
56=================
57
58 I. Building the meta-crownbay BSP layer
59 II. Booting the images in /binary
60
61
62I. Building the meta-crownbay BSP layer
63=======================================
64
65In order to build an image with BSP support for a given release, you
66need to download the corresponding BSP tarball from the 'Board Support
67Package (BSP) Downloads' page of the Yocto Project website.
68
69Having done that, and assuming you extracted the BSP tarball contents
70at the top-level of your yocto build tree, you can build a crownbay
71image by adding the location of the meta-crownbay layer to
72bblayers.conf, along with the meta-intel layer itself (to access
73common metadata shared between BSPs) e.g.:
74
75 yocto/meta-intel \
76 yocto/meta-intel/meta-crownbay \
77
78The meta-crownbay layer contains support for the crownbay-noemgd machine
79configuration. The previously supported crownbay machine with the
80proprietary EMGD graphics driver has been retired. The 'crownbay-noemgd'
81machine configuration uses the open source 'vesa' kernel driver.
82
83To enable the layer add the following to the local.conf file:
84
85 MACHINE ?= "crownbay-noemgd"
86
87You should then be able to build a crownbay image as such:
88
89 $ source oe-init-build-env
90 $ bitbake core-image-sato
91
92At the end of a successful build, you should have a live image that
93you can boot from a USB flash drive (see instructions on how to do
94that below, in the section 'Booting the images from /binary').
95
96As an alternative to downloading the BSP tarball, you can also work
97directly from the meta-intel git repository. For each BSP in the
98'meta-intel' repository, there are multiple branches, one
99corresponding to each major release starting with 'laverne' (0.90), in
100addition to the latest code which tracks the current master (note that
101not all BSPs are present in every release). Instead of extracting
102a BSP tarball at the top level of your yocto build tree, you can
103equivalently check out the appropriate branch from the meta-intel
104repository at the same location.
105
106
107II. Booting the images in /binary
108=================================
109
110This BSP contains bootable live images, which can be used to directly
111boot Yocto off of a USB flash drive.
112
113Under Linux, insert a USB flash drive. Assuming the USB flash drive
114takes device /dev/sdf, use dd to copy the live image to it. For
115example:
116
117# dd if=core-image-sato-crownbay-noemgd.hddimg of=/dev/sdf
118# sync
119# eject /dev/sdf
120
121This should give you a bootable USB flash device. Insert the device
122into a bootable USB socket on the target, and power on. This should
123result in a system booted to the Sato graphical desktop.
124
125If you want a terminal, use the arrows at the top of the UI to move to
126different pages of available applications, one of which is named
127'Terminal'. Clicking that should give you a root terminal.
128
129If you want to ssh into the system, you can use the root terminal to
130ifconfig the IP address and use that to ssh in. The root password is
131empty, so to log in type 'root' for the user name and hit 'Enter' at
132the Password prompt: and you should be in.
133
134----
135
136If you find you're getting corrupt images on the USB (it doesn't show
137the syslinux boot: prompt, or the boot: prompt contains strange
138characters), try doing this first:
139
140# dd if=/dev/zero of=/dev/sdf bs=1M count=512
diff --git a/meta-crownbay/README.sources b/meta-crownbay/README.sources
deleted file mode 100644
index 0d4d849a..00000000
--- a/meta-crownbay/README.sources
+++ /dev/null
@@ -1,17 +0,0 @@
1The sources for the packages comprising the images shipped with this
2BSP can be found at the following location:
3
4http://downloads.yoctoproject.org/mirror/sources/
5
6The metadata used to generate the images shipped with this BSP, in
7addition to the code contained in this BSP, can be found at the
8following location:
9
10http://downloads.yoctoproject.org/releases/yocto/yocto-1.3/poky-danny-8.0.tar.bz2
11
12The metadata used to generate the images shipped with this BSP, in
13addition to the code contained in this BSP, can also be found at the
14following locations:
15
16git://git.yoctoproject.org/poky.git
17git://git.yoctoproject.org/meta-intel
diff --git a/meta-crownbay/binary/.gitignore b/meta-crownbay/binary/.gitignore
deleted file mode 100644
index e69de29b..00000000
--- a/meta-crownbay/binary/.gitignore
+++ /dev/null
diff --git a/meta-crownbay/conf/layer.conf b/meta-crownbay/conf/layer.conf
deleted file mode 100644
index e6cc2a02..00000000
--- a/meta-crownbay/conf/layer.conf
+++ /dev/null
@@ -1,12 +0,0 @@
1# We have a conf and classes directory, add to BBPATH
2BBPATH .= ":${LAYERDIR}"
3
4# We have a recipes directory, add to BBFILES
5BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
6 ${LAYERDIR}/recipes-*/*/*.bbappend"
7
8BBFILE_COLLECTIONS += "crownbay"
9BBFILE_PATTERN_crownbay := "^${LAYERDIR}/"
10BBFILE_PRIORITY_crownbay = "6"
11
12LAYERDEPENDS_crownbay = "intel"
diff --git a/meta-crownbay/conf/machine/crownbay-noemgd.conf b/meta-crownbay/conf/machine/crownbay-noemgd.conf
deleted file mode 100644
index 9f0aa300..00000000
--- a/meta-crownbay/conf/machine/crownbay-noemgd.conf
+++ /dev/null
@@ -1,22 +0,0 @@
1#@TYPE: Machine
2#@NAME: crownbay-noemgd
3
4#@WEBTITLE: Intel Atom E6xx Processor With Intel EG20T Controller Hub Development Kit (Crown Bay) With Open Source VESA Graphics
5
6#@DESCRIPTION: Machine configuration for Crown Bay systems, without Intel-proprietary graphics bits
7# i.e. E660 + EG20T
8
9PREFERRED_VERSION_linux-yocto ?= "3.19%"
10
11require conf/machine/include/meta-intel.inc
12require conf/machine/include/intel-core2-32-common.inc
13require conf/machine/include/intel-common-pkgarch.inc
14
15MACHINE_FEATURES += "intel-ucode"
16
17XSERVER ?= "${XSERVER_X86_BASE} \
18 ${XSERVER_X86_EXT} \
19 ${XSERVER_X86_VESA} \
20 "
21
22APPEND += "video=vesafb vga=0x318"
diff --git a/meta-crownbay/recipes-bsp/formfactor/formfactor/crownbay-noemgd/machconfig b/meta-crownbay/recipes-bsp/formfactor/formfactor/crownbay-noemgd/machconfig
deleted file mode 100644
index ffce0122..00000000
--- a/meta-crownbay/recipes-bsp/formfactor/formfactor/crownbay-noemgd/machconfig
+++ /dev/null
@@ -1,3 +0,0 @@
1# Assume a USB mouse and keyboard are connected
2HAVE_TOUCHSCREEN=0
3HAVE_KEYBOARD=1
diff --git a/meta-crownbay/recipes-bsp/formfactor/formfactor_0.0.bbappend b/meta-crownbay/recipes-bsp/formfactor/formfactor_0.0.bbappend
deleted file mode 100644
index 72d991c7..00000000
--- a/meta-crownbay/recipes-bsp/formfactor/formfactor_0.0.bbappend
+++ /dev/null
@@ -1 +0,0 @@
1FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
diff --git a/meta-crownbay/recipes-kernel/kmod/kmod_git.bbappend b/meta-crownbay/recipes-kernel/kmod/kmod_git.bbappend
deleted file mode 100644
index 56d8fcb0..00000000
--- a/meta-crownbay/recipes-kernel/kmod/kmod_git.bbappend
+++ /dev/null
@@ -1,3 +0,0 @@
1do_install_append () {
2 echo "blacklist gma500_gfx" > ${D}${sysconfdir}/modprobe.d/prohibit_gma500_gfx.conf
3}
diff --git a/meta-emenlow/COPYING.MIT b/meta-emenlow/COPYING.MIT
deleted file mode 100644
index fb950dc6..00000000
--- a/meta-emenlow/COPYING.MIT
+++ /dev/null
@@ -1,17 +0,0 @@
1Permission is hereby granted, free of charge, to any person obtaining a copy
2of this software and associated documentation files (the "Software"), to deal
3in the Software without restriction, including without limitation the rights
4to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
5copies of the Software, and to permit persons to whom the Software is
6furnished to do so, subject to the following conditions:
7
8The above copyright notice and this permission notice shall be included in
9all copies or substantial portions of the Software.
10
11THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
12IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
13FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
14AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
15LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
16OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
17THE SOFTWARE.
diff --git a/meta-emenlow/README b/meta-emenlow/README
deleted file mode 100644
index eccc9f33..00000000
--- a/meta-emenlow/README
+++ /dev/null
@@ -1,148 +0,0 @@
1This README file contains information on building the meta-emenlow
2BSP layer using any of the supported machine configurations, and
3booting the images contained in the /binary directory.
4
5The 'eMenlow' platform consists of the Intel Atom Z5xx processor,
6plus the Intel US15W System Controller Hub.
7
8Further information on the platform supported by this BSP can be
9found here:
10
11 http://www.portwell.com/products/detail.asp?CUSTCHAR1=WEBS-2120
12
13Information on all Intel® embedded platforms can be found here:
14
15 http://www.intel.com/p/en_US/embedded/hwsw/hardware
16
17If you're only interested in booting the images in the /binary
18directory of a BSP tarball you've downloaded, there's nothing special
19to do - the appropriate images are already in the /binary directory
20depending on which BSP tarball you downloaded.
21
22Please see the corresponding sections below for details.
23
24
25Yocto Project Compatible
26========================
27
28This BSP is compatible with the Yocto Project as per the requirements
29listed here:
30
31 https://www.yoctoproject.org/webform/yocto-project-compatible-registration
32
33
34Dependencies
35============
36
37This layer depends on:
38
39 URI: git://git.openembedded.org/bitbake
40 branch: master
41
42 URI: git://git.openembedded.org/openembedded-core
43 layers: meta
44 branch: master
45
46 URI: git://git.yoctoproject.org/meta-intel
47 layers: intel
48 branch: master
49
50
51Patches
52=======
53
54Please submit any patches against this BSP to the meta-intel mailing list
55(meta-intel@yoctoproject.org) and cc: the maintainer:
56
57Maintainer: Saul Wold <sgw@linux.intel.com>
58
59Please see the meta-intel/MAINTAINERS file for more details.
60
61
62Table of Contents
63=================
64
65 I. Building the meta-emenlow BSP layer
66II. Booting the images in /binary
67
68
69I. Building the meta-emenlow BSP layer
70=======================================
71
72In order to build an image with BSP support for a given release, you
73need to download the corresponding BSP tarball from the 'Board Support
74Package (BSP) Downloads' page of the Yocto Project website.
75
76Having done that, and assuming you extracted the BSP tarball contents
77at the top-level of your yocto build tree, you can build an emenlow
78image by adding the location of the meta-emenlow layer to
79bblayers.conf, along with the meta-intel layer itself (to access
80common metadata shared between BSPs) e.g.:
81
82 yocto/meta-intel \
83 yocto/meta-intel/meta-emenlow \
84
85The meta-emenlow layer contains support for emenlow-noemgd machine
86configuration. The previously supported emenlow machine with the
87proprietary EMGD graphics driver has been retired. The 'emenlow-noemgd'
88machine configuration uses the open source 'gma500' kernel DRM driver
89along with the 'modesetting' X driver.
90
91To enable the layer add the following to the local.conf file:
92
93 MACHINE ?= "emenlow-noemgd"
94
95You should then be able to build an emenlow image as such:
96
97 $ source oe-init-build-env
98 $ bitbake core-image-sato
99
100At the end of a successful build, you should have a live image that
101you can boot from a USB flash drive (see instructions on how to do
102that below, in the section 'Booting the images from /binary').
103
104As an alternative to downloading the BSP tarball, you can also work
105directly from the meta-intel git repository. For each BSP in the
106'meta-intel' repository, there are multiple branches, one
107corresponding to each major release starting with 'laverne' (0.90), in
108addition to the latest code which tracks the current master (note that
109not all BSPs are present in every release). Instead of extracting a
110BSP tarball at the top level of your yocto build tree, you can
111equivalently check out the appropriate branch from the meta-intel
112repository at the same location.
113
114
115II. Booting the images in /binary
116=================================
117
118This BSP contains bootable live images, which can be used to directly
119boot Yocto off of a USB flash drive.
120
121Under Linux, insert a USB flash drive. Assuming the USB flash drive
122takes device /dev/sdf, use dd to copy the live image to it. For
123example:
124
125# dd if=core-image-sato-emenlow-noemgd.hddimg of=/dev/sdf
126# sync
127# eject /dev/sdf
128
129This should give you a bootable USB flash device. Insert the device
130into a bootable USB socket on the target, and power on. This should
131result in a system booted to the Sato graphical desktop.
132
133If you want a terminal, use the arrows at the top of the UI to move to
134different pages of available applications, one of which is named
135'Terminal'. Clicking that should give you a root terminal.
136
137If you want to ssh into the system, you can use the root terminal to
138ifconfig the IP address and use that to ssh in. The root password is
139empty, so to log in type 'root' for the user name and hit 'Enter' at
140the Password prompt: and you should be in.
141
142----
143
144If you find you're getting corrupt images on the USB (it doesn't show
145the syslinux boot: prompt, or the boot: prompt contains strange
146characters), try doing this first:
147
148# dd if=/dev/zero of=/dev/sdf bs=1M count=512
diff --git a/meta-emenlow/README.sources b/meta-emenlow/README.sources
deleted file mode 100644
index 0d4d849a..00000000
--- a/meta-emenlow/README.sources
+++ /dev/null
@@ -1,17 +0,0 @@
1The sources for the packages comprising the images shipped with this
2BSP can be found at the following location:
3
4http://downloads.yoctoproject.org/mirror/sources/
5
6The metadata used to generate the images shipped with this BSP, in
7addition to the code contained in this BSP, can be found at the
8following location:
9
10http://downloads.yoctoproject.org/releases/yocto/yocto-1.3/poky-danny-8.0.tar.bz2
11
12The metadata used to generate the images shipped with this BSP, in
13addition to the code contained in this BSP, can also be found at the
14following locations:
15
16git://git.yoctoproject.org/poky.git
17git://git.yoctoproject.org/meta-intel
diff --git a/meta-emenlow/binary/.gitignore b/meta-emenlow/binary/.gitignore
deleted file mode 100644
index e69de29b..00000000
--- a/meta-emenlow/binary/.gitignore
+++ /dev/null
diff --git a/meta-emenlow/conf/layer.conf b/meta-emenlow/conf/layer.conf
deleted file mode 100644
index b5832e4f..00000000
--- a/meta-emenlow/conf/layer.conf
+++ /dev/null
@@ -1,12 +0,0 @@
1# We have a conf and classes directory, add to BBPATH
2BBPATH .= ":${LAYERDIR}"
3
4# We have recipes-* directories, add to BBFILES
5BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
6 ${LAYERDIR}/recipes-*/*/*.bbappend"
7
8BBFILE_COLLECTIONS += "emenlow"
9BBFILE_PATTERN_emenlow := "^${LAYERDIR}/"
10BBFILE_PRIORITY_emenlow = "6"
11
12LAYERDEPENDS_emenlow = "intel"
diff --git a/meta-emenlow/conf/machine/emenlow-noemgd.conf b/meta-emenlow/conf/machine/emenlow-noemgd.conf
deleted file mode 100644
index 0a92845c..00000000
--- a/meta-emenlow/conf/machine/emenlow-noemgd.conf
+++ /dev/null
@@ -1,20 +0,0 @@
1#@TYPE: Machine
2#@NAME: emenlow-noemgd
3
4#@WEBTITLE: Intel Atom Z5xx Processor With Intel US15W Controller Hub (eMenlow) with open source graphics
5
6#@DESCRIPTION: Machine configuration for eMenlow based systems, like the Webs-2120 box, without the Intel-proprietary graphics bits
7
8PREFERRED_VERSION_linux-yocto ?= "3.19%"
9
10require conf/machine/include/intel-core2-32-common.inc
11require conf/machine/include/intel-common-pkgarch.inc
12require conf/machine/include/meta-intel.inc
13
14MACHINE_FEATURES += "intel-ucode"
15
16XSERVER ?= "${XSERVER_X86_BASE} \
17 ${XSERVER_X86_EXT} \
18 ${XSERVER_X86_MODESETTING} \
19 "
20APPEND += "reboot=pci"
diff --git a/meta-emenlow/recipes-bsp/formfactor/formfactor/emenlow-noemgd/machconfig b/meta-emenlow/recipes-bsp/formfactor/formfactor/emenlow-noemgd/machconfig
deleted file mode 100644
index ffce0122..00000000
--- a/meta-emenlow/recipes-bsp/formfactor/formfactor/emenlow-noemgd/machconfig
+++ /dev/null
@@ -1,3 +0,0 @@
1# Assume a USB mouse and keyboard are connected
2HAVE_TOUCHSCREEN=0
3HAVE_KEYBOARD=1
diff --git a/meta-emenlow/recipes-bsp/formfactor/formfactor_0.0.bbappend b/meta-emenlow/recipes-bsp/formfactor/formfactor_0.0.bbappend
deleted file mode 100644
index 72d991c7..00000000
--- a/meta-emenlow/recipes-bsp/formfactor/formfactor_0.0.bbappend
+++ /dev/null
@@ -1 +0,0 @@
1FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
diff --git a/meta-emenlow/recipes-graphics/xorg-xserver/xserver-xf86-config/emenlow-noemgd/xorg.conf b/meta-emenlow/recipes-graphics/xorg-xserver/xserver-xf86-config/emenlow-noemgd/xorg.conf
deleted file mode 100644
index 3316e541..00000000
--- a/meta-emenlow/recipes-graphics/xorg-xserver/xserver-xf86-config/emenlow-noemgd/xorg.conf
+++ /dev/null
@@ -1,22 +0,0 @@
1Section "Device"
2 Identifier "gma500"
3 Driver "modesetting"
4 Option "SWCursor" "ON"
5EndSection
6
7Section "Monitor"
8 Identifier "Generic Monitor"
9 Option "DPMS"
10EndSection
11
12Section "Screen"
13 Identifier "Default Screen"
14 Device "gma500"
15 Monitor "Generic Monitor"
16 DefaultDepth 24
17EndSection
18
19Section "ServerLayout"
20 Identifier "Default Layout"
21 Screen "Default Screen"
22EndSection
diff --git a/meta-emenlow/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend b/meta-emenlow/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
deleted file mode 100644
index e6c4c7ec..00000000
--- a/meta-emenlow/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
+++ /dev/null
@@ -1,3 +0,0 @@
1FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
2
3PR := "${PR}.2"
diff --git a/meta-emenlow/recipes-kernel/linux/linux-yocto-dev.bbappend b/meta-emenlow/recipes-kernel/linux/linux-yocto-dev.bbappend
deleted file mode 100644
index 61aed2f4..00000000
--- a/meta-emenlow/recipes-kernel/linux/linux-yocto-dev.bbappend
+++ /dev/null
@@ -1,10 +0,0 @@
1FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
2
3COMPATIBLE_MACHINE_emenlow-noemgd = "emenlow-noemgd"
4KMACHINE_emenlow-noemgd = "emenlow"
5KBRANCH_emenlow-noemgd = "standard/emenlow"
6KERNEL_FEATURES_append_emenlow-noemgd = " features/drm-gma500/drm-gma500"
7
8# NOTE: We do not set SRCREVs here as -dev is intended to be built with AUTOREV
9# and setting them here breaks the default mechanism to use AUTOREV if the
10# default SRCREV is set and linux-yocto-dev is the preferred provider.
diff --git a/meta-emenlow/recipes-kernel/linux/linux-yocto_3.14.bbappend b/meta-emenlow/recipes-kernel/linux/linux-yocto_3.14.bbappend
deleted file mode 100644
index a2b8d67c..00000000
--- a/meta-emenlow/recipes-kernel/linux/linux-yocto_3.14.bbappend
+++ /dev/null
@@ -1,10 +0,0 @@
1FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
2
3COMPATIBLE_MACHINE_emenlow-noemgd = "emenlow-noemgd"
4KMACHINE_emenlow-noemgd = "emenlow"
5KBRANCH_emenlow-noemgd = "standard/base"
6KERNEL_FEATURES_append_emenlow-noemgd = " features/drm-gma500/drm-gma500"
7
8LINUX_VERSION_emenlow-noemgd = "3.14.36"
9SRCREV_machine_emenlow-noemgd = "4434aa71ff7043c570f9eae493df1ccadbda9b85"
10SRCREV_meta_emenlow-noemgd = "c33d39561807e1073ca412f1c771f43e4da75994"
diff --git a/meta-fri2/COPYING.MIT b/meta-fri2/COPYING.MIT
deleted file mode 100644
index fb950dc6..00000000
--- a/meta-fri2/COPYING.MIT
+++ /dev/null
@@ -1,17 +0,0 @@
1Permission is hereby granted, free of charge, to any person obtaining a copy
2of this software and associated documentation files (the "Software"), to deal
3in the Software without restriction, including without limitation the rights
4to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
5copies of the Software, and to permit persons to whom the Software is
6furnished to do so, subject to the following conditions:
7
8The above copyright notice and this permission notice shall be included in
9all copies or substantial portions of the Software.
10
11THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
12IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
13FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
14AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
15LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
16OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
17THE SOFTWARE.
diff --git a/meta-fri2/README b/meta-fri2/README
deleted file mode 100644
index 6e90c335..00000000
--- a/meta-fri2/README
+++ /dev/null
@@ -1,339 +0,0 @@
1This README file contains information on building the meta-fri2 BSP
2layer and booting the images contained in the /binary directory.
3Please see the corresponding sections below for details.
4
5The Fish River Island II BSP supports the Kontron M2M Smart Services
6Developer Kit, as described here:
7
8http://us.kontron.com/products/systems+and+platforms/m2m/m2m+smart+services+developer+kit.html
9
10The 'Queens Bay' platform consists of the Intel Atom E640T processor plus the
11Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff). The Fish River
12Island II includes a variety of communications options and other
13machine-to-machine (m2m) capabilities.
14
15Information on all Intel embedded platforms can be found here:
16
17 http://www.intel.com/p/en_US/embedded/hwsw/hardware
18
19
20Yocto Project Compatible
21========================
22
23This BSP is compatible with the Yocto Project as per the requirements
24listed here:
25
26 https://www.yoctoproject.org/webform/yocto-project-compatible-registration
27
28
29Dependencies
30============
31
32This layer depends on:
33
34 URI: git://git.openembedded.org/bitbake
35 branch: master
36
37 URI: git://git.openembedded.org/openembedded-core
38 layers: meta
39 branch: master
40
41 URI: git://git.yoctoproject.org/meta-intel
42 layers: intel
43 branch: master
44
45
46Patches
47=======
48
49Please submit any patches against this BSP to the meta-intel mailing list
50(meta-intel@yoctoproject.org) and cc: the maintainer:
51
52Maintainer: Darren Hart <dvhart@linux.intel.com>
53
54Please see the meta-intel/MAINTAINERS file for more details.
55
56
57Table of Contents
58=================
59
60 I. Building the meta-fri2 BSP layer
61 II. Booting the images in /binary
62III. Device Notes
63 a. BIOS and Firmware
64 b. Serial Port
65 c. HDMI
66 d. Power Reset
67 e. Accelerometer
68 f. GPIO
69 g. MMC
70 h. 802.11
71 i. 802.15.4
72 j. Audio
73 k. Optional Devices
74 IV. Known Issues
75 a. EFI boot fails
76 b. Client USB is disabled
77 c. Audio over secondary HDMI port only
78 V. Additional Resources
79
80
81I. Building the meta-fri2 BSP layer
82===================================
83
84In order to build an image with BSP support for a given release, you
85need to download the corresponding BSP tarball from the 'Board Support
86Package (BSP) Downloads' page of the Yocto Project website.
87
88Having done that, and assuming you extracted the BSP tarball contents
89at the top-level of your yocto build tree, you can build an fri2 image
90by adding the location of the meta-intel and meta-fri2 layers to
91bblayers.conf, e.g.:
92
93 yocto/meta-intel \
94 yocto/meta-intel/meta-fri2 \
95
96The meta-fri2 layer contains support for fri2-noemgd machine configuration.
97The previously supported fri2 machine with the proprietary EMGD graphics
98driver has been retired. The 'fri2-noemgd' machine configuration uses
99the open source 'vesa' kernel driver.
100
101To enable the layer add the following to the local.conf file:
102
103 MACHINE ?= "fri2-noemgd"
104
105You should then be able to build an fri2 image as such:
106
107 $ source oe-init-build-env
108 $ bitbake core-image-sato
109
110At the end of a successful build, you should have a live image that
111you can boot from a USB flash drive (see instructions on how to do
112that below, in the section 'Booting the images from /binary').
113
114As an alternative to downloading the BSP tarball, you can also work
115directly from the meta-intel git repository. For each BSP in the
116'meta-intel' repository, there are multiple branches, one
117corresponding to each major release starting with 'laverne' (0.90), in
118addition to the latest code which tracks the current master (note that
119not all BSPs are present in every release). Instead of extracting a
120BSP tarball at the top level of your yocto build tree, you can
121equivalently check out the appropriate branch from the meta-intel
122repository at the same location.
123
124
125II. Booting the images in /binary
126=================================
127
128This BSP contains bootable live images, which can be used to directly
129boot Yocto off of a USB flash drive.
130
131Under Linux, insert a USB flash drive. Assuming the USB flash drive
132takes device /dev/sdf, use dd to copy the live image to it. For
133example:
134
135# dd if=core-image-sato-fri2-noemgd.hddimg of=/dev/sdf
136# sync
137# eject /dev/sdf
138
139This should give you a bootable USB flash device. Insert the device
140into one of the USB host ports on the target, and power on. This
141should result in a system booted to the Sato graphical desktop.
142
143If you want a terminal, use the arrows at the top of the UI to move to
144different pages of available applications, one of which is named
145'Terminal'. Clicking that should give you a root terminal.
146
147If you want to ssh into the system, you can use the root terminal to
148ifconfig the IP address and use that to ssh in. The root password is
149empty, so to log in type 'root' for the user name and hit 'Enter' at
150the Password prompt: and you should be in.
151
152If instead of a live image, you would like to prepare an EFI bootable
153partitioned image, use the mkefidisk.sh script provided in the scripts
154directory of this BSP. Future versions of the images have an EFI
155installer integrated into the live image.
156
157----
158
159If you find you're getting corrupt images on the USB (it doesn't show
160the syslinux boot: prompt, or the boot: prompt contains strange
161characters), try doing this first:
162
163# dd if=/dev/zero of=/dev/sdf bs=1M count=512
164
165
166III. Device Notes
167================================
168a. BIOS and Firmware
169
170Units provided from the Yocto Project Fish River Island 2 Giveaway
171Program are preconfigured with the Intel provided Fast Boot EFI
172firmware. This firmware will search the available devices (USB, SD,
173and mSATA) for a valid EFI payload at "EFI\BOOT\BOOTIA32.EFI". If it
174fails to find one, it will launch the EFI shell and optionally execute
175a "startup.nsh" script if it finds the script on the available storage
176devices. It searches the devices in the following order: USB, SD,
177mSATA.
178
179Units acquired via other channels may have the Kontron supplied APTIO
180(AMI) BIOS. This is a PCBIOS and EFI firmware with a traditional BIOS
181configuration menu which can be used to define a variety of boot
182configurations.
183
184b. Serial Port
185--------------
186The FRI2 has an optional serial daughter card providing a serial
187console via the micro-USB port on the top of the device adjacent the
188SIM card slot.
189
190The UART from the EG20T is connected to a TI UART-to-USB device
191(TUSB3410) which appears as a serial port on the host computer. From a
192Linux host, load the driver with the following options:
193
194# modprobe ti_usb_3410_5052 vendor_3410=0x0451 product_3410=0x5053
195
196In future versions of the Linux kernel (3.4 and later), the
197vendor and product codes are detected automatically.
198
199When you power on your FRI2, your host will discover a serial device
200and name it /dev/ttyUSB0 (or similar). You can communicate with this
201device at 115200 8N1 using your preferred terminal emulator.
202
203If using the Intel provided Fast Boot EFI firmware, no additional
204configuration is required. If using the APTIO (AMI) BIOS, use the
205following settings to configure console redirection in the BIOS menu:
206
207 Advanced
208 Serial Port Console Redirection
209 COM2
210 Console Redirection [Enabled]
211 Console Redirection Settings
212 Terminal Type [ANSI]
213 Bits per second [115200]
214 Data Bits [8]
215 Parity [None]
216 Stop Bits [1]
217 Flow Control [None]
218 Recorder Mode [Disabled]
219 Resolution 100x31 [Disabled]
220 Legacy OS Redirection [80x24]
221
222c. HDMI
223-------
224The FRI2 has two micro HDMI ports. For the Intel provided Fast Boot
225EFI firmware, the one closest to the bottom of the device is the
226primary display. For the APTIO (AMI) BIOS, the jack nearest the 1/8"
227audio jacks is the primary display.
228
229d. Power Reset
230--------------
231The recessed button adjacent the LEDs on the top of the device is a
232power reset button.
233
234e. Accelerometer
235----------------
236The LIS331DLH accelerometer is connected to the I2C bus on the CPLD on
237the compute module. The driver for this chip is under active
238development and will be included in the BSP once completed.
239
240f. GPIO
241-------
242The FRI2 has two I2C PCA555x GPIO devices used for internal control
243signals. These have not been exposed in the current release of the
244BSP, but may be in the future. Regardless, these would not provide
245general purpose IO with which to read or drive additional signals.
246
247g. MMC
248------
249The FRI2 provides two microSD card MMC devices. One is located
250adjacent the 1/8" audio jacks, another is located on the board inside
251the chassis. These devices can be used to boot the device, or as
252secondary storage.
253
254h. 802.11
255---------
256The Intel Corporation Centrino Advanced-N 6205 that ships with the
257FRI2 is supported. You can use connman-gnome to configures the
258interface.
259
260i. 802.15.4
261-----------
262The TI CC2531 802.15.4 radio is a USB ACM modem. The MAC is enabled by
263issuing the following command:
264
265# echo J > /dev/ttyACM0
266
267The bank of 3 LEDs nearest the power reset button will change if this
268command is executed successfully. If you have a 3G modem installed,
269the 802.15.4 device may appear as /dev/ttyACM3 instead.
270
271No further testing or integration has been done.
272
273j. Audio
274--------------------
275The FRI2 has an 1/8" analog output (nearest the antennae), a line-in
276input below that, as well as SPDIF over HDMI. These can be tested
277using the alsa-utils package. The aplay -l command will list both
278playback devices:
279
280# aplay -l
281**** List of PLAYBACK Hardware Devices ****
282card 0: MID [HDA Intel MID], device 0: ALC262 Analog [ALC262 Analog]
283 Subdevices: 1/1
284 Subdevice #0: subdevice #0
285card 0: MID [HDA Intel MID], device 3: ALC262 Digital [ALC262 Digital]
286 Subdevices: 1/1
287 Subdevice #0: subdevice #0
288
289Using a sample WAV file, you can use aplay to play to either device:
290
291Over analog:
292# aplay -D plughw:0,0 sample.wav
293
294Over HDMI:
295# aplay -D plughw:0,3 sample.wav
296
297
298k. Optional Devices
299-------------------
300The FRI2 has two mini-PCIe slots internally. The device ships with a
301half-length wireless card installed. This can be replaced with a
302wireless + bluetooth card. The other slot is available for use with
303cellular cards or mSATA SSDs.
304
305The Ericsson F5521gw 3G modem has been verifed with the FRI2 images.
306Note that the connman-gnome UI does not allow for configuring the
307cellular interface. The ofono-tests package can be used to configure
308the modem and bring up an interface.
309
310
311IV. Known Issues
312----------------
313a. EFI
314------
315The APTIO (AMI) BIOS does not yet boot the EFI payload provided on the
316FRI2 live image. This is a known issue under investigation. If using
317this firmware, boot using PCBIOS mode, rather than EFI. The Intel
318provided Fast Boot EFI firmware will boot the EFI payload.
319
320b. Client USB is disabled
321-------------------------
322The micro-USB port adjacent the primary HDMI port is intended for Client
323USB functionality, but is not supported on current revisions of the
324device.
325
326c. Audio over secondary HDMI port only
327--------------------------------------
328While audio over HDMI has been shown to work, it seems to only work over
329the secondary (bottom-most) HDMI port. There does not appear to be a
330deterministic way of getting the device to output the signal (video and
331audio) over the secondary port.
332
333
334V. Additional Resources
335-----------------------
336In addition to this README, please see the following wiki page for tips
337on using the FRI2 with the Yocto Project:
338
339https://wiki.yoctoproject.org/wiki/BSPs/FRI2
diff --git a/meta-fri2/README.sources b/meta-fri2/README.sources
deleted file mode 100644
index 0d4d849a..00000000
--- a/meta-fri2/README.sources
+++ /dev/null
@@ -1,17 +0,0 @@
1The sources for the packages comprising the images shipped with this
2BSP can be found at the following location:
3
4http://downloads.yoctoproject.org/mirror/sources/
5
6The metadata used to generate the images shipped with this BSP, in
7addition to the code contained in this BSP, can be found at the
8following location:
9
10http://downloads.yoctoproject.org/releases/yocto/yocto-1.3/poky-danny-8.0.tar.bz2
11
12The metadata used to generate the images shipped with this BSP, in
13addition to the code contained in this BSP, can also be found at the
14following locations:
15
16git://git.yoctoproject.org/poky.git
17git://git.yoctoproject.org/meta-intel
diff --git a/meta-fri2/binary/.gitignore b/meta-fri2/binary/.gitignore
deleted file mode 100644
index e69de29b..00000000
--- a/meta-fri2/binary/.gitignore
+++ /dev/null
diff --git a/meta-fri2/conf/layer.conf b/meta-fri2/conf/layer.conf
deleted file mode 100644
index 0bb29a13..00000000
--- a/meta-fri2/conf/layer.conf
+++ /dev/null
@@ -1,12 +0,0 @@
1# We have a conf and classes directory, add to BBPATH
2BBPATH .= ":${LAYERDIR}"
3
4# We have a recipes directory, add to BBFILES
5BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
6 ${LAYERDIR}/recipes-*/*/*.bbappend"
7
8BBFILE_COLLECTIONS += "fri2"
9BBFILE_PATTERN_fri2 := "^${LAYERDIR}/"
10BBFILE_PRIORITY_fri2 = "6"
11
12LAYERDEPENDS_fri2 = "intel"
diff --git a/meta-fri2/conf/machine/fri2-noemgd.conf b/meta-fri2/conf/machine/fri2-noemgd.conf
deleted file mode 100644
index bdf4b0dd..00000000
--- a/meta-fri2/conf/machine/fri2-noemgd.conf
+++ /dev/null
@@ -1,36 +0,0 @@
1#@TYPE: Machine
2#@NAME: fri2
3
4#@WEBTITLE: Intel Atom E640T Processor with Intel EG20T Controller Hub Development Kit (Queens Bay) with Open Source VESA Graphics for Fish River Island II systems
5
6#@DESCRIPTION: Machine configuration for Fish River Island II systems, without Intel-proprietary graphics bits
7
8require conf/machine/include/intel-core2-32-common.inc
9require conf/machine/include/intel-common-pkgarch.inc
10require conf/machine/include/meta-intel.inc
11
12MACHINE_FEATURES += "wifi 3g pcbios efi"
13MACHINE_FEATURES += "intel-ucode"
14
15MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-iwlwifi-6000g2a-5"
16
17PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
18PREFERRED_VERSION_linux-yocto ?= "3.19%"
19
20XSERVER ?= "${XSERVER_X86_BASE} \
21 ${XSERVER_X86_EXT} \
22 ${XSERVER_X86_FBDEV} \
23 "
24
25# Syslinux does not know about the 64MHz uart clock and it does not detect the
26# serial device by number. Use the IO port directly and divide the baud down to
27# trick syslinux into configuring a 115200 baud.
28SYSLINUX_OPTS = "serial 0xb060 3318"
29SERIAL_CONSOLE = "115200 ttyPCH1"
30APPEND += "console=ttyPCH1,115200 console=tty0"
31
32# EFI boot will ignore this and use the EFI framebuffer at 800x600
33APPEND += "video=vesafb vga=0x318"
34
35# MSI interrupts fail for the HDA device when using the EFI firmware
36APPEND += "snd_hda_intel.enable_msi=0"
diff --git a/meta-fri2/recipes-bsp/alsa-state/alsa-state.bbappend b/meta-fri2/recipes-bsp/alsa-state/alsa-state.bbappend
deleted file mode 100644
index 72d991c7..00000000
--- a/meta-fri2/recipes-bsp/alsa-state/alsa-state.bbappend
+++ /dev/null
@@ -1 +0,0 @@
1FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
diff --git a/meta-fri2/recipes-bsp/alsa-state/alsa-state/fri2-noemgd/asound.state b/meta-fri2/recipes-bsp/alsa-state/alsa-state/fri2-noemgd/asound.state
deleted file mode 100644
index 8a89f0bc..00000000
--- a/meta-fri2/recipes-bsp/alsa-state/alsa-state/fri2-noemgd/asound.state
+++ /dev/null
@@ -1,411 +0,0 @@
1state.MID {
2 control.1 {
3 iface MIXER
4 name 'PCM Playback Volume'
5 value.0 24
6 value.1 24
7 comment {
8 access 'read write'
9 type INTEGER
10 count 2
11 range '0 - 30'
12 dbmin -4500
13 dbmax 0
14 dbvalue.0 -900
15 dbvalue.1 -900
16 }
17 }
18 control.2 {
19 iface MIXER
20 name 'PCM Playback Switch'
21 value.0 true
22 value.1 true
23 comment {
24 access 'read write'
25 type BOOLEAN
26 count 2
27 }
28 }
29 control.3 {
30 iface MIXER
31 name 'Headphone Playback Volume'
32 value.0 0
33 value.1 0
34 comment {
35 access 'read write'
36 type INTEGER
37 count 2
38 range '0 - 30'
39 dbmin -4500
40 dbmax 0
41 dbvalue.0 -4500
42 dbvalue.1 -4500
43 }
44 }
45 control.4 {
46 iface MIXER
47 name 'Headphone Playback Switch'
48 value.0 false
49 value.1 false
50 comment {
51 access 'read write'
52 type BOOLEAN
53 count 2
54 }
55 }
56 control.5 {
57 iface MIXER
58 name 'Rear Mic Playback Volume'
59 value.0 0
60 value.1 0
61 comment {
62 access 'read write'
63 type INTEGER
64 count 2
65 range '0 - 31'
66 dbmin -3450
67 dbmax 1200
68 dbvalue.0 -3450
69 dbvalue.1 -3450
70 }
71 }
72 control.6 {
73 iface MIXER
74 name 'Rear Mic Playback Switch'
75 value.0 false
76 value.1 false
77 comment {
78 access 'read write'
79 type BOOLEAN
80 count 2
81 }
82 }
83 control.7 {
84 iface MIXER
85 name 'Front Mic Playback Volume'
86 value.0 0
87 value.1 0
88 comment {
89 access 'read write'
90 type INTEGER
91 count 2
92 range '0 - 31'
93 dbmin -3450
94 dbmax 1200
95 dbvalue.0 -3450
96 dbvalue.1 -3450
97 }
98 }
99 control.8 {
100 iface MIXER
101 name 'Front Mic Playback Switch'
102 value.0 false
103 value.1 false
104 comment {
105 access 'read write'
106 type BOOLEAN
107 count 2
108 }
109 }
110 control.9 {
111 iface MIXER
112 name 'Line Playback Volume'
113 value.0 0
114 value.1 0
115 comment {
116 access 'read write'
117 type INTEGER
118 count 2
119 range '0 - 31'
120 dbmin -3450
121 dbmax 1200
122 dbvalue.0 -3450
123 dbvalue.1 -3450
124 }
125 }
126 control.10 {
127 iface MIXER
128 name 'Line Playback Switch'
129 value.0 false
130 value.1 false
131 comment {
132 access 'read write'
133 type BOOLEAN
134 count 2
135 }
136 }
137 control.11 {
138 iface MIXER
139 name 'CD Playback Volume'
140 value.0 0
141 value.1 0
142 comment {
143 access 'read write'
144 type INTEGER
145 count 2
146 range '0 - 31'
147 dbmin -3450
148 dbmax 1200
149 dbvalue.0 -3450
150 dbvalue.1 -3450
151 }
152 }
153 control.12 {
154 iface MIXER
155 name 'CD Playback Switch'
156 value.0 false
157 value.1 false
158 comment {
159 access 'read write'
160 type BOOLEAN
161 count 2
162 }
163 }
164 control.13 {
165 iface MIXER
166 name 'Auto-Mute Mode'
167 value Disabled
168 comment {
169 access 'read write'
170 type ENUMERATED
171 count 1
172 item.0 Disabled
173 item.1 Enabled
174 }
175 }
176 control.14 {
177 iface MIXER
178 name 'Rear Mic Boost Volume'
179 value.0 0
180 value.1 0
181 comment {
182 access 'read write'
183 type INTEGER
184 count 2
185 range '0 - 3'
186 dbmin 0
187 dbmax 3000
188 dbvalue.0 0
189 dbvalue.1 0
190 }
191 }
192 control.15 {
193 iface MIXER
194 name 'Front Mic Boost Volume'
195 value.0 0
196 value.1 0
197 comment {
198 access 'read write'
199 type INTEGER
200 count 2
201 range '0 - 3'
202 dbmin 0
203 dbmax 3000
204 dbvalue.0 0
205 dbvalue.1 0
206 }
207 }
208 control.16 {
209 iface MIXER
210 name 'Capture Switch'
211 value.0 true
212 value.1 true
213 comment {
214 access 'read write'
215 type BOOLEAN
216 count 2
217 }
218 }
219 control.17 {
220 iface MIXER
221 name 'Capture Switch'
222 index 1
223 value.0 false
224 value.1 false
225 comment {
226 access 'read write'
227 type BOOLEAN
228 count 2
229 }
230 }
231 control.18 {
232 iface MIXER
233 name 'Capture Switch'
234 index 2
235 value.0 false
236 value.1 false
237 comment {
238 access 'read write'
239 type BOOLEAN
240 count 2
241 }
242 }
243 control.19 {
244 iface MIXER
245 name 'Capture Volume'
246 value.0 25
247 value.1 25
248 comment {
249 access 'read write'
250 type INTEGER
251 count 2
252 range '0 - 31'
253 dbmin -1200
254 dbmax 3450
255 dbvalue.0 2550
256 dbvalue.1 2550
257 }
258 }
259 control.20 {
260 iface MIXER
261 name 'Capture Volume'
262 index 1
263 value.0 0
264 value.1 0
265 comment {
266 access 'read write'
267 type INTEGER
268 count 2
269 range '0 - 31'
270 dbmin -1200
271 dbmax 3450
272 dbvalue.0 -1200
273 dbvalue.1 -1200
274 }
275 }
276 control.21 {
277 iface MIXER
278 name 'Capture Volume'
279 index 2
280 value.0 0
281 value.1 0
282 comment {
283 access 'read write'
284 type INTEGER
285 count 2
286 range '0 - 31'
287 dbmin -1200
288 dbmax 3450
289 dbvalue.0 -1200
290 dbvalue.1 -1200
291 }
292 }
293 control.22 {
294 iface MIXER
295 name 'Input Source'
296 value Line
297 comment {
298 access 'read write'
299 type ENUMERATED
300 count 1
301 item.0 'Rear Mic'
302 item.1 'Front Mic'
303 item.2 Line
304 item.3 CD
305 }
306 }
307 control.23 {
308 iface MIXER
309 name 'Input Source'
310 index 1
311 value 'Rear Mic'
312 comment {
313 access 'read write'
314 type ENUMERATED
315 count 1
316 item.0 'Rear Mic'
317 item.1 'Front Mic'
318 item.2 Line
319 item.3 CD
320 }
321 }
322 control.24 {
323 iface MIXER
324 name 'Input Source'
325 index 2
326 value 'Rear Mic'
327 comment {
328 access 'read write'
329 type ENUMERATED
330 count 1
331 item.0 'Rear Mic'
332 item.1 'Front Mic'
333 item.2 Line
334 item.3 CD
335 }
336 }
337 control.25 {
338 iface MIXER
339 name 'IEC958 Playback Con Mask'
340 value '0fff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
341 comment {
342 access read
343 type IEC958
344 count 1
345 }
346 }
347 control.26 {
348 iface MIXER
349 name 'IEC958 Playback Pro Mask'
350 value '0f00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
351 comment {
352 access read
353 type IEC958
354 count 1
355 }
356 }
357 control.27 {
358 iface MIXER
359 name 'IEC958 Playback Default'
360 value '0400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
361 comment {
362 access 'read write'
363 type IEC958
364 count 1
365 }
366 }
367 control.28 {
368 iface MIXER
369 name 'IEC958 Playback Switch'
370 value true
371 comment {
372 access 'read write'
373 type BOOLEAN
374 count 1
375 }
376 }
377 control.29 {
378 iface MIXER
379 name 'IEC958 Default PCM Playback Switch'
380 value true
381 comment {
382 access 'read write'
383 type BOOLEAN
384 count 1
385 }
386 }
387 control.30 {
388 iface MIXER
389 name 'Master Playback Volume'
390 value 24
391 comment {
392 access 'read write'
393 type INTEGER
394 count 1
395 range '0 - 30'
396 dbmin -4500
397 dbmax 0
398 dbvalue.0 -900
399 }
400 }
401 control.31 {
402 iface MIXER
403 name 'Master Playback Switch'
404 value true
405 comment {
406 access 'read write'
407 type BOOLEAN
408 count 1
409 }
410 }
411}
diff --git a/meta-fri2/recipes-bsp/formfactor/formfactor/fri2-noemgd/machconfig b/meta-fri2/recipes-bsp/formfactor/formfactor/fri2-noemgd/machconfig
deleted file mode 100644
index ffce0122..00000000
--- a/meta-fri2/recipes-bsp/formfactor/formfactor/fri2-noemgd/machconfig
+++ /dev/null
@@ -1,3 +0,0 @@
1# Assume a USB mouse and keyboard are connected
2HAVE_TOUCHSCREEN=0
3HAVE_KEYBOARD=1
diff --git a/meta-fri2/recipes-bsp/formfactor/formfactor_0.0.bbappend b/meta-fri2/recipes-bsp/formfactor/formfactor_0.0.bbappend
deleted file mode 100644
index 72d991c7..00000000
--- a/meta-fri2/recipes-bsp/formfactor/formfactor_0.0.bbappend
+++ /dev/null
@@ -1 +0,0 @@
1FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
diff --git a/meta-fri2/recipes-bsp/grub/grub-efi_2.00.bbappend b/meta-fri2/recipes-bsp/grub/grub-efi_2.00.bbappend
deleted file mode 100644
index f6105711..00000000
--- a/meta-fri2/recipes-bsp/grub/grub-efi_2.00.bbappend
+++ /dev/null
@@ -1,13 +0,0 @@
1# The Intel provided Fast Boot Firmware may not initialize the USB keyboard
2# before launching the grub.efi payload. Ensure GRUB has keyboard control by
3# building in the usb, usb_keyboard, and ohci modules.
4
5do_deploy() {
6 # Search for the grub.cfg on the local boot media by using the
7 # built in cfg file provided via this recipe
8 grub-mkimage -c ../cfg -p /EFI/BOOT -d ./grub-core/ \
9 -O ${GRUB_TARGET}-efi -o ./${GRUB_IMAGE} \
10 boot linux ext2 fat serial part_msdos part_gpt normal efi_gop iso9660 search \
11 usb usb_keyboard ohci
12 install -m 644 ${B}/${GRUB_IMAGE} ${DEPLOYDIR}
13}
diff --git a/meta-fri2/recipes-core/init-ifupdown/files/fri2-noemgd/interfaces b/meta-fri2/recipes-core/init-ifupdown/files/fri2-noemgd/interfaces
deleted file mode 100644
index f5bb9468..00000000
--- a/meta-fri2/recipes-core/init-ifupdown/files/fri2-noemgd/interfaces
+++ /dev/null
@@ -1,9 +0,0 @@
1# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
2
3# The loopback interface
4auto lo
5iface lo inet loopback
6
7# Wired or wireless interfaces
8auto eth0
9iface eth0 inet dhcp
diff --git a/meta-fri2/recipes-core/init-ifupdown/init-ifupdown_1.0.bbappend b/meta-fri2/recipes-core/init-ifupdown/init-ifupdown_1.0.bbappend
deleted file mode 100644
index 81fe7b79..00000000
--- a/meta-fri2/recipes-core/init-ifupdown/init-ifupdown_1.0.bbappend
+++ /dev/null
@@ -1 +0,0 @@
1FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
diff --git a/meta-fri2/recipes-kernel/kmod/kmod_git.bbappend b/meta-fri2/recipes-kernel/kmod/kmod_git.bbappend
deleted file mode 100644
index 56d8fcb0..00000000
--- a/meta-fri2/recipes-kernel/kmod/kmod_git.bbappend
+++ /dev/null
@@ -1,3 +0,0 @@
1do_install_append () {
2 echo "blacklist gma500_gfx" > ${D}${sysconfdir}/modprobe.d/prohibit_gma500_gfx.conf
3}
diff --git a/meta-jasperforest/COPYING.MIT b/meta-jasperforest/COPYING.MIT
deleted file mode 100644
index fb950dc6..00000000
--- a/meta-jasperforest/COPYING.MIT
+++ /dev/null
@@ -1,17 +0,0 @@
1Permission is hereby granted, free of charge, to any person obtaining a copy
2of this software and associated documentation files (the "Software"), to deal
3in the Software without restriction, including without limitation the rights
4to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
5copies of the Software, and to permit persons to whom the Software is
6furnished to do so, subject to the following conditions:
7
8The above copyright notice and this permission notice shall be included in
9all copies or substantial portions of the Software.
10
11THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
12IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
13FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
14AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
15LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
16OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
17THE SOFTWARE.
diff --git a/meta-jasperforest/README b/meta-jasperforest/README
deleted file mode 100644
index d82b2af0..00000000
--- a/meta-jasperforest/README
+++ /dev/null
@@ -1,137 +0,0 @@
1This README file contains information on building the
2meta-jasperforest BSP layer, and booting the images contained in the
3/binary directory. Please see the corresponding sections below for
4details.
5
6'Jasper Forest' refers to the Intel Xeon C5500/C3500 processors, which
7combined with the Intel 3420 PCH chipset (Ibex Peak) make up the
8'Picket Post' CRB this BSP was developed on.
9
10Further information on the platforms supported by this BSP can be
11found here:
12
13 http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-c5500-c3500-3420/overview
14
15Information on all Intel® embedded platforms can be found here:
16
17 http://www.intel.com/p/en_US/embedded/hwsw/hardware
18
19
20Yocto Project Compatible
21========================
22
23This BSP is compatible with the Yocto Project as per the requirements
24listed here:
25
26 https://www.yoctoproject.org/webform/yocto-project-compatible-registration
27
28
29Dependencies
30============
31
32This layer depends on:
33
34 URI: git://git.openembedded.org/bitbake
35 branch: master
36
37 URI: git://git.openembedded.org/openembedded-core
38 layers: meta
39 branch: master
40
41 URI: git://git.yoctoproject.org/meta-intel
42 layers: intel
43 branch: master
44
45
46Patches
47=======
48
49Please submit any patches against this BSP to the meta-intel mailing list
50(meta-intel@yoctoproject.org) and cc: the maintainer:
51
52Maintainer: Saul Wold <sgw@linux.intel.com>
53
54Please see the meta-intel/MAINTAINERS file for more details.
55
56
57Table of Contents
58=================
59
60 I. Building the meta-jasperforest BSP layer
61 II. Booting the images in /binary
62
63
64I. Building the meta-jasperforest BSP layer
65=======================================
66
67In order to build an image with BSP support for a given release, you
68need to download the corresponding BSP tarball from the 'Board Support
69Package (BSP) Downloads' page of the Yocto Project website.
70
71Having done that, and assuming you extracted the BSP tarball contents
72at the top-level of your yocto build tree, you can build a
73jasperforest image by adding the location of the meta-jasperforest
74layer to bblayers.conf, along with the meta-intel layer itself (to
75access common metadata shared between BSPs) e.g.:
76
77 yocto/meta-intel \
78 yocto/meta-intel/meta-jasperforest \
79
80To enable the jasperforest layer, add the jasperforest MACHINE to local.conf:
81
82 MACHINE ?= "jasperforest"
83
84You should then be able to build a jasperforest image as such:
85
86 $ source oe-init-build-env
87 $ bitbake core-image-sato
88
89At the end of a successful build, you should have a live image that
90you can boot from a USB flash drive (see instructions on how to do
91that below, in the section 'Booting the images from /binary').
92
93As an alternative to downloading the BSP tarball, you can also work
94directly from the meta-intel git repository. For each BSP in the
95'meta-intel' repository, there are multiple branches, one
96corresponding to each major release starting with 'laverne' (0.90), in
97addition to the latest code which tracks the current master (note that
98not all BSPs are present in every release). Instead of extracting a
99BSP tarball at the top level of your yocto build tree, you can
100equivalently check out the appropriate branch from the meta-intel
101repository at the same location.
102
103
104II. Booting the images in /binary
105=================================
106
107This BSP contains bootable live images, which can be used to directly
108boot Yocto off of a USB flash drive.
109
110Under Linux, insert a USB flash drive. Assuming the USB flash drive
111takes device /dev/sdf, use dd to copy the live image to it. For
112example:
113
114# dd if=core-image-sato-jasperforest.hddimg of=/dev/sdf
115# sync
116# eject /dev/sdf
117
118This should give you a bootable USB flash device. Insert the device
119into a bootable USB socket on the target, and power on. This should
120result in a system booted to the Sato graphical desktop.
121
122If you want a terminal, use the arrows at the top of the UI to move to
123different pages of available applications, one of which is named
124'Terminal'. Clicking that should give you a root terminal.
125
126If you want to ssh into the system, you can use the root terminal to
127ifconfig the IP address and use that to ssh in. The root password is
128empty, so to log in type 'root' for the user name and hit 'Enter' at
129the Password prompt: and you should be in.
130
131----
132
133If you find you're getting corrupt images on the USB (it doesn't show
134the syslinux boot: prompt, or the boot: prompt contains strange
135characters), try doing this first:
136
137# dd if=/dev/zero of=/dev/sdf bs=1M count=512
diff --git a/meta-jasperforest/README.sources b/meta-jasperforest/README.sources
deleted file mode 100644
index 0d4d849a..00000000
--- a/meta-jasperforest/README.sources
+++ /dev/null
@@ -1,17 +0,0 @@
1The sources for the packages comprising the images shipped with this
2BSP can be found at the following location:
3
4http://downloads.yoctoproject.org/mirror/sources/
5
6The metadata used to generate the images shipped with this BSP, in
7addition to the code contained in this BSP, can be found at the
8following location:
9
10http://downloads.yoctoproject.org/releases/yocto/yocto-1.3/poky-danny-8.0.tar.bz2
11
12The metadata used to generate the images shipped with this BSP, in
13addition to the code contained in this BSP, can also be found at the
14following locations:
15
16git://git.yoctoproject.org/poky.git
17git://git.yoctoproject.org/meta-intel
diff --git a/meta-jasperforest/binary/.gitignore b/meta-jasperforest/binary/.gitignore
deleted file mode 100644
index e69de29b..00000000
--- a/meta-jasperforest/binary/.gitignore
+++ /dev/null
diff --git a/meta-jasperforest/conf/layer.conf b/meta-jasperforest/conf/layer.conf
deleted file mode 100644
index 6d096e7e..00000000
--- a/meta-jasperforest/conf/layer.conf
+++ /dev/null
@@ -1,12 +0,0 @@
1# We have a conf and classes directory, add to BBPATH
2BBPATH .= ":${LAYERDIR}"
3
4# We have a recipes directory, add to BBFILES
5BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
6 ${LAYERDIR}/recipes-*/*/*.bbappend"
7
8BBFILE_COLLECTIONS += "jasperforest"
9BBFILE_PATTERN_jasperforest := "^${LAYERDIR}/"
10BBFILE_PRIORITY_jasperforest = "6"
11
12LAYERDEPENDS_jasperforest = "intel"
diff --git a/meta-jasperforest/conf/machine/jasperforest.conf b/meta-jasperforest/conf/machine/jasperforest.conf
deleted file mode 100644
index e0948eb0..00000000
--- a/meta-jasperforest/conf/machine/jasperforest.conf
+++ /dev/null
@@ -1,22 +0,0 @@
1#@TYPE: Machine
2#@NAME: jasperforest
3
4#@WEBTITLE: Intel Xeon C5500/C3500 Series Processors With Intel 3420 PCH Chipset (Jasper Forest)
5
6#@DESCRIPTION: Machine configuration for Jasper Forest Picket Post
7# systems i.e. Xeon C5500/C3500 (Nehalem) + Intel 3420 chipset (Ibex Peak)
8
9PREFERRED_VERSION_linux-yocto ?= "3.19%"
10
11require conf/machine/include/meta-intel.inc
12require conf/machine/include/intel-corei7-64-common.inc
13require conf/machine/include/intel-common-pkgarch.inc
14
15MACHINE_FEATURES += "intel-ucode"
16
17XSERVER ?= "${XSERVER_X86_BASE} \
18 ${XSERVER_X86_EXT} \
19 ${XSERVER_X86_VESA} \
20 "
21
22APPEND += "video=vesafb vga=0x318"
diff --git a/meta-jasperforest/recipes-bsp/formfactor/formfactor/jasperforest/machconfig b/meta-jasperforest/recipes-bsp/formfactor/formfactor/jasperforest/machconfig
deleted file mode 100644
index ffce0122..00000000
--- a/meta-jasperforest/recipes-bsp/formfactor/formfactor/jasperforest/machconfig
+++ /dev/null
@@ -1,3 +0,0 @@
1# Assume a USB mouse and keyboard are connected
2HAVE_TOUCHSCREEN=0
3HAVE_KEYBOARD=1
diff --git a/meta-jasperforest/recipes-bsp/formfactor/formfactor_0.0.bbappend b/meta-jasperforest/recipes-bsp/formfactor/formfactor_0.0.bbappend
deleted file mode 100644
index 72d991c7..00000000
--- a/meta-jasperforest/recipes-bsp/formfactor/formfactor_0.0.bbappend
+++ /dev/null
@@ -1 +0,0 @@
1FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
diff --git a/meta-nuc/COPYING.MIT b/meta-nuc/COPYING.MIT
deleted file mode 100644
index 89de3547..00000000
--- a/meta-nuc/COPYING.MIT
+++ /dev/null
@@ -1,17 +0,0 @@
1Permission is hereby granted, free of charge, to any person obtaining a copy
2of this software and associated documentation files (the "Software"), to deal
3in the Software without restriction, including without limitation the rights
4to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
5copies of the Software, and to permit persons to whom the Software is
6furnished to do so, subject to the following conditions:
7
8The above copyright notice and this permission notice shall be included in
9all copies or substantial portions of the Software.
10
11THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
12IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
13FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
14AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
15LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
16OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
17THE SOFTWARE.
diff --git a/meta-nuc/README b/meta-nuc/README
deleted file mode 100644
index 7753755e..00000000
--- a/meta-nuc/README
+++ /dev/null
@@ -1,156 +0,0 @@
1This README file contains information on building the meta-nuc
2BSP layer, and booting the images contained in the /binary directory.
3Please see the corresponding sections below for details.
4
5This BSP is made specifically for "Next Unit of Computing Kit DC3217IYE"
6with Intel Centrino Advanced-N 6235 Wireless mini PCI Express card.
7
8Further information on this NUC platform can be found here:
9
10 http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-boards-d33217gke-dc3217iye.html
11
12Information on all Intel® embedded platforms can be found here:
13
14 http://www.intel.com/p/en_US/embedded/hwsw/hardware
15
16
17Yocto Project Compatible
18========================
19
20This BSP is compatible with the Yocto Project as per the requirements
21listed here:
22
23 https://www.yoctoproject.org/webform/yocto-project-compatible-registration
24
25
26Dependencies
27============
28
29This layer depends on:
30
31 URI: git://git.openembedded.org/bitbake
32 branch: master
33
34 URI: git://git.openembedded.org/openembedded-core
35 layers: meta
36 branch: master
37
38 URI: git://git.yoctoproject.org/meta-intel
39 layers: intel
40 branch: master
41
42
43Patches
44=======
45
46Please submit any patches against this BSP to the meta-intel mailing list
47(meta-intel@yoctoproject.org) and cc: the maintainer:
48
49Maintainer: Saul Wold <sgw@linux.intel.com>
50
51Please see the meta-intel/MAINTAINERS file for more details.
52
53
54Table of Contents
55=================
56
57 I. Building the meta-nuc BSP layer
58 II. Booting the images in /binary
59
60
61I. Building the meta-nuc BSP layer
62=========================================
63
64In order to build an image with BSP support for a given release, you
65need to download the corresponding BSP tarball from the 'Board Support
66Package (BSP) Downloads' page of the Yocto Project website.
67
68Having done that, and assuming you extracted the BSP tarball contents
69at the top-level of your yocto build tree, you can build a nuc
70image by adding the location of the meta-nuc layer to
71bblayers.conf, along with the meta-intel layer itself (to access
72common metadata shared between BSPs) e.g.:
73
74 yocto/meta-intel \
75 yocto/meta-intel/meta-nuc \
76
77To enable the nuc layer, add the nuc MACHINE to local.conf:
78
79 MACHINE ?= "nuc"
80
81You should then be able to build a nuc image as such:
82
83 $ source oe-init-build-env
84 $ bitbake core-image-sato
85
86At the end of a successful build, you should have a live image that
87you can boot from a USB flash drive (see instructions on how to do
88that below, in the section 'Booting the images from /binary').
89
90NOTE: The 'nuc' machine will include support for hardware video
91acceleration via gstreamer if and only if the "commercial" string is
92added to the the LICENSE_FLAGS_WHITELIST variable in your local.conf.
93
94For example:
95
96 LICENSE_FLAGS_WHITELIST = "commercial"
97
98The reason this is needed is to prevent the image from including
99anything that might violate the license terms of the packages used to
100implement the the video acceleration feature, such as gst-ffmpeg and
101ffmpeg. As always, please consult the licenses included in the
102specific packages for details if you use packages that require
103particular LICENSE_FLAGS.
104
105The xf86-video-intel recipe depends on Xorg's dri and glx modules,
106which are built only when 'opengl' is listed in DISTRO_FEATURES. So
107if the distro doesn't list 'opengl' in the DISTRO_FEATURES, then you
108would need this additional line in your local.conf:
109
110 DISTRO_FEATURES_append = " opengl"
111
112As an alternative to downloading the BSP tarball, you can also work
113directly from the meta-intel git repository. For each BSP in the
114'meta-intel' repository, there are multiple branches, one
115corresponding to each major release starting with 'laverne' (0.90), in
116addition to the latest code which tracks the current master (note that
117not all BSPs are present in every release). Instead of extracting a
118BSP tarball at the top level of your yocto build tree, you can
119equivalently check out the appropriate branch from the meta-intel
120repository at the same location.
121
122
123II. Booting the images in /binary
124=================================
125
126This BSP contains bootable live images, which can be used to directly
127boot Yocto off of a USB flash drive.
128
129Under Linux, insert a USB flash drive. Assuming the USB flash drive
130takes device /dev/sdf, use dd to copy the live image to it. For
131example:
132
133# dd if=core-image-sato-nuc.hddimg of=/dev/sdf
134# sync
135# eject /dev/sdf
136
137This should give you a bootable USB flash device. Insert the device
138into a bootable USB socket on the target, and power on. This should
139result in a system booted to the Sato graphical desktop.
140
141If you want a terminal, use the arrows at the top of the UI to move to
142different pages of available applications, one of which is named
143'Terminal'. Clicking that should give you a root terminal.
144
145If you want to ssh into the system, you can use the root terminal to
146ifconfig the IP address and use that to ssh in. The root password is
147empty, so to log in type 'root' for the user name and hit 'Enter' at
148the Password prompt: and you should be in.
149
150----
151
152If you find you're getting corrupt images on the USB (it doesn't show
153the syslinux boot: prompt, or the boot: prompt contains strange
154characters), try doing this first:
155
156# dd if=/dev/zero of=/dev/sdf bs=1M count=512
diff --git a/meta-nuc/README.sources b/meta-nuc/README.sources
deleted file mode 100644
index 0d4d849a..00000000
--- a/meta-nuc/README.sources
+++ /dev/null
@@ -1,17 +0,0 @@
1The sources for the packages comprising the images shipped with this
2BSP can be found at the following location:
3
4http://downloads.yoctoproject.org/mirror/sources/
5
6The metadata used to generate the images shipped with this BSP, in
7addition to the code contained in this BSP, can be found at the
8following location:
9
10http://downloads.yoctoproject.org/releases/yocto/yocto-1.3/poky-danny-8.0.tar.bz2
11
12The metadata used to generate the images shipped with this BSP, in
13addition to the code contained in this BSP, can also be found at the
14following locations:
15
16git://git.yoctoproject.org/poky.git
17git://git.yoctoproject.org/meta-intel
diff --git a/meta-nuc/conf/layer.conf b/meta-nuc/conf/layer.conf
deleted file mode 100644
index 174411ff..00000000
--- a/meta-nuc/conf/layer.conf
+++ /dev/null
@@ -1,10 +0,0 @@
1# We have a conf and classes directory, add to BBPATH
2BBPATH .= ":${LAYERDIR}"
3
4# We have a recipes directory, add to BBFILES
5BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
6 ${LAYERDIR}/recipes-*/*/*.bbappend"
7
8BBFILE_COLLECTIONS += "nuc"
9BBFILE_PATTERN_nuc := "^${LAYERDIR}/"
10BBFILE_PRIORITY_nuc = "6"
diff --git a/meta-nuc/conf/machine/nuc.conf b/meta-nuc/conf/machine/nuc.conf
deleted file mode 100644
index bdc4bca1..00000000
--- a/meta-nuc/conf/machine/nuc.conf
+++ /dev/null
@@ -1,27 +0,0 @@
1#@TYPE: Machine
2#@NAME: chiefriver
3
4#@WEBTITLE: Intel Next Unit of Computing (NUC) Model: DC3217IYE
5
6#@DESCRIPTION: Machine configuration for Intel NUC model DC3217IYE
7# i.e. Ivy Bridge + Panther Point
8
9PREFERRED_VERSION_linux-yocto ?= "3.19%"
10MACHINE_FEATURES += "va-impl-intel wifi efi"
11MACHINE_FEATURES += "intel-ucode"
12
13require conf/machine/include/meta-intel.inc
14require conf/machine/include/intel-corei7-64-common.inc
15require conf/machine/include/intel-common-pkgarch.inc
16
17MACHINE_HWCODECS ?= "va-intel gstreamer-vaapi-1.0"
18
19XSERVER ?= "${XSERVER_X86_BASE} \
20 ${XSERVER_X86_EXT} \
21 ${XSERVER_X86_I965} \
22 "
23
24MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-iwlwifi-6000g2b-6 lms8"
25
26# disable the serial port configuration
27SERIAL_CONSOLE = ""
diff --git a/meta-nuc/recipes-bsp/alsa-state/alsa-state.bbappend b/meta-nuc/recipes-bsp/alsa-state/alsa-state.bbappend
deleted file mode 100644
index 72d991c7..00000000
--- a/meta-nuc/recipes-bsp/alsa-state/alsa-state.bbappend
+++ /dev/null
@@ -1 +0,0 @@
1FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
diff --git a/meta-nuc/recipes-bsp/alsa-state/alsa-state/nuc/asound.conf b/meta-nuc/recipes-bsp/alsa-state/alsa-state/nuc/asound.conf
deleted file mode 100644
index 1defe77d..00000000
--- a/meta-nuc/recipes-bsp/alsa-state/alsa-state/nuc/asound.conf
+++ /dev/null
@@ -1,24 +0,0 @@
1pcm.!default {
2 type plug
3 slave.pcm "dmixer"
4}
5
6pcm.dmixer {
7 type dmix
8 ipc_key 1024
9 ipc_key_add_uid 0
10 ipc_perm 0666
11 slave {
12 pcm "hw:0,3" # HDMI CARD AND DEVICE
13 period_time 0
14 period_size 1024
15 buffer_size 8192
16 rate 48000 #or 44100
17 }
18}
19
20ctl.dmixer {
21 type hw
22 card 0
23}
24
diff --git a/meta-nuc/recipes-bsp/formfactor/formfactor/nuc/machconfig b/meta-nuc/recipes-bsp/formfactor/formfactor/nuc/machconfig
deleted file mode 100644
index ffce0122..00000000
--- a/meta-nuc/recipes-bsp/formfactor/formfactor/nuc/machconfig
+++ /dev/null
@@ -1,3 +0,0 @@
1# Assume a USB mouse and keyboard are connected
2HAVE_TOUCHSCREEN=0
3HAVE_KEYBOARD=1
diff --git a/meta-nuc/recipes-bsp/formfactor/formfactor_0.0.bbappend b/meta-nuc/recipes-bsp/formfactor/formfactor_0.0.bbappend
deleted file mode 100644
index 72d991c7..00000000
--- a/meta-nuc/recipes-bsp/formfactor/formfactor_0.0.bbappend
+++ /dev/null
@@ -1 +0,0 @@
1FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
diff --git a/meta-nuc/recipes-core/initscripts/initscripts/hdmi_port_audio.sh b/meta-nuc/recipes-core/initscripts/initscripts/hdmi_port_audio.sh
deleted file mode 100644
index 69d8a53f..00000000
--- a/meta-nuc/recipes-core/initscripts/initscripts/hdmi_port_audio.sh
+++ /dev/null
@@ -1,28 +0,0 @@
1#!/bin/sh
2### BEGIN INIT INFO
3# Provides:
4# Required-Start:
5# Required-Stop:
6# Default-Start: S
7# Default-Stop:
8# Short-Description: Configure ALSA audio output to the connected HDMI port
9### END INIT INFO
10
11#
12# If both HDMI ports are connected then use HDMI0 for default ALSA audio out..
13
14ALSA_CONF_FILE="/etc/asound.conf"
15
16HDMI0_STATUS_FILE="/sys/class/drm/card0-HDMI-A-1/status"
17HDMI1_STATUS_FILE="/sys/class/drm/card0-HDMI-A-2/status"
18
19HDMI0_ALSA_CONF="hw:0,3"
20HDMI1_ALSA_CONF="hw:0,7"
21
22if [ -f "${HDMI0_STATUS_FILE}" ] && [ "`cat ${HDMI0_STATUS_FILE}`" == "connected" ]
23then
24 sed -i "s/pcm *\"hw:[0-9]*,[0-9]*\"/pcm \"${HDMI0_ALSA_CONF}\"/" ${ALSA_CONF_FILE}
25elif [ -f "${HDMI1_STATUS_FILE}" ] && [ "`cat ${HDMI1_STATUS_FILE}`" == "connected" ]
26then
27 sed -i "s/pcm \"hw:[0-9]*,[0-9]*\"/pcm \"${HDMI1_ALSA_CONF}\"/" ${ALSA_CONF_FILE}
28fi
diff --git a/meta-nuc/recipes-core/initscripts/initscripts_1.0.bbappend b/meta-nuc/recipes-core/initscripts/initscripts_1.0.bbappend
deleted file mode 100644
index abc5fe01..00000000
--- a/meta-nuc/recipes-core/initscripts/initscripts_1.0.bbappend
+++ /dev/null
@@ -1,10 +0,0 @@
1FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
2
3SRC_URI += "file://hdmi_port_audio.sh"
4
5PR .= ".1"
6
7do_install_append() {
8 install -m 0755 ${WORKDIR}/hdmi_port_audio.sh ${D}${sysconfdir}/init.d
9 ln -sf ../init.d/hdmi_port_audio.sh ${D}${sysconfdir}/rcS.d/S66hdmi_port_audio.sh
10}
diff --git a/meta-sugarbay/COPYING.MIT b/meta-sugarbay/COPYING.MIT
deleted file mode 100644
index fb950dc6..00000000
--- a/meta-sugarbay/COPYING.MIT
+++ /dev/null
@@ -1,17 +0,0 @@
1Permission is hereby granted, free of charge, to any person obtaining a copy
2of this software and associated documentation files (the "Software"), to deal
3in the Software without restriction, including without limitation the rights
4to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
5copies of the Software, and to permit persons to whom the Software is
6furnished to do so, subject to the following conditions:
7
8The above copyright notice and this permission notice shall be included in
9all copies or substantial portions of the Software.
10
11THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
12IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
13FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
14AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
15LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
16OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
17THE SOFTWARE.
diff --git a/meta-sugarbay/README b/meta-sugarbay/README
deleted file mode 100644
index 52835196..00000000
--- a/meta-sugarbay/README
+++ /dev/null
@@ -1,158 +0,0 @@
1This README file contains information on building the meta-sugarbay
2BSP layer, and booting the images contained in the /binary directory.
3Please see the corresponding sections below for details.
4
5The 'Sugar Bay' platform consists of the Intel Sandy Bridge processor,
6plus the Cougar Point PCH (Q67 Express or B65 Express chipsets). This
7BSP assumes that the Sandy Bridge integrated graphics are being used.
8
9Further information on the platforms supported by this BSP can be
10found here:
11
12 http://www.intel.com/p/en_US/embedded/hwsw/hardware/core-q67-b65/overview
13
14And information on all Intel® embedded platforms can be found here:
15
16 http://www.intel.com/p/en_US/embedded/hwsw/hardware
17
18
19Yocto Project Compatible
20========================
21
22This BSP is compatible with the Yocto Project as per the requirements
23listed here:
24
25 https://www.yoctoproject.org/webform/yocto-project-compatible-registration
26
27
28Dependencies
29============
30
31This layer depends on:
32
33 URI: git://git.openembedded.org/bitbake
34 branch: master
35
36 URI: git://git.openembedded.org/openembedded-core
37 layers: meta
38 branch: master
39
40 URI: git://git.yoctoproject.org/meta-intel
41 layers: intel
42 branch: master
43
44
45Patches
46=======
47
48Please submit any patches against this BSP to the meta-intel mailing list
49(meta-intel@yoctoproject.org) and cc: the maintainer:
50
51Maintainer: Saul Wold <sgw@linux.intel.com>
52
53Please see the meta-intel/MAINTAINERS file for more details.
54
55
56Table of Contents
57=================
58
59 I. Building the meta-sugarbay BSP layer
60 II. Booting the images in /binary
61
62
63I. Building the meta-sugarbay BSP layer
64=======================================
65
66In order to build an image with BSP support for a given release, you
67need to download the corresponding BSP tarball from the 'Board Support
68Package (BSP) Downloads' page of the Yocto Project website.
69
70Having done that, and assuming you extracted the BSP tarball contents
71at the top-level of your yocto build tree, you can build a sugarbay
72image by adding the location of the meta-sugarbay layer to
73bblayers.conf, along with the meta-intel layer itself (to access
74common metadata shared between BSPs) e.g.:
75
76 yocto/meta-intel \
77 yocto/meta-intel/meta-sugarbay \
78
79To enable the sugarbay layer, add the sugarbay MACHINE to local.conf:
80
81 MACHINE ?= "sugarbay"
82
83You should then be able to build a sugarbay image as such:
84
85 $ source oe-init-build-env
86 $ bitbake core-image-sato
87
88At the end of a successful build, you should have a live image that
89you can boot from a USB flash drive (see instructions on how to do
90that below, in the section 'Booting the images from /binary').
91
92NOTE: The 'sugarbay' machine will include support for hardware video
93acceleration via gstreamer if and only if the "commercial" string is
94added to the the LICENSE_FLAGS_WHITELIST variable in your local.conf.
95
96For example:
97
98 LICENSE_FLAGS_WHITELIST = "commercial"
99
100The reason this is needed is to prevent the image from including
101anything that might violate the license terms of the packages used to
102implement the the video acceleration feature, such as gst-ffmpeg and
103ffmpeg. As always, please consult the licenses included in the
104specific packages for details if you use packages that require
105particular LICENSE_FLAGS.
106
107The xf86-video-intel recipe depends on Xorg's dri and glx modules,
108which are built only when 'opengl' is listed in DISTRO_FEATURES. So
109if the distro doesn't list 'opengl' in the DISTRO_FEATURES, then you
110would need this additional line in your local.conf:
111
112 DISTRO_FEATURES_append = " opengl"
113
114As an alternative to downloading the BSP tarball, you can also work
115directly from the meta-intel git repository. For each BSP in the
116'meta-intel' repository, there are multiple branches, one
117corresponding to each major release starting with 'laverne' (0.90), in
118addition to the latest code which tracks the current master (note that
119not all BSPs are present in every release). Instead of extracting a
120BSP tarball at the top level of your yocto build tree, you can
121equivalently check out the appropriate branch from the meta-intel
122repository at the same location.
123
124
125II. Booting the images in /binary
126=================================
127
128This BSP contains bootable live images, which can be used to directly
129boot Yocto off of a USB flash drive.
130
131Under Linux, insert a USB flash drive. Assuming the USB flash drive
132takes device /dev/sdf, use dd to copy the live image to it. For
133example:
134
135# dd if=core-image-sato-sugarbay.hddimg of=/dev/sdf
136# sync
137# eject /dev/sdf
138
139This should give you a bootable USB flash device. Insert the device
140into a bootable USB socket on the target, and power on. This should
141result in a system booted to the Sato graphical desktop.
142
143If you want a terminal, use the arrows at the top of the UI to move to
144different pages of available applications, one of which is named
145'Terminal'. Clicking that should give you a root terminal.
146
147If you want to ssh into the system, you can use the root terminal to
148ifconfig the IP address and use that to ssh in. The root password is
149empty, so to log in type 'root' for the user name and hit 'Enter' at
150the Password prompt: and you should be in.
151
152----
153
154If you find you're getting corrupt images on the USB (it doesn't show
155the syslinux boot: prompt, or the boot: prompt contains strange
156characters), try doing this first:
157
158# dd if=/dev/zero of=/dev/sdf bs=1M count=512
diff --git a/meta-sugarbay/README.sources b/meta-sugarbay/README.sources
deleted file mode 100644
index 0d4d849a..00000000
--- a/meta-sugarbay/README.sources
+++ /dev/null
@@ -1,17 +0,0 @@
1The sources for the packages comprising the images shipped with this
2BSP can be found at the following location:
3
4http://downloads.yoctoproject.org/mirror/sources/
5
6The metadata used to generate the images shipped with this BSP, in
7addition to the code contained in this BSP, can be found at the
8following location:
9
10http://downloads.yoctoproject.org/releases/yocto/yocto-1.3/poky-danny-8.0.tar.bz2
11
12The metadata used to generate the images shipped with this BSP, in
13addition to the code contained in this BSP, can also be found at the
14following locations:
15
16git://git.yoctoproject.org/poky.git
17git://git.yoctoproject.org/meta-intel
diff --git a/meta-sugarbay/binary/.gitignore b/meta-sugarbay/binary/.gitignore
deleted file mode 100644
index e69de29b..00000000
--- a/meta-sugarbay/binary/.gitignore
+++ /dev/null
diff --git a/meta-sugarbay/conf/layer.conf b/meta-sugarbay/conf/layer.conf
deleted file mode 100644
index 9576330b..00000000
--- a/meta-sugarbay/conf/layer.conf
+++ /dev/null
@@ -1,12 +0,0 @@
1# We have a conf and classes directory, add to BBPATH
2BBPATH .= ":${LAYERDIR}"
3
4# We have a recipes directory, add to BBFILES
5BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
6 ${LAYERDIR}/recipes-*/*/*.bbappend"
7
8BBFILE_COLLECTIONS += "sugarbay"
9BBFILE_PATTERN_sugarbay := "^${LAYERDIR}/"
10BBFILE_PRIORITY_sugarbay = "6"
11
12LAYERDEPENDS_sugarbay = "intel"
diff --git a/meta-sugarbay/conf/machine/sugarbay.conf b/meta-sugarbay/conf/machine/sugarbay.conf
deleted file mode 100644
index a3357370..00000000
--- a/meta-sugarbay/conf/machine/sugarbay.conf
+++ /dev/null
@@ -1,26 +0,0 @@
1#@TYPE: Machine
2#@NAME: sugarbay
3
4#@WEBTITLE: Intel 2nd Generation Core Platforms: Core i3, i5, i7 (Sandy Bridge)
5
6#@DESCRIPTION: Machine configuration for Sugar Bay systems
7# i.e. Sandy Bridge + Cougar Point
8
9MACHINE_FEATURES += "va-impl-intel"
10
11PREFERRED_VERSION_linux-yocto ?= "3.19%"
12
13require conf/machine/include/meta-intel.inc
14require conf/machine/include/intel-corei7-64-common.inc
15require conf/machine/include/intel-common-pkgarch.inc
16
17MACHINE_HWCODECS ?= "va-intel gstreamer-vaapi-1.0"
18MACHINE_EXTRA_RRECOMMENDS += "linux-firmware"
19
20MACHINE_FEATURES += "wifi"
21MACHINE_FEATURES += "intel-ucode"
22
23XSERVER ?= "${XSERVER_X86_BASE} \
24 ${XSERVER_X86_EXT} \
25 ${XSERVER_X86_I965} \
26 "
diff --git a/meta-sugarbay/recipes-bsp/formfactor/formfactor/sugarbay/machconfig b/meta-sugarbay/recipes-bsp/formfactor/formfactor/sugarbay/machconfig
deleted file mode 100644
index ffce0122..00000000
--- a/meta-sugarbay/recipes-bsp/formfactor/formfactor/sugarbay/machconfig
+++ /dev/null
@@ -1,3 +0,0 @@
1# Assume a USB mouse and keyboard are connected
2HAVE_TOUCHSCREEN=0
3HAVE_KEYBOARD=1
diff --git a/meta-sugarbay/recipes-bsp/formfactor/formfactor_0.0.bbappend b/meta-sugarbay/recipes-bsp/formfactor/formfactor_0.0.bbappend
deleted file mode 100644
index 72d991c7..00000000
--- a/meta-sugarbay/recipes-bsp/formfactor/formfactor_0.0.bbappend
+++ /dev/null
@@ -1 +0,0 @@
1FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2026-01-24 12:56:22 +0000