fri2, sys940x, n450 WEBTITLE and README updates
cover fri2, sys940x, n450 WEBTITLE and README updates
Add the WEBTITLE tag to the machine configs and update the READMEs with compliance information. Add a boilerplate README for the n450.
PATCH 1/3 fri2: Add WEBTITLE and compliance information
The WEBTITLE will be used to publish the BSP on the Yocto Project website. Adding the Yocto Project compliance information for the 1.3 release.
Update the DESCRIPTION in the machine config and the platform description in the README to be consistent.
--- meta-fri2/README | 19 ++++++++++++++----- meta-fri2/conf/machine/fri2-noemgd.conf | 5 +++-- meta-fri2/conf/machine/fri2.conf | 3 ++- 3 files changed, 19 insertions(+), 8 deletions(-)
meta-fri2/README +14 -5
@@ -7,13 +7,22 @@ Developer Kit, as described here: http://us.kontron.com/products/systems+and+platforms/m2m/m2m+smart+services+developer+kit.html -The platform consists of the Intel Atom E640T processor plus the Intel -EG20T Platform Controller Hub (Tunnel Creek + Topcliff), along with a -variety of communications options and other machine-to-machine (m2m) -capabilities. +The 'Queens Bay' platform consists of the Intel Atom E640T processor plus the +Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff). The Fish River +Island II includes a variety of communications options and other +machine-to-machine (m2m) capabilities. It also supports the E6xx embedded on-chip graphics via the Intel -Embedded Media and Graphics Driver (EMGD) 1.10 Driver. +Embedded Media and Graphics Driver (EMGD). + + +Compliance +========== + +This BSP is compliant with the Yocto Project as per the requirements +listed here: + + http://www.yoctoproject.org/yocto-project-compatible-registration Dependencies
meta-fri2/conf/machine/fri2-noemgd.conf +3 -2
@@ -1,8 +1,9 @@ #@TYPE: Machine #@NAME: fri2 -#@DESCRIPTION: Machine configuration for Fish River Island II systems -# i.e. E660 + EG20T +#@WEBTITLE: Intel Atom E640T Processor with Intel EG20T Controller Hub Development Kit (Queens Bay) with Open Source VESA Graphics for Fish River Island II systems + +#@DESCRIPTION: Machine configuration for Fish River Island II systems, without Intel-proprietary graphics bits require conf/machine/include/tune-atom.inc require conf/machine/include/ia32-base.inc
meta-fri2/conf/machine/fri2.conf +2 -1
@@ -1,8 +1,9 @@ #@TYPE: Machine #@NAME: fri2 +#@WEBTITLE: Intel Atom E640T Processor with Intel EG20T Controller Hub Development Kit (Queens Bay) with Proprietary IEMGD Accelerated Graphics for Fish River Island II systems + #@DESCRIPTION: Machine configuration for Fish River Island II systems -# i.e. E660 + EG20T require conf/machine/include/tune-atom.inc require conf/machine/include/ia32-base.inc
Signature · 1 line
1.7.11.7
PATCH 2/3 sys940x: Add WEBTITLE and compliance information
In reply to Darren HartThe WEBTITLE will be used to publish the BSP on the Yocto Project website. Adding the Yocto Project compliance information for the 1.3 release.
Update the DESCRIPTION in the machine config and the platform description in the README to be consistent.
--- meta-sys940x/README | 13 +++++++++++-- meta-sys940x/conf/machine/sys940x-noemgd.conf | 5 +++-- meta-sys940x/conf/machine/sys940x.conf | 3 ++- 3 files changed, 16 insertions(+), 5 deletions(-)
meta-sys940x/README +11 -2
@@ -2,17 +2,26 @@ This README file contains information on building the meta-sys940x BSP layer, and booting the images contained in the /binary directory. Please see the corresponding sections below for details. -The Inforce SYS940x platform consists of the Intel Atom E6xx +The 'Queens Bay' platform consists of the Intel Atom E6xx 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.10 Driver. +Embedded Media and Graphics Driver (EMGD). More details available on the product page: http://www.inforcecomputing.com/SYS940X_ECX.html +Compliance +========== + +This BSP is compliant with the Yocto Project as per the requirements +listed here: + + http://www.yoctoproject.org/yocto-project-compatible-registration + + Dependencies ============
meta-sys940x/conf/machine/sys940x-noemgd.conf +3 -2
@@ -1,8 +1,9 @@ #@TYPE: Machine #@NAME: sys940x-noemgd -#@DESCRIPTION: Machine configuration for Inforce SYS940X systems -# i.e. E660 + EG20T +#@WEBTITLE: Intel Atom E6xx Processor with Intel EG20T Controller Hub Development Kit (Queens Bay) with Open Source VESA Graphics for Inforce SYS940X systems. + +#@DESCRIPTION: Machine configuration for Inforce SYS940X systems, without Intel-proprietary graphics bits require conf/machine/include/tune-atom.inc require conf/machine/include/ia32-base.inc
meta-sys940x/conf/machine/sys940x.conf +2 -1
@@ -1,8 +1,9 @@ #@TYPE: Machine #@NAME: sys940x +#@WEBTITLE: Intel Atom E6xx Processor with Intel EG20T Controller Hub Development Kit (Queens Bay) with Proprietary IEMGD Accelerated Graphics + #@DESCRIPTION: Machine configuration for Inforce SYS940x systems -# i.e. E660 + EG20T + emgd require conf/machine/include/tune-atom.inc require conf/machine/include/ia32-base.inc
Signature · 1 line
1.7.11.7
PATCH 3/3 n450: Add WEBTITLE and boilerplate README
In reply to Darren HartThe WEBTITLE will be used to publish the BSP on the Yocto Project website. Add a boilerplate README including the Yocto Project compliance information for the 1.3 release.
--- meta-n450/README | 125 +++++++++++++++++++++++++++++++++++++++ meta-n450/conf/machine/n450.conf | 4 +- 2 files changed, 128 insertions(+), 1 deletion(-) create mode 100644 meta-n450/README
meta-n450/README new file +125 -0
@@ -0,0 +1,125 @@ +This README file contains information on building the meta-n450 +BSP layer, and booting the images contained in the /binary directory. +Please see the corresponding sections below for details. + +The Luna Pier platform consists of the Intel Atom E4xx processor (Pineview), +plus the Intel 82801Hm I/O Controller. + + +Compliance +========== + +This BSP is compliant with the Yocto Project as per the requirements +listed here: + + http://www.yoctoproject.org/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 +([email protected]) and cc: the maintainer: + +Maintainer: Darren Hart <[email protected]> + +Please see the meta-intel/MAINTAINERS file for more details. + + +Table of Contents +================= + + I. Building the meta-n450 BSP layer + II. Booting the images in /binary + + +I. Building the meta-n450 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 an n450 +image by adding the location of the meta-n450 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-n450 \ + +Configure your build to build for the n450 machine in your local.conf file: + + MACHINE ?= "n450" + +You should then be able to build an n450 image as such: + + $ 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-n450-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
meta-n450/conf/machine/n450.conf +3 -1
@@ -1,7 +1,9 @@ #@TYPE: Machine #@NAME: n450 -#@DESCRIPTION: Machine configuration for Intel 1-N450 based systems +#@WEBTITLE: Intel Atom N450 Processor with Intel 82801 HM I/O Controller Compute Module (Luna Pier) with Intel Compute Module Mini-ITX Carrier + +#@DESCRIPTION: Machine configuration for Intel Embedded Development Board 1-N450 PREFERRED_PROVIDER-virtual/kernel ?= "linux-yocto" PREFERRED_VERSION_linux-yocto ?= "3.2%"
Signature · 1 line
1.7.11.7
Quoted 3 lines · Darren Hart
Add the WEBTITLE tag to the machine configs and update the READMEs with compliance information. Add a boilerplate README for the n450.
For all these,