From 95fd3fd97769526f766fd1ec95c8235cb8e203d5 Mon Sep 17 00:00:00 2001 From: Tom Zanussi Date: Wed, 30 Mar 2011 17:34:44 -0500 Subject: meta-fishriver: new layer for Fish River Island (Z530/EG20T) systems This layer provides support for Z530 + EG20T Intel systems. Currently it supports only vesa graphics, which will be upgraded shortly. Signed-off-by: Tom Zanussi --- meta-fishriver/README | 94 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 94 insertions(+) create mode 100644 meta-fishriver/README (limited to 'meta-fishriver/README') diff --git a/meta-fishriver/README b/meta-fishriver/README new file mode 100644 index 00000000..57b49264 --- /dev/null +++ b/meta-fishriver/README @@ -0,0 +1,94 @@ +This README file contains information on building the meta-fishriver +BSP layer, and booting the images contained in the /binary directory. +Please see the corresponding sections below for details. + + +Table of Contents +================= + + I. Special notes on the meta-fishriver BSP layer + II. Building the meta-fishriver BSP layer +III. Booting the images in /binary + + +I. Special notes on the meta-fishriver BSP layer +================================================ + +The meta-fishriver layer currently and temporarily uses the crownbay +kernel branch. This will change once we have new patches and/or +config changes for: + +- Zigbee +- wifi +- upstream gma500 +- EMGD? + + +II. Building the meta-fishriver BSP layer +========================================= + +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. + +In order to build an image with BSP support for a given release, you +need to check out the 'meta-intel' branch corresponding to the release +you're building against e.g. to build for laverne (0.90), check out +the 'laverne' branch of both poky and 'meta-intel'. + +Having done that, and assuming you cloned the 'meta-intel' repository +at the top-level of your yocto build tree, you can build a fishriver +image by adding the location of the meta-fishriver layer to +bblayers.conf e.g.: + + yocto/meta-intel/meta-fishriver \ + +To enable the fishriver layer, add the fishriver MACHINE to local.conf: + + MACHINE ?= "fishriver" + +You should then be able to build a fishriver image as such: + + $ source poky-init-build-env + $ bitbake poky-image-sato-live + +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'). + + +III. 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=poky-image-sato-live-fishriver-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 -- cgit v1.2.3-54-g00ecf