All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@intel.com>
To: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: [PATCH] meta-crownbay: update README
Date: Fri, 17 Dec 2010 17:23:46 -0600	[thread overview]
Message-ID: <1292628226.2104.506.camel@elmorro> (raw)

Update the crownbay README with information explaining the available
machine configurations.

Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
---
 meta-crownbay/README |   36 +++++++++++++++++++++++++++++++++---
 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 @@
 This README file contains information on building the meta-crownbay
-BSP layer, and booting the images contained in the /binary directory.
+BSP layer using any of the supported machine configurations, and
+booting the images contained in the /binary directory.
+
+The meta-crownbay layer contains support for 2 different machine
+configurations, identical except for the fact that one ('crownbay')
+makes use of the Intel-proprietary EMGD 1.5 graphics driver, and the
+other ('crownbay-noemgd') does not.
+
+The default 'crownbay' configuration requires an extra manual step
+before building in order for the build to complete.  Please see
+section II below for details.
+
+The 'crownbay-noemgd' configuration doesn't require any special setup,
+but since it uses generic vesa, the graphics aren't as nice and don't
+perform as well as the 'crownbay', which does make use of the EMGD
+graphics driver.
+
+If you're only interested in booting the images in the /binary
+directory of a BSP tarball you've downloaded, there's nothing special
+to do - the appropriate images (for either normal or -noemgd) are
+already in the /binary directory depending on which BSP tarball you
+downloaded.
+
 Please see the corresponding sections below for details.
 
 
@@ -7,7 +29,8 @@ Table of Contents
 =================
 
   I. Building the meta-crownbay BSP layer
- II. Special notes for building the meta-crownbay BSP layer
+ II. Special notes for building the meta-crownbay BSP layer (with EMGD
+     graphics)
 III. Booting the images in /binary
 
 
@@ -31,10 +54,16 @@ bblayers.conf e.g.:
 
   yocto/meta-intel/meta-crownbay \
 
-To enable the crownbay layer, add the crownbay MACHINE to local.conf:
+To enable the crownbay (with EMGD graphics) layer, add the crownbay
+MACHINE to local.conf:
 
   MACHINE ?= "crownbay"
 
+To enable the crownbay-noemgd layer, add the crownbay-noemgd MACHINE
+to local.conf:
+
+  MACHINE ?= "crownbay-noemgd"
+
 You should then be able to build a crownbay image as such:
 
   $ source poky-init-build-env
@@ -46,6 +75,7 @@ that below, in the section 'Booting the images from /binary').
 
 
 II. Special notes for building the meta-crownbay BSP layer
+    (with EMGD graphics)
 ==========================================================
 
 The meta-crownbay layer makes use of the proprietary Intel EMGD
-- 
1.7.0.4





                 reply	other threads:[~2010-12-17 23:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1292628226.2104.506.camel@elmorro \
    --to=tom.zanussi@intel.com \
    --cc=poky@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.