|
[PATCH yocto-autobuilder-helper 1/4] config.json: transition ptests to weston-based images
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
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
|
By
Alexander Kanavin
·
#53252
·
|
|
Re: [meta-rockchip][PATCH v3 0/7] OP-TEE support for ARM and rk3399
On 4/23/21 11:58 AM, Yann Dirson wrote:
In general, it seems like a lot of these changes should be in the upstream recipes, not the meta-rockchip bbappends.
Also, the things
On 4/23/21 11:58 AM, Yann Dirson wrote:
In general, it seems like a lot of these changes should be in the upstream recipes, not the meta-rockchip bbappends.
Also, the things
|
By
Joshua Watt
·
#53251
·
|
|
[meta-rockchip][PATCH v3 7/7] WIP kernel config feature for OP-TEE activation
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:
- provide an .scc with proper information
- maybe bundle with dts overlay
- select a more suitable path in config namespace
---
|
By
Yann Dirson
·
#53250
·
|
|
[meta-rockchip][PATCH v3 6/7] WIP nanopi-m4: declare OP-TEE presence in devicetree
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@...>
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
|
By
Yann Dirson
·
#53249
·
|
|
[meta-rockchip][PATCH v3 5/7] RFC: optee: only enable the recipes when "optee" is included in DISTRO_FEATURES
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 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
|
By
Yann Dirson
·
#53248
·
|
|
[meta-rockchip][PATCH v3 4/7] RFC optee: new "optee" DISTRO_FEATURE to enable optee-os integration
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@...>
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
|
By
Yann Dirson
·
#53247
·
|
|
[meta-rockchip][PATCH v3 3/7] optee-os: enable rk3399 support, including serial console support
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@...>
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
|
By
Yann Dirson
·
#53246
·
|
|
[meta-rockchip][PATCH v3 2/7] u-boot: include optee-os as BL32 when requested by DISTRO_FEATURE
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
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
|
By
Yann Dirson
·
#53245
·
|
|
[meta-rockchip][PATCH v3 0/7] OP-TEE support for ARM and rk3399
From: Yann Dirson <yann@...>
Changes from v2:
- turn the DISTRO_FEATURE idea into separate RFC patches so as to allow
merging of basic support
- remove optee-os patch that proved
From: Yann Dirson <yann@...>
Changes from v2:
- turn the DISTRO_FEATURE idea into separate RFC patches so as to allow
merging of basic support
- remove optee-os patch that proved
|
By
Yann Dirson
·
#53244
·
|
|
[meta-rockchip][PATCH v3 1/7] trusted-firmware-a: include optee support when requested by DISTRO_FEATURE
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 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
|
By
Yann Dirson
·
#53243
·
|
|
The Yocto Project 2021 virtual Summit CFP reminder
Hello all,
This is a reminder that the 2021 Yocto Project Summit CFP window closes
this Sunday at 11:59 PM PST.
If anyone is interested, please
Hello all,
This is a reminder that the 2021 Yocto Project Summit CFP window closes
this Sunday at 11:59 PM PST.
If anyone is interested, please
|
By
Armin Kuster
·
#53242
·
|
|
[meta-rockchip][PATCH v3 3/3] linux-yocto: add an initial NanoPi-M4 BSP
From: Yann Dirson <yann@...>
This patch provides "standard" and "tiny" BSP.
There is still much work to be done in dispatching feature to individual
scc files - the more boards we can
From: Yann Dirson <yann@...>
This patch provides "standard" and "tiny" BSP.
There is still much work to be done in dispatching feature to individual
scc files - the more boards we can
|
By
Yann Dirson
·
#53241
·
|
|
[meta-rockchip][PATCH v3 2/3] NanoPi-M4: declare "usbhost" in MACHINE_FEATURES
From: Yann Dirson <yann@...>
Lets USB tools be installed if the distro activates the feature.
Signed-off-by: Yann Dirson <yann@...>
---
conf/machine/include/nanopi-m4.inc |
From: Yann Dirson <yann@...>
Lets USB tools be installed if the distro activates the feature.
Signed-off-by: Yann Dirson <yann@...>
---
conf/machine/include/nanopi-m4.inc |
|
By
Yann Dirson
·
#53240
·
|
|
[meta-rockchip][PATCH v3 0/3] kmeta BSP for nanopi-m4
From: Yann Dirson <yann@...>
Changes from in v3:
- relocate the bsp files into files/ so we don't have to add linux-yocto/
to FILESEXTRAPATHS for all other kernels
- removed the "don't
From: Yann Dirson <yann@...>
Changes from in v3:
- relocate the bsp files into files/ so we don't have to add linux-yocto/
to FILESEXTRAPATHS for all other kernels
- removed the "don't
|
By
Yann Dirson
·
#53239
·
|
|
[meta-rockchip][PATCH v3 1/3] NanoPi-M4: let all variants use the same KMACHINE type
From: Yann Dirson <yann@...>
This will allow us to define a single set of kernel BSP for all
variants of the board (which only need to differ in u-boot dts).
Signed-off-by: Yann Dirson
From: Yann Dirson <yann@...>
This will allow us to define a single set of kernel BSP for all
variants of the board (which only need to differ in u-boot dts).
Signed-off-by: Yann Dirson
|
By
Yann Dirson
·
#53238
·
|
|
Re: #yocto #sdk #cmake
#yocto
#sdk
#cmake
Thanks you...
By
Monsees, Steven C (US)
·
#53237
·
|
|
Re: #bitbake Can't use 'bitbake -g <image-name> -u taskdep
#bitbake
As for project here Poky operates on headless server. Developers use SSH to interact with Poky, to handle its input data, and to access build results. Must gtk3 be installed locally to Poky or will
As for project here Poky operates on headless server. Developers use SSH to interact with Poky, to handle its input data, and to access build results. Must gtk3 be installed locally to Poky or will
|
By
keydi <krzysztof.dudziak@...>
·
#53236
·
|
|
Re: Problems building hardknott for raspberri pi
Then it should not be using Mesa-gl so it’s a bit confusing how you end up needing it
Then it should not be using Mesa-gl so it’s a bit confusing how you end up needing it
|
By
Khem Raj
·
#53235
·
|
|
Re: Problems building hardknott for raspberri pi
No, I'm not using DISABLE_VC4GRAPHICS - should I?
/Morten
No, I'm not using DISABLE_VC4GRAPHICS - should I?
/Morten
|
By
Morten Bruun
·
#53234
·
|
|
Re: Problems building hardknott for raspberri pi
never mind, I think we perhaps have is broken on master too. Are you
using DISABLE_VC4GRAPHICS = "1" ?
never mind, I think we perhaps have is broken on master too. Are you
using DISABLE_VC4GRAPHICS = "1" ?
|
By
Khem Raj
·
#53233
·
|