summaryrefslogtreecommitdiffstats
path: root/documentation/kernel-manual/kernel-how-to.xml
Commit message (Collapse)AuthorAgeFilesLines
* documentation/kernel-manual: Converted to use variables from poky.ent.Scott Rifenbark2012-03-231-17/+19
| | | | | | Also removed a broken link. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/kernel-manual/kernel-how-to.xml: edits to tree constructionScott Rifenbark2012-03-081-10/+19
| | | | | | | | | | | I made some clarifying edits to the section that describes how the YP team constructs the kernel repositories (the tree). There were some things that just weren't clear. (From yocto-docs rev: 127f0c8c89ec9b926a4ff348acc39a73f41e6fe7) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/kernel-manual/kernel-how-to.xml: links to manuals removedScott Rifenbark2012-03-081-14/+7
| | | | | | | | | | | | Several redundant links existed to manuals that are not required to be linked. The actual link takes the reader to the section being referenced. Then, after the link, the manual is referenced. Previously, the manual was also linked. We don't need these links to the manuals. (From yocto-docs rev: 579f4efd765dc20b38e1b022ae4b7a98a8fa53cd) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/kernel-manual/kernel-how-to.xml: general editsScott Rifenbark2012-01-061-9/+11
| | | | | | | | | Some general edits up to section 3.4. (From yocto-docs rev: 5bcd22b6372017c4f78b18035193879890ed8244) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation: Changed all manual links to point to "latest"Scott Rifenbark2011-11-251-11/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | There are many references to YP documentation throughout the YP manual set. They used to have hard-coded links to the current release (e.g. yoctoproject.org/docs/1.1 for Edison). This created a situation where if you went to a document on the website and clicked on a external reference to another manual, you would redirect to the current manual on the website. Really, you would want to go to the latest manual, which is one that is under development. Changing the links to "yoctoproject.org/docs/latest" makes the tip of master, which is used for devloping the next release, always have references to the manuals being developed and not back to the stable released set of manuals. This "latest" and "current" scheme for the links is not perfect. What has to happen when the latest set of the manuals freezes and becomes the next stable release, all the links in the docs will need to be changed from "latest" in the URL to the new release number. So for example, all the "latest" occurences would need to be changed to "1.2". Then for the next cycle as development begins again, the links need to be infused with "latest" again. (From yocto-docs rev: a234aef34303b07671da956de0e94b352797143e) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/kernel-manual/kernel-how-to.xml: Updated build strategyScott Rifenbark2011-10-041-9/+8
| | | | | | | | | | | | | This section used the term "tree construction" somewhat out of context. The section really focuses on what the build process and the user does prior to compilation. I changed wording to indicate the tree is validated to be sure that the SRC_URI point to the right stuff and that the BSP build branch exists. (From yocto-docs rev: e6332d5045b21354b53bbbe1203f9d52d4d97964) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/kernel-manual: Added some references to other areas of YP docs.Scott Rifenbark2011-10-041-1/+29
| | | | | | | (From yocto-docs rev: 20754cb376e65b7262b754afad839e0c2b82d7f7) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/kernel-manual: Scrub for 1.1Scott Rifenbark2011-10-041-1460/+231
| | | | | | | | | | | I went through and made sure examples are relevant, wording is correct, large blocks of unused text was removed, and some references included to other YP documents. (From yocto-docs rev: 2231082530dd9cecc234f5f024c4e246afb2968d) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/kernel-manual/kernel-how-to.xml: command indentation fixed.Scott Rifenbark2011-08-231-2/+2
| | | | | | | (From yocto-docs rev: d3116dbda4af7f469e10449ed27b2885474317b5) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/kernel-manual/kernel-how-to.xml: Tree Construction section ↵Scott Rifenbark2011-07-211-32/+54
| | | | | | | | | | | | | | further explained Added text to help put tree construction into context with the developer. The section felt as if the developer needed to be taking action on the steps when in reality the steps are describing a lot of "behind-the-scenes" stuff that happens when the YP tree is constructed. (From yocto-docs rev: 1aafca94f3f3d5e07a0b2244ff5dbfe4a2c1ba8f) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/kernel-manual/kernel-how-to.xml: Defined audience for chapterScott Rifenbark2011-07-211-0/+2
| | | | | | | | | | | Added a sentence clarifying the intended audience of this chapter. It is specifically for developers that want to modify the YP kernel and contribute changes upstream to YP. (From yocto-docs rev: 1012dcb8312cb83fe64397742142071f20ae4e24) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/kernel-manual/kernel-how-to.xml: Updated the create BSP sectionScott Rifenbark2011-07-211-228/+49
| | | | | | | | | | | | This section has been re-written to just include high-level overview of the steps. The detailed example that used to be the section is not needed as there is adequate documentation of this process in the Yocto Project Development Manual and on the wiki courtesy of Tom Zanussi. (From yocto-docs rev: 7355734a5ed965401027ba23bfb15fd926a171f7) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/kernel-manual/kernel-how-to.xml: Added 'git' for a push example.Scott Rifenbark2011-07-211-1/+1
| | | | | | | | | | I forgot the 'git' part of the 'git push' command for the fix requested by Robert P. J. Day. (From yocto-docs rev: 458e18bd9d33c12ff3367cae8a4cc0c6c640b932) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/kernel-manual/kernel-how-to.xml: Command line example fixesScott Rifenbark2011-07-211-2/+4
| | | | | | | | | | Changes requested by Robert P. J. Day at rpjday@crashcourse.ca to add a missing system prompt character and fix an overly long git push example. (From yocto-docs rev: 71ac0b23682c6a405ae454cab02120993d2f370e) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/kernel-manual/kernel-how-to.xml: changed git to Git as needed ↵Scott Rifenbark2011-07-211-72/+72
| | | | | | | (From yocto-docs rev: 65a839ea3d8decd1dd3e95bfeeeb3f95cfa77ef4) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/adt-manual/kernel-how-to.xml: Changed Bitbake to BitBake (From ↵Scott Rifenbark2011-07-211-1/+1
| | | | | | | yocto-docs rev: c3b3d7f7b16bc222d599bdfb5e99c86694a1c865) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/kernel-manual/kernel-how-to.xml: Partial - more general edits ↵Scott Rifenbark2011-07-211-25/+41
| | | | | | | (From yocto-docs rev: 60d084a5b17bf78fafd8a4d13b9055093fca708a) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/kernel-manual/kernel-how-to.xml: partial - more edits to BSP ↵Scott Rifenbark2011-07-211-8/+8
| | | | | | | procedure (From yocto-docs rev: 694b00c080633be874f2842badedf1e453038f88) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/kernel-manual/kernel-how-to.xml: Partial - Re-write of BSP ↵Scott Rifenbark2011-07-211-40/+60
| | | | | | | | | | | | creation This is a partial edit of re-writing the BSP creation section so that it is clearer for the naive user. It is not quite done yet. (From yocto-docs rev: 7a552e72a1d2d1b6ffa93f4fe3074f318ff35715) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/kernel-manual/kernel-how-to.xml: Edits to "Build Strategy" ↵Scott Rifenbark2011-07-211-3/+5
| | | | | | | (From yocto-docs rev: f98e4804da9477e260e24df1586b624e386a2dba) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/kernel-manual/kernel-how-to.xml: Edits to "Tree Construction" ↵Scott Rifenbark2011-07-211-4/+4
| | | | | | | (From yocto-docs rev: 601e0fd1bb00c433716170a124b3ca32ca2cdcad) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Rename poky-image-* -> core-image-* and task-poky-* -> task-core-*Richard Purdie2011-04-211-1/+1
| | | | | | (From yocto-docs rev: 0feb6b8f9621087ba5fd77d3c8f3e23132c97187) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/kernel-manual/kernel-how-to.xml: replaced 'pokylinux' with ↵Scott Rifenbark2011-04-181-2/+2
| | | | | | | | | 'yoctoproject' (From OE-Core rev: 39f8b1b13072598729a189fb58c14622d300db69) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/kernel-manual/kernel-how-to.xml: Spell checkedScott Rifenbark2011-03-181-3/+3
| | | | | | | | | Performed a spell check and found a couple items. (From OE-Core rev: 45039d008519c13f97d9b195bba4505b3865b5ea) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation: Kernel Manual fixesTom Zanussi2011-03-141-59/+65
| | | | | | | | | | | Upgraded to reflect 1.0 usage rather than 0.90 usage, and some other clarifications and minor changes. [RP - added tweaks suggested by Darren Hart] (From OE-Core rev: c6f06f478ac229c4619f815b8b313711d47b1551) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/kernel-manual/kernel-how-to.xml: Changes to section 3.4.4 and ↵Scott Rifenbark2011-02-181-0/+31
| | | | | | | | | | new 3.4.5 I made some updates to the 3.4.4 section according to Bruce Ashfield's feedback. I also added a new section 3.4.5 (Creating a BSP Based on an Existing Similar BSP Without a Local Kernel Repository). Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
* documentation/kernel-manual/kernel-how-to.xml: fix to step 3 and 4 of ↵Scott Rifenbark2011-02-181-1/+6
| | | | | | | | | | | | | section 3.4.4 Added text after the sample bbappend file stating that the user needs to update the KSRC assignment statement and also remove its comment. Also they have to remove the comment from the SRC_URI line. Changed the bitbake command in step 4 to use the linux-yocto-stable file rather than the linux-yocto file. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
* documentation/kernel-manual/kernel-how-to.xml: Fix to step 3 of section 3.4.4Scott Rifenbark2011-02-181-1/+1
| | | | | | | | Changed 'linux-yocto_git.bbappend' to 'linux-yocto-stable_git.bbappend' in step 3 just before the code example. This makes the code consistent with the rest of the example supporting the 2.6.34 kernel. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
* documentation/kernel-manual/kernel-how-to.xml: Fix to step 1 of section 3.4.4Scott Rifenbark2011-02-181-1/+2
| | | | | | | | | | Step one states that the linux-yocto_git.bbappend file is left. This file is associated with distro 2.6.37 kernel and the rest of the example is associated with the 2.6.34 kernel. So, I changed the step to indicate that the directory is left with a linux-yocto-stable_git.bbappend file. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
* documentation/kernel-manual/kernel-how-to.xml: More changes to the creating ↵Scott Rifenbark2011-02-141-12/+17
| | | | | | | | | BSP section. These changes implemented Bruce Ashfield's next round of changes to the section 4.3.3 example. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
* documentation/kernel-manual/kernel-how-to.xml: Fixed typeScott Rifenbark2011-02-141-1/+1
| | | | | | | In section 4.3.3 step 2 there was a directory 'build/donf/bblayers.conf'. I fixed the typo to 'build/conf/bblayers.conf'. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
* documentation/kernel-manual/kernel-how-to.xml: - Condense and merge example ↵Scott Rifenbark2011-02-141-1/+1
| | | | | | | | | | changed. The example used to show how to condense and merge two BSPs into a second SCM used a non-existant machine (cav_ebt5800-standard). I replaced this machine with 'common_pc_64-standard, which is a real machine. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
* documentation/kernel-manual/kernel-how-to.xml: [BUGID# 597] Reversing ↵Scott Rifenbark2011-02-141-6/+6
| | | | | | | | | | | common-pc-standard [BUGID# 597] - After talking with Bruce Ashfield the kernel documentation needs to support the 2.6.34 disribution. So, the 'common-pc-standard' strings need to be changed back to 'common_pc-standard'. This fix restores them. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
* documentation/kernel-manual/kernel-how-to.xml: [BUGID# 597] Fixed common_pcScott Rifenbark2011-02-141-6/+6
| | | | | | [BUGID# 597] - Changed the string "common_pc" to "common-pc". Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
* documentation/kernel-manual/kernel-how-to.xml: added newline characterScott Rifenbark2010-12-141-1/+2
| | | | | | | There was a git checkout and git push command that did not have a newline character between the two line in a literallayout block. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
* documentation/kernel-manual/kernel-how-to.xml: fixed typo bug 588Scott Rifenbark2010-12-141-1/+1
| | | | | | | removed the ";" character that was part of the git log --pretty=oneline command example. This fixes bug [BUGID# 588]. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
* documentation/kernel-manual: Added Bruce Ashfields review comments.Scott Rifenbark2010-12-101-17/+16
| | | | | | | Comments covered some minor points. We did remove the "Creating a Transition Kernel Layer" section however. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
* documentation/kernel-manual/kernel-how-to.xml: Completed scrub to the text.Scott Rifenbark2010-12-101-223/+302
| | | | | | This version represents the completed first draft with all of Bruce Ashfield's comments applied and a good scrubbing of the text. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
* documentation/kernel-manual/kerenel-how-to.xml: Edits to clean up text.Scott Rifenbark2010-12-101-341/+438
| | | | | | | Re-writing up to the "Export for External (Upstream) Submission" section. I am cleaning up the English and style. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
* documentation/kernel-manual: Added these files so the book could have chapters.Scott Rifenbark2010-12-101-0/+1954
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>