linux/poky.git/documentation/dev-manual/dev-manual-bsp-appendix.xml, branch 1.2_M2.final

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

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

2011-11-08T16:26:32+00:00

Per Tom Zanussi's suggestion, we added a footnote to the paragraph instructing the user on build problems for the example. I don't have clean fonts in the HTML version of the output. I am still working on figuring that out. Reported by: Tom Zanussi (From yocto-docs rev: 30fe7bd239292ed92f76fbc2f1fad62469f7fe9b) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation/dev-manual/dev-manual-bsp-appendix.xml: Tom Zanussi edits.

2011-11-08T16:26:32+00:00

Some wording changes to keep things accurate. Also inserted some " " characters in some headings to force an extra space between normal font and courier font words. It appears the PDF version of the generated manual shoves these words together with no intervening space. Looks like hell. Reported by: Tom Zanussi (From yocto-docs rev: 5dcb9ae99f1752599fd56a276ccafd79a52334f8) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation/dev-manual/dev-manual-bsp-appendix.xml: Robert P. J. Day edits

2011-11-08T16:26:31+00:00

As Reported by: Robert P. J. Day. Two corrections identified by Robert. One is a wrong reference to the tarball needed for the example. The other is a more complete description of what the appendix is trying to accomplish. (From yocto-docs rev: 387c6cbd84bafd7f15c064a8e801d0750b0b4007) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation/dev-manual/dev-manual-bsp-appendix.xml: Added text to find t-ball

2011-11-08T16:26:31+00:00

As Reported by Robert P. J. Day. Robert indicated that it was a bit of a search to find the tarball for the example. Tom suggested that we have some text that helps to locate the Crown Bay no-emgd tarball for edison. I added some clarifying text to help. (From yocto-docs rev: d21120bbae81f58a9816cf56c61181d287afd295) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation/dev-manual/dev-manual-bsp-appendix.xml: BSP example scrub

2011-11-08T16:26:31+00:00

As Reported by Robert P. J. Day. Robert was working through this BSP example in the development manual and ran into some problems and some confusion in areas. This launched a long "help-desk" session with Tom Zanussi. In addressing Robert's issues, Tom decided to make a run through of the example as it was written. For the most part the example was sound but needed some technical tweaks as well as some expansion of the text to make things clearer. Tom submitted the patch that addressed these concerns. Scott Rifenbark reviewed the patch and further modified some of the writing to make it consistent with the existing writing in the manual. (From yocto-docs rev: deda08b372c02889398d24ae7159f8b2fbe3c8cf) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation/dev-manual/dev-manual-bsp-appendix.xml: Robert P. J. Day edits.

2011-11-08T16:26:31+00:00

Two typos fixed. (From yocto-docs rev: 6d99eb7f728b812be37a3865cbebd3c4cb4b67be) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation/dev-manual/dev-manual-bsp-appendix.xml: changes to references

2011-10-04T22:12:06+00:00

More changes to the internal section references. Using rather than to get rid of the section number in the reference. (From yocto-docs rev: 4351fd4898c517e25235611893b1cd059cbcc2f8) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documenation/dev-manual/dev-manual-bsp-appendix.xml: fixed reference form

2011-10-04T22:12:06+00:00

I am using a certain form to reference other sections in the current or other manual. I updated the references to follow this form. (From yocto-docs rev: 2ba41ac2f355dbe66af19e356f9246b7485585b5) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie