[yocto] [Recipe reporting system] Upgradable recipe name list

This mail was sent out by Recipe reporting system. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade at this time, they can fill RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder until newer upstream version

Re: [yocto] Read Only File System

Hi Jose, I don't know if you're using a custom device tree or not, but I ran into this issue and solved it by disabling write protection in the device tree: https://github.com/kratsg/meta-l1calo/blob/master/recipes-bsp/device-tree/files/gfex-prototype4/gfex-prototype4.dts#L48-L51 {

[yocto] [meta-security][PATCH] xmlsec1: fix a typo in examples/verify3.c

From: Jackie Huang Signed-off-by: Jackie Huang --- .../xmlsec1-fix-a-typo-in-examples-verify3.c.patch | 25 ++ recipes-security/xmlsec1/xmlsec1_1.2.25.bb | 1 + 2 files changed, 26 insertions(+) create mode

[yocto] Read Only File System

I'm building a image using Yocto rocky and Xilinx for my zynq-702 board. But for some reason my root file system can only be mounted as a read only. If I put rw in the u-boot load command it fails. I'm booting from a SD card, that doesn't have any lock switch. And if I boot using other

[yocto] [meta-intel][PATCH] systemd-boot: fix bbappend file to suit latest version

Fix the bbappend file to suit the latest systemd version. As systemd has now dropped autotools support, using ninja instead of make in do_compile. Signed-off-by: Chen Qi --- recipes-bsp/systemd-boot/systemd-boot_%.bbappend | 4 ++-- 1 file changed, 2 insertions(+), 2

[linux-yocto] [Yocto kernel 4.1 pull request]

This series includes the lsb runqemu kvm boot issue [ Yocto #12570 ], Spectre v1 and misc bug fixes 4.4 backports. The following changes since commit 1368b7448d693cedb384f6e0b9a0237adb1b8259: kaiser: x86: Fix NMI handling (2018-02-22 12:18:09 -0800) are available in the git repository at: