mirror of
git://git.yoctoproject.org/meta-intel
synced 2026-01-01 13:58:05 +00:00
83a4aa1a44
1.14 is the latest released driver for emgd. This change is tested on crownbay machine. Add runtime dependency to libxcb-dri2 Otherwise the libxcb-dri2.so is not getting installed, and video acceleration of emgd does not work. It is dynamic dependency of emgd_drv_video.so put files in gstreamer-0.10/.debug directory to the debug package. It avoids debug files packaging warnings. add downloadfilename param to SRC_URI As the url does not have the filename of the tarball, specify it here so that updated wget bitbake fetcher can save the downloaded file accordingly. BTW now EDC has also published another download URL on our request: http://edc.intel.com/App_Shared/Downloads/LIN_IEMGD_1_14_GOLD_2443.tgz And update emgd driver version in the README. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Tested-by: Tom Zanussi <tom.zanussi@intel.com>
140 lines
4.7 KiB
Plaintext
140 lines
4.7 KiB
Plaintext
This README file contains information on building the meta-crownbay
|
|
BSP layer, and booting the images contained in the /binary directory.
|
|
Please see the corresponding sections below for details.
|
|
|
|
The Crown Bay platform consists of the Intel Atom Z6xx processor,
|
|
plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff).
|
|
|
|
It also supports the E6xx embedded on-chip graphics via the Intel
|
|
Embedded Media and Graphics Driver (EMGD) 1.14 Driver.
|
|
|
|
|
|
Dependencies
|
|
============
|
|
|
|
This layer depends on:
|
|
|
|
URI: git://git.openembedded.org/bitbake
|
|
branch: master
|
|
|
|
URI: git://git.openembedded.org/openembedded-core
|
|
layers: meta
|
|
branch: master
|
|
|
|
URI: git://git.yoctoproject.org/meta-intel
|
|
layers: intel
|
|
branch: master
|
|
|
|
|
|
Patches
|
|
=======
|
|
|
|
Please submit any patches against this BSP to the Yocto mailing list
|
|
(yocto@yoctoproject.org) and cc: the maintainer:
|
|
|
|
Maintainer: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
Please see the meta-intel/MAINTAINERS file for more details.
|
|
|
|
|
|
Table of Contents
|
|
=================
|
|
|
|
I. Building the meta-crownbay BSP layer
|
|
II. Booting the images in /binary
|
|
|
|
|
|
I. Building the meta-crownbay BSP layer
|
|
=======================================
|
|
|
|
In order to build an image with BSP support for a given release, you
|
|
need to download the corresponding BSP tarball from the 'Board Support
|
|
Package (BSP) Downloads' page of the Yocto Project website.
|
|
|
|
Having done that, and assuming you extracted the BSP tarball contents
|
|
at the top-level of your yocto build tree, you can build a crownbay
|
|
image by adding the location of the meta-crownbay layer to
|
|
bblayers.conf, along with the meta-intel layer itself (to access
|
|
common metadata shared between BSPs) e.g.:
|
|
|
|
yocto/meta-intel \
|
|
yocto/meta-intel/meta-crownbay \
|
|
|
|
The meta-crownbay layer contains support for two different machine
|
|
configurations. These configurations are identical except for the fact
|
|
that the one prefixed with 'crownbay' makes use of the
|
|
Intel-proprietary EMGD 1.14 graphics driver, while the one prefixed
|
|
with 'crownbay-noemgd' does not.
|
|
|
|
If you want to enable the layer that supports EMGD graphics add the
|
|
following to the local.conf file:
|
|
|
|
MACHINE ?= "crownbay"
|
|
|
|
The 'crownbay' machine includes the emgd-driver-bin package, which has
|
|
a proprietary license that must be whitelisted by adding the string
|
|
"license_emgd-driver-bin_1.14" to the LICENSE_FLAGS_WHITELIST variable
|
|
in your local.conf. For example:
|
|
|
|
LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.14"
|
|
|
|
If you want to enable the layer that does not support EMGD graphics
|
|
add the following to the local.conf file:
|
|
|
|
MACHINE ?= "crownbay-noemgd"
|
|
|
|
You should then be able to build a crownbay image as such:
|
|
|
|
$ source oe-init-build-env
|
|
$ bitbake core-image-sato
|
|
|
|
At the end of a successful build, you should have a live image that
|
|
you can boot from a USB flash drive (see instructions on how to do
|
|
that below, in the section 'Booting the images from /binary').
|
|
|
|
As an alternative to downloading the BSP tarball, you can also work
|
|
directly from the meta-intel git repository. For each BSP in the
|
|
'meta-intel' repository, there are multiple branches, one
|
|
corresponding to each major release starting with 'laverne' (0.90), in
|
|
addition to the latest code which tracks the current master (note that
|
|
not all BSPs are present in every release). Instead of extracting
|
|
a BSP tarball at the top level of your yocto build tree, you can
|
|
equivalently check out the appropriate branch from the meta-intel
|
|
repository at the same location.
|
|
|
|
|
|
II. Booting the images in /binary
|
|
=================================
|
|
|
|
This BSP contains bootable live images, which can be used to directly
|
|
boot Yocto off of a USB flash drive.
|
|
|
|
Under Linux, insert a USB flash drive. Assuming the USB flash drive
|
|
takes device /dev/sdf, use dd to copy the live image to it. For
|
|
example:
|
|
|
|
# dd if=core-image-sato-crownbay-20101207053738.hddimg of=/dev/sdf
|
|
# sync
|
|
# eject /dev/sdf
|
|
|
|
This should give you a bootable USB flash device. Insert the device
|
|
into a bootable USB socket on the target, and power on. This should
|
|
result in a system booted to the Sato graphical desktop.
|
|
|
|
If you want a terminal, use the arrows at the top of the UI to move to
|
|
different pages of available applications, one of which is named
|
|
'Terminal'. Clicking that should give you a root terminal.
|
|
|
|
If you want to ssh into the system, you can use the root terminal to
|
|
ifconfig the IP address and use that to ssh in. The root password is
|
|
empty, so to log in type 'root' for the user name and hit 'Enter' at
|
|
the Password prompt: and you should be in.
|
|
|
|
----
|
|
|
|
If you find you're getting corrupt images on the USB (it doesn't show
|
|
the syslinux boot: prompt, or the boot: prompt contains strange
|
|
characters), try doing this first:
|
|
|
|
# dd if=/dev/zero of=/dev/sdf bs=1M count=512
|