diff options
author | Saul Wold <sgw@linux.intel.com> | 2015-08-25 16:39:01 -0700 |
---|---|---|
committer | Saul Wold <sgw@linux.intel.com> | 2015-08-28 14:25:29 -0700 |
commit | 4172351baa285b83eb54d54368fe2f037c48159b (patch) | |
tree | c2c1991e05b0260615b83abf59acee81a534ec10 /meta-jasperforest/README | |
parent | 44df7ddf395f82c28c494b92fb3f627f81e2e627 (diff) | |
download | meta-intel-4172351baa285b83eb54d54368fe2f037c48159b.tar.gz |
Remove older platform specific BSPs
The intel-core* BSPs supercede these older BSPs therefore it's time
to remove these older platform specific bsps.
Bump LAYERVERSION to 3 to allow the Autobuilder to know that these
BSPs have been removed.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Diffstat (limited to 'meta-jasperforest/README')
-rw-r--r-- | meta-jasperforest/README | 137 |
1 files changed, 0 insertions, 137 deletions
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 @@ | |||
1 | This README file contains information on building the | ||
2 | meta-jasperforest BSP layer, and booting the images contained in the | ||
3 | /binary directory. Please see the corresponding sections below for | ||
4 | details. | ||
5 | |||
6 | 'Jasper Forest' refers to the Intel Xeon C5500/C3500 processors, which | ||
7 | combined with the Intel 3420 PCH chipset (Ibex Peak) make up the | ||
8 | 'Picket Post' CRB this BSP was developed on. | ||
9 | |||
10 | Further information on the platforms supported by this BSP can be | ||
11 | found here: | ||
12 | |||
13 | http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-c5500-c3500-3420/overview | ||
14 | |||
15 | Information on all IntelĀ® embedded platforms can be found here: | ||
16 | |||
17 | http://www.intel.com/p/en_US/embedded/hwsw/hardware | ||
18 | |||
19 | |||
20 | Yocto Project Compatible | ||
21 | ======================== | ||
22 | |||
23 | This BSP is compatible with the Yocto Project as per the requirements | ||
24 | listed here: | ||
25 | |||
26 | https://www.yoctoproject.org/webform/yocto-project-compatible-registration | ||
27 | |||
28 | |||
29 | Dependencies | ||
30 | ============ | ||
31 | |||
32 | This 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 | |||
46 | Patches | ||
47 | ======= | ||
48 | |||
49 | Please submit any patches against this BSP to the meta-intel mailing list | ||
50 | (meta-intel@yoctoproject.org) and cc: the maintainer: | ||
51 | |||
52 | Maintainer: Saul Wold <sgw@linux.intel.com> | ||
53 | |||
54 | Please see the meta-intel/MAINTAINERS file for more details. | ||
55 | |||
56 | |||
57 | Table of Contents | ||
58 | ================= | ||
59 | |||
60 | I. Building the meta-jasperforest BSP layer | ||
61 | II. Booting the images in /binary | ||
62 | |||
63 | |||
64 | I. Building the meta-jasperforest BSP layer | ||
65 | ======================================= | ||
66 | |||
67 | In order to build an image with BSP support for a given release, you | ||
68 | need to download the corresponding BSP tarball from the 'Board Support | ||
69 | Package (BSP) Downloads' page of the Yocto Project website. | ||
70 | |||
71 | Having done that, and assuming you extracted the BSP tarball contents | ||
72 | at the top-level of your yocto build tree, you can build a | ||
73 | jasperforest image by adding the location of the meta-jasperforest | ||
74 | layer to bblayers.conf, along with the meta-intel layer itself (to | ||
75 | access common metadata shared between BSPs) e.g.: | ||
76 | |||
77 | yocto/meta-intel \ | ||
78 | yocto/meta-intel/meta-jasperforest \ | ||
79 | |||
80 | To enable the jasperforest layer, add the jasperforest MACHINE to local.conf: | ||
81 | |||
82 | MACHINE ?= "jasperforest" | ||
83 | |||
84 | You should then be able to build a jasperforest image as such: | ||
85 | |||
86 | $ source oe-init-build-env | ||
87 | $ bitbake core-image-sato | ||
88 | |||
89 | At the end of a successful build, you should have a live image that | ||
90 | you can boot from a USB flash drive (see instructions on how to do | ||
91 | that below, in the section 'Booting the images from /binary'). | ||
92 | |||
93 | As an alternative to downloading the BSP tarball, you can also work | ||
94 | directly from the meta-intel git repository. For each BSP in the | ||
95 | 'meta-intel' repository, there are multiple branches, one | ||
96 | corresponding to each major release starting with 'laverne' (0.90), in | ||
97 | addition to the latest code which tracks the current master (note that | ||
98 | not all BSPs are present in every release). Instead of extracting a | ||
99 | BSP tarball at the top level of your yocto build tree, you can | ||
100 | equivalently check out the appropriate branch from the meta-intel | ||
101 | repository at the same location. | ||
102 | |||
103 | |||
104 | II. Booting the images in /binary | ||
105 | ================================= | ||
106 | |||
107 | This BSP contains bootable live images, which can be used to directly | ||
108 | boot Yocto off of a USB flash drive. | ||
109 | |||
110 | Under Linux, insert a USB flash drive. Assuming the USB flash drive | ||
111 | takes device /dev/sdf, use dd to copy the live image to it. For | ||
112 | example: | ||
113 | |||
114 | # dd if=core-image-sato-jasperforest.hddimg of=/dev/sdf | ||
115 | # sync | ||
116 | # eject /dev/sdf | ||
117 | |||
118 | This should give you a bootable USB flash device. Insert the device | ||
119 | into a bootable USB socket on the target, and power on. This should | ||
120 | result in a system booted to the Sato graphical desktop. | ||
121 | |||
122 | If you want a terminal, use the arrows at the top of the UI to move to | ||
123 | different pages of available applications, one of which is named | ||
124 | 'Terminal'. Clicking that should give you a root terminal. | ||
125 | |||
126 | If you want to ssh into the system, you can use the root terminal to | ||
127 | ifconfig the IP address and use that to ssh in. The root password is | ||
128 | empty, so to log in type 'root' for the user name and hit 'Enter' at | ||
129 | the Password prompt: and you should be in. | ||
130 | |||
131 | ---- | ||
132 | |||
133 | If you find you're getting corrupt images on the USB (it doesn't show | ||
134 | the syslinux boot: prompt, or the boot: prompt contains strange | ||
135 | characters), try doing this first: | ||
136 | |||
137 | # dd if=/dev/zero of=/dev/sdf bs=1M count=512 | ||