perusing the QS guide in prep for giving a yocto talk this week to my local LUG and some cosmetic changes i can submit a patch for: 1) www.yoctoproject.org/downloads clearly redirects to downloads.yoc

perhaps outside the scope of QS, but might it be worth adding a short section on appending something like this to one's local.conf file before starting the download? PREMIRRORS_prepend = "\ git://.*/.

all the docs recommend twice the number of cores (AFAICT), yet the template local.conf file suggests that, for a quad core, the value of 4 would be appropriate. shouldn't that say 8? same with PARALLE

if that's the case, anyone object to my submitting a patch to update local.conf.sample appropriately? rday

(yes, i *am* going to be this pedantic all day long. at least until football starts.) over at http://downloads.yoctoproject.org/releases/yocto/yocto-1.1/toolchain/, a couple optional fixups: 1) the to

QS guide suggests build process using sato will use about 50G of disk space. where does that figure come from? i just did a configure and build of core-image-sato for beagleboard on my 64-bit ubuntu 1

A number of cosmetic fixes for the Yocto Quick Start Guide: * spelling/grammar fixes * Updating URLs to point at new location of downloads/toolchains. * Correct name of toolchains, prefix of "yocto" -

i can believe that, i just want to make that claim in the QS guide a bit more precise and explain what it represents. ah, well, tomorrow's another day. rday

One more set of patches for the QS Guide, covering the remainder of the Guide from the kernel section to the end; mostly updating filenames and URLs to reflect what actually exists these days. Signed-

i wish i had more info on this. the topic came up when i was chatting with the people who run the fedora arm farm at seneca college, so they're pretty knowledgeable. the symptom was that after they in

yes, that's a judgment call, someone else can make that decision. obviously, not a critical change. i suspect you've already seen the two patches i posted yesterday. just apply what you think is usefu

i know about the PREMIRRORS stuff in the poky reference manual -- i was just toying with the idea that knowing how PREMIRRORS works would be useful, even for a beginner. perhaps i'm not using it prope

that's what i would normally use, assuming that having an overly high value for either of those settings can't possibly hurt. if that's the consensus, i can adjust the references to say 2x everywhere

just noticed that Appendix D of the poky reference manual lists the supported images, and suggests you can see them all with: $ ls meta*/recipes*/images/*.bb but the list in that appendix doesn't ment

i'm sure there's a simple solution for this but i'm building core-image-sato-dev for the beagleboard on my 64-bit ubuntu system and the build eventually fails with *numerous* errors of the form: Proce

ironically, i'm working on this very example and something in the dev manual doesn't look right. section A.5.2.1: These commands take care of the recipes-bsp recipes: $ rm -rf meta-mymachine/recipes-g

... snip ... let me finish following this through and i'll make notes on anything else that looks odd and report back. rday

some questions/observations as i'm getting close to the end of this appendix (some of which you've already seen and addressed), all done on my 64-bit ubuntu 11.10 system: * section A.3: rather than fo

On Tue, 1 Nov 2011, Tom Zanussi wrote: ... snip ... > Or at least that's what I'm building now. I'll post the full transcript > assuming I get a good build out of it... i'm also into task 301 of 4426

Some fairly straightforward to Appendix A: BSP Development Example in the Yocto Project Development Manual: * Remove obsolete commands * Fix spelling mistakes. Signed-off-by: Robert P. J. Day <rpjday@