summaryrefslogtreecommitdiffstats
path: root/meta-n450/README
diff options
context:
space:
mode:
authorNitin A Kamble <nitin.a.kamble@intel.com>2014-03-12 12:12:32 -0700
committerTom Zanussi <tom.zanussi@intel.com>2014-03-26 22:41:49 -0500
commit8d79fb4e0cec07fe05ca440578414eaa6be80a3a (patch)
tree067a7cc91fcd612e9d9797900378970f010f838f /meta-n450/README
parenta1491bc54b60a1c622a9060756fd9b145bc01378 (diff)
downloadmeta-intel-8d79fb4e0cec07fe05ca440578414eaa6be80a3a.tar.gz
Remove chiefriver, sys940x & n450 BSPs
Configuration for the chiefriver, sys940x, sys940x-noemgd, n450 BSPs are deleted. The consolidated BSPs viz intel-corei7-64 and intel-core2-32 support these boards. As part of the usual retirement process, a heads-up email was sent to the meta-intel mailing list requesting any feedback regarding retirement of these BSPs. The community did not had any concerning feedback to reconsider the retirement decision. The MAINTAINERS file and the layer version of the meta-intel layer are updated to reflect removal of the BSPs. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> CC: Darren Hart <dvhart@linux.intel.com> Reviewed-by: Darren Hart <dvhart@linux.intel.com>
Diffstat (limited to 'meta-n450/README')
-rw-r--r--meta-n450/README134
1 files changed, 0 insertions, 134 deletions
diff --git a/meta-n450/README b/meta-n450/README
deleted file mode 100644
index 2f652dbb..00000000
--- a/meta-n450/README
+++ /dev/null
@@ -1,134 +0,0 @@
1This README file contains information on building the meta-n450
2BSP layer, and booting the images contained in the /binary directory.
3Please see the corresponding sections below for details.
4
5The Luna Pier platform consists of the Intel Atom E4xx processor (Pineview),
6plus the Intel 82801Hm I/O Controller.
7
8Further information on the platforms supported by this BSP can be
9found here:
10
11 http://www.intel.com/p/en_US/embedded/hwsw/hardware/atom-400-500/overview
12
13Information on all IntelĀ® embedded platforms can be found here:
14
15 http://www.intel.com/p/en_US/embedded/hwsw/hardware
16
17
18Yocto Project Compatible
19========================
20
21This BSP is compatible with the Yocto Project as per the requirements
22listed here:
23
24 https://www.yoctoproject.org/webform/yocto-project-compatible-registration
25
26
27Dependencies
28============
29
30This layer depends on:
31
32 URI: git://git.openembedded.org/bitbake
33 branch: master
34
35 URI: git://git.openembedded.org/openembedded-core
36 layers: meta
37 branch: master
38
39 URI: git://git.yoctoproject.org/meta-intel
40 layers: intel
41 branch: master
42
43
44Patches
45=======
46
47Please submit any patches against this BSP to the Yocto mailing list
48(yocto@yoctoproject.org) and cc: the maintainer:
49
50Maintainer: Darren Hart <dvhart@linux.intel.com>
51
52Please see the meta-intel/MAINTAINERS file for more details.
53
54
55Table of Contents
56=================
57
58 I. Building the meta-n450 BSP layer
59 II. Booting the images in /binary
60
61
62I. Building the meta-n450 BSP layer
63=======================================
64
65In order to build an image with BSP support for a given release, you
66need to download the corresponding BSP tarball from the 'Board Support
67Package (BSP) Downloads' page of the Yocto Project website.
68
69Having done that, and assuming you extracted the BSP tarball contents
70at the top-level of your yocto build tree, you can build an n450
71image by adding the location of the meta-n450 layer to
72bblayers.conf, along with the meta-intel layer itself (to access
73common metadata shared between BSPs) e.g.:
74
75 yocto/meta-intel \
76 yocto/meta-intel/meta-n450 \
77
78Configure your build to build for the n450 machine in your local.conf file:
79
80 MACHINE ?= "n450"
81
82You should then be able to build an n450 image as such:
83
84 $ bitbake core-image-sato
85
86At the end of a successful build, you should have a live image that
87you can boot from a USB flash drive (see instructions on how to do
88that below, in the section 'Booting the images from /binary').
89
90As an alternative to downloading the BSP tarball, you can also work
91directly from the meta-intel git repository. For each BSP in the
92'meta-intel' repository, there are multiple branches, one
93corresponding to each major release starting with 'laverne' (0.90), in
94addition to the latest code which tracks the current master (note that
95not all BSPs are present in every release). Instead of extracting
96a BSP tarball at the top level of your yocto build tree, you can
97equivalently check out the appropriate branch from the meta-intel
98repository at the same location.
99
100
101II. Booting the images in /binary
102=================================
103
104This BSP contains bootable live images, which can be used to directly
105boot Yocto off of a USB flash drive.
106
107Under Linux, insert a USB flash drive. Assuming the USB flash drive
108takes device /dev/sdf, use dd to copy the live image to it. For
109example:
110
111# dd if=core-image-sato-n450.hddimg of=/dev/sdf
112# sync
113# eject /dev/sdf
114
115This should give you a bootable USB flash device. Insert the device
116into a bootable USB socket on the target, and power on. This should
117result in a system booted to the Sato graphical desktop.
118
119If you want a terminal, use the arrows at the top of the UI to move to
120different pages of available applications, one of which is named
121'Terminal'. Clicking that should give you a root terminal.
122
123If you want to ssh into the system, you can use the root terminal to
124ifconfig the IP address and use that to ssh in. The root password is
125empty, so to log in type 'root' for the user name and hit 'Enter' at
126the Password prompt: and you should be in.
127
128----
129
130If you find you're getting corrupt images on the USB (it doesn't show
131the syslinux boot: prompt, or the boot: prompt contains strange
132characters), try doing this first:
133
134# dd if=/dev/zero of=/dev/sdf bs=1M count=512