summaryrefslogtreecommitdiffstats
path: root/meta-romley/README
diff options
context:
space:
mode:
authorWU CHIA CHUAN <chia.chuan.wu@intel.com>2015-09-28 08:03:16 (GMT)
committerSaul Wold <sgw@linux.intel.com>2015-09-30 01:05:49 (GMT)
commit84c049b9cb80b50fd32b716c2ae97e3f0d4e3cd7 (patch)
treeef1fb0171d8e087a7d4f7d1b04a8d9b59c522801 /meta-romley/README
parent5e218aeacace801c4f01a1db8c99ac8a51421661 (diff)
downloadmeta-intel-84c049b9cb80b50fd32b716c2ae97e3f0d4e3cd7.tar.gz
meta-intel: meta-romley BSP retirement from YP 2.0
Remove meta-romley BSP layer from meta-intel master branch which is targeting for YP 2.0. A heads-up email was sent to the meta-intel mailing list for requesting any feedback regarding retirement of these BSP. Since there is no concern, we assume that it is agreed upon and thus this patch to retire the BSP. The "MAINTAINERS file" and "conf/machine/README file" are updated to reflect removal of the BSP. We expect intel-corei7-64 machine is continued to be used to support the platform and dpdk recipe under meta-romley is now supported under meta-isg/common/recipes-extended/dpdk. Signed-off-by: WU CHIA CHUAN <chia.chuan.wu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
Diffstat (limited to 'meta-romley/README')
-rw-r--r--meta-romley/README199
1 files changed, 0 insertions, 199 deletions
diff --git a/meta-romley/README b/meta-romley/README
deleted file mode 100644
index acdcb99..0000000
--- a/meta-romley/README
+++ /dev/null
@@ -1,199 +0,0 @@
1This README file contains information on building the meta-romley
2BSP layer, and booting the images contained in the /binary directory.
3Please see the corresponding sections below for details.
4
5The romley platform consists of two versions:
61. romley - Sandy Bridge
72. romley - Ivy Bridge
8
9The romley - Sandy Bridge platform consists of the Intel Xeon E5-2600
10and E5-2400 Series processors, plus the Intel C604/C602-J chipset
11(Sandy Bridge-EP/EN + Patsburg).
12
13The romley - Ivy Bridge platform consists of the Intel Xeon E5-2600
14and E5-2400 v2 Series processors with the Intel C604/C602-J chipset
15(Ivy Bridge-EP/EN + Patsburg).
16
17This BSP assumes Matrox graphics is being used.
18
19Further information about the platforms supported by this BSP can be
20found here:
21
22 http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-e5-c604/overview
23
24Information on all IntelĀ® embedded platforms can be found here:
25
26 http://www.intel.com/p/en_US/embedded/hwsw/hardware
27
28
29Yocto Project Compatible
30========================
31
32This BSP is compatible with the Yocto Project as per the requirements
33listed here:
34
35 https://www.yoctoproject.org/webform/yocto-project-compatible-registration
36
37
38Dependencies
39============
40
41This layer depends on:
42
43 URI: git://git.openembedded.org/bitbake
44 branch: master
45
46 URI: git://git.openembedded.org/openembedded-core
47 layers: meta
48 branch: master
49
50 URI: git://git.yoctoproject.org/meta-intel
51 layers: intel
52 branch: master
53
54
55Patches
56=======
57
58Please submit any patches against this BSP to the meta-intel mailing
59list (meta-intel@yoctoproject.org) and cc: the maintainer:
60
61Maintainer: Chan Wei Sern <wei.sern.chan@intel.com>
62
63Please see the meta-intel/MAINTAINERS file for more details.
64
65
66Table of Contents
67=================
68
69 I. Building the meta-romley BSP layer
70 II. Booting the images in /binary
71III. Device Notes
72 a. Boot Loader
73 b. I/O drivers
74IV. Enabling Intel DPDK Technology
75
76I. Building the meta-romley BSP layer
77=======================================
78
79In order to build an image with BSP support for a given release, you
80need to download the corresponding BSP tarball from the 'Board Support
81Package (BSP) Downloads' page of the Yocto Project website.
82
83Having done that, and assuming you extracted the BSP tarball contents
84at the top-level of your yocto build tree, you can build a romley
85image by adding the location of the meta-romley layer to
86bblayers.conf, along with the meta-intel layer itself (to access
87common metadata shared between BSPs) e.g.:
88
89 yocto/meta-intel \
90 yocto/meta-intel/meta-romley \
91
92To enable the romley Sandy Bridge layer, add the romley MACHINE to local.conf:
93
94 MACHINE ?= "romley"
95
96To enable the romley Ivy Bridge layer, add the romley-ivb MACHINE to local.conf:
97
98 MACHINE ?= "romley-ivb"
99
100You should then be able to build a romley image as such:
101
102 $ source oe-init-build-env
103 $ bitbake core-image-sato
104
105At the end of a successful build, you should have a live image that
106you can boot from a USB flash drive (see instructions on how to do
107that below, in the section 'Booting the images from /binary').
108
109As an alternative to downloading the BSP tarball, you can also work
110directly from the meta-intel git repository. For each BSP in the
111'meta-intel' repository, there are multiple branches, one
112corresponding to each major release starting with 'laverne' (0.90), in
113addition to the latest code which tracks the current master (note that
114not all BSPs are present in every release). Instead of extracting a
115BSP tarball at the top level of your yocto build tree, you can
116equivalently check out the appropriate branch from the meta-intel
117repository at the same location.
118
119
120II. Booting the images in /binary
121=================================
122
123This BSP contains bootable live images, which can be used to directly
124boot Yocto off of a USB flash drive.
125
126Under Linux, insert a USB flash drive. Assuming the USB flash drive
127takes device /dev/sdf, use dd to copy the live image to it. For
128example:
129
130# dd if=core-image-sato-romley.hddimg of=/dev/sdf
131# sync
132# eject /dev/sdf
133
134This should give you a bootable USB flash device. Insert the device
135into a bootable USB socket on the target, and power on. This should
136result in a system booted to the Sato graphical desktop.
137
138If you want a terminal, use the arrows at the top of the UI to move to
139different pages of available applications, one of which is named
140'Terminal'. Clicking that should give you a root terminal.
141
142If you want to ssh into the system, you can use the root terminal to
143ifconfig the IP address and use that to ssh in. The root password is
144empty, so to log in type 'root' for the user name and hit 'Enter' at
145the Password prompt: and you should be in.
146
147If you're using Rose City and does not have ME firmware and struggling with
148rebooting the machine. This is because broken ME firmware can contribute to long wait of
149reboot. We have to changing the kernel command line to blacklist MEI driver to be loaded:
150
1511. Open your syslinux in VI editor eg:
152 # vi /media/sda/syslinux.cfg
153
1542. Look for the line that has kernel command line which has certain similiarity
155 as below:
156
157 "APPEND initrd=/initrd LABEL=boot root=/dev/ram0 ....."
158
159 or
160
161 "APPEND initrd=/initrd LABEL=install root=/dev/ram0 ...."
162
1633. Add "mei_me.blacklist=yes"at the end of that line and it will be like below:
164 "APPEND inird=/initRD LABEL=boot root=/dev/ram0 .... mei_me.blacklist=yes"
165
1664. Save this syslinux.cfg
167
1685. Boot up the Romley with this new changed.
169
170
171III. Device Notes
172=================
173
174a. Boot Loader
175--------------
176- Support BIOS version at RoseCity board :RMLCRB.86J.R0.45.D018
177
178b. I/O drivers
179--------------
180-Support Matrox graphic card.
181-Support SATA, USB Host v2.0
182-Supported I/O devices (APIC, RTC, SPI, UART, I2C, LPS, SMBus i801,
183 WDT, and HPET)
184
185IV. Enabling Intel DPDK Technology
186===================================
187
188There are recipes available for the 'Intel Data Plane Development Kit
189Technology components for use with this BSP. Please contact your
190Intel Field Sales Representative or visit Intel Embedded Design
191Center (www.intel.com/p/en_US/embedded/designcenter) for instructions on how
192to locate and use these recipes.
193----
194
195If you find you're getting corrupt images on the USB (it doesn't show
196the syslinux boot: prompt, or the boot: prompt contains strange
197characters), try doing this first:
198
199# dd if=/dev/zero of=/dev/sdf bs=1M count=512