for a current project (and subsequent projects), i want to define a hardware bringup image; that is, a really basic image chock-full of low-level utilities for debugging initial board bringup. this

Hi, Could you please let me know if there is any update on this change? Thanks & Regards, Purushottam

From: Meng Li <Meng.Li@...> Signed-off-by: Meng Li <Meng.Li@...> --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf

Hi, My comments are inline. ... if everybody does what they are supposed to - which is not the case. This does not sound too bad. This would also mean, that if the outside repo dies you can still

I was able to solve it by forcing recompiling nodejs with `bitbake -f -c compile nodejs` Not sure what happened there -- Alessandro Tagliapietra

Hi everyone, I've installed nodejs and node-red by using meta-oe and meta-iot-cloud, with IMAGE_INSTALL_append = " nodejs node-red bash" it was initially working but then I've got some pseudo aborts

Working with zeus 3.0.4, extended SDK… Could someone explain what I overlooked, or why this issue pops up with python-native support inclusion ? Thanks… When I add in native-python3

Yocto Technical Team Minutes, Engineering Sync, for April 13, 2021 archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == announcements == The upcoming Yocto

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 the current state of working patches being discussed in https://github.com/OP-TEE/optee_os/issues/4542 --- conf/machine/include/rk3399.inc

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 is configured

From: Yann Dirson <yann@...> This instructs TF-A to: - load OP-TEE OS as BL32, but still relies on the actual image to be provided through other means, eg. in u-boot.itb - run

From: Yann Dirson <yann@...> This tries to provide a generic framework for easier OP-TEE support in BSP layers. It would probably make sense to have the generic parts in meta-arm when

From: Yann Dirson <yann@...> This effectively sets up a single switch to activate OP-TEE support. Disabling optee-* recipes when the feature is not set is not the primary goal, though it

merged, Thanks

Merged, Thanks

merged, Thanks

merged thanks, armin

merged. thanks -armin