From 19e3648390b011715f7446161a05d9d568aed765 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 17 Mar 2016 12:59:39 -0700 Subject: dev-manual: Edits from a 2.1 read-through. * Removed some eMenlow stuff * Cleaned up the description of the BSP structures we have now. * Various links fixed into the SDK manual. * Other minor fixes. (From yocto-docs rev: 5e45005d7ff2254df2754a5ea2d7efd7f1c19a42) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-model.xml | 126 +++++++++++++++++--------- 1 file changed, 81 insertions(+), 45 deletions(-) (limited to 'documentation/dev-manual/dev-manual-model.xml') diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml index 4fb1e61559..838fc58922 100644 --- a/documentation/dev-manual/dev-manual-model.xml +++ b/documentation/dev-manual/dev-manual-model.xml @@ -48,7 +48,9 @@ that allows you to start builds and examine build statistics. Using a Development Shell: - You can use a devshell to efficiently debug + You can use a + devshell + to efficiently debug commands or simply edit packages. Working inside a development shell is a quick way to set up the OpenEmbedded build environment to work on parts of a project. @@ -147,38 +149,60 @@ "Creating a New BSP Layer Using the yocto-bsp Script" section in the Yocto Project Board Support (BSP) Developer's Guide. + - Another example that illustrates a layer is an application. - Suppose you are creating an application that has library or other dependencies in - order for it to compile and run. - The layer, in this case, would be where all the recipes that define those dependencies - are kept. - The key point for a layer is that it is an isolated area that contains - all the relevant information for the project that the OpenEmbedded build - system knows about. - For more information on layers, see the - "Understanding and Creating Layers" - section. - For more information on BSP layers, see the - "BSP Layers" section in the - Yocto Project Board Support Package (BSP) Developer's Guide. - Five BSPs exist that are part of the - Yocto Project release: genericx86, genericx86-64, - beaglebone (ARM), - mpc8315e (PowerPC), - and edgerouter (MIPS). - The recipes and configurations for these five BSPs are located and dispersed - within the Source Directory. - On the other hand, the meta-intel layer - contains BSP layers for many supported BSPs (e.g. - Crystal Forest, Emenlow, Fish River Island 2, Haswell, - Jasper Forest, and so forth). - Aside from the BSPs in the meta-intel - layer, the - Source Repositories - contain additional BSP layers such as - meta-minnow and - meta-raspberrypi. + Another example that illustrates a layer + is an application. + Suppose you are creating an application that has + library or other dependencies in order for it to + compile and run. + The layer, in this case, would be where all the + recipes that define those dependencies are kept. + The key point for a layer is that it is an isolated + area that contains all the relevant information for + the project that the OpenEmbedded build system knows + about. + For more information on layers, see the + "Understanding and Creating Layers" + section. + For more information on BSP layers, see the + "BSP Layers" + section in the Yocto Project Board Support Package (BSP) + Developer's Guide. + + + Five BSPs exist that are part of the Yocto Project release: + beaglebone (ARM), + mpc8315e (PowerPC), + and edgerouter (MIPS). + The recipes and configurations for these five BSPs + are located and dispersed within the + Source Directory. + + + + Three core Intel BSPs exist as part of the Yocto + Project release in the + meta-intel layer: + + intel-core2-32, + which is a BSP optimized for the Core2 family of CPUs + as well as all CPUs prior to the Silvermont core. + + intel-corei7-64, + which is a BSP optimized for Nehalem and later + Core and Xeon CPUs as well as Silvermont and later + Atom CPUs, such as the Baytrail SoCs. + + intel-quark, + which is a BSP optimized for the Intel Galileo + gen1 & gen2 development boards. + + + + + + When you set up a layer for a new BSP, you should follow a standard layout. This layout is described in the "Example Filesystem Layout" @@ -288,18 +312,6 @@ Within this group, you will find several kernels supported by the Yocto Project: - - linux-yocto-3.8 - The - stable Yocto Project kernel to use with the Yocto - Project Release 1.4. This kernel is based on the - Linux 3.8 released kernel. - - - linux-yocto-3.10 - An - additional, unsupported Yocto Project kernel used with - the Yocto Project Release 1.5. - This kernel is based on the Linux 3.10 released kernel. - linux-yocto-3.14 - The stable Yocto Project kernel to use with the Yocto @@ -318,12 +330,36 @@ Project Release 1.8. This kernel is based on the Linux 3.19 released kernel. + + linux-yocto-4.1 - The + stable Yocto Project kernel to use with the Yocto + Project Release 2.0. + This kernel is based on the Linux 4.1 released kernel. + + + linux-yocto-4.4 - The + stable Yocto Project kernel to use with the Yocto + Project Release 2.1. + This kernel is based on the Linux 4.4 released kernel. + linux-yocto-dev - A development kernel based on the latest upstream release candidate available. + + Long Term Support Initiative (LTSI) for Yocto Project kernels + is as follows: + + For Yocto Project releases 1.7, 1.8, and 2.0, + the LTSI kernel is linux-yocto-3.14. + + For Yocto Project release 2.1, the + LTSI kernel is linux-yocto-4.1. + + + @@ -538,7 +574,7 @@ Tools exist to help the application developer during any phase of development. For information on how to install and use an SDK, see the - Yocto Project Software Development Kit (SDK) Developer's Guide. + Yocto Project Software Development Kit (SDK) Developer's Guide. -- cgit v1.2.3-54-g00ecf