diff options
Diffstat (limited to 'meta-isg/meta-haswell-wc/README')
| -rw-r--r-- | meta-isg/meta-haswell-wc/README | 172 |
1 files changed, 0 insertions, 172 deletions
diff --git a/meta-isg/meta-haswell-wc/README b/meta-isg/meta-haswell-wc/README deleted file mode 100644 index 3e344467..00000000 --- a/meta-isg/meta-haswell-wc/README +++ /dev/null @@ -1,172 +0,0 @@ -This README file contains information on building the meta-haswell-wc -BSP layer, and booting the images contained in the /binary directory. -Please see the corresponding sections below for details. - -The BSP is made specifically for 4th Gen Intel Core Processor (Haswell) -Development Kit with Mobile Intel QM87 & HM86 Chipset (formerly known as -Shark Bay). This BSP assumes that integrated graphics are being used. -The "haswell-wc" BSP is meant to support "Walnut Canyon" Shark Bay -development kit. - -Further information about the Haswell Platforms supported by this BSP can be -found here: - - http://www.intel.com/content/www/us/en/intelligent-systems/shark-bay/4th-generation-core-qm87-hm86-chipsets.html - -Information on all Intel® embedded platforms can be found here: - - http://www.intel.com/p/en_US/embedded/hwsw/hardware - - -Compliance -========== - -This BSP is compliant with the Yocto Project as per the requirements -listed here: - - https://www.yoctoproject.org/webform/yocto-project-compatible-registration - - -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 -(meta-intel@yoctoproject.org) and cc: the maintainer: - -Maintainer: Ong Boon Leong <boon.leong.ong@intel.com> - -Please see the meta-intel/MAINTAINERS file for more details. - - -Table of Contents -================= - - I. Building the meta-haswell-wc BSP layer - II. Booting the images in /binary -III. Device Notes - a. Boot Loader - b. I/O drivers - - -I. Building the meta-haswell-wc 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 haswell-wc -image by adding the location of the meta-haswell-wc 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-isg/meta-haswell-wc \ - -To enable the haswell-wc layer, add the haswell-wc MACHINE to local.conf: - - MACHINE ?= "haswell-wc" - -You should then be able to build a haswell-wc 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'). - -NOTE: The 'haswell-wc' machine will include support for hardware video -acceleration via gstreamer if and only if the "commercial" string is -added to the the LICENSE_FLAGS_WHITELIST variable in your local.conf. - -For example: - - LICENSE_FLAGS_WHITELIST = "commercial" - -The reason this is needed is to prevent the image from including -anything that might violate the license terms of the packages used to -implement the the video acceleration feature, such as gst-ffmpeg and -ffmpeg. As always, please consult the licenses included in the -specific packages for details if you use packages that require -particular LICENSE_FLAGS. - -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-haswell-wc.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 - - -III. Device Notes -================= - -a. Boot Loader --------------- -BIOS: HSWLPTU1.86C.0131.R05.1308140140 - -b. I/O drivers --------------- -Support integrated graphics driver (i965) - -Support SATA, USB Host v2.0 - -Supported I/O devices (APIC, RTC, SPI, UART, I2C, LPS, SMBus i801, -WDT, and HPET) |