Such access tokens are best placed into files which can be accessed
only by processes that need them, same as private ssh keys. What
executable is using it, specifically and with which protocol?
Alex
On Thu, 13 Apr 2023 at 21:54, Philippe Lafontaine via
lists.yoctoproject.org
wrote:
>
>
Hello Philippe,
On Thu, Apr 13, 2023 at 9:54 PM Philippe Lafontaine via
lists.yoctoproject.org
wrote:
> I have a recipe that fetch a pre-built binary from a build machine using an
> access token. Every developer will have different access token, for obvious
> reason. Therefore, the token
Greeting,
I have a recipe that fetch a pre-built binary from a build machine using an
access token. Every developer will have different access token, for obvious
reason. Therefore, the token cannot be hard coded in the recipe.
Our current build setup uses a docker container (crops/poky). Our
As an update for anyone looking at this..
I managed to get the raspberry pi build going. It seems after running
source oe-init-build-env rpi-build
the local.conf from meta-atmel was copied into the rpi-build folder. This
local.conf amongst other things had
DISTRO ?= "poky-atmel"
Which was
Btw does Poky have a central switch for venus Vulkan driver? I feel like making
another attempt.
From: Alexander Kanavin
Sent: Wednesday, April 12, 2023 5:45 PM
To: Edgar Mobile
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] Adding SSH access to runqemu
Hi,
I am using meta-microcontroller (
https://github.com/schnitzeltony/meta-microcontroller ) to build an AVR image
at build-time. The target device will then image the microcontroller at
runtime. I want to put the avr utilities into the produce yocto sdk to I can do
development for the
Hello all,
I'm using Dunfell & up to know I've being using meta-atmel to build images.
I'd like to now add the capability to build images using meta-raspberrypi
but I'm having issues with the source oe-init-build-env step, it keeps
pulling in the meta-atmel shell environment. My folder layout is
Make sure that all changes a saved after running the tests.
Signed-off-by: Anton Antonov
---
meta-parsec/lib/oeqa/runtime/cases/parsec.py | 4
1 file changed, 4 insertions(+)
diff --git a/meta-parsec/lib/oeqa/runtime/cases/parsec.py
b/meta-parsec/lib/oeqa/runtime/cases/parsec.py
index
Hello All,
i want to add a recipe lorawan-server in my source. here i am facing
some errors as below.
Can anyone help me out to solve these errors,
NOTE:
Hi Qi,
This seems to solve the issue, though I'm not sure this behaviour was intended
in the original commit by Richard. Anyways, thanks a lot!
--Adrian
From: Chen, Qi
Sent: Wednesday, April 5, 2023 6:17 PM
To: Chen, Qi ; Adrian Dudau
; Bruce Ashfield
Cc:
From: Quanyang Wang
This patch is based on the patch:
wryocto/layers/meta-aptiv/recipes-kernel/linux/files/0001-dts-s32g-pfe-modify-BMU2-reserved-memory-node-to.patch
Signed-off-by: Quanyang Wang
---
.../boot/dts/freescale/s32g274a-aptiv-pfems.dts| 14 ++
1 file changed, 14
From: Felix Lelchuk
BZX-1487: Pfe slave driver is integrated on the Windriver linux
-device tree adaptations
-#include "s32g-pfe-slave.dtsi"
-override pfe_slave properties for our use case:
-unset dma-coherent as was done by OBE (=Olaf?) for the master case
(why?)
From: Quanyang Wang
For now, dts files for NXP rdb/evb boards are following the naming
rules as s32gXXX.dtsi/s32gXXX.dts/s32gXXX-pfems.dts. Let's switch
Aptiv dts files to the same rule.
Rename original s32g274a-aptiv.dts to be s32g274a-aptiv.dtsi and make a
new s32g274a-aptiv.dts to include
From: Quanyang Wang
For now, dts files for NXP rdb/evb boards are following the naming
rules as s32gXXX.dtsi/s32gXXX.dts/s32gXXX-pfems.dts. Let's switch
Aptiv dts files to the same rule.
Rename original s32g399a-cvc-fl.dts to be s32g399a-cvc-fl.dtsi and make
new s32g399a-cvc-fl.dts and
From: Quanyang Wang
Hi Bruce,
Would you please help merge these 4 patches to the branches:
v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g
v5.15/standard/nxp-sdk-5.15/nxp-s32g
Thanks,
Quanyang
Felix Lelchuk (1):
Fix DTS for Aptiv PFE Slave
Quanyang Wang (3):
dts: Aptiv:
Hi Team,
I'm using dm-verity in yocto Linux 5.15 on the imx6dl board. On boot
when device mapper creates I'm getting a data block corrupted error,
Can you please help to fix this issue.?
Error log:
# cryptsetup 2.4.3 processing "veritysetup create rootfs
/dev/mmcblk3p3 /dev/mmcblk3p2
16 matches
Mail list logo