[yocto] Can't parse unset of variables with override

Hi, I'm not sure if this has been brought up already. After the syntax change from underscore to colon, I noticed the error when using unset on variables with override. Could someone confirm if this is expected? # in bbappend unset SRCREV:xyz # in build log ERROR: ParseError at

Re: [yocto] Hardknott systemd-journald issue

Hello Jupiter, This might provide you a great help: https://askubuntu.com/questions/864722/where-is-journalctl-data-stored Namely: *Usually the storage directory is /var/log/journal or /run/log/journal, but it doesn't have to necessarily exist in your system.If you just want to check the

Re: [yocto] [meta-mingw] [PATCH 1/3] protobuf: static link tools when generating sdk

On Mon, Aug 16, 2021 at 6:36 PM Sinan Kaya wrote: > Dynamically linked protoc.exe is failing as follows: > > [libprotobuf ERROR google/protobuf/descriptor_database.cc:641] > File already exists in database: google/protobuf/descriptor.proto > [libprotobuf FATAL google/protobuf/descriptor.cc:1371]

[yocto] M+ & H bugs with Milestone Movements WW33

All, YP M+ or high bugs which moved to a new milestone in WW33 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 13975 cve-checker: save to alternate file format like JSON

[yocto] Enhancements/Bugs closed WW33!

All, The below were the owners of enhancements or bugs closed during the last week! Who Count randy.macl...@windriver.com 2 mhalst...@linuxfoundation.org 2 r...@burtonini.com 2 Grand Total 6 Thanks, Stephen K. Jolley Yocto Project Program Manager *Cell:

[yocto] Current high bug count owners for Yocto Project 3.4

All, Below is the list as of top 50 bug owners as of the end of WW33 of who have open medium or higher bugs and enhancements against YP 3.4. There are 52 possible work days left until the final release candidates for YP 3.4 needs to be released. Who Count r...@burtonini.com 32

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

[yocto] Hardknott systemd-journald issue

Hi, I've just upgraded from Zeus to Hardknott with the kernel 5.10.59, the /run/log/journal was running out of space and crashed, is it a kernel issue or Hardknott build issue? I never seen that issue in Zeus, I thought that systemd-journald should be capable of detecting the space, if it is no

[yocto] [meta-mingw] [PATCH 2/3] protobuf-c: static link when generating sdk

[libprotobuf ERROR google/protobuf/descriptor_database.cc:641] File already exists in database: google/protobuf/descriptor.proto [libprotobuf FATAL google/protobuf/descriptor.cc:1371] CHECK failed: GeneratedDatabase()->Add(encoded_file_descriptor, size): Switch to static linkage per upstream

[yocto] [meta-mingw] [PATCH 3/3] grpc: static link tools when generating SDK

[libprotobuf ERROR google/protobuf/descriptor_database.cc:641] File already exists in database: google/protobuf/descriptor.proto [libprotobuf FATAL google/protobuf/descriptor.cc:1371] CHECK failed: GeneratedDatabase()->Add(encoded_file_descriptor, size): Switch to static linkage per upstream

[yocto] [meta-mingw] [PATCH 1/3] protobuf: static link tools when generating sdk

Dynamically linked protoc.exe is failing as follows: [libprotobuf ERROR google/protobuf/descriptor_database.cc:641] File already exists in database: google/protobuf/descriptor.proto [libprotobuf FATAL google/protobuf/descriptor.cc:1371] CHECK failed:

[linux-yocto] [yocto-kernel-cache yocto-5.10]: nxp-s32g2xx: change CAN LLCE config to y to fix build warning

Hi Bruce, There is an patch related with CAN LLCE feature to fix a kernel build warning for nxp-s32g2xx bsp, would you please help to merge this patch into yocto-kernel-cache, branch yocto-5.10? Thanks, Zhantao -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group.

[linux-yocto] [PATCH] nxp-s32g2xx: change CAN LLCE config to y to fix build warning

Due to the rc5 update of bsp30, the CAN_LLCE kernel config should change to y to fix the following build warning: do_kernel_configcheck: [kernel config]: specified values did not make it into the kernel's final configuration: [NOTE]: 'CONFIG_CAN_LLCE' last val (m) and .config val (n)

[linux-yocto][yocto-kernel-cache][yocto-5.10 only][PATCH] bsp: axxia: add new kernel options for axm56xx

From: Quanyang Wang This patch includes modifications as below: 1. add CONFIG_PROFILING and CONFIG_ARM_CCN_PMU to enable ccn for axm56xx. 2. add CONFIG_ARM_SP804_WATCHDOG_AXXIA to enable sp804 watchdog for axm56xx. Signed-off-by: Quanyang Wang --- bsp/axxiaarm/axxia-common.cfg | 1 +

[linux-yocto][v5.10/standard/preempt-rt/sdkv5.10/axxia][PATCH 6/6] edac: remove dependency MACH_AXXIA for EDAC_AXXIA_L3_5500

From: Quanyang Wang I add "MACH_AXXIA" dependency for EDAC_AXXIA_L3_5500 to fix allyesconfig building error. But there is no MACH_AXXIA kernel option and this will cause warning as below: Config 'EDAC_AXXIA_L2_CPU_5500' has the following Direct dependencies (EDAC_AXXIA_L2_CPU_5500=n):

[linux-yocto][v5.10/standard/preempt-rt/sdkv5.10/axxia][PATCH 5/6] axxia: use udelay instead of usleep in kexec/kdump routine

From: Quanyang Wang The kexec/kdump routine is mostly running at a atomic context, calling usleep will trigger the calltrace as below: WARNING: CPU: 0 PID: 529 at kernel/sched/core.c:4844 preempt_count_sub+0x74/0xf0 DEBUG_LOCKS_WARN_ON(val > preempt_count()) Modules linked in: CPU: 0 PID: 529

[linux-yocto][v5.10/standard/preempt-rt/sdkv5.10/axxia][PATCH 4/6] axxia: add sync between cpu_die and cpu_kill

From: Quanyang Wang Normally, a CPU should run cpu_die first and then the CPUs stand by it are in charge of killing it by calling cpu_kill. If a CPU doesn't call cpu_die before other CPUs call cpu_kill, the system will hang. So add synchronization implement between cpu_die and cpu_kill.

[linux-yocto][v5.10/standard/preempt-rt/sdkv5.10/axxia][PATCH 3/6] arm: mach-axxia: kexec_reinit to set L3 CACHE shutdown

From: Xulin Sun Shut down to flush L3 cache for KEXEC to avoid the hung issue for capture kernel booting, since for ARM capture kernel just one CPU allowed to boot, and no L3 cache coherency issue existed for SMP situation, so just shut down the flush to L3 CACHE. The function calling

[linux-yocto][v5.10/standard/preempt-rt/sdkv5.10/axxia][PATCH 2/6] arch/arm/mach-axxia: use mpidr_to_hwcpu to retrieve real hardware cpuid

From: Quanyang Wang In function arm_dt_init_cpu_maps, it will use hwid whose value is "reg" property in cpu node to compare with mpidr whose value read from MPIDR register. When boot in normal condition, hwid is equal to MPIDR value which is "0" by chance. But in kdump, the boot cpu will be any

[linux-yocto][v5.10/standard/preempt-rt/sdkv5.10/axxia][PATCH 0/6]

From: Quanyang Wang Hi Bruce, Would you please help merge these patches to the 2 branches? v5.10/standard/preempt-rt/sdkv5.10/axxia v5.10/standard/sdkv5.10/axxia Thanks, Quanyang Quanyang Wang (5): kexec: adjust dtb_mem address to adapt to axm55xx's weird entry arch/arm/mach-axxia: use

[linux-yocto][v5.10/standard/preempt-rt/sdkv5.10/axxia][PATCH 1/6] kexec: adjust dtb_mem address to adapt to axm55xx's weird entry

From: Quanyang Wang When kexec load secondary kernel, it will calculate dtb_mem according to the formula as below: dtb_mem = kernel_entry + image_size * 5 But axm55xx's entry is not the default value 0x8000 but 0x408000, this will result that when zImage as the secondary kernel decompresses,

Re: [yocto] Failed to boot kernel 5 after upgrading to Hardknott

On 8/15/21 10:36 PM, Zoran wrote: You are using systemd with the wrong defconfig setup, my best guess. cgroup option in the config must be set to Y while using systemd: CONFIG_CGROUP=Y . Zee ___ On Mon, Aug 16, 2021 at 6:24 AM JH wrote: Hi, I upgrade Zeus to Hardknott, the kernel