Not sure if I need to commit these again. They are showing up in the
git status command so I might have updated them and forgot to commit
them. Doing so to be sure.
(From yocto-docs rev: 75c87592c10647ec09f42a1363a8ae123cd6e33d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is a comprehensive pass through this entire section that incorporates
understanding given to me by Scott Garman. I have added more detail and
text that helps the non-developer understand what is fundamentally going
on.
(From yocto-docs rev: 124c722ccf0316f6e62790ca77c88d0444559378)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added a reference to the Image appendix for the description of
images. Also, added a new term "meta-toolchain."
(From yocto-docs rev: a9c1110ec7499afa669416c00bc81573fcbf920d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added more general description of what this section's purpose it.
I felt it was missing some basic information and making too many
assumptions.
(From yocto-docs rev: 4a5faeecc616313147283e50fe947c68555f55a2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It seems that this manual should be named the yocto project reference
manual as we slowly try to rid ourselves of the "Poky" term.
(From yocto-docs rev: c9d30285adf83bbcfc06233be54aec4203cbfd13)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the PDF version of the manual the "‐‐" docbook statement
does not display correctly. I changed this to "--".
(From yocto-docs rev: b0596e0ce370d6c6e1680e89d9c5a5b9da26dd93)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the PDF version of the manual the "‐‐" statement does not
display correctly. I changed this to "--".
(From yocto-docs rev: ae3a5bc15d30668b6f9048245f70dcd82f89da32)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In anticipation of 1.1 I have changes several filenames that
had "1.0" to include "1.1" instead. I am unsure if the names are
correct at this time. I will need to check them when the release is
created.
(From yocto-docs rev: ae50f920c5cf18f6c0494280a453feb41ef56d83)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the PDF version of the manual the "‐‐" docbook statement
does not disply correctly. I changed them to "--".
(From yocto-docs rev: 8aea27a6de1ca2d5dffc84cfb7a26d29c3eb0e8d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the PDF version of the manual the "‐‐" docbook command
does not display. I changed this to "--".
(From yocto-docs rev: b5f42fad0c7447a480e0557988f868ef4833abbf)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are examples that use "1.0". i have changed these to "1.1"
in anticipation of the 1.1 release. At the time of the change I don't
know if the actual file names i put in are correct. I need to check them
when Beth sends me the real stuff.
(From yocto-docs rev: 3d5bd0bd38fd2d99e7d5cbb6bedf0fde0fdd5fa9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Errors caught by Robert P. J. Day:
1. An extra ">" character removed.
2. Overly long commands changed to use the continuation symbol.
(From yocto-docs rev: e84b7d5a46817fdc9c0f55242840989cbe8494c7)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Comment from Bruce Ashfield indicated that this statement needed to be
SRCREV_meta_pn-linux-yocto_mymachine ?= \
"84f1a422d7e21fbc23a687035bdf9d42471f19e0"
(From yocto-docs rev: 917bfca1af7f82ad330854849e0ec4f30289543a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
this example uses the CONFIG_SMP configuration. By default, this configuration is
disabled. The example shows how to use menuconfig and explains the .config file
role and how you can use it combined with menuconfig to manage multiple configuration
changes.
Thanks to Darren Hart for identifying this simple change to demonstrate how to
change the kernel configuration.
(From yocto-docs rev: c571c01b8589ad6f76e66388c3ae24a1de029f65)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Made several editing corrections for various terms and phrasings based on
Scott Garman's review.
(From yocto-docs rev: a21ba80151ce82683d45cd67ddb0728d779b007a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield suggested adding a note near the explanation of creating
a bare clone that suggests if the user already has a linux yocto kernel
Git repo handy they can reference that repo in the 'git clone --bare'
command rather than referencing the upstream source repository as
a way to speed up the process.
(From yocto-docs rev: 132a9cfcef3397677b54eace7831d25f8a321b93)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
1. now refer to the linux 2.6.39-rc1 as the 'latest upstream release
candidate available.
2. Noted where you can find the linux-2.6 kernel - in the meta-kernel-dev
area.
These changes were from Bruce Ashfield's review of an early version
of the Yocto Project Development Manual.
(From yocto-docs rev: 83d6e75e7d5f4d60040c4b7ebb0c7bb11b1b67e8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield's review comments indicated that we will be using
linux-yocto-3.0 and not linux-yocto-2.6.37. So I am putting these
changes in to anticipate the 1.1 release.
(From yocto-docs rev: ecbe1c90c5aa65b2dde77ba6094b5956e37d061d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Had to set to scalefit="1" so this figure would appear correctly in the
PDF version of the manual.
(From yocto-docs rev: 166305f39859e11f15702a8f6eb1f5a524b589c4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Two additional section placeholders added for changing kernel
configuration and for adding kernel recipes added to the appendix.
(From yocto-docs rev: 27c0ea3dddb652c4367b097b612edbdb76d7725d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
After getting the example in kenerl example appendix working I discovered
much that was wrong in this overview. The overview attempts to generalize
all the situations for kernel modification. These include code changes,
configuration changes, and the addition of new recipes. It also includes
the situation where a developer wants to gather all the changes into a
separate layer for distribution and for when they want to push them up
the tree.
(From yocto-docs rev: 5498d7b38d3a2f14befa82b66af9919a449e0f04)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are some issues with the fact that the build process parses
all kernel .bbappend files whether they are used or not during the
build process. I added an extra build configuration note regarding
editing the .bbappend file. I noted that you either have to edit
every .bbappend file and comment out the COMPATIBLE_MACHINE statement
or simply remove all the kernel recipe append files except the one
you are interested in.
(From yocto-docs rev: ecece911a1623b9b12bb73bab50891fbdea7afbe)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I changed 'linux-yocto-2.6.37.bbappend' to 'linux-yocto_2.6.37'.
Also started a new note.
(From yocto-docs rev: c78a937b9df37f68beee31c51914811ddd4d771f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
Had to tweak the viewing area to get two figures to display
correctly in the PDF version of the file.
(From yocto-docs rev: 89b2618e11c05744f54a9fbd39cd899117a2affc)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added the figures/kernel-example-repos.png to the list of tarfiles.
(From yocto-docs rev: 8967a9b8ae6fb27f7c0aeb44c2d04eacba98ed81)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This figure provides a conceptual look at the repos and file structures
needed to run the example. Or, for that matter, to get set up to
modify the kernel.
(From yocto-docs rev: d469449f1d416a6a96bdde297daae68a9f3094e5)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I performed a major re-write of this section that touched all
aspects of it. This was necessary due to the fact I could not get
the example running because of not understanding the repo location
and branch needs to set it up.
(From yocto-docs rev: 160e66d0c8ddf11584c53306def916a45a05f62b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I separated the section that explains how to set up the poky-extras
git repository. This used to be in the kernel area right after
creating the bare clone and the copy of the bare clone. I thought
it would be better as a stand-alone bulleted item.
(From yocto-docs rev: 4ea917c7218f238e2b0d2bb377a97f4b1f5eb1f6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added instruction on how to set up a bare clone of the linux yocto
kernel files and then how to create a clone of the bare clone.
Finally added a part about setting up the meta-kernel-dev repository.
This setup should do it for those that want to modify the kernel and
not have to download source files from the upstream everytime they
make a change.
(From yocto-docs rev: 90ae8249d119d5db17507eea37eb6deb0822a682)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added a new section for the example that ensures the image for qemu
is available.
(From yocto-docs rev: a3ca52cb7088ec85502b507093082f35f23befd4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I placed an anchor point in the Index of Downloads bulleted item for
reference from other documents.
(From yocto-docs rev: 7d4f96d20667fbf5f52e25840b39f1994b1c4cd3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
tightened up the section that talks about setting up the environment
and starting qemu. I just added a little more clarification on the
kernel-image variable.
(From yocto-docs rev: 54c037d45ca46c09544dae67793237c76a1205f5)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the downloading the filesystem section to have an inclusive list
of image profiles and a reference to more information on that. Also
included more explanation of the two types of image tarballs.
(From yocto-docs rev: 14965cbedd719beb6191771c6dcb92742f4229bf)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
