Folks, As we get ready for M3 opening up shortly, I wanted to get folks aware of where we are with M2 and the recipe updating process. Based on my rough reckoning, we had about 266 recipes that

Hi all, This is the Sanity Test Report for M2 20101211 build. QA finished sanity+weekly test cases. Toolchain testing and qemuppc testing is blocked because there is no image built out. There

Hi, all, I start looking into our LTP failures now and get some cursory picture. ( http://bugzilla.pokylinux.org/show_bug.cgi?id=169 ) I tried qemux86 sato image from latest M2 build, and there're

Liping, The newly update scripts are at: http://git.pokylinux.org/cgit.cgi/poky-contrib/commit/?h=jzhang/installer_ne w With following changes: more messages cleanup, fix issues: 1) download all the

Hi, Jessica I have checked in the changes based on your changeset. Now nfs extraction folders could be deleted/operated by user. And also, the config file is changed since the version number now is

OK. It's caused because you changed 0.9-post to 0.9+snapshot. The version is now defined in the yocto_installer.conf. Also, for solving the user priviledge problem, I will change user nfs root owner

Liping, All my changes are captured under: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=jzhang/installer My installation stopped at: ./yocto_installer_internal: line

Hi, Scott Thanks for the review! Sure, I will use the script following distro-team conventions. And also, $MYNAME will be used in the final patch. And the debug line for building will be removed

One final thing - when you resubmit your patch this time, could you use the create-pull-request/send-pull-request scripts? That way the patch can be pulled in by Richard or Saul with minimal effort,

Thanks for the patch, Criping. This patch includes the addition of a do_configure_prepend step for the libxfixes recipe? That looks like some debugging info crept in that may not have been

We are pleased to announce some new resources on the Yocto Project. When you build a custom Linux distribution for your device using the Yocto Project, you can also build an Application Development

The leading part of the image name is dependent on the type of kernel we are booting. ]> grep KERNEL_IMAGETYPE qemu* qemuarm.conf:KERNEL_IMAGETYPE = "zImage" qemumips.conf:KERNEL_IMAGETYPE =

Hi all, This is latest Yocto bug trend chart. Submitted/Fixed bug number both raised in last week(20 vs. 19). The open bug number is 160 now. Best Regards, Jiajun

Hi, Jessica For tracing the file, I temporarily checked in all needed files into my branch: http://git.pokylinux.org/cgit/cgit.cgi/poky-contrib/log/?h=lke/adt_installer_initial If you have some

Hi, Jessica I have updated the script and it is still put under http://llu-piketon.sh.intel.com/installer.tar. 1. For util path problem, the solution is that we need to find the dirname of running

What's more, I found sometimes, for example, there's no symbolic links, so the name is very long and strange. Such as one ppc image:

This is done, but there's a bug (581) against blktrace that I need to look at. BSP work not on the schedule has pushed this out - I'll be getting to it as soon as that work's done, sometime this

Hi, Jessica I found qemu bin file name convention is different for different archs, for example, for x86, it is bzImage-qemuXXX. For arm, it is zImage-qemuXXX. My question is why it is bzXXX or zXXX,

Oh, it's caused by the include grammar. I need to check how to solve the relative path problem with include grammar in shell script. It should not be difficult. No problem, I will unify all error

Hi, Scott I have updated the patch and tested with poky-tree mode (arm, x86). Since kvm and serial needs special processing, so for avoiding repeating the code, I will exclude serial and kvm in