In the case of kirkstone, this is what I get using `LINUX_KERNEL_TYPE =
"preempt-rt"`:
Linux raspberrypi4-64 5.15.34-v8 #1 SMP PREEMPT Tue Apr 19 19:21:26 UTC
2022 aarch64 aarch64 aarch64 GNU/Linux
I've experienced KERNEL_FEATURE conflicts using meta-virtualization with
DISTRO_FEATURES += "virtualization kvm" with meta-raspberrypi. Where the
fragment applied is not compatible with Aarch64, and it just disables the
linux-raspberrypi default config. It's quite possible you are also
experiencing something similar. I would check the kernel build logs and
see what fragments are being applied, and if there are any complaints with
any of them. The error may be a single line in a log file, and not
entirely descriptive. More context here:
https://github.com/agherzan/meta-raspberrypi/pull/1141
Working CI job:
https://github.com/meta-flutter/meta-flutter/blob/kirkstone/.github/workflows/kirkstone-rpi4-64-vulkan.yml
On Thu, Feb 2, 2023 at 2:24 AM Carles Sole via lists.yoctoproject.org
<[email protected]> wrote:
> Hello Joel,
>
> thanks for your reply. I was not aware about this possibility. I have
> tried it and the preemptive rt kernel is built instead of standard
> ("linux-raspberrypi4_64-preempt-rt-build" is available in
> build/work/linux-raspberrypi/...) but still the configuration file does not
> set the CONFIG_PREEMPT_RT=y for raspberrypi4-64, even if a .cfg is added
> using a .bbappend file. So in the end the RT option is not enabled.
>
> Any idea why it works for raspberrypi4 but not for raspberrypi4-64?
>
> Best Regards,
> Carles
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59152): https://lists.yoctoproject.org/g/yocto/message/59152
Mute This Topic: https://lists.yoctoproject.org/mt/96470693/21656
Mute #raspberrypi:https://lists.yoctoproject.org/g/yocto/mutehashtag/raspberrypi
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
