Hello Jan, Huzzah I can try :) Good question. @Prabhakar Mahadev Lad or @Hung Tran, could you help answer this? The Yocto BSP is here:

Hi! There are rumors that powerful x86 with qemu should outperform SiFive, that could be one option. Other one would be this, but I'm not sure when it will be

Hi Chris, after getting qemu-riscv64 ready (patches will come tomorrow), I also had a quick look at the RZ/Five eval board you shared with us. But that raised a couple of questions, maybe you can

Hi! To be clear, majority of the mailing list trafic is certainly not about UEFI. Best regards, Pavel -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235

Hello Phil, Thank you for getting in touch. You can sign up to the mailing list here: https://lists.cip-project.org/g/cip-dev Please let us know if you have any issues. Kind regards, Chris

Hi all, worth to read (also those of previous months): https://lists.debian.org/debian-riscv/2022/09/msg00012.html In a nutshell, build hardware is a key bottleneck right now. The preferred SiFive

cip/linux-5.10.y-cip-rt ltp-timers: 10 runs, 1 regressions (v5.10.145-cip17-rt7) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig

cip/linux-5.10.y-cip-rt kselftest-filesystems: 3 runs, 1 regressions (v5.10.145-cip17-rt7) Regressions Summary ------------------- platform | arch | lab | compiler |

cip/linux-5.10.y-cip-rt kselftest-futex: 3 runs, 1 regressions (v5.10.145-cip17-rt7) Regressions Summary ------------------- platform | arch | lab | compiler |

cip/linux-5.10.y-cip-rt baseline: 176 runs, 2 regressions (v5.10.145-cip17-rt7) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig |

cip/linux-5.10.y-cip-rt baseline-nfs: 49 runs, 2 regressions (v5.10.145-cip17-rt7) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig

cip/linux-5.10.y-cip-rt build: 174 builds: 3 failed, 171 passed, 4 errors, 6 warnings (v5.10.145-cip17-rt7) Full Build Summary:

Hi! New realtime trees should be available at kernel.org. Trees are available

The LAYERDIR_cip-core contains an absolute path to the layer at the current location on the fs. This breaks sstate caching in case the layer is checked out at a different location on the next build

When using the cip-core layer in another layer that has a slightly different directory structure, bitbake is not able to resolve the included files. To fix this, we simply add the full path to the

Hi there, This email address was presented at the Embedded Linux Conference 2022, please add me to the mail list if it covers UEFI topics. Thanks, Phil

cip/linux-4.4.y-cip smc: 6 runs, 2 regressions (v4.4.302-cip70-98-g7f7838c92740f) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig

cip/linux-4.4.y-cip ltp-pty: 3 runs, 1 regressions (v4.4.302-cip70-98-g7f7838c92740f) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig

cip-gitlab/ci/pavel/linux-test smc: 6 runs, 5 regressions (v4.4.302-cip70-98-gb2bfffe124dae) Regressions Summary ------------------- platform | arch | lab | compiler

cip-gitlab/ci/pavel/linux-test ltp-pty: 3 runs, 3 regressions (v4.4.302-cip70-98-gb2bfffe124dae) Regressions Summary ------------------- platform | arch | lab | compiler