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