diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2013-04-16 16:10:05 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-04-17 22:34:22 +0100 |
commit | 3b83bc90341d7ebb88785f20b4fd62a04afed8c7 (patch) | |
tree | 2948c86ad177208acd0517a2c05ecc820f8f2982 /documentation/bsp-guide | |
parent | 61ab619d1464dff6a77f4c27ad1534f57685e32f (diff) | |
download | openembedded-core-contrib-3b83bc90341d7ebb88785f20b4fd62a04afed8c7.tar.gz |
bsp-guide: Some minor edits.
(From yocto-docs rev: 01121297f5b3c6ac4bfca4603ad3536fd1379639)
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 | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml index 872db18191..81a6c8b76d 100644 --- a/documentation/bsp-guide/bsp.xml +++ b/documentation/bsp-guide/bsp.xml @@ -1033,7 +1033,7 @@ The Yocto Project includes a couple of tools that enable you to create a <link linkend='bsp-layers'>BSP layer</link> from scratch and do basic configuration and maintenance - of the kernel without ever looking at a metadata file. + of the kernel without ever looking at a Metadata file. These tools are <filename>yocto-bsp</filename> and <filename>yocto-kernel</filename>, respectively. </para> @@ -1283,16 +1283,16 @@ In the example, we use the ARM architecture. </para></listitem> <listitem><para>The script then prompts you for the kernel. - The default 3.4 kernel is acceptable. + The default 3.8 kernel is acceptable. So, the example accepts the default. If you enter 'n', the script prompts you to further enter the kernel - you do want to use (e.g. 3.0, 3.2_preempt-rt, and so forth.).</para></listitem> + you do want to use (e.g. 3.2, 3.2_preempt-rt, and so forth.).</para></listitem> <listitem><para>Next, the script asks whether you would like to have a new branch created especially for your BSP in the local <ulink url='&YOCTO_DOCS_DEV_URL;#local-kernel-files'>Linux Yocto Kernel</ulink> Git repository . If not, then the script re-uses an existing branch.</para> - <para>In this example, the default (or 'yes') is accepted. + <para>In this example, the default (or "yes") is accepted. Thus, a new branch is created for the BSP rather than using a common, shared branch. The new branch is the branch committed to for any patches you might later add. @@ -1304,8 +1304,8 @@ you are now given the opportunity to select a particular machine branch on which to base your new BSP-specific machine branch (or to re-use if you had elected to not create a new branch). - Because this example is generating an <filename>arm</filename> BSP, the example - uses <filename>#1</filename> at the prompt, which selects the arm-versatile branch. + Because this example is generating an ARM-based BSP, the example + uses <filename>#1</filename> at the prompt, which selects the ARM-versatile branch. </para></listitem> <listitem><para>The remainder of the prompts are routine. Defaults are accepted for each.</para></listitem> @@ -1336,7 +1336,7 @@ </literallayout> Adding the layer to this file allows the build system to build the BSP and the <filename>yocto-kernel</filename> tool to be able to find the layer and - other metadata it needs on which to operate. + other Metadata it needs on which to operate. </para> </section> |