I think Joshua's response is in line with what I'm thinking. Distro is where all the policy is specified. The image is just a list of pieces of software to include, its not meant to be much more than

yes there was a patch to rename that to IMAGE_EXTRA_INSTALL or COREIMAGE_EXTRA_INSTALL

These all sounds like policy (and therefore distro) decisions to me. As with much of our system there's no hard and fast rule but this certainly sounds like a distro to me. I think it's perfectly

I'm trying to wrap up my work on meta-tiny and integrate it into poky proper. I'm having some difficulty drawing a line between the responsibility of the distro definition versus that of the image

Hmm, your analysis seems sound enough. We do call the setVariable command on the cooker which I had expected to ensure the variable was set appropriately without a reparse. We can easily add a patch

Attendees: Sean, Beth, Tom, Richard, Darren, Bruce, Dave, Joshua, Mark, ScottR, Saul New Action Item List: * Action item Review - 5 min 1. Mark will review unsorted features from Wind River team

If you use the prebuilt binaries they have EMGD already included. I had to download and install the EMGD before baking it all, as mentioned in the README below: Downloading and extracting the

In the .config, do you see this?: CONFIG_DRM_EGD=m If not, then for some reason the options in drm-emgd.cfg from the drm-emgd feature aren't being picked up. Let me try a build myself here from the

I think that I did. Included is an excerpt that says that I need not do anything except bitbake core image sato when MACHINE="crownbay". As instructed, I followed the steps in section one (Building

Check out the README file in the meta-crownbay directory. There are instructions on integrating the EMGD driver files into the build. Jim A

I built the "crownbay" (not crownbay-noemgd) image as outlined in the E660 development kit

I think we should pull in the patch for 1236 from master, update the DISTRO_VERSION and respin. Any thoughts? Joshua -- Joshua Lock Yocto Project "Johannes factotum" Intel Open

The bug you filed needs to get fixed, when it does, the MACHINE_FEATURES += "bluetooth" combined with the stock linux-yocto kernel will combine with the definition of task-base-bluetooth to give you

Agenda: * Opens collection - 5 min (Saul) * Yocto 1.0.2 and 1.1.1 point release update - 10 min (Josh/Beth) * Yocto 1.2 M1 Status (features development) - 10 min (Saul/Beth)

directly = git repository commits? What is the value of having base and standard as separate branches? Isn't base easily derivable from the standard git history? Still if it isn't used anywhere, then

All, You may have noticed over the past few days some slowness when trying to access the autobuilder or the downloads area on the yocto websites. This was due to someone attempting to wget the entire

<paul.eggleton@...> wrote: I'm not 100% sure what I did to bring up our CentOS box but I think all I needed was to install python 2.6. -M

EPEL has a python26 RPM which works perfectly well if you add a ~/bin/python symlink to python26. No need to compile python from scratch. -- Michael

It's been a while since I wrote them, and therefore since I tested them, but: https://wiki.yoctoproject.org/wiki/Poky/GettingStarted/Dependencies Joshua -- Joshua Lock Yocto Project

I can definitely see a compelling reason to mark CentOS 5.x as supported, but the problem with it is it doesn't come with Python 2.6, so BitBake won't work out of the box (actually right now it