Our last IRC Bugscrub during the master stabilization cycle will be tomorrow Thursday February 24th @ 07:00 GMT / Thurs 24th 23:00 PST / Fri 25th 15:00 China If you can make it, please take some time

All, Today I implemented some modifications to the current autobuilder infrastructure that I would like to go over so no one is surprised. Most of these won't effect people's day to day operations

Merged to master, thanks Bruce. Cheers, Richard

Hi Yocto Team and Julie, Below is my assessment: a. Which architecture you chose in step 3. 1. Qemux86 1. Poky-image-sato 2. Qemuarm 1. Poky-image-sato 2.

Pursuant to the notice sent on Friday, February 18th, the Yocto Release Tracking Meeting was held on Tuesday February 22nd 8-9:15am Pacific time. Notes are below for all interested. Attendees:

Hi all, Below is my assessment. Regards, Helia --- Alpha tester: helia.correia@... Technical background: Medium a. Which architecture you chose in step 3. Targets:

Fixes [BUGID #488 #734] Enable audio for qemux86/qemux86-64 via the following kernel configuration options. CONFIG_SOUND_OSS_CORE=y CONFIG_SOUND_OSS_CORE_PRECLAIM=y CONFIG_SND_RAWMIDI=m

Richard/Saul, This Fixes [BUGID #488 #734] As discussed, this enables the configuration options for qemu audio for x86/x86-64 (limited to this for now). I did build and boot testing (but couldn't

Hi, jessica Yes, for clean testing, I choose to clean all installed materials before Starting testing, including installed material under /opt/poky, all compiled test project. Everything is newly

Setup details: * Image was created for 'poky-image-sato' targeteting 'qemux86' * Configuration was slightly tweaked from default: PACKAGE_CLASSES was set to 'package_deb' instead of the default

Is there a simple way to set a root password in the images that are created? I'm currently using sed in a .bbappend to edit the root entry in the password file, but this doesn't 'feel' right

The symlinks are created. One gotcha for ADT installer testing is, please completely delete the toolchain that installed from the toolchain tar ball under /opt/poky. Since the toolchain tarball

a. Which architecture you chose in step 3. I used poky-image-sato. b. How easily you were able to build an image and boot an image. I did it quite easily. - I installed the

Hi all, This is the weekly test report for 20110217 build. There are 3 new bugs found with this build. Toolchain testing is BLOCK because there is no tarball built out.

How do I get v86d in to my rootfs image? I'm building using my own machine.conf (LX800) and I've got a v86d_0.1.9.bbappend file so I can add compatibility for it: COMPATIBLE_MACHINE_LX800 =

Hi，Jessica Thanks! And I am now writing a script for automating our toolchain test. Currently: Test input 1) Test_image (meta-toolchain tarball, target rootfs tarball, adt_installer tarball) 2)

Ke, Liping wrote: They were manually copied and since you don't have account, I'll create the symlink for you...

Merged to master, thanks. Richard

Hi all, This is latest Yocto bug trend chart for WW08. We have 42 bugs marked as fixed in last week, which makes current open bug number decrease a lot, from 170+ to 160. Best Regards, Jiajun

1 more issue that blocks meta-toolchain-sdk for many targets: Commands are meta-toolchain-sdk -k Changed to