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