summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorOng Boon Leong <boon.leong.ong@intel.com>2015-07-23 10:08:06 (GMT)
committerDarren Hart <dvhart@linux.intel.com>2015-07-23 21:25:09 (GMT)
commit7c8a68e7a62185b4b6c94b061af65361084a92b8 (patch)
treecc78f4e59440552115c934725f05ecf4b6d1536c
parent3f1d14b990f8f775aa388459966957d11d524f21 (diff)
downloadmeta-intel-7c8a68e7a62185b4b6c94b061af65361084a92b8.tar.gz
meta-crystalforest: update README to include support for River Forest
This adds further clarification on how various Intel Communication platforms that are supported across different branches within meta-crystalforest layer. Signed-off-by: Ong Boon Leong <boon.leong.ong@intel.com> Signed-off-by: Darren Hart <dvhart@linux.intel.com> (cherry picked from commit 9aa6c066ebf44aecef40caec333772cd970f6842)
-rw-r--r--meta-crystalforest/README100
1 files changed, 62 insertions, 38 deletions
diff --git a/meta-crystalforest/README b/meta-crystalforest/README
index 210df56..2053a3c 100644
--- a/meta-crystalforest/README
+++ b/meta-crystalforest/README
@@ -2,34 +2,38 @@ This README file contains information on building the meta-crystalforest
2BSP layer, and booting the images contained in the /binary directory. 2BSP layer, and booting the images contained in the /binary directory.
3Please see the corresponding sections below for details. 3Please see the corresponding sections below for details.
4 4
5The 'Crystal Forest' platform consists of two versions. 5Overview of Intel Communication Product Offering
61. GLADDEN 6------------------------------------------------
72. SERVER
8 7
9The Gladden Platform consists of Intel Xeon E3-1125C/E3-1105C Processor, 8The following platforms are supported on meta-intel dizzy branch ONLY:
10plus the Intel Communication Chipset 89xx for Smaller Form Factor
11Communication Infrastructure.
12(Gladden + Cave Creek) also known as CrystalForest-Gladden
13 9
14The Server Platform consists of Intel Xeon E5-2600 and E5-2400 Processors, 10Crystal Forest/Server - Shumway reference platform configurations:
15plus the Intel Communication Chipset 89xx for Large-Scale Communications 11processor: Intel Xeon E5-2600/E5-2400 (Sandy Bridge-based) or
16Infrastructure. 12 Intel Xeon E5-2600v2/E5-2400v2 (Ivy Bridge-based)
17(Ivy Bridge-EP/EN + Coleto Creek) also known as HighlandForest 13chipset: Intel Communication Chipset 8900-8920 Series (Cave Creek)
18(Sandy Bridge-EP/EN + Cave Creek) also known as CrystalForest-Server 14url: http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-e5-89xx/overview
19 15
20Both Platforms use Matrox graphics Card. 16Crystal Forest/Gladden - Stargo reference platform configurations:
17processor: Intel Xeon E3-1125C/E3-1105C (Sandy Bridge-based) or
18 Intel Xeon E3-1125v2/E3-1105v2 (Ivy Bridge-based)
19chipset: Intel Communication Chipset 8900-8920 Series (Cave Creek)
20url: http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-core-pentium-celeron-89xx/overview
21 21
22Further information about the Crystal Forest Gladden platform supported 22Highland Forest (Crystal Forest/Server Refresh) - Shumway reference platform configurations:
23by this BSP can be found here: 23processor: Intel Xeon E5-2600v2/E5-2400v2 (Ivy Bridge-based)
24chipset: Intel Communication Chipset 8925-8955 Series (Coleto Creek)
25url: https://www-ssl.intel.com/content/www/us/en/intelligent-systems/crystal-forest-server/xeon-e5-v2-89xx-chipset-ibd.html
24 26
25 http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-core-pentium-celeron-89xx/overview 27The following platform is supported on meta-intel fido branch and beyond.
26 28
27Further information about the Crystal Forest server platform supported 29River Forest - Long Brook reference platform configurations:
28by this BSP can be found here: 30processor: Intel Xeon E5-2600v3/E5-2400v3 (Haswell EP-based)
31chipset: Intel Communication Chipset 8925-8955 Series (Coleto Creek)
32url: https://www-ssl.intel.com/content/www/my/en/embedded/products/river-forest/overview.html?wapkw=coleto
29 33
30 http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-e5-89xx/overview 34All above four platforms use PCIe-based Matrox graphics card for display.
31 35
32Information on all IntelĀ® embedded platforms can be found here: 36More Information on all IntelĀ® embedded platforms can be found here:
33 37
34 http://www.intel.com/p/en_US/embedded/hwsw/hardware 38 http://www.intel.com/p/en_US/embedded/hwsw/hardware
35 39
@@ -65,7 +69,7 @@ Patches
65Please submit any patches against this BSP to the meta-intel mailing 69Please submit any patches against this BSP to the meta-intel mailing
66list (meta-intel@yoctoproject.org) and cc: the maintainer: 70list (meta-intel@yoctoproject.org) and cc: the maintainer:
67 71
68Maintainer: Chan Wei Sern <wei.sern.chan@intel.com> 72Maintainer: Wu Chia Chuan <chia.chuan.wu@intel.com>
69 73
70Please see the meta-intel/MAINTAINERS file for more details. 74Please see the meta-intel/MAINTAINERS file for more details.
71 75
@@ -114,6 +118,8 @@ At the end of a successful build, you should have a live image that
114you can boot from a USB flash drive (see instructions on how to do 118you can boot from a USB flash drive (see instructions on how to do
115that below, in the section 'Booting the images from /binary'). 119that below, in the section 'Booting the images from /binary').
116 120
121The live image is located within build/tmp/deploy/images/<machine> folder.
122
117As an alternative to downloading the BSP tarball, you can also work 123As an alternative to downloading the BSP tarball, you can also work
118directly from the meta-intel git repository. For each BSP in the 124directly from the meta-intel git repository. For each BSP in the
119'meta-intel' repository, there are multiple branches, one 125'meta-intel' repository, there are multiple branches, one
@@ -131,15 +137,26 @@ II. Booting the images in /binary
131This BSP contains bootable live images, which can be used to directly 137This BSP contains bootable live images, which can be used to directly
132boot Yocto off of a USB flash drive. 138boot Yocto off of a USB flash drive.
133 139
134Under Linux, insert a USB flash drive. Assuming the USB flash drive 140You can deploy the hddimg image to a USB or SATA device. You will
135takes device /dev/sdf, use dd to copy the live image to it. For 141need to know the device name on your host as well as the device name on
136example: 142the target. Be careful with this step as using the wrong host device can
143result in overwriting data on your host machine.
144
145Under Linux, USB and SATA devices typically appears as /dev/sdb,
146/dev/sdc, etc. Watching your system messages as you connect the device
147will tell you exactly which device name is assigned to the device.
148On the Valley Island platform, assuming only one storage device is
149attached at boot, a USB or SATA device will be /dev/sda.
150
151After inserting the boot media into your host machine and determining
152your host and target device, create the image using the mkefidisk.sh
153script, provided by poky under scripts/contrib/. Note that root
154privileges are required. For example, using an USB device which appears
155as /dev/sdc on the host:
137 156
138To boot on both Gladden and Server Platforms: 157$ sudo ./mkefidisk.sh /dev/sdc core-image-sato-<machine>.hddimg /dev/sda
139 158
140# dd if=core-image-sato-crystalforest.hddimg of=/dev/sdf 159Follow the prompts on the screen to confirm the action.
141# sync
142# eject /dev/sdf
143 160
144This should give you a bootable USB flash device. Insert the device 161This should give you a bootable USB flash device. Insert the device
145into a bootable USB socket on the target, and power on. This should 162into a bootable USB socket on the target, and power on. This should
@@ -165,6 +182,9 @@ a. Boot Loader
165- Support BIOS version at Stargo board ( CrystalForest-Gladden ): 182- Support BIOS version at Stargo board ( CrystalForest-Gladden ):
166 CIVGCCK1.86C.0003.P00 183 CIVGCCK1.86C.0003.P00
167 184
185- Support BIOS version at Long Brook board (RiverForest)
186 GRNDCRB1.86B.0022.R01.i02.1405151000
187
168b. I/O drivers 188b. I/O drivers
169-------------- 189--------------
170-Support Matrox graphic card. 190-Support Matrox graphic card.
@@ -176,16 +196,20 @@ b. I/O drivers
176IV. Enabling Intel DPDK and QuickAssist Technology 196IV. Enabling Intel DPDK and QuickAssist Technology
177=================================================== 197===================================================
178 198
179There are recipes available for the 'Intel Data Plane Development Kit and 199DPDK recipe: meta-intel/meta-isg/common/recipes-extended/dpdk
180Intel QuickAssist Technology components for use with this BSP. Please 200QAT recipe: meta-crystalforest/recipes-extended/qat
181contact your Intel Field Sales Representative or visit Intel Embedded Design 201QAT-enable zlib recipe: meta-crystalforest/recipes-extended/zlib-qat
182Center (www.intel.com/p/en_US/embedded/designcenter) for instructions on how 202
183to locate and use these recipes. 203Note:
204qat16 recipe is meant for platform with Coleto Creek chipset.
205qat15 recipe is meant for platform with Cave Creek chipset.
184 206
185---- 207By default, the machine configuration does not assume that the above
208ingredients are pre-installed onto the BSP. Developers are required
209to either use smart tool to install those software packages or
210configure IMAGE_INSTALL under build/conf/local.conf, for example.
186 211
187If you find you're getting corrupt images on the USB (it doesn't show 212IMAGE_INSTALL += "dpdk qat16 zlib-qat"
188the syslinux boot: prompt, or the boot: prompt contains strange
189characters), try doing this first:
190 213
191# dd if=/dev/zero of=/dev/sdf bs=1M count=512 214The list of packages can be searched under tmp/deploy/<package-type>
215folder.