diff options
| author | Tom Zanussi <tom.zanussi@intel.com> | 2011-04-25 15:52:00 -0500 |
|---|---|---|
| committer | Tom Zanussi <tom.zanussi@intel.com> | 2011-04-25 16:07:29 -0500 |
| commit | 36cf032e3a06856aca7f0c26ab35004f90da1d7b (patch) | |
| tree | 37b5ca30eb8d4b943ccb26698afdfa9d0effa58e /meta-crownbay/README | |
| parent | 6d373cd4d9adc8e72a3a9fee8736340c7243a963 (diff) | |
| download | meta-intel-36cf032e3a06856aca7f0c26ab35004f90da1d7b.tar.gz | |
meta-crownbay: update documentation with hw and build details
Add missing info on supported hardware, and update the details with
respect to building with/without emgd.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Diffstat (limited to 'meta-crownbay/README')
| -rw-r--r-- | meta-crownbay/README | 42 |
1 files changed, 31 insertions, 11 deletions
diff --git a/meta-crownbay/README b/meta-crownbay/README index 468608c8..11770246 100644 --- a/meta-crownbay/README +++ b/meta-crownbay/README | |||
| @@ -2,6 +2,11 @@ This README file contains information on building the meta-crownbay | |||
| 2 | BSP layer, and booting the images contained in the /binary directory. | 2 | BSP layer, and booting the images contained in the /binary directory. |
| 3 | Please see the corresponding sections below for details. | 3 | Please see the corresponding sections below for details. |
| 4 | 4 | ||
| 5 | The Crown Bay platform consists of the Intel Atom Z6xx processor, | ||
| 6 | plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff). | ||
| 7 | |||
| 8 | It also supports the E6xx embedded on-chip graphics via the Intel | ||
| 9 | Embedded Media and Graphics Driver (EMGD) 1.5 Gold Driver. | ||
| 5 | 10 | ||
| 6 | Table of Contents | 11 | Table of Contents |
| 7 | ================= | 12 | ================= |
| @@ -21,8 +26,8 @@ current master. | |||
| 21 | 26 | ||
| 22 | In order to build an image with BSP support for a given release, you | 27 | In order to build an image with BSP support for a given release, you |
| 23 | need to check out the 'meta-intel' branch corresponding to the release | 28 | need to check out the 'meta-intel' branch corresponding to the release |
| 24 | you're building against e.g. to build for laverne (0.90), check out | 29 | you're building against e.g. to build for bernard (1.0), check out |
| 25 | the 'laverne' branch of both poky and 'meta-intel'. | 30 | the 'bernard' branch of both poky and 'meta-intel'. |
| 26 | 31 | ||
| 27 | Having done that, and assuming you cloned the 'meta-intel' repository | 32 | Having done that, and assuming you cloned the 'meta-intel' repository |
| 28 | at the top-level of your yocto build tree, you can build a crownbay | 33 | at the top-level of your yocto build tree, you can build a crownbay |
| @@ -31,10 +36,22 @@ bblayers.conf e.g.: | |||
| 31 | 36 | ||
| 32 | yocto/meta-intel/meta-crownbay \ | 37 | yocto/meta-intel/meta-crownbay \ |
| 33 | 38 | ||
| 34 | To enable the crownbay layer, add the crownbay MACHINE to local.conf: | 39 | The meta-crownbay layer contains support for two different machine |
| 40 | configurations. These configurations are identical except for the fact | ||
| 41 | that the one prefixed with 'crownbay' makes use of the | ||
| 42 | Intel-proprietary EMGD 1.5 graphics driver, while the one prefixed | ||
| 43 | with 'crownbay-noemgd' does not. | ||
| 44 | |||
| 45 | If you want to enable the layer that supports EMGD graphics add | ||
| 46 | following to the local.conf file: | ||
| 35 | 47 | ||
| 36 | MACHINE ?= "crownbay" | 48 | MACHINE ?= "crownbay" |
| 37 | 49 | ||
| 50 | If you want to enable the layer that does not support EMGD graphics | ||
| 51 | add the following to the local.conf file: | ||
| 52 | |||
| 53 | MACHINE ?= "crownbay-noemgd" | ||
| 54 | |||
| 38 | You should then be able to build a crownbay image as such: | 55 | You should then be able to build a crownbay image as such: |
| 39 | 56 | ||
| 40 | $ source poky-init-build-env | 57 | $ source poky-init-build-env |
| @@ -49,14 +66,17 @@ II. Special notes for building the meta-crownbay BSP layer | |||
| 49 | ========================================================== | 66 | ========================================================== |
| 50 | 67 | ||
| 51 | The meta-crownbay layer makes use of the proprietary Intel EMGD | 68 | The meta-crownbay layer makes use of the proprietary Intel EMGD |
| 52 | userspace drivers, which at this point in time require that the user | 69 | userspace drivers when building the "crownbay" machine (but not when |
| 53 | accept the Intel license by manually extracting the binaries and | 70 | building the "crownbay-noemgd" machine). If you got the BSP from the |
| 54 | copying them to the proper location in the meta-crownbay layer. | 71 | 'BSP Downloads' section of the Yocto website, the EMGD binaries needed |
| 55 | 72 | to perform the build will already be present in the BSP, located in | |
| 56 | There currently isn't an automated way to do this, thus the manual | 73 | the recipes-graphics/xorg-xserver/xserver-xf86-emgd-bin directory, and |
| 57 | step. When Yocto supports a click-through installation mechanism, the | 74 | you can ignore the rest of this section. |
| 58 | binary files will be packaged as part of the recipe, and this step | 75 | |
| 59 | will be unnecessary. | 76 | If you didn't get the BSP from the 'BSP Downloads' section of the |
| 77 | Yocto website, you'll need to download the a Windows executable from | ||
| 78 | the official EMGD website, extract the binaries from it, and copy them | ||
| 79 | to the proper location in the meta-crownbay layer. | ||
| 60 | 80 | ||
| 61 | These steps require that you run a graphical application in Windows. | 81 | These steps require that you run a graphical application in Windows. |
| 62 | Windows 7 was used for these instructions, but it shouldn't matter | 82 | Windows 7 was used for these instructions, but it shouldn't matter |
