diff options
author | Kishore Bodke <kishore.k.bodke@intel.com> | 2011-10-27 14:21:43 -0700 |
---|---|---|
committer | Tom Zanussi <tom.zanussi@intel.com> | 2011-10-28 00:04:20 -0500 |
commit | 478969defe862a2779bf7eb3bca30e2067827d7e (patch) | |
tree | 7f4eca944555205306c3a9d2145268a31cead89a /meta-romley/README | |
parent | b5c9f0af18b80c2b4c478fd7cfb537e0a04a4e22 (diff) | |
download | meta-intel-478969defe862a2779bf7eb3bca30e2067827d7e.tar.gz |
New Romley BSP created. Uses Matrox MGA graphics driver.
This layer provides new BSP meta-romley.
This provides the support for Romley + Patsburg Chipset for Intel Systems.
Romley refers to the Intel Rosecity Board.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Diffstat (limited to 'meta-romley/README')
-rw-r--r-- | meta-romley/README | 88 |
1 files changed, 88 insertions, 0 deletions
diff --git a/meta-romley/README b/meta-romley/README new file mode 100644 index 00000000..d242534d --- /dev/null +++ b/meta-romley/README | |||
@@ -0,0 +1,88 @@ | |||
1 | This README file contains information on building the meta-romley | ||
2 | BSP layer, and booting the images contained in the /binary directory. | ||
3 | Please see the corresponding sections below for details. | ||
4 | |||
5 | The 'romley' platform consists of the Intel Sandy Bridge processor, | ||
6 | plus the Patsburg chipset. This BSP assumes Matrox graphics is being used. | ||
7 | |||
8 | Table of Contents | ||
9 | ================= | ||
10 | |||
11 | I. Building the meta-romley BSP layer | ||
12 | II. Booting the images in /binary | ||
13 | |||
14 | |||
15 | I. Building the meta-romley BSP layer | ||
16 | ======================================= | ||
17 | |||
18 | In order to build an image with BSP support for a given release, you | ||
19 | need to download the corresponding BSP tarball from the 'Board Support | ||
20 | Package (BSP) Downloads' page of the Yocto Project website. | ||
21 | |||
22 | Having done that, and assuming you extracted the BSP tarball contents | ||
23 | at the top-level of your yocto build tree, you can build a romley | ||
24 | image by adding the location of the meta-romley layer to | ||
25 | bblayers.conf e.g.: | ||
26 | |||
27 | yocto/meta-intel/meta-romley \ | ||
28 | |||
29 | To enable the romley layer, add the romley MACHINE to local.conf: | ||
30 | |||
31 | MACHINE ?= "romley" | ||
32 | |||
33 | You should then be able to build a romley image as such: | ||
34 | |||
35 | $ source oe-init-build-env | ||
36 | $ bitbake core-image-sato | ||
37 | |||
38 | At the end of a successful build, you should have a live image that | ||
39 | you can boot from a USB flash drive (see instructions on how to do | ||
40 | that below, in the section 'Booting the images from /binary'). | ||
41 | |||
42 | As an alternative to downloading the BSP tarball, you can also work | ||
43 | directly from the meta-intel git repository. For each BSP in the | ||
44 | 'meta-intel' repository, there are multiple branches, one | ||
45 | corresponding to each major release starting with 'laverne' (0.90), in | ||
46 | addition to the latest code which tracks the current master (note that | ||
47 | not all BSPs are present in every release). Instead of extracting a | ||
48 | BSP tarball at the top level of your yocto build tree, you can | ||
49 | equivalently check out the appropriate branch from the meta-intel | ||
50 | repository at the same location. | ||
51 | |||
52 | |||
53 | II. Booting the images in /binary | ||
54 | ================================= | ||
55 | |||
56 | This BSP contains bootable live images, which can be used to directly | ||
57 | boot Yocto off of a USB flash drive. | ||
58 | |||
59 | Under Linux, insert a USB flash drive. Assuming the USB flash drive | ||
60 | takes device /dev/sdf, use dd to copy the live image to it. For | ||
61 | example: | ||
62 | |||
63 | # dd if=core-image-sato-romley-20111007220323.hddimg of=/dev/sdf | ||
64 | # sync | ||
65 | # eject /dev/sdf | ||
66 | |||
67 | This should give you a bootable USB flash device. Insert the device | ||
68 | into a bootable USB socket on the target, and power on. This should | ||
69 | result in a system booted to the Sato graphical desktop. | ||
70 | |||
71 | If you want a terminal, use the arrows at the top of the UI to move to | ||
72 | different pages of available applications, one of which is named | ||
73 | 'Terminal'. Clicking that should give you a root terminal. | ||
74 | |||
75 | If you want to ssh into the system, you can use the root terminal to | ||
76 | ifconfig the IP address and use that to ssh in. The root password is | ||
77 | empty, so to log in type 'root' for the user name and hit 'Enter' at | ||
78 | the Password prompt: and you should be in. | ||
79 | |||
80 | ---- | ||
81 | |||
82 | If you find you're getting corrupt images on the USB (it doesn't show | ||
83 | the syslinux boot: prompt, or the boot: prompt contains strange | ||
84 | characters), try doing this first: | ||
85 | |||
86 | # dd if=/dev/zero of=/dev/sdf bs=1M count=512 | ||
87 | |||
88 | |||