diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2014-04-09 11:09:16 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2014-04-11 18:22:50 +0100 |
commit | e371eaf9c95f42122b4c45ec62a8c3b932ed7a3b (patch) | |
tree | 07fd689d101453a9da3fe347e19fd1674341cab9 /documentation/bsp-guide | |
parent | f5bd39bf84e90c881ac9e52e2bf64adf94244102 (diff) | |
download | poky-e371eaf9c95f42122b4c45ec62a8c3b932ed7a3b.tar.gz |
bsp-guide: Updated the yocto-bsp example.
This example does not run as described. It said that the
setup script was run and the user would be in the top-level
Source Directory (e.g. poky). The script errors out unless
run from the poky/build directory. So I took out the requirement
of being in the top directory.
(From yocto-docs rev: 800e4001319cde3e665c0271fd5a19646fb2bd7a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/bsp-guide')
-rw-r--r-- | documentation/bsp-guide/bsp.xml | 11 |
1 files changed, 5 insertions, 6 deletions
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml index 29d975b6ff..70aeef24fe 100644 --- a/documentation/bsp-guide/bsp.xml +++ b/documentation/bsp-guide/bsp.xml | |||
@@ -83,7 +83,7 @@ | |||
83 | <para> | 83 | <para> |
84 | Some layers function as a layer to hold other BSP layers. | 84 | Some layers function as a layer to hold other BSP layers. |
85 | An example of this type of layer is the <filename>meta-intel</filename> layer. | 85 | An example of this type of layer is the <filename>meta-intel</filename> layer. |
86 | The <filename>meta-intel</filename> layer contains over 10 individual BSP layers. | 86 | The <filename>meta-intel</filename> layer contains many individual BSP layers. |
87 | </para> | 87 | </para> |
88 | 88 | ||
89 | <para> | 89 | <para> |
@@ -1238,8 +1238,7 @@ | |||
1238 | is created in the current working directory. | 1238 | is created in the current working directory. |
1239 | This example assumes you have sourced the | 1239 | This example assumes you have sourced the |
1240 | <ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink> | 1240 | <ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink> |
1241 | and are currently in the top-level folder of the | 1241 | setup script. |
1242 | <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. | ||
1243 | </para> | 1242 | </para> |
1244 | 1243 | ||
1245 | <para> | 1244 | <para> |
@@ -1283,17 +1282,17 @@ | |||
1283 | 1282 | ||
1284 | New qemu BSP created in meta-myarm | 1283 | New qemu BSP created in meta-myarm |
1285 | </literallayout> | 1284 | </literallayout> |
1286 | Let's take a closer look at the example now: | 1285 | Take a closer look at the example now: |
1287 | <orderedlist> | 1286 | <orderedlist> |
1288 | <listitem><para>For the QEMU architecture, | 1287 | <listitem><para>For the QEMU architecture, |
1289 | the script first prompts you for which emulated architecture to use. | 1288 | the script first prompts you for which emulated architecture to use. |
1290 | In the example, we use the ARM architecture. | 1289 | In the example, we use the ARM architecture. |
1291 | </para></listitem> | 1290 | </para></listitem> |
1292 | <listitem><para>The script then prompts you for the kernel. | 1291 | <listitem><para>The script then prompts you for the kernel. |
1293 | The default 3.10 kernel is acceptable. | 1292 | The default 3.14 kernel is acceptable. |
1294 | So, the example accepts the default. | 1293 | So, the example accepts the default. |
1295 | If you enter 'n', the script prompts you to further enter the kernel | 1294 | If you enter 'n', the script prompts you to further enter the kernel |
1296 | you do want to use (e.g. 3.2, 3.2_preempt-rt, and so forth.).</para></listitem> | 1295 | you do want to use.</para></listitem> |
1297 | <listitem><para>Next, the script asks whether you would like to have a new | 1296 | <listitem><para>Next, the script asks whether you would like to have a new |
1298 | branch created especially for your BSP in the local | 1297 | branch created especially for your BSP in the local |
1299 | <ulink url='&YOCTO_DOCS_DEV_URL;#local-kernel-files'>Linux Yocto Kernel</ulink> | 1298 | <ulink url='&YOCTO_DOCS_DEV_URL;#local-kernel-files'>Linux Yocto Kernel</ulink> |