Tian, Kevin wrote: As Kevin mentioned, can we derive SDK_VERSION from DISTRO_VERSION so only contains 0.9?

Hi, Jessica I have put the installer script tar ball in the below links: http://llu-piketon.sh.intel.com/installer.tar You can have a try. Below is some key notes: 1. since now version has

I think Josh has laid down the base for multiple version SDK support. The only problem is: SDKPATH = "/opt/${DISTRO}/${DISTRO_VERSION}" which obviously is not what we want. We need a similar

Hi, Jessica & Josh When we are trying to run installer script on lianhao's x86_64 machine, we found if the images are build in two days, according to current version naming convention, some of the

During the last phase of the recipe factoring, the board compatibility lists ended up in the wrong place, which meant we had an incomplete list of boards, and the same set of boards for both kernels

During the last phase of the recipe factoring, the board compatibility lists ended up in the wrong place, which meant we had an incomplete list of boards, and the same set of boards for both kernels

<bruce.ashfield@...> wrote: I made some changes (patch will be out shortly), they fix the emenlow, and I can easily build the fsl and beagleboard out of the box with the changes in place.

Fixes [BUGID: 585] The qemuppc irq handling was only partially updated to 2.6.37, this completes the job. qemuppc builds and boots with this change. Signed-off-by: Bruce Ashfield

Somehow the ppc32 irq routines were only partially updated to 2.6.37. I'll have to check later to see what happened, since these were all built and booted here. The fix is simple enough, here's the

Both those boards are building random kernels .. one is building the omap-pm (which is broken) and the other built linux-dummy. So something went wrong with the merge of the new kernel, and could be

For beagleboard, http://autobuilder.pokylinux.org:8010/builders/nightly-release/builds/146/steps/shell_46/logs/stdio/text. For mpc8315e-rdb,

Is there somewhere I can check a log of the build errors ? We flipped in the 2.6.37 kernel and associated tools, but the any hardware targets should still be building 2.6.34 and be unaffected. If it

Yes, please respin the patch with those changes. Thanks! Scott -- Scott Garman Embedded Linux Distro Engineer - Yocto Project

Hi Saul, Nightly build is near finished now. PPC and some non-x86 real hardware target building failed. I begin downloading them now and will start QA testing. Best Regards, Jiajun

Hi, Scott So the conclusion is that I should keep the old (serial nographic) option while adding the new "<-XXX -XXX -XXX>" option? OK. I will send out the modified patch to you for review

[Resend with correct mailing lists] Yocto / Poky Folks: Thanks to everyone's hard work, we are currently on working getting the first build of M2 started and available for QA testing on Monday. I

Richard, I've seen your recent bitbake change that reverts exec to fork, is there intended to be the preparation for pseudo changes? Do you have some kind of plan of next steps? Btw, since pseudo

Hi Lianhao, These patches are just what we need, thanks. We do however need to go one step further and complete the change which is to remove the idea of "cross-canadian" packages from the

do_install and all tasks that work on the output of do_install run under pseduo which can mean the permissions on disk might not match the real permissions as seen within a pseduo session. To

commit e388771458b4ff3ad81ab70e390b24d069647da4 in the upstream kernel factored/cleaned the SP804 timer code. This commit exposed issues in the qemu timer emulation that was dependent on the old