summaryrefslogtreecommitdiffstats
path: root/meta-nuc/README
diff options
context:
space:
mode:
Diffstat (limited to 'meta-nuc/README')
-rw-r--r--meta-nuc/README156
1 files changed, 0 insertions, 156 deletions
diff --git a/meta-nuc/README b/meta-nuc/README
deleted file mode 100644
index 7753755e..00000000
--- a/meta-nuc/README
+++ /dev/null
@@ -1,156 +0,0 @@
1This README file contains information on building the meta-nuc
2BSP layer, and booting the images contained in the /binary directory.
3Please see the corresponding sections below for details.
4
5This BSP is made specifically for "Next Unit of Computing Kit DC3217IYE"
6with Intel Centrino Advanced-N 6235 Wireless mini PCI Express card.
7
8Further information on this NUC platform can be found here:
9
10 http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-boards-d33217gke-dc3217iye.html
11
12Information on all IntelĀ® embedded platforms can be found here:
13
14 http://www.intel.com/p/en_US/embedded/hwsw/hardware
15
16
17Yocto Project Compatible
18========================
19
20This BSP is compatible with the Yocto Project as per the requirements
21listed here:
22
23 https://www.yoctoproject.org/webform/yocto-project-compatible-registration
24
25
26Dependencies
27============
28
29This layer depends on:
30
31 URI: git://git.openembedded.org/bitbake
32 branch: master
33
34 URI: git://git.openembedded.org/openembedded-core
35 layers: meta
36 branch: master
37
38 URI: git://git.yoctoproject.org/meta-intel
39 layers: intel
40 branch: master
41
42
43Patches
44=======
45
46Please submit any patches against this BSP to the meta-intel mailing list
47(meta-intel@yoctoproject.org) and cc: the maintainer:
48
49Maintainer: Saul Wold <sgw@linux.intel.com>
50
51Please see the meta-intel/MAINTAINERS file for more details.
52
53
54Table of Contents
55=================
56
57 I. Building the meta-nuc BSP layer
58 II. Booting the images in /binary
59
60
61I. Building the meta-nuc BSP layer
62=========================================
63
64In order to build an image with BSP support for a given release, you
65need to download the corresponding BSP tarball from the 'Board Support
66Package (BSP) Downloads' page of the Yocto Project website.
67
68Having done that, and assuming you extracted the BSP tarball contents
69at the top-level of your yocto build tree, you can build a nuc
70image by adding the location of the meta-nuc layer to
71bblayers.conf, along with the meta-intel layer itself (to access
72common metadata shared between BSPs) e.g.:
73
74 yocto/meta-intel \
75 yocto/meta-intel/meta-nuc \
76
77To enable the nuc layer, add the nuc MACHINE to local.conf:
78
79 MACHINE ?= "nuc"
80
81You should then be able to build a nuc image as such:
82
83 $ source oe-init-build-env
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
90NOTE: The 'nuc' machine will include support for hardware video
91acceleration via gstreamer if and only if the "commercial" string is
92added to the the LICENSE_FLAGS_WHITELIST variable in your local.conf.
93
94For example:
95
96 LICENSE_FLAGS_WHITELIST = "commercial"
97
98The reason this is needed is to prevent the image from including
99anything that might violate the license terms of the packages used to
100implement the the video acceleration feature, such as gst-ffmpeg and
101ffmpeg. As always, please consult the licenses included in the
102specific packages for details if you use packages that require
103particular LICENSE_FLAGS.
104
105The xf86-video-intel recipe depends on Xorg's dri and glx modules,
106which are built only when 'opengl' is listed in DISTRO_FEATURES. So
107if the distro doesn't list 'opengl' in the DISTRO_FEATURES, then you
108would need this additional line in your local.conf:
109
110 DISTRO_FEATURES_append = " opengl"
111
112As an alternative to downloading the BSP tarball, you can also work
113directly from the meta-intel git repository. For each BSP in the
114'meta-intel' repository, there are multiple branches, one
115corresponding to each major release starting with 'laverne' (0.90), in
116addition to the latest code which tracks the current master (note that
117not all BSPs are present in every release). Instead of extracting a
118BSP tarball at the top level of your yocto build tree, you can
119equivalently check out the appropriate branch from the meta-intel
120repository at the same location.
121
122
123II. Booting the images in /binary
124=================================
125
126This BSP contains bootable live images, which can be used to directly
127boot Yocto off of a USB flash drive.
128
129Under Linux, insert a USB flash drive. Assuming the USB flash drive
130takes device /dev/sdf, use dd to copy the live image to it. For
131example:
132
133# dd if=core-image-sato-nuc.hddimg of=/dev/sdf
134# sync
135# eject /dev/sdf
136
137This should give you a bootable USB flash device. Insert the device
138into a bootable USB socket on the target, and power on. This should
139result in a system booted to the Sato graphical desktop.
140
141If you want a terminal, use the arrows at the top of the UI to move to
142different pages of available applications, one of which is named
143'Terminal'. Clicking that should give you a root terminal.
144
145If you want to ssh into the system, you can use the root terminal to
146ifconfig the IP address and use that to ssh in. The root password is
147empty, so to log in type 'root' for the user name and hit 'Enter' at
148the Password prompt: and you should be in.
149
150----
151
152If you find you're getting corrupt images on the USB (it doesn't show
153the syslinux boot: prompt, or the boot: prompt contains strange
154characters), try doing this first:
155
156# dd if=/dev/zero of=/dev/sdf bs=1M count=512