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

Ke, Liping wrote: Why we must run the script under the adt-installer directory? Actually I tried to run under $HOME or / but specifying the full path to yocto_installer, and got the error: [ADT_INST]

Joshua Lock wrote: Since the DATE element is only included in the DISTRO_VERSION for development, then I'd suggest that our SDK_VERSION logic to be as: If DISTRO_VERSION contains snapshot SDK_VERSION

Enable the kernel configuration values required for blktrace by default. Individual boards can opt out as required. Signed-off-by: Bruce Ashfield <bruce.ashfield@...> ---

Richard/Saul, This has been queued for some time, but was held up for the 2.6.37 work. Enable the kernel configuration values required for blktrace by default. Individual boards can opt out as

Lianhao, This may require Richard to look at a little more closely, I do notice that you are missing the LIC_FILES_CHKSUM, for this on you can use one similar to recipes-core/tasks/task-base.bb The

Mark, go ahead and submit it, so that we can have it available, and can make the call, there is clearly going to be a rebuild of M2 due to the kernel failures, but I am not sure that I want to bring

Bruce, Thanks for the fast turn on these fixes, there are pulled into master and the 1.0 M2 branch. Sau!

Mark, go ahead and submit it, so that we can have it available, and can make the call, there is clearly going to be a rebuild of M2 due to the kernel failures, but I am not sure that I want to bring

fakeroot doesn't intercept or alter fopen(). It'd be better to test something that is actually affected by fakeroot for a comparison. :) fakeroot only traps things like stat and chmod, pseudo

Pending Patch is in distro Stage Phase one status was best effort on the the update list, and I will have a summary later this week. All recipes now have SRC_URI Checksums, the checking work is part

I'd second Scott's opinion here. I wasn't marking my bugs as verified, since as a submitter, I've never had to do this in 10+ years in the 'biz'. Cheers, Bruce