Tested-by: Tom Zanuss <tom.zanussi@...>

Hmm, not following you here - why would I want a new image recipe for systemtap? Systemtap fits in with the other profiling tools in the task-core-tools-profile as far as I can see; this patch

Wouldn't it make more sense to add systemtap to and image recipe, either a new recipe or a bbappend? Also, it seems to me that RRECOMMENDS would make more sense than RDEPENDS - as it isn't required

From: Tom Zanussi <tom.zanussi@...> To configure crownbay, crownbay-noemgd, fishriver, jasperforest, n450, and sugarbay as compatible machines for systemtap. Signed-off-by: Tom Zanussi

From: Tom Zanussi <tom.zanussi@...> To configure this is a compatible machine for systemtap. Signed-off-by: Tom Zanussi <tom.zanussi@...> --- .../systemtap/systemtap_git.bbappend

From: Tom Zanussi <tom.zanussi@...> Add a 'utrace feature' that turns on the kernel options required for utrace, used mainly to enable userspace tracing for systemtap. Signed-off-by: Tom

From: Tom Zanussi <tom.zanussi@...> This adds a utrace feature, in support of userspace tracing for systemtap. It's been tested on actual x86 and x86-64 hardware, as well as qemux86-64 and

From: Tom Zanussi <tom.zanussi@...> Used by SystemTap. Patch generated by diff of 2.6.37 base and utrace branches of the official utrace git repo

From: Tom Zanussi <tom.zanussi@...> This adds support for utrace to linux-yocto, for userspace tracing in systemtap. Please pull into the yocto/base branch linux-yocto. Pull URL:

From: Tom Zanussi <tom.zanussi@...> Removing any old references to systemtap from meta means we need to add it here. It also adds systemtap support for the other, previously uncovered

Hi all, The open bug number of last week increased to 210. QA finished Yocto 1.1 M1 testing with no critical bugs open now. Bug status of WW24 could be found on

It's my intention to get the document updated ASAP so that we don't confuse anyone else as to which version to download. Regards, Joshua -- Joshua Lock Yocto Build System Monkey

I have pending fixes for a number of the build_errors list, many where dependency issues that build on a full build, I am going to research those. We have bugs for alsa-tools, gobject-interospection

Thanks Joshua. I assume that http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html won't be updated until the next release (if this makes it into the next release)? And the

Please let me know if you would like to add anything else to the Agenda. - Song Agenda: - Final check on Yocto 1.1 M1 release - 5 min (Song) - Review Yocto 1.1 M2 schedule and Release Criteria -

Hello, As a data point for where we stand in ensuring our packages are producing documentation, I have some scripts which build all recipes (using the output of bitbake -s, not world), and then check

This allows meta-intel sub-layers to coexist with meta-yocto when building formfactor for different machines with the same layer setup. Signed-off-by: Paul Eggleton

The following changes since commit 01d1a545477cbc1b2a1da5b66edb52fd9e783206: meta-intel: update kernel SRCREVs (2011-06-06 16:13:01 -0500) are available in the git repository at:

Just for interest, for the first time ever I did a dump out of profile information on the python side of bitbake's task execution for all tasks of a core-image-sato build. I enabled profiling of each

Op 10 jun 2011, om 10:44 heeft Richard Purdie het volgende geschreven: Do you have pretty bootchart graphs for that? regards, Koen