Fixed a few references and links. Also standardized on the
capitalization for the term "Source Directory" where it
refers to the YP poky structure on the development machine.
(From yocto-docs rev: 1a20418d8791d754ad66c5a059e65bd68a4c6b32)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removing the Appendix A (BSP) example had some rippling affects
throughout the doc set. There were several links into the appendix.
All these links had to either be modified (if possible) or simply
removed since the appendix will be removed.
(From yocto-docs rev: fff35abd87e945de1806eef63a56a956d104bf92)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changed the title and a single reference from the Kernel manual
to a title more representative of how these patches are sent -
not using scripts.
(From yocto-docs rev: ff908c34fae88eab9724891a008142a834f34081)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changed the section heading for the part describing how to
push changes upstream via the poky scripts. Also had to
change one cross-reference to the section in the kernel
manual.
(From yocto-docs rev: be7712aba044238e8781cdf869c5d14e77eb09a2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The references to the YP Development Manual were inconsistant.
These references were fixed.
(From yocto-docs rev: f4ded0b965fcbce7b500ca21886ee9b755c38383)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I did a read-through of the manual and spotted several nits that
I fixed. All these are minor fixes.
(From yocto-docs rev: 0c8f9c660ecea0b36e2b6af0315d3d239f70a688)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changed all occurrences of "Yocto Project" to terms better suited
to reality.
(From yocto-docs rev: fdd7b8c2bcbaf566cad336c67c582c2a24aa9dc1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I updated the "Show a Particular Feature or Branch Change" section so
that it reads better. I also included some real examples.
(From yocto-docs rev: 42aa13c7fbf45abf869b056deec063be6682c70b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
According to Bruce Ashfield, we will be using linux-yocto-3.4. So
I changed the linux-yocto-3.0 strings to linux-yocto-3.4.
(From yocto-docs rev: 23df0251b04ed7c31ad2297a4a7870861554beef)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
[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>
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>
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>
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>
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>
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>
Scott Rifenbark
Richard Purdie
Tom Zanussi