Martin, OK, so regardless of what the arch was finally getting set at, in this case since “-marm” was in the GCC compiler options it was always compiling all the code in ARM mode and never in

Using and not using thumb was also controlled not only by TUNE_FEATURES (MACHINE defines that) but also by ARM_INSTRUCTION_SET (DISTRO defines that). So you weren't building with thumb enabled even

bitbake-diffsigs is the basic tool to compare signatures when those have changed. Find the siginfo / sigdata file for one of the early tasks that executed and compare them to see what changed. How

I'm in the process of upgrading from the dizzy branch to the fido branch, and I'm still a little confused about some tune changes that I'm seeing. I'm using an Atmel AT91SAM9G25 processor. The

Upgrade status email should indicate the URL of the log folder instead of the tar URL [YOCTO #10670] Signed-off-by: Edwin Plauchu <edwin.plauchu.camacho@...> --- upgradehelper.py | 2

Makes sense, I'll submit soon. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no

Makes sense, I'll submit soon. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no

Interesting, I hadn't thought of using it like that. When doing this, does it download the "from-0" pack files? "swupd bundle-add" uses those; I'm less sure about verify. It would have to detect that

Compare the signatures of these 2 native builds. I'm still using sstate-diff-machines.sh to create archives of sstate signatures for interesting builds, so that I can easily compare them with other

Yes. In our case we can only provision the NOR flash in the factory (which is too small for the real file system), so I have the swupd-client inside a small initramfs in NOR flash, and from there I

I have a build machine where I build for lots of targets. On all of these targets (save a primary), I set the SSTATE_MIRROR to point to the sstate-cache of the primary target. I always build for the

Let's discuss here and if necessary, summarize in the wiki. I might have seen it at some point, but I hadn't paid that much attention then and it's a good, timely reminder. I'll link to it from the

You should use latest master where we have switched to tarball fetch especially http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/commit/?id=716b6a9cd7f24a8bacd539bb40519d185e3f963a

Patch Series created without a cover letter are named using a non-descriptive generic string. This change names the series using either the first 30 characters in patch #1 plus the remaining patches

From: Jonathan Liu <net147@...> A patch is backported to check if the firmware loaded a device tree blob into memory and set the fdt_addr variable if it is found. The U-Boot script will then

Jonathan Liu <net147@...> wrote: Will do. Currently in progress, will send once I've given it a quick test. Thanks, Paul Barker

i want to get a drone, and i'd prefer that it was linux-powered -- specifically, i'd like an ARM-based drone with an OS created by yocto project. i can see that there's an atom-powered drone

In the wiki or here? I'll be out for the next week, but when I come back I will write some more. BTW, you probably know this:

Patch Series created without a cover letter are named using a non-descriptive generic string. This change names the series using either the first 30 characters in patch #1 plus the remaining patches

Sure, no worries. A.