Ah, documentation :) excellent -- Jeff Osier-Mixon http://jefro.net/blog Yocto Project Community Manager @Intel http://yoctoproject.org

<jeffrey.osier-mixon@...> wrote: it means that all patches have a field 'Upstream-Status' and for most of them it reflects the status of patch w.r.t. upstream of given package

Not quite - we still have most of the patches, it's just we've now declared on each and every one whether it can be/has been upstreamed. Cheers, Paul -- Paul Eggleton Intel Open Source Technology

This sounds fantastic, and I'd love to create a page on the website reflecting this. Just so I am clear, what exactly is this 100% of? Do we have no local patches to upstream projects at all? On Wed,

Nicely done, all! I'm hoping we have can a reputation as a strong supporter of upstream projects, giving back wherever we can.

Have you installed the Virtualbox guest additions within your VM? Fwiw I've not run into any issues doing this with a Fedora 14 and Fedora 16 VM (other than the builds themselves being dog slow). I

Joshua, Did you consider taking this patch and adding it to the proper recipe? -M

Now, I want to load my module at startup. The preferred way to load my module at startup would be by to place a file called hello-mod in /etc/modutils Is this correct? Is there a recipe already

Qemu starts apparently fine, but the qemu window stays black.

So, what is the problem?

We do have a lot of open questions that we will answer in good time: 1) Should the application be executed as root or as some user or as nobody 2) Should we trim the image? (we are not short on

Hello all, Forgot to mention, the issue already has been reported for boost.m4 at https://github.com/tsuna/boost.m4/issues/26 I have added my patch (not yocto specific one) there

Hello all, While trying to build my user space application in yocto, the boost.m4 was looking packages in the host (i.e host contamination, thereby resulting in configure error). This appears to be a

Just to clarify: videos show relevant functionality to a specific design piece. The fact that a video does not show something it doesn't mean the functionality has gone away. If I showed everything on

Saul Wold wrote: Who sets the Upstream-Status? Are there guidelines how to do it? I spoke to the author of curl and mentioned the two patches in Yocto against it, both of which are marked as

Very impressive indeed. I run a Raspberry Pi website at the moment, and in due course I plan on (attempting) to write a BSP for Yocto and maybe do a blog post on setting up quemuarm so people can play

We finally did it! After getting some final patches yesterday, we made it to 100% with patch Upsteam-Status. Total Patches Files: 1243 All Upstream-Status: 1243 Fix Upstream-Status: 0 Need

Hi, I have build x86 qemu image using "bitbake -k core-image-sato" following the instructions given at http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html I'm running Ubuntu

Hi, I've recently found this amazing project and I'd really love to contribute to it. So, I have a question. Is there any ongoing effort or interest on adding Pandaboard to the supported hardware? If

becomes the UI. development core-image-sato and writing a full screen app on top of it. Likely to be written in .NET (mono). A prototype (proof of concept) has been successfully developed :-) may