Yocto Technical Team, Here is the agenda for our weekly meeting on Tuesday, May 10th at 8am Pacific. Thanks. - Julie Dial in: 916-356-2663, Bridge: 1, Passcode: 4926307 Agenda: 1) Review Yocto 1.1

There are valid reasons to build repositories without meta data present and there are times when this is an error. This change adds sanity tests to the build process to detect missing meta data and

The non-qemu compatibility references have been removed from the main linux-yocto recipe. This change restores them in the meta-yocto layer. Signed-off-by: Bruce Ashfield

The machine configuration of the non-core (non-qemu) machines exists in other layers. Moving the branch mappings, compatibility and SRCREVs of these machines out of the main linux-yocto recipe is the

Saul/Richard, The first two patches are a split and resend of the machine movement patch: [ linux-yocto: move non-core machines to meta-yocto The machine configuration of the non-core

Hi all, This is latest Yocto bug trend chart for WW19. The open bug number decreased from 182 to 175. All meta-intel BSP build still failed on autobuilder. Best Regards, Jiajun

My clone for meta-yocto is a bit old then, I checked this explicitly and it isn't a separate repo for me at all, hence why it's a single patch .. but wait. When I clone again from poky.git, it's still

I'm not particularly concerned about the kernel packages. I think we can ignore it. I'll update my script to not report these recipes. The main goal is to ensure that man pages and the like are being

Bruce, This need to be 2 pull requests, since the first 4 files are actually in meta-yotco, part of poky.git and the linux-yocto_git.bb is in OE-core Please split this into 2 requests, one for

I see "linux-*" in the list. What sort of documentation are we looking for? The linux-image* packages in Ubuntu, for example, include a changelog and a copyright. Thanks, -- Darren -- Darren

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

Acked-by: Tom Zanussi <tom.zanussi@...> Pulled into meta-intel/master. Thanks, Paul!

The machine configuration of the non-core (non-qemu) machines has moved to meta-yocto. Moving the branch mappings, compatibility and SRCREVs of these machines to meta-yocto should also

The machine configuration of the non-core (non-qemu) machines has moved to meta-yocto. Moving the branch mappings, compatibility and SRCREVs of these machines to meta-yocto should also

From: Paul Eggleton <paul.eggleton@...> Signed-off-by: Paul Eggleton <paul.eggleton@...> --- .../recipes-core/tasks/task-core-tools.bbappend | 2 ++

From: Paul Eggleton <paul.eggleton@...> This adds back the emenlow-specific pieces recently removed from oe-core. Thanks, Paul Eggleton <paul.eggleton@...> --- Paul

Hi all, This is latest Yocto bug trend chart for WW18. The open bug number increased a lot from 182 to 185. Best Regards, Jiajun

Updating the linux-yocto/2.6.37 SRCREVs to pickup: perf tool: Fix gcc 4.6.0 issues 1/1 [ Author: Kyle McMartin Email: kyle@... Subject: perf tool: Fix gcc 4.6.0 issues

The BSP bootstrap and -dev use cases can be applied against unbranched or repos without meta data. To allow the proper and safe processing of those repositories, slight modifications to the tools are

To support quick uprev and testing, it is desireable to build repositories that do not have embedded meta data. In this scenario the meta data can be automatically created or provided externally. This