diff options
| author | Saul Wold <sgw@linux.intel.com> | 2015-08-25 16:39:01 -0700 |
|---|---|---|
| committer | Saul Wold <sgw@linux.intel.com> | 2015-08-28 14:25:29 -0700 |
| commit | 4172351baa285b83eb54d54368fe2f037c48159b (patch) | |
| tree | c2c1991e05b0260615b83abf59acee81a534ec10 /meta-emenlow/README | |
| parent | 44df7ddf395f82c28c494b92fb3f627f81e2e627 (diff) | |
| download | meta-intel-4172351baa285b83eb54d54368fe2f037c48159b.tar.gz | |
Remove older platform specific BSPs
The intel-core* BSPs supercede these older BSPs therefore it's time
to remove these older platform specific bsps.
Bump LAYERVERSION to 3 to allow the Autobuilder to know that these
BSPs have been removed.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Diffstat (limited to 'meta-emenlow/README')
| -rw-r--r-- | meta-emenlow/README | 148 |
1 files changed, 0 insertions, 148 deletions
diff --git a/meta-emenlow/README b/meta-emenlow/README deleted file mode 100644 index eccc9f33..00000000 --- a/meta-emenlow/README +++ /dev/null | |||
| @@ -1,148 +0,0 @@ | |||
| 1 | This README file contains information on building the meta-emenlow | ||
| 2 | BSP layer using any of the supported machine configurations, and | ||
| 3 | booting the images contained in the /binary directory. | ||
| 4 | |||
| 5 | The 'eMenlow' platform consists of the Intel Atom Z5xx processor, | ||
| 6 | plus the Intel US15W System Controller Hub. | ||
| 7 | |||
| 8 | Further information on the platform supported by this BSP can be | ||
| 9 | found here: | ||
| 10 | |||
| 11 | http://www.portwell.com/products/detail.asp?CUSTCHAR1=WEBS-2120 | ||
| 12 | |||
| 13 | Information on all IntelĀ® embedded platforms can be found here: | ||
| 14 | |||
| 15 | http://www.intel.com/p/en_US/embedded/hwsw/hardware | ||
| 16 | |||
| 17 | If you're only interested in booting the images in the /binary | ||
| 18 | directory of a BSP tarball you've downloaded, there's nothing special | ||
| 19 | to do - the appropriate images are already in the /binary directory | ||
| 20 | depending on which BSP tarball you downloaded. | ||
| 21 | |||
| 22 | Please see the corresponding sections below for details. | ||
| 23 | |||
| 24 | |||
| 25 | Yocto Project Compatible | ||
| 26 | ======================== | ||
| 27 | |||
| 28 | This BSP is compatible with the Yocto Project as per the requirements | ||
| 29 | listed here: | ||
| 30 | |||
| 31 | https://www.yoctoproject.org/webform/yocto-project-compatible-registration | ||
| 32 | |||
| 33 | |||
| 34 | Dependencies | ||
| 35 | ============ | ||
| 36 | |||
| 37 | This layer depends on: | ||
| 38 | |||
| 39 | URI: git://git.openembedded.org/bitbake | ||
| 40 | branch: master | ||
| 41 | |||
| 42 | URI: git://git.openembedded.org/openembedded-core | ||
| 43 | layers: meta | ||
| 44 | branch: master | ||
| 45 | |||
| 46 | URI: git://git.yoctoproject.org/meta-intel | ||
| 47 | layers: intel | ||
| 48 | branch: master | ||
| 49 | |||
| 50 | |||
| 51 | Patches | ||
| 52 | ======= | ||
| 53 | |||
| 54 | Please submit any patches against this BSP to the meta-intel mailing list | ||
| 55 | (meta-intel@yoctoproject.org) and cc: the maintainer: | ||
| 56 | |||
| 57 | Maintainer: Saul Wold <sgw@linux.intel.com> | ||
| 58 | |||
| 59 | Please see the meta-intel/MAINTAINERS file for more details. | ||
| 60 | |||
| 61 | |||
| 62 | Table of Contents | ||
| 63 | ================= | ||
| 64 | |||
| 65 | I. Building the meta-emenlow BSP layer | ||
| 66 | II. Booting the images in /binary | ||
| 67 | |||
| 68 | |||
| 69 | I. Building the meta-emenlow BSP layer | ||
| 70 | ======================================= | ||
| 71 | |||
| 72 | In order to build an image with BSP support for a given release, you | ||
| 73 | need to download the corresponding BSP tarball from the 'Board Support | ||
| 74 | Package (BSP) Downloads' page of the Yocto Project website. | ||
| 75 | |||
| 76 | Having done that, and assuming you extracted the BSP tarball contents | ||
| 77 | at the top-level of your yocto build tree, you can build an emenlow | ||
| 78 | image by adding the location of the meta-emenlow layer to | ||
| 79 | bblayers.conf, along with the meta-intel layer itself (to access | ||
| 80 | common metadata shared between BSPs) e.g.: | ||
| 81 | |||
| 82 | yocto/meta-intel \ | ||
| 83 | yocto/meta-intel/meta-emenlow \ | ||
| 84 | |||
| 85 | The meta-emenlow layer contains support for emenlow-noemgd machine | ||
| 86 | configuration. The previously supported emenlow machine with the | ||
| 87 | proprietary EMGD graphics driver has been retired. The 'emenlow-noemgd' | ||
| 88 | machine configuration uses the open source 'gma500' kernel DRM driver | ||
| 89 | along with the 'modesetting' X driver. | ||
| 90 | |||
| 91 | To enable the layer add the following to the local.conf file: | ||
| 92 | |||
| 93 | MACHINE ?= "emenlow-noemgd" | ||
| 94 | |||
| 95 | You should then be able to build an emenlow image as such: | ||
| 96 | |||
| 97 | $ source oe-init-build-env | ||
| 98 | $ bitbake core-image-sato | ||
| 99 | |||
| 100 | At the end of a successful build, you should have a live image that | ||
| 101 | you can boot from a USB flash drive (see instructions on how to do | ||
| 102 | that below, in the section 'Booting the images from /binary'). | ||
| 103 | |||
| 104 | As an alternative to downloading the BSP tarball, you can also work | ||
| 105 | directly from the meta-intel git repository. For each BSP in the | ||
| 106 | 'meta-intel' repository, there are multiple branches, one | ||
| 107 | corresponding to each major release starting with 'laverne' (0.90), in | ||
| 108 | addition to the latest code which tracks the current master (note that | ||
| 109 | not all BSPs are present in every release). Instead of extracting a | ||
| 110 | BSP tarball at the top level of your yocto build tree, you can | ||
| 111 | equivalently check out the appropriate branch from the meta-intel | ||
| 112 | repository at the same location. | ||
| 113 | |||
| 114 | |||
| 115 | II. Booting the images in /binary | ||
| 116 | ================================= | ||
| 117 | |||
| 118 | This BSP contains bootable live images, which can be used to directly | ||
| 119 | boot Yocto off of a USB flash drive. | ||
| 120 | |||
| 121 | Under Linux, insert a USB flash drive. Assuming the USB flash drive | ||
| 122 | takes device /dev/sdf, use dd to copy the live image to it. For | ||
| 123 | example: | ||
| 124 | |||
| 125 | # dd if=core-image-sato-emenlow-noemgd.hddimg of=/dev/sdf | ||
| 126 | # sync | ||
| 127 | # eject /dev/sdf | ||
| 128 | |||
| 129 | This should give you a bootable USB flash device. Insert the device | ||
| 130 | into a bootable USB socket on the target, and power on. This should | ||
| 131 | result in a system booted to the Sato graphical desktop. | ||
| 132 | |||
| 133 | If you want a terminal, use the arrows at the top of the UI to move to | ||
| 134 | different pages of available applications, one of which is named | ||
| 135 | 'Terminal'. Clicking that should give you a root terminal. | ||
| 136 | |||
| 137 | If you want to ssh into the system, you can use the root terminal to | ||
| 138 | ifconfig the IP address and use that to ssh in. The root password is | ||
| 139 | empty, so to log in type 'root' for the user name and hit 'Enter' at | ||
| 140 | the Password prompt: and you should be in. | ||
| 141 | |||
| 142 | ---- | ||
| 143 | |||
| 144 | If you find you're getting corrupt images on the USB (it doesn't show | ||
| 145 | the syslinux boot: prompt, or the boot: prompt contains strange | ||
| 146 | characters), try doing this first: | ||
| 147 | |||
| 148 | # dd if=/dev/zero of=/dev/sdf bs=1M count=512 | ||
