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

One of my friends sent me a funny quote he saw today: "The most amazing thing about this device is the ability to download a Broadcom spec sheet without a pile of signed NDA's, 4 months

Yes, I'm on the list to get one (from Nokia's QtonPi program) end of Feb. and plan to use Yocto. Regards, Brian

Somehow they managed to convince Broadcom to release a datasheet for the SoC: http://www.raspberrypi.org/archives/615 Cheers, Joshua -- Joshua Lock Yocto Project "Johannes factotum"

The features are defined in core-image.bbclass: http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/core-image.bbclass Most of them translate into one or more task recipes

I built core-image-core and it works and is basic. So it's not a really small Sato??? I have difficulty understanding the difference in IMAGE_FEATURES and IMAGE_INSTALL. To me IMAGE_INSTALL is clear

Fond the bug - it was a problem in the recipe FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" I was missing the ${PN} at the end. Bruce - Thank you for all the help :-)

A key selling point of the Yocto approach is to provide a highly customised OS for your target application, rather than taking an existing solution and stripping it back. 2. is the antithesis of the

We are still in the very early stages of architecture design and development For now we are leaning towards keeping everything that comes with core-image-sato and writing a full screen app on top of

Hi Belen, Thanks for clarifying. Shane - I noticed at least one bug has been closed because the second video didn't show the features (#1804) - seems like this isn't what was intended by features

Confirmed - after following all the steps in section II of the README in meta-intel/meta-crownbay - the build worked.

On Tue, Feb 7, 2012 at 10:49 AM, Tom Zanussi <tom.zanussi@...> wrote: I can confirm that using the master branch is the way to go to make this easy. I documented my test of it at

This may be a dumb question, but I'll ask anyway. Suppose you have a project where you need a very custom user interface. Not just a series of applications that appear on a desktop like you see in

It looks like the problem may be forgetting to carry out the steps in section 'II. Special notes for building the meta-crownbay BSP layer' in the README. Note that this is no longer necessary if you

Chatted with TomZ on #yocto on freenode IRC, it looks like I did not perform the steps in section II from README in meta-intel/meta-crownbay. It is likely that that's what I am missing.

I am bitbaking core image sato for machine corwnbay (with the emgd driver) and the emgd-driver-bin recipe seems to fail. Here is the error. I searched the archives, but could not find

The paths issue your are speculating on was fixed by myself and Richard last November. I would suggest running bitbake-diffsig to determine the actual sstate differences. -M On Feb 3, 2012 10:51 PM,