diff options
author | Darren Hart <dvhart@linux.intel.com> | 2012-10-29 11:48:06 -0700 |
---|---|---|
committer | Darren Hart <dvhart@linux.intel.com> | 2012-10-31 08:40:15 -0700 |
commit | 43b2e9c34363ade4241a60f699b47179929c6fb6 (patch) | |
tree | 9aa6d99d27f45c71a8b3cf5fab66af024680d759 /meta-n450/README | |
parent | eb413f9fdb34db05fd3fd40ce15bf896272acbf3 (diff) | |
download | meta-intel-43b2e9c34363ade4241a60f699b47179929c6fb6.tar.gz |
n450: Add WEBTITLE and boilerplate README
The WEBTITLE will be used to publish the BSP on the Yocto Project website.
Add a boilerplate README including the Yocto Project compliance
information for the 1.3 release.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Diffstat (limited to 'meta-n450/README')
-rw-r--r-- | meta-n450/README | 125 |
1 files changed, 125 insertions, 0 deletions
diff --git a/meta-n450/README b/meta-n450/README new file mode 100644 index 00000000..95000e90 --- /dev/null +++ b/meta-n450/README | |||
@@ -0,0 +1,125 @@ | |||
1 | This README file contains information on building the meta-n450 | ||
2 | BSP layer, and booting the images contained in the /binary directory. | ||
3 | Please see the corresponding sections below for details. | ||
4 | |||
5 | The Luna Pier platform consists of the Intel Atom E4xx processor (Pineview), | ||
6 | plus the Intel 82801Hm I/O Controller. | ||
7 | |||
8 | |||
9 | Compliance | ||
10 | ========== | ||
11 | |||
12 | This BSP is compliant with the Yocto Project as per the requirements | ||
13 | listed here: | ||
14 | |||
15 | http://www.yoctoproject.org/yocto-project-compatible-registration | ||
16 | |||
17 | |||
18 | Dependencies | ||
19 | ============ | ||
20 | |||
21 | This layer depends on: | ||
22 | |||
23 | URI: git://git.openembedded.org/bitbake | ||
24 | branch: master | ||
25 | |||
26 | URI: git://git.openembedded.org/openembedded-core | ||
27 | layers: meta | ||
28 | branch: master | ||
29 | |||
30 | URI: git://git.yoctoproject.org/meta-intel | ||
31 | layers: intel | ||
32 | branch: master | ||
33 | |||
34 | |||
35 | Patches | ||
36 | ======= | ||
37 | |||
38 | Please submit any patches against this BSP to the Yocto mailing list | ||
39 | (yocto@yoctoproject.org) and cc: the maintainer: | ||
40 | |||
41 | Maintainer: Darren Hart <dvhart@linux.intel.com> | ||
42 | |||
43 | Please see the meta-intel/MAINTAINERS file for more details. | ||
44 | |||
45 | |||
46 | Table of Contents | ||
47 | ================= | ||
48 | |||
49 | I. Building the meta-n450 BSP layer | ||
50 | II. Booting the images in /binary | ||
51 | |||
52 | |||
53 | I. Building the meta-n450 BSP layer | ||
54 | ======================================= | ||
55 | |||
56 | In order to build an image with BSP support for a given release, you | ||
57 | need to download the corresponding BSP tarball from the 'Board Support | ||
58 | Package (BSP) Downloads' page of the Yocto Project website. | ||
59 | |||
60 | Having done that, and assuming you extracted the BSP tarball contents | ||
61 | at the top-level of your yocto build tree, you can build an n450 | ||
62 | image by adding the location of the meta-n450 layer to | ||
63 | bblayers.conf, along with the meta-intel layer itself (to access | ||
64 | common metadata shared between BSPs) e.g.: | ||
65 | |||
66 | yocto/meta-intel \ | ||
67 | yocto/meta-intel/meta-n450 \ | ||
68 | |||
69 | Configure your build to build for the n450 machine in your local.conf file: | ||
70 | |||
71 | MACHINE ?= "n450" | ||
72 | |||
73 | You should then be able to build an n450 image as such: | ||
74 | |||
75 | $ bitbake core-image-sato | ||
76 | |||
77 | At the end of a successful build, you should have a live image that | ||
78 | you can boot from a USB flash drive (see instructions on how to do | ||
79 | that below, in the section 'Booting the images from /binary'). | ||
80 | |||
81 | As an alternative to downloading the BSP tarball, you can also work | ||
82 | directly from the meta-intel git repository. For each BSP in the | ||
83 | 'meta-intel' repository, there are multiple branches, one | ||
84 | corresponding to each major release starting with 'laverne' (0.90), in | ||
85 | addition to the latest code which tracks the current master (note that | ||
86 | not all BSPs are present in every release). Instead of extracting | ||
87 | a BSP tarball at the top level of your yocto build tree, you can | ||
88 | equivalently check out the appropriate branch from the meta-intel | ||
89 | repository at the same location. | ||
90 | |||
91 | |||
92 | II. Booting the images in /binary | ||
93 | ================================= | ||
94 | |||
95 | This BSP contains bootable live images, which can be used to directly | ||
96 | boot Yocto off of a USB flash drive. | ||
97 | |||
98 | Under Linux, insert a USB flash drive. Assuming the USB flash drive | ||
99 | takes device /dev/sdf, use dd to copy the live image to it. For | ||
100 | example: | ||
101 | |||
102 | # dd if=core-image-sato-n450-20101207053738.hddimg of=/dev/sdf | ||
103 | # sync | ||
104 | # eject /dev/sdf | ||
105 | |||
106 | This should give you a bootable USB flash device. Insert the device | ||
107 | into a bootable USB socket on the target, and power on. This should | ||
108 | result in a system booted to the Sato graphical desktop. | ||
109 | |||
110 | If you want a terminal, use the arrows at the top of the UI to move to | ||
111 | different pages of available applications, one of which is named | ||
112 | 'Terminal'. Clicking that should give you a root terminal. | ||
113 | |||
114 | If you want to ssh into the system, you can use the root terminal to | ||
115 | ifconfig the IP address and use that to ssh in. The root password is | ||
116 | empty, so to log in type 'root' for the user name and hit 'Enter' at | ||
117 | the Password prompt: and you should be in. | ||
118 | |||
119 | ---- | ||
120 | |||
121 | If you find you're getting corrupt images on the USB (it doesn't show | ||
122 | the syslinux boot: prompt, or the boot: prompt contains strange | ||
123 | characters), try doing this first: | ||
124 | |||
125 | # dd if=/dev/zero of=/dev/sdf bs=1M count=512 | ||