summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTom Zanussi <tom.zanussi@intel.com>2010-12-17 23:14:24 (GMT)
committerSaul Wold <sgw@linux.intel.com>2011-01-03 23:37:29 (GMT)
commitb47ea34b2ebeaf61ea796f079a1a70e2e5057c04 (patch)
treead6764183c545675e649947b102f4360250a2060
parent9c3b6e9251844aac4415df67bdbf6031d5a6df3a (diff)
downloadmeta-intel-b47ea34b2ebeaf61ea796f079a1a70e2e5057c04.tar.gz
meta-crownbay: update README
Update the crownbay README with information explaining the available machine configurations. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
-rw-r--r--meta-crownbay/README36
1 files changed, 33 insertions, 3 deletions
diff --git a/meta-crownbay/README b/meta-crownbay/README
index f0a710b..be842d6 100644
--- a/meta-crownbay/README
+++ b/meta-crownbay/README
@@ -1,5 +1,27 @@
1This README file contains information on building the meta-crownbay 1This README file contains information on building the meta-crownbay
2BSP layer, and booting the images contained in the /binary directory. 2BSP layer using any of the supported machine configurations, and
3booting the images contained in the /binary directory.
4
5The meta-crownbay layer contains support for 2 different machine
6configurations, identical except for the fact that one ('crownbay')
7makes use of the Intel-proprietary EMGD 1.5 graphics driver, and the
8other ('crownbay-noemgd') does not.
9
10The default 'crownbay' configuration requires an extra manual step
11before building in order for the build to complete. Please see
12section II below for details.
13
14The 'crownbay-noemgd' configuration doesn't require any special setup,
15but since it uses generic vesa, the graphics aren't as nice and don't
16perform as well as the 'crownbay', which does make use of the EMGD
17graphics driver.
18
19If you're only interested in booting the images in the /binary
20directory of a BSP tarball you've downloaded, there's nothing special
21to do - the appropriate images (for either normal or -noemgd) are
22already in the /binary directory depending on which BSP tarball you
23downloaded.
24
3Please see the corresponding sections below for details. 25Please see the corresponding sections below for details.
4 26
5 27
@@ -7,7 +29,8 @@ Table of Contents
7================= 29=================
8 30
9 I. Building the meta-crownbay BSP layer 31 I. Building the meta-crownbay BSP layer
10 II. Special notes for building the meta-crownbay BSP layer 32 II. Special notes for building the meta-crownbay BSP layer (with EMGD
33 graphics)
11III. Booting the images in /binary 34III. Booting the images in /binary
12 35
13 36
@@ -31,10 +54,16 @@ bblayers.conf e.g.:
31 54
32 yocto/meta-intel/meta-crownbay \ 55 yocto/meta-intel/meta-crownbay \
33 56
34To enable the crownbay layer, add the crownbay MACHINE to local.conf: 57To enable the crownbay (with EMGD graphics) layer, add the crownbay
58MACHINE to local.conf:
35 59
36 MACHINE ?= "crownbay" 60 MACHINE ?= "crownbay"
37 61
62To enable the crownbay-noemgd layer, add the crownbay-noemgd MACHINE
63to local.conf:
64
65 MACHINE ?= "crownbay-noemgd"
66
38You should then be able to build a crownbay image as such: 67You should then be able to build a crownbay image as such:
39 68
40 $ source poky-init-build-env 69 $ source poky-init-build-env
@@ -46,6 +75,7 @@ that below, in the section 'Booting the images from /binary').
46 75
47 76
48II. Special notes for building the meta-crownbay BSP layer 77II. Special notes for building the meta-crownbay BSP layer
78 (with EMGD graphics)
49========================================================== 79==========================================================
50 80
51The meta-crownbay layer makes use of the proprietary Intel EMGD 81The meta-crownbay layer makes use of the proprietary Intel EMGD