diff options
| author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2011-08-10 15:37:05 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-08-15 15:27:01 +0100 |
| commit | ae7a21452237e0bd0a7b379fe71685d08047c447 (patch) | |
| tree | a856dee8347ab070e69a7bda5f954ca2b8826105 /documentation/dev-manual | |
| parent | 264785096a0ff74ece5e3b8e0e385e5328d1f597 (diff) | |
| download | ast2050-yocto-poky-ae7a21452237e0bd0a7b379fe71685d08047c447.zip ast2050-yocto-poky-ae7a21452237e0bd0a7b379fe71685d08047c447.tar.gz | |
documentation/dev-manual/dev-manual-bsp-appendix.xml: changed file name
I changed 'linux-yocto-2.6.37.bbappend' to 'linux-yocto_2.6.37.
(From yocto-docs rev: 0eb284374ef9dfb26142ae4d0254a0fe4056d0ab)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual')
| -rw-r--r-- | documentation/dev-manual/dev-manual-bsp-appendix.xml | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/documentation/dev-manual/dev-manual-bsp-appendix.xml b/documentation/dev-manual/dev-manual-bsp-appendix.xml index bbf9e2b..6a35985 100644 --- a/documentation/dev-manual/dev-manual-bsp-appendix.xml +++ b/documentation/dev-manual/dev-manual-bsp-appendix.xml @@ -300,7 +300,7 @@ The recipe for that kernel is not located in the BSP layer but rather in the local Yocto Project files at <filename>meta/recipes-kernel/linux</filename> and is - named <filename>linux-yocto-2.6.37.bb</filename>. + named <filename>linux-yocto_2.6.37.bb</filename>. The <filename>SRCREV_machine</filename> and <filename>SRCREV_meta</filename> statements point to the exact commits used by the Yocto Project development team in their source repositories that identify the right kernel for our hardware. @@ -309,7 +309,7 @@ <para> However, in the <filename>meta-mymachine</filename> layer in <filename>recipes-kernel/linux</filename> resides a <filename>.bbappend</filename> - file named <filename>linux-yocto-2.6.37.bbappend</filename> that + file named <filename>linux-yocto_2.6.37.bbappend</filename> that is appended to the recipe of the same name in <filename>meta/recipes-kernel/link</filename>. Thus, the <filename>SRCREV</filename> statements in the "append" file override the more general statements found in <filename>meta</filename>. @@ -343,7 +343,7 @@ </para> <para> - To fix this situation in <filename>linux-yocto-2.6.37.bbappend</filename> + To fix this situation in <filename>linux-yocto_2.6.37.bbappend</filename> we delete the two <filename>SRCREV</filename> statements that support EMGD (the top pair). We also change the remaining pair to specify <filename>mymachine</filename> @@ -376,7 +376,7 @@ branch</para></listitem> <listitem><para>Click on the commit column header to view the top commit</para></listitem> <listitem><para>Copy the commit string for use in the - <filename>linux-yocto-2.6.37.bbappend</filename> file</para></listitem> + <filename>linux-yocto_2.6.37.bbappend</filename> file</para></listitem> </orderedlist> </para> @@ -387,14 +387,14 @@ </para> <para> - Also in the <filename>linux-yocto-2.6.37.bbappend</filename> file are + Also in the <filename>linux-yocto_2.6.37.bbappend</filename> file are <filename>COMPATIBLE_MACHINE</filename>, <filename>KMACHINE</filename>, and <filename>KERNEL_FEATURES</filename> statements. Two sets of these exist: one set supports EMGD and one set does not. Because we are not interested in supporting EMGD those three can be deleted. The remaining three must be changed so that <filename>mymachine</filename> replaces <filename>crownbay-noemgd</filename> and <filename>crownbay</filename>. - Here is the final <filename>linux-yocto-2.6.37.bbappend</filename> file after all + Here is the final <filename>linux-yocto_2.6.37.bbappend</filename> file after all the edits: <literallayout class='monospaced'> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" |
