Ah, I forgot to put all of this in a bsp/rockchip/ dir, will reroll.

Generally speaking, I'd say yes, and it would be great if we are able to do that. But from what I've seen of op-tee integration, it looks like vendor platforms usually have different ways of

OE-Core rev: fd1c26ab426c3699ffd8082b83d65a84c8eb8bff added an additional parameter, tmpfsdir, to the API. This caused testimage to no longer work in meta-zephyr. Add that parameter and everything

Signed-off-by: Armin Kuster <akuster808@...> --- ...Makefile-drop-running-scrips-install.patch | 37 +++ .../0002-Makefile-don-t-set-uid-gid.patch | 251 ++++++++++++++++++

Hi Guys, I am facing one more issue No eligible RPROVIDERs exist for 'core-image-sato' Thanks & Regards, Sateesh -- Regards, Sateesh

Hi Guys, I am newly facing this when I want to build core-image-sato image. how can I fix this issue can anybody know please suggest me. local.conf I enabled EXTRA_IMAGE_FEATURES +=

Hi Sateesh, It seems you're trying to install static development packages. if that's the case, then I think you should try adding "staticdev-pkgs" to the EXTRA_IMAGE_FEATURES variable in the

Hi Guys, I am newly facing this when I want to build core-image-sato image. how can I fix this issue can anybody know please suggest me. Loading cache: 100% |

What is the relationship between OpenBIOS and YOCTO? Between OpenBIOS and U-boot?

Signed-off-by: Alexander Kanavin <alex.kanavin@...> --- config.json | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/config.json b/config.json index 6de85a4..b38bc61 100644 ---

Signed-off-by: Alexander Kanavin <alex.kanavin@...> --- config.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/config.json b/config.json index 8e0f0ac..6de85a4

I believe the time has come for YP to be defaulting to Wayland and not X11. X11 is effectively deprecated technology at this point with only minimal maintenance; standalone X server will not

Signed-off-by: Alexander Kanavin <alex.kanavin@...> --- config.json | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/config.json b/config.json index

In general, it seems like a lot of these changes should be in the upstream recipes, not the meta-rockchip bbappends. Also, the things that do belong in this layer need proper

From: Yann Dirson <yann@...> FIXME: - provide an .scc with proper information - maybe bundle with dts overlay - select a more suitable path in config namespace ---

From: Yann Dirson <yann@...> FIXME: - this is not specific to the board, and would indeed apply to any SoC supported by OP-TEE. - should rather be selected by "optee" in

From: Yann Dirson <yann@...> This is meant as a safeguard against having optee-os included without the required support in u-boot and trusted-firmware-a. Signed-off-by: Yann Dirson

From: Yann Dirson <yann@...> This sets up a central switch for OP-TEE operation, activating support in all dependent recipes at the same time: - u-boot - trusted-firmware-a - kernel (not

From: Yann Dirson <yann@...> As discussed in https://github.com/OP-TEE/optee_os/issues/4542, ASLR support currently has to be disabled for OP-TEE to boot. Signed-off-by: Yann Dirson

From: Yann Dirson <yann@...> This causes OP-TEE to get included into the u-boot.itb fitImage so u-boot can load it for the trusted-firmware-a BL31 to run it. This has to be enabled