summaryrefslogtreecommitdiffstats
path: root/meta-sugarbay/README
diff options
context:
space:
mode:
authorTom Zanussi <tom.zanussi@intel.com>2011-01-31 01:05:15 -0600
committerTom Zanussi <tom.zanussi@intel.com>2011-01-31 01:05:15 -0600
commit2deb57956fc6a721c46c67bcdf844ed29c71f3a3 (patch)
tree4bac2da3a3c4dc87b3e87a8527451e3d5f9e2a00 /meta-sugarbay/README
parentc5ecc11dec2402aa05e68bd03b65a6460837b748 (diff)
downloadmeta-intel-2deb57956fc6a721c46c67bcdf844ed29c71f3a3.tar.gz
meta-sugarbay: new layer for Sandy Bridge/Cougar Point systems
This layer provides support for Sandy Bridge + Cougar Point Intel systems. The 'Sugar Bay' platform consists of the Intel Sandy Bridge processor, plus the Cougar Point PCH (Q67 Express or B65 Express chipsets). This BSP assumes that the Sandy Bridge integrated graphics are being used, and makes use of the grub2 and associated live-install changes in meta-intel/common. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Diffstat (limited to 'meta-sugarbay/README')
-rw-r--r--meta-sugarbay/README84
1 files changed, 84 insertions, 0 deletions
diff --git a/meta-sugarbay/README b/meta-sugarbay/README
new file mode 100644
index 00000000..bcc46c23
--- /dev/null
+++ b/meta-sugarbay/README
@@ -0,0 +1,84 @@
1This README file contains information on building the meta-sugarbay
2BSP layer, and booting the images contained in the /binary directory.
3Please see the corresponding sections below for details.
4
5The 'Sugar Bay' platform consists of the Intel Sandy Bridge processor,
6plus the Cougar Point PCH (Q67 Express or B65 Express chipsets). This
7BSP assumes that the Sandy Bridge integrated graphics are being used.
8
9Table of Contents
10=================
11
12 I. Building the meta-sugarbay BSP layer
13 II. Special notes for building the meta-sugarbay BSP layer
14III. Booting the images in /binary
15
16
17I. Building the meta-sugarbay BSP layer
18=======================================
19
20For each BSP in the 'meta-intel' repository, there are multiple
21branches, one corresponding to each major release starting with
22'laverne' (0.90), in addition to the latest code which tracks the
23current master.
24
25In order to build an image with BSP support for a given release, you
26need to check out the 'meta-intel' branch corresponding to the release
27you're building against e.g. to build for laverne (0.90), check out
28the 'laverne' branch of both poky and 'meta-intel'.
29
30Having done that, and assuming you cloned the 'meta-intel' repository
31at the top-level of your yocto build tree, you can build a sugarbay
32image by adding the location of the meta-sugarbay layer to
33bblayers.conf e.g.:
34
35 yocto/meta-intel/meta-sugarbay \
36
37To enable the sugarbay layer, add the sugarbay MACHINE to local.conf:
38
39 MACHINE ?= "sugarbay"
40
41You should then be able to build a sugarbay image as such:
42
43 $ source poky-init-build-env
44 $ bitbake poky-image-sato-live
45
46At the end of a successful build, you should have a live image that
47you can boot from a USB flash drive (see instructions on how to do
48that below, in the section 'Booting the images from /binary').
49
50
51II. Booting the images in /binary
52=================================
53
54This BSP contains bootable live images, which can be used to directly
55boot Yocto off of a USB flash drive.
56
57Under Linux, insert a USB flash drive. Assuming the USB flash drive
58takes device /dev/sdf, use dd to copy the live image to it. For
59example:
60
61# dd if=poky-image-sato-live-sugarbay-20101207053738.hddimg of=/dev/sdf
62# sync
63# eject /dev/sdf
64
65This should give you a bootable USB flash device. Insert the device
66into a bootable USB socket on the target, and power on. This should
67result in a system booted to the Sato graphical desktop.
68
69If you want a terminal, use the arrows at the top of the UI to move to
70different pages of available applications, one of which is named
71'Terminal'. Clicking that should give you a root terminal.
72
73If you want to ssh into the system, you can use the root terminal to
74ifconfig the IP address and use that to ssh in. The root password is
75empty, so to log in type 'root' for the user name and hit 'Enter' at
76the Password prompt: and you should be in.
77
78----
79
80If you find you're getting corrupt images on the USB (it doesn't show
81the syslinux boot: prompt, or the boot: prompt contains strange
82characters), try doing this first:
83
84# dd if=/dev/zero of=/dev/sdf bs=1M count=512