summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-02-24 17:44:44 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-03-08 12:08:04 -0800
commit6aeeeba08fe307e8c790386d5eb3d006162acf13 (patch)
tree9af995ff20966fe78846ae8a826cf56b6291c84a
parent758dd351a76968f075689b4cfd9ca8e5dced6f43 (diff)
downloadpoky-6aeeeba08fe307e8c790386d5eb3d006162acf13.tar.gz
documentation/dev-manual: Added anchor point and edits to kernel config
I added a reference anchor to the spot in the dev-manual for the "Yocto Project Source Repositories". Other changes were to the bsp guide and were general edits to the "Linux Kernel Configuration" section. (From yocto-docs rev: def35923199d48c879ff06a68f81b5cd28d55185) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/bsp-guide/bsp.xml23
-rw-r--r--documentation/dev-manual/dev-manual-newbie.xml2
2 files changed, 14 insertions, 11 deletions
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index d5cb8769f0..bc5957ae39 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -427,7 +427,10 @@
427 Furthermore, there are machine-specific settings used during the build that are 427 Furthermore, there are machine-specific settings used during the build that are
428 defined by the <filename>machconfig</filename> files. 428 defined by the <filename>machconfig</filename> files.
429 In the Crown Bay example, two <filename>machconfig</filename> files exist: 429 In the Crown Bay example, two <filename>machconfig</filename> files exist:
430 one that supports the Intel EMGD and one that does not: 430 one that supports the
431 <trademark class='registered'>Intel</trademark> Embedded
432 Media and Graphics Driver (<trademark class='registered'>Intel</trademark>
433 EMGD) and one that does not:
431 <literallayout class='monospaced'> 434 <literallayout class='monospaced'>
432 meta-crownbay/recipes-bsp/formfactor/formfactor/crownbay/machconfig 435 meta-crownbay/recipes-bsp/formfactor/formfactor/crownbay/machconfig
433 meta-crownbay/recipes-bsp/formfactor/formfactor/crownbay-noemgd/machconfig 436 meta-crownbay/recipes-bsp/formfactor/formfactor/crownbay-noemgd/machconfig
@@ -507,14 +510,14 @@
507 </para> 510 </para>
508 <para> 511 <para>
509 For your BSP, you typically want to use an existing Yocto Project kernel found in the 512 For your BSP, you typically want to use an existing Yocto Project kernel found in the
510 Yocto Project repository at <filename>meta/recipes-kernel/linux</filename>. 513 <ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#yocto-project-files'>Yocto
514 Project Files</ulink> at <filename>meta/recipes-kernel/linux</filename>.
511 You can append your specific changes to the kernel recipe by using a 515 You can append your specific changes to the kernel recipe by using a
512 similarly named append file, which is located in the 516 similarly named append file, which is located in BSP Layer (e.g.
513 <filename>meta-&lt;bsp_name&gt;/recipes-kernel/linux</filename> 517 the <filename>meta-&lt;bsp_name&gt;/recipes-kernel/linux</filename> directory).
514 directory.
515 </para> 518 </para>
516 <para> 519 <para>
517 Suppose you use a BSP that uses the <filename>linux-yocto_3.0.bb</filename> kernel, 520 Suppose the BSP uses the <filename>linux-yocto_3.0.bb</filename> kernel,
518 which is the preferred kernel to use for developing a new BSP using the Yocto Project. 521 which is the preferred kernel to use for developing a new BSP using the Yocto Project.
519 In other words, you have selected the kernel in your 522 In other words, you have selected the kernel in your
520 <filename>&lt;bsp_name&gt;.conf</filename> file by adding the following statements: 523 <filename>&lt;bsp_name&gt;.conf</filename> file by adding the following statements:
@@ -533,7 +536,7 @@
533 </literallayout> 536 </literallayout>
534 The following listing shows the file. 537 The following listing shows the file.
535 Be aware that the actual commit ID strings in this example listing might be different 538 Be aware that the actual commit ID strings in this example listing might be different
536 than the actual strings in the file from the Yocto Project <filename>meta-intel</filename> 539 than the actual strings in the file from the <filename>meta-intel</filename>
537 Git source repository. 540 Git source repository.
538 <literallayout class='monospaced'> 541 <literallayout class='monospaced'>
539 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" 542 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
@@ -552,8 +555,8 @@
552 SRCREV_machine_pn-linux-yocto_crownbay-noemgd ?= "63c65842a3a74e4bd3128004ac29b5639f16433f" 555 SRCREV_machine_pn-linux-yocto_crownbay-noemgd ?= "63c65842a3a74e4bd3128004ac29b5639f16433f"
553 SRCREV_meta_pn-linux-yocto_crownbay-noemgd ?= "59314a3523e360796419d76d78c6f7d8c5ef2593" 556 SRCREV_meta_pn-linux-yocto_crownbay-noemgd ?= "59314a3523e360796419d76d78c6f7d8c5ef2593"
554 </literallayout> 557 </literallayout>
555 This append file contains statements used to support the Crown Bay BSP for both 558 This append file contains statements used to support the Crown Bay BSP for both
556 Intel EMGD and non-EMGD. 559 <trademark class='registered'>Intel</trademark> EMGD and the VESA graphics.
557 The build process, in this case, recognizes and uses only the statements that 560 The build process, in this case, recognizes and uses only the statements that
558 apply to the defined machine name - <filename>crownbay</filename> in this case. 561 apply to the defined machine name - <filename>crownbay</filename> in this case.
559 So, the applicable statements in the <filename>linux-yocto_3.0.bbappend</filename> 562 So, the applicable statements in the <filename>linux-yocto_3.0.bbappend</filename>
@@ -571,7 +574,7 @@
571 The append file defines <filename>crownbay</filename> as the compatible machine, 574 The append file defines <filename>crownbay</filename> as the compatible machine,
572 defines the <filename>KMACHINE</filename>, points to some configuration fragments 575 defines the <filename>KMACHINE</filename>, points to some configuration fragments
573 to use by setting the <filename>KERNEL_FEATURES</filename> variable, and then points 576 to use by setting the <filename>KERNEL_FEATURES</filename> variable, and then points
574 to the specific commits in the Yocto Project files Git repository and the 577 to the specific commits in the Yocto Project Files Git repository and the
575 <filename>meta</filename> Git repository branches to identify the exact kernel needed 578 <filename>meta</filename> Git repository branches to identify the exact kernel needed
576 to build the Crown Bay BSP. 579 to build the Crown Bay BSP.
577 </para> 580 </para>
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index e9077c4efc..e076c8ff02 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -94,7 +94,7 @@
94 <para> 94 <para>
95 In summary, here is where you can get the Yocto Project files needed for development: 95 In summary, here is where you can get the Yocto Project files needed for development:
96 <itemizedlist> 96 <itemizedlist>
97 <listitem><para><emphasis><ulink url='http://git.yoctoproject.org/cgit/cgit.cgi'>Source Repositories:</ulink></emphasis> 97 <listitem><para id='source-repositories'><emphasis><ulink url='http://git.yoctoproject.org/cgit/cgit.cgi'>Source Repositories:</ulink></emphasis>
98 This area contains IDE Plugins, Matchbox, Poky, Poky Support, Tools, Yocto Linux Kernel, and Yocto 98 This area contains IDE Plugins, Matchbox, Poky, Poky Support, Tools, Yocto Linux Kernel, and Yocto
99 Metadata Layers. 99 Metadata Layers.
100 You can create Git repositories for each of these areas.</para> 100 You can create Git repositories for each of these areas.</para>