linux/poky.git/documentation/dev-manual/dev-manual-bsp-appendix.xml, branch 1.2_M4.rc4.0

documentation/dev-manual/dev-manual-bsp-appendix.xml: minor edits.

2012-03-23T14:24:47+00:00

(From yocto-docs rev: f109ca75f7a1d8fdd6051da989adda2207049209) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation/dev-manual/dev-manual-bsp-appendix.xml: removed quotes

2012-03-23T14:24:47+00:00

(From yocto-docs rev: f4f599db60f3da74ac37db54cc812f9836afc893) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation/dev-manual/dev-manual-bsp-appendix.xml: Added .bbappend

2012-03-23T14:24:47+00:00

(From yocto-docs rev: 3c7e51fa6ad5eb69f4b09a9041714044edf585d7) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation/dev-manual: Converted to use poky.ent

2012-03-23T14:24:43+00:00

I converted the hard links to use the variables as established in the file poky.ent. Also, Cleaned up some bad text in the term "Yocto Project Files." Looks like a cut-and-paste problem. (From yocto-docs rev: e2e20bf4895d80dae73595e93132f37fb31121d1) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation/dev-manual: Reference link clean-up

2012-03-08T20:07:51+00:00

I made another pass through the document and cleaned up some mistakes and also removed redundant links to manuals where I had already provided a link to the specific section. (From yocto-docs rev: 5da8ffe100127f5fe4bfd2b478f177d6bef3a968) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation/dev-manual/dev-manual-bsp-appendix.xml: Edits to examples

2012-03-08T20:07:50+00:00

Updated the tarball and Git repo example in section where user is getting the source files. I was not using the default Yocto Project Files top-level name for the tarball method. Reported-by: Joshua.lock (From yocto-docs rev: 770c6799ea58df3d81df8f466f1bb9878532a995) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation/dev-manual/dev-manual-bsp-appendix.xml: tags/branches edits

2012-03-08T20:07:49+00:00

Edits to the section describing how to set up the YP files before the BSP example. I am working with Joshua Lock on these to settle them down. The edits are trying to establish understanding between a Git repository and a tarball... just what the user has a hold of after getting the files by either method. Reported-by: Joshua Lock (From yocto-docs rev: ddb8333ea2f9898b7016ca01887e1acdc0581c06) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation/dev-manual/dev-manual-bsp-appendix.xml: edits to poky repo setup

2012-03-08T20:07:46+00:00

There is confusion as to how to set up the Git repository and be sure you have the snapshot of the release. I have changed the description to use a tag rather than the branch names. The stuff is out for review with Josh. (From yocto-docs rev: 2521873e1bf8e1ad398fae4b7297f8746a34258f) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation: BB_NUMBER_THREADS and PARALLEL_MAKE suggestions

2011-11-25T15:24:19+00:00

Text that suggests setting the BB_NUMBER_THREADS and PARALLEL_MAKE variables to speed build time has been updated to suggest a setting of twice the number of host cores supported. The 2x number came to light through a discussion on the project mailing list initiated by Robert P. J. Day. Reported-by: Robert P. J. Day (From yocto-docs rev: 1846b41a595b7bd905ca828eaa04112d1533d7a1) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation: Changed all manual links to point to "latest"

2011-11-25T15:24:17+00:00

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 Signed-off-by: Richard Purdie