Re: [yocto] QA notification for completed autobuilder build (yocto-3.1.rc1)

Hi Richard, Thanks for update on https://autobuilder.yocto.io/pub/releases/yocto-3.1.rc1 Unfortunately, I didn't received any mail for 3.1.rc1 or rc2 build notification. Looks like automated mail has some issues. I will now start the QA on

Re: [yocto] QA notification for completed autobuilder build (yocto-3.1.rc1)

On Mon, 2020-04-06 at 22:53 +, Poky Build User wrote: > A build flagged for QA (yocto-3.1.rc1) was completed on the > autobuilder and is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-3.1.rc1 I haven't see any "started QA" email about this yet. We have had some

Re: [yocto] sstate causing stripped kernel vs symbols mismatch

The kernel doesn’t have reproducible builds by default because of a handful of variables (including timestamps). If you rebuild, you get a different binary every time. Those can be changed and overridden so that you get consistent binary output (see here:

Re: [yocto] sstate causing stripped kernel vs symbols mismatch

On Tue, 7 Apr 2020 at 21:03, Sean McKay wrote: > If you’re interested, this is quite easy to reproduce – these are my > repro steps > >- Check out a clean copy of zeus (22.0.2) >- Add kernel-image to core-image-minimal in whatever fashion you >choose (I just dumped it in the

[yocto] sstate causing stripped kernel vs symbols mismatch

Hi all, We've discovered that (quite frequently) the kernel that we deploy doesn't match the unstripped one that we're saving for debug symbols. I've traced the issue to a combination of an sstate miss for the kernel do_deploy step combined with an sstate hit for do_package_write_rpm. (side

[yocto] Yocto Project Status WW14'20

Current Dev Position: YP 3.1 M4 - RC built and in QA Next Deadline: YP 3.1 release date 4/24/2020 Next Team Meetings: * Bug Triage meeting Thursday Apr. 9th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Apr. 7th at

Re: [yocto] initramfs with mdev: No match for argument: busybox-mdev

My guess is that your busybox isn't configured to produce mdev. Run "bitbake -c menuconfig busybox" and enable it (and save the config fragment for later) On 02-04-2020 12:08, y1dekel via lists.yoctoproject.org wrote: I am new to yocto. I have read some messages on this forum which suggest

Re: [yocto] Novice question on makefile in yocto environment

On 30-03-2020 05:08, Raghu Icecraft Software Trainings via Lists.Yoctoproject.Org wrote: Hi,   I have some general idea on makefile in C, C++ environment. Related to my Yocto project having a very tough time in getting my makefile ready on shape after almost every development change. Is

[linux-yocto] [linux-yocto-dev] Another patch series for the Marvell cn96xx SoC support

Hi Bruce, Here is another patch series for the Marvell cn96xx SoC support. The main changes include: - Add tuning support for HS400 mode for octeontx2 mmc - Misc Ethernet bug fixes - A new driver to to handle GPINT0 interrupt on Loki SoC - RAS error-injection for octeontx2 - Add debug

[linux-yocto] [linux-yocto v5.4] Another patch series for the Marvell cn96xx SoC support

Hi Bruce, Here is another patch series for the Marvell cn96xx SoC support. The main changes include: - Add tuning support for HS400 mode for octeontx2 mmc - Misc Ethernet bug fixes - A new driver to to handle GPINT0 interrupt on Loki SoC - RAS error-injection for octeontx2 - Add debug