Re: [yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2023-09-25 Thread MOHAMMED HASSAN 
What prerequiste knowledge should I have before deciding to help. I have less 
experience with yocto and embedded linux in general.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61115): https://lists.yoctoproject.org/g/yocto/message/61115
Mute This Topic: https://lists.yoctoproject.org/mt/101587890/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-rockchip] [PATCH] Allow KERNEL_IMAGETYPE override v2

2023-09-25 Thread Anthony Davies 
From: Anthony Davies 

Apologies, this is the correct patch

Updated inc files to allow overriding KERNEL_IMAGETYPE in local.conf

Fixed bug where dtb couldnt be found when generating KERNEL_IMAGETYPE
other then fitImage image due to KERNEL_DEVICETREE containing the dtb
directory which is not available in the DEPLOY_DIR_IMAGE directory
---
 conf/machine/include/px30.inc | 2 +-
 conf/machine/include/rk3066.inc   | 2 +-
 conf/machine/include/rk3188.inc   | 2 +-
 conf/machine/include/rk3288.inc   | 2 +-
 conf/machine/include/rk3328.inc   | 2 +-
 conf/machine/include/rk3399.inc   | 2 +-
 conf/machine/include/rockchip-wic.inc | 5 -
 7 files changed, 10 insertions(+), 7 deletions(-)

diff --git a/conf/machine/include/px30.inc b/conf/machine/include/px30.inc
index a3727fb..badcbcd 100644
--- a/conf/machine/include/px30.inc
+++ b/conf/machine/include/px30.inc
@@ -12,7 +12,7 @@ require conf/machine/include/rockchip-wic.inc
 
 KBUILD_DEFCONFIG ?= "defconfig"
 KERNEL_CLASSES = "kernel-fitimage"
-KERNEL_IMAGETYPE = "fitImage"
+KERNEL_IMAGETYPE ?= "fitImage"
 
 TFA_PLATFORM = "px30"
 TFA_BUILD_TARGET = "bl31"
diff --git a/conf/machine/include/rk3066.inc b/conf/machine/include/rk3066.inc
index fa97906..3510df2 100644
--- a/conf/machine/include/rk3066.inc
+++ b/conf/machine/include/rk3066.inc
@@ -11,4 +11,4 @@ SERIAL_CONSOLES = "115200;ttyS2"
 
 KBUILD_DEFCONFIG = "multi_v7_defconfig"
 KERNEL_FEATURES:append:rk3066 = " 
bsp/rockchip/remove-non-rockchip-arch-arm.scc"
-KERNEL_IMAGETYPE = "zImage"
+KERNEL_IMAGETYPE ?= "zImage"
diff --git a/conf/machine/include/rk3188.inc b/conf/machine/include/rk3188.inc
index bc96a0c..830f908 100644
--- a/conf/machine/include/rk3188.inc
+++ b/conf/machine/include/rk3188.inc
@@ -11,4 +11,4 @@ SERIAL_CONSOLES = "115200;ttyFIQ0"
 
 KBUILD_DEFCONFIG = "multi_v7_defconfig"
 KERNEL_FEATURES:append:rk3188 = " 
bsp/rockchip/remove-non-rockchip-arch-arm.scc"
-KERNEL_IMAGETYPE = "zImage"
+KERNEL_IMAGETYPE ?= "zImage"
diff --git a/conf/machine/include/rk3288.inc b/conf/machine/include/rk3288.inc
index b4c559d..e682c0b 100644
--- a/conf/machine/include/rk3288.inc
+++ b/conf/machine/include/rk3288.inc
@@ -11,6 +11,6 @@ SERIAL_CONSOLES = "115200;ttyS2"
 
 KBUILD_DEFCONFIG ?= "multi_v7_defconfig"
 KERNEL_FEATURES:append:rk3288 = " 
bsp/rockchip/remove-non-rockchip-arch-arm.scc"
-KERNEL_IMAGETYPE = "zImage"
+KERNEL_IMAGETYPE ?= "zImage"
 
 UBOOT_SUFFIX ?= "bin"
diff --git a/conf/machine/include/rk3328.inc b/conf/machine/include/rk3328.inc
index f9f8792..6be777c 100644
--- a/conf/machine/include/rk3328.inc
+++ b/conf/machine/include/rk3328.inc
@@ -13,7 +13,7 @@ require conf/machine/include/rockchip-wic.inc
 KBUILD_DEFCONFIG ?= "defconfig"
 KERNEL_FEATURES:append:rk3328 = " 
bsp/rockchip/remove-non-rockchip-arch-arm64.scc"
 KERNEL_CLASSES = "kernel-fitimage"
-KERNEL_IMAGETYPE = "fitImage"
+KERNEL_IMAGETYPE ?= "fitImage"
 
 TFA_PLATFORM = "rk3328"
 TFA_BUILD_TARGET = "bl31"
diff --git a/conf/machine/include/rk3399.inc b/conf/machine/include/rk3399.inc
index 88c87af..5a3f439 100644
--- a/conf/machine/include/rk3399.inc
+++ b/conf/machine/include/rk3399.inc
@@ -13,7 +13,7 @@ require conf/machine/include/rockchip-wic.inc
 KBUILD_DEFCONFIG ?= "defconfig"
 KERNEL_FEATURES:append:rk3399 = " 
bsp/rockchip/remove-non-rockchip-arch-arm64.scc"
 KERNEL_CLASSES = "kernel-fitimage"
-KERNEL_IMAGETYPE = "fitImage"
+KERNEL_IMAGETYPE ?= "fitImage"
 
 TFA_PLATFORM = "rk3399"
 TFA_BUILD_TARGET = "bl31"
diff --git a/conf/machine/include/rockchip-wic.inc 
b/conf/machine/include/rockchip-wic.inc
index 635288c..8ff6066 100644
--- a/conf/machine/include/rockchip-wic.inc
+++ b/conf/machine/include/rockchip-wic.inc
@@ -11,9 +11,12 @@ WKS_FILE_DEPENDS ?= " \
virtual/bootloader \
virtual/kernel \
"
+ 
+KERNEL_DEVICETREE_BASENAME = "${@os.path.basename('${KERNEL_DEVICETREE}')}"
+
 IMAGE_BOOT_FILES = " \
${KERNEL_IMAGETYPE} \
-   ${@bb.utils.contains('KERNEL_IMAGETYPE', 'fitImage', '', 
'${KERNEL_DEVICETREE}', d)} \
+   ${@bb.utils.contains('KERNEL_IMAGETYPE', 'fitImage', '', 
'${KERNEL_DEVICETREE_BASENAME}', d)} \
"
 
 # use the first-defined ; pair in SERIAL_CONSOLES
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61114): https://lists.yoctoproject.org/g/yocto/message/61114
Mute This Topic: https://lists.yoctoproject.org/mt/101589776/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-rockchip] [PATCH] Allow KERNEL_IMAGETYPE override

2023-09-25 Thread Anthony Davies 
So sorry, this is the wrong branch, I will send a new one.

On Tue, 26 Sept 2023 at 13:07, Anthony Davies via lists.yoctoproject.org
 wrote:

> From: Anthony Davies 
>
> Updated inc files to allow overriding KERNEL_IMAGETYPE in local.conf
>
> Fixed bug where dtb couldnt be found when generating KERNEL_IMAGETYPE
> other then fitImage image due to KERNEL_DEVICETREE containing the dtb
> directory which is not available in the DEPLOY_DIR_IMAGE directory
> ---
>  conf/machine/include/px30.inc  | 2 +-
>  conf/machine/include/rk3066.inc| 2 +-
>  conf/machine/include/rk3188.inc| 2 +-
>  conf/machine/include/rk3288.inc| 2 +-
>  conf/machine/include/rk3328.inc| 2 +-
>  conf/machine/include/rk3399.inc| 2 +-
>  conf/machine/include/rockchip-defaults.inc | 2 +-
>  conf/machine/include/rockchip-wic.inc  | 6 +-
>  8 files changed, 12 insertions(+), 8 deletions(-)
>
> diff --git a/conf/machine/include/px30.inc b/conf/machine/include/px30.inc
> index a3727fb..badcbcd 100644
> --- a/conf/machine/include/px30.inc
> +++ b/conf/machine/include/px30.inc
> @@ -12,7 +12,7 @@ require conf/machine/include/rockchip-wic.inc
>
>  KBUILD_DEFCONFIG ?= "defconfig"
>  KERNEL_CLASSES = "kernel-fitimage"
> -KERNEL_IMAGETYPE = "fitImage"
> +KERNEL_IMAGETYPE ?= "fitImage"
>
>  TFA_PLATFORM = "px30"
>  TFA_BUILD_TARGET = "bl31"
> diff --git a/conf/machine/include/rk3066.inc
> b/conf/machine/include/rk3066.inc
> index fa97906..3510df2 100644
> --- a/conf/machine/include/rk3066.inc
> +++ b/conf/machine/include/rk3066.inc
> @@ -11,4 +11,4 @@ SERIAL_CONSOLES = "115200;ttyS2"
>
>  KBUILD_DEFCONFIG = "multi_v7_defconfig"
>  KERNEL_FEATURES:append:rk3066 = "
> bsp/rockchip/remove-non-rockchip-arch-arm.scc"
> -KERNEL_IMAGETYPE = "zImage"
> +KERNEL_IMAGETYPE ?= "zImage"
> diff --git a/conf/machine/include/rk3188.inc
> b/conf/machine/include/rk3188.inc
> index bc96a0c..830f908 100644
> --- a/conf/machine/include/rk3188.inc
> +++ b/conf/machine/include/rk3188.inc
> @@ -11,4 +11,4 @@ SERIAL_CONSOLES = "115200;ttyFIQ0"
>
>  KBUILD_DEFCONFIG = "multi_v7_defconfig"
>  KERNEL_FEATURES:append:rk3188 = "
> bsp/rockchip/remove-non-rockchip-arch-arm.scc"
> -KERNEL_IMAGETYPE = "zImage"
> +KERNEL_IMAGETYPE ?= "zImage"
> diff --git a/conf/machine/include/rk3288.inc
> b/conf/machine/include/rk3288.inc
> index b4c559d..e682c0b 100644
> --- a/conf/machine/include/rk3288.inc
> +++ b/conf/machine/include/rk3288.inc
> @@ -11,6 +11,6 @@ SERIAL_CONSOLES = "115200;ttyS2"
>
>  KBUILD_DEFCONFIG ?= "multi_v7_defconfig"
>  KERNEL_FEATURES:append:rk3288 = "
> bsp/rockchip/remove-non-rockchip-arch-arm.scc"
> -KERNEL_IMAGETYPE = "zImage"
> +KERNEL_IMAGETYPE ?= "zImage"
>
>  UBOOT_SUFFIX ?= "bin"
> diff --git a/conf/machine/include/rk3328.inc
> b/conf/machine/include/rk3328.inc
> index f9f8792..6be777c 100644
> --- a/conf/machine/include/rk3328.inc
> +++ b/conf/machine/include/rk3328.inc
> @@ -13,7 +13,7 @@ require conf/machine/include/rockchip-wic.inc
>  KBUILD_DEFCONFIG ?= "defconfig"
>  KERNEL_FEATURES:append:rk3328 = "
> bsp/rockchip/remove-non-rockchip-arch-arm64.scc"
>  KERNEL_CLASSES = "kernel-fitimage"
> -KERNEL_IMAGETYPE = "fitImage"
> +KERNEL_IMAGETYPE ?= "fitImage"
>
>  TFA_PLATFORM = "rk3328"
>  TFA_BUILD_TARGET = "bl31"
> diff --git a/conf/machine/include/rk3399.inc
> b/conf/machine/include/rk3399.inc
> index 88c87af..5a3f439 100644
> --- a/conf/machine/include/rk3399.inc
> +++ b/conf/machine/include/rk3399.inc
> @@ -13,7 +13,7 @@ require conf/machine/include/rockchip-wic.inc
>  KBUILD_DEFCONFIG ?= "defconfig"
>  KERNEL_FEATURES:append:rk3399 = "
> bsp/rockchip/remove-non-rockchip-arch-arm64.scc"
>  KERNEL_CLASSES = "kernel-fitimage"
> -KERNEL_IMAGETYPE = "fitImage"
> +KERNEL_IMAGETYPE ?= "fitImage"
>
>  TFA_PLATFORM = "rk3399"
>  TFA_BUILD_TARGET = "bl31"
> diff --git a/conf/machine/include/rockchip-defaults.inc
> b/conf/machine/include/rockchip-defaults.inc
> index 3ce2e24..c5cf6c2 100644
> --- a/conf/machine/include/rockchip-defaults.inc
> +++ b/conf/machine/include/rockchip-defaults.inc
> @@ -1,7 +1,7 @@
>  # meta-rockchip default settings
>
>  # kernel
> -PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
> +PREFERRED_PROVIDER_virtual/kernel ??= "linux-yocto"
>  KCONFIG_MODE ?= "alldefconfig"
>
>  # xserver
> diff --git a/conf/machine/include/rockchip-wic.inc
> b/conf/machine/include/rockchip-wic.inc
> index 635288c..23ac9d9 100644
> --- a/conf/machine/include/rockchip-wic.inc
> +++ b/conf/machine/include/rockchip-wic.inc
> @@ -11,10 +11,14 @@ WKS_FILE_DEPENDS ?= " \
> virtual/bootloader \
> virtual/kernel \
> "
> +
> +KERNEL_DEVICETREE_BASENAME =
> "${@os.path.basename('${KERNEL_DEVICETREE}')}"
> +
>  IMAGE_BOOT_FILES = " \
> ${KERNEL_IMAGETYPE} \
> -   ${@bb.utils.contains('KERNEL_IMAGETYPE', 'fitImage', '',
> '${KERNEL_DEVICETREE}', d)} \
> +   ${@bb.utils.contains('KERNEL_IMAGETYPE', 'fitImage', '',
> '${KERNEL_DEVICETREE_BASENAME}', d)} \
>

[yocto] [meta-rockchip] [PATCH] Allow KERNEL_IMAGETYPE override

2023-09-25 Thread Anthony Davies 
From: Anthony Davies 

Updated inc files to allow overriding KERNEL_IMAGETYPE in local.conf

Fixed bug where dtb couldnt be found when generating KERNEL_IMAGETYPE
other then fitImage image due to KERNEL_DEVICETREE containing the dtb
directory which is not available in the DEPLOY_DIR_IMAGE directory
---
 conf/machine/include/px30.inc  | 2 +-
 conf/machine/include/rk3066.inc| 2 +-
 conf/machine/include/rk3188.inc| 2 +-
 conf/machine/include/rk3288.inc| 2 +-
 conf/machine/include/rk3328.inc| 2 +-
 conf/machine/include/rk3399.inc| 2 +-
 conf/machine/include/rockchip-defaults.inc | 2 +-
 conf/machine/include/rockchip-wic.inc  | 6 +-
 8 files changed, 12 insertions(+), 8 deletions(-)

diff --git a/conf/machine/include/px30.inc b/conf/machine/include/px30.inc
index a3727fb..badcbcd 100644
--- a/conf/machine/include/px30.inc
+++ b/conf/machine/include/px30.inc
@@ -12,7 +12,7 @@ require conf/machine/include/rockchip-wic.inc
 
 KBUILD_DEFCONFIG ?= "defconfig"
 KERNEL_CLASSES = "kernel-fitimage"
-KERNEL_IMAGETYPE = "fitImage"
+KERNEL_IMAGETYPE ?= "fitImage"
 
 TFA_PLATFORM = "px30"
 TFA_BUILD_TARGET = "bl31"
diff --git a/conf/machine/include/rk3066.inc b/conf/machine/include/rk3066.inc
index fa97906..3510df2 100644
--- a/conf/machine/include/rk3066.inc
+++ b/conf/machine/include/rk3066.inc
@@ -11,4 +11,4 @@ SERIAL_CONSOLES = "115200;ttyS2"
 
 KBUILD_DEFCONFIG = "multi_v7_defconfig"
 KERNEL_FEATURES:append:rk3066 = " 
bsp/rockchip/remove-non-rockchip-arch-arm.scc"
-KERNEL_IMAGETYPE = "zImage"
+KERNEL_IMAGETYPE ?= "zImage"
diff --git a/conf/machine/include/rk3188.inc b/conf/machine/include/rk3188.inc
index bc96a0c..830f908 100644
--- a/conf/machine/include/rk3188.inc
+++ b/conf/machine/include/rk3188.inc
@@ -11,4 +11,4 @@ SERIAL_CONSOLES = "115200;ttyFIQ0"
 
 KBUILD_DEFCONFIG = "multi_v7_defconfig"
 KERNEL_FEATURES:append:rk3188 = " 
bsp/rockchip/remove-non-rockchip-arch-arm.scc"
-KERNEL_IMAGETYPE = "zImage"
+KERNEL_IMAGETYPE ?= "zImage"
diff --git a/conf/machine/include/rk3288.inc b/conf/machine/include/rk3288.inc
index b4c559d..e682c0b 100644
--- a/conf/machine/include/rk3288.inc
+++ b/conf/machine/include/rk3288.inc
@@ -11,6 +11,6 @@ SERIAL_CONSOLES = "115200;ttyS2"
 
 KBUILD_DEFCONFIG ?= "multi_v7_defconfig"
 KERNEL_FEATURES:append:rk3288 = " 
bsp/rockchip/remove-non-rockchip-arch-arm.scc"
-KERNEL_IMAGETYPE = "zImage"
+KERNEL_IMAGETYPE ?= "zImage"
 
 UBOOT_SUFFIX ?= "bin"
diff --git a/conf/machine/include/rk3328.inc b/conf/machine/include/rk3328.inc
index f9f8792..6be777c 100644
--- a/conf/machine/include/rk3328.inc
+++ b/conf/machine/include/rk3328.inc
@@ -13,7 +13,7 @@ require conf/machine/include/rockchip-wic.inc
 KBUILD_DEFCONFIG ?= "defconfig"
 KERNEL_FEATURES:append:rk3328 = " 
bsp/rockchip/remove-non-rockchip-arch-arm64.scc"
 KERNEL_CLASSES = "kernel-fitimage"
-KERNEL_IMAGETYPE = "fitImage"
+KERNEL_IMAGETYPE ?= "fitImage"
 
 TFA_PLATFORM = "rk3328"
 TFA_BUILD_TARGET = "bl31"
diff --git a/conf/machine/include/rk3399.inc b/conf/machine/include/rk3399.inc
index 88c87af..5a3f439 100644
--- a/conf/machine/include/rk3399.inc
+++ b/conf/machine/include/rk3399.inc
@@ -13,7 +13,7 @@ require conf/machine/include/rockchip-wic.inc
 KBUILD_DEFCONFIG ?= "defconfig"
 KERNEL_FEATURES:append:rk3399 = " 
bsp/rockchip/remove-non-rockchip-arch-arm64.scc"
 KERNEL_CLASSES = "kernel-fitimage"
-KERNEL_IMAGETYPE = "fitImage"
+KERNEL_IMAGETYPE ?= "fitImage"
 
 TFA_PLATFORM = "rk3399"
 TFA_BUILD_TARGET = "bl31"
diff --git a/conf/machine/include/rockchip-defaults.inc 
b/conf/machine/include/rockchip-defaults.inc
index 3ce2e24..c5cf6c2 100644
--- a/conf/machine/include/rockchip-defaults.inc
+++ b/conf/machine/include/rockchip-defaults.inc
@@ -1,7 +1,7 @@
 # meta-rockchip default settings
 
 # kernel
-PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
+PREFERRED_PROVIDER_virtual/kernel ??= "linux-yocto"
 KCONFIG_MODE ?= "alldefconfig"
 
 # xserver
diff --git a/conf/machine/include/rockchip-wic.inc 
b/conf/machine/include/rockchip-wic.inc
index 635288c..23ac9d9 100644
--- a/conf/machine/include/rockchip-wic.inc
+++ b/conf/machine/include/rockchip-wic.inc
@@ -11,10 +11,14 @@ WKS_FILE_DEPENDS ?= " \
virtual/bootloader \
virtual/kernel \
"
+ 
+KERNEL_DEVICETREE_BASENAME = "${@os.path.basename('${KERNEL_DEVICETREE}')}"
+
 IMAGE_BOOT_FILES = " \
${KERNEL_IMAGETYPE} \
-   ${@bb.utils.contains('KERNEL_IMAGETYPE', 'fitImage', '', 
'${KERNEL_DEVICETREE}', d)} \
+   ${@bb.utils.contains('KERNEL_IMAGETYPE', 'fitImage', '', 
'${KERNEL_DEVICETREE_BASENAME}', d)} \
"
+IMAGE_EFI_BOOT_FILES += ${IMAGE_BOOT_FILES}
 
 # use the first-defined ; pair in SERIAL_CONSOLES
 # for the console parameter in the wks files
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61112): https://lists.yoctoproject.org/g/yocto/message/61112
Mute This Topic: https://lists.yoctoproject.org/mt/1

[yocto] [kirkstone][mickledore][master][PATCH] mingw-libgnurx: dev package conflicts with libc6-dev

2023-09-25 Thread Changqing Li 
From: Changqing Li 

bitbake core-image-minimal, do_rootfs will fail with following configs:
SDKMACHINE = "x86_64-mingw32"
IMAGE_INSTALL:append = " mingw-libgnurx"
EXTRA_IMAGE_FEATURES = "dbg-pkgs dev-pkgs debug-tweaks"

libgnurx is the regex functionality from glibc 2.5 extracted into a
separate library, for Win32. So its dev package has conflict files with
libc6-dev.

Signed-off-by: Changqing Li 
---
 recipes-support/mingw-libgnurx/mingw-libgnurx_2.5.1.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/recipes-support/mingw-libgnurx/mingw-libgnurx_2.5.1.bb 
b/recipes-support/mingw-libgnurx/mingw-libgnurx_2.5.1.bb
index 4547298..127cdcd 100644
--- a/recipes-support/mingw-libgnurx/mingw-libgnurx_2.5.1.bb
+++ b/recipes-support/mingw-libgnurx/mingw-libgnurx_2.5.1.bb
@@ -15,3 +15,5 @@ inherit autotools
 EXTRA_OECONF = ""
 
 BBCLASSEXTEND = "nativesdk"
+
+RCONFLICTS:${PN}-dev = "libc6-dev"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6): https://lists.yoctoproject.org/g/yocto/message/6
Mute This Topic: https://lists.yoctoproject.org/mt/101588801/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] M+ & H bugs with Milestone Movements WW38

2023-09-25 Thread Stephen Jolley 
All,

YP M+ or high bugs which moved to a new milestone in WW38 are listed below:
Priority Bug ID Short Description Changer Owner Was Became
Medium+ 15218  Using
SSTATE_MIRRORS does not work with https and basic authentication
randy.macl...@windriver.com peter.zsifkov...@at.bosch.com 0.0.0 5.0 M1

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

(*Cell*:(208) 244-4460

* *Email*: *s
jolley.yp...@gmail.com *

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61110): https://lists.yoctoproject.org/g/yocto/message/61110
Mute This Topic: https://lists.yoctoproject.org/mt/101587971/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Enhancements/Bugs closed WW38!

2023-09-25 Thread Stephen Jolley 
All,

The below were the owners of enhancements or bugs closed during the last
week!
Who Count
richard.pur...@linuxfoundation.org 7
ross.bur...@arm.com 1
Grand Total 8

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

(*Cell*:(208) 244-4460

* *Email*: *s
jolley.yp...@gmail.com *

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61109): https://lists.yoctoproject.org/g/yocto/message/61109
Mute This Topic: https://lists.yoctoproject.org/mt/101587957/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Current high bug count owners for Yocto Project 4.3

2023-09-25 Thread Stephen Jolley 
All,

Below is the list of top 27 bug owners as of the end of WW38 who have open
medium or higher bugs and enhancements against YP 4.3. There are 3 possible
work days left until the final release candidates for YP 4.3 needs to be
released.
Who Count
michael.opdenac...@bootlin.com 34
ross.bur...@arm.com 31
richard.pur...@linuxfoundation.org 24
david.re...@windriver.com 23
randy.macl...@windriver.com 22
bruce.ashfi...@gmail.com 15
jpewhac...@gmail.com 11
pi...@pidge.org 7
pa...@zhukoff.net 6
sakib.sa...@windriver.com 5
yash.shi...@windriver.com 4
tim.orl...@konsulko.com 2
sundeep.kokko...@windriver.com 2
jon.ma...@arm.com 2
alexis.loth...@bootlin.com 2
alexandre.bell...@bootlin.com 2
tvgamb...@gmail.com 1
thr...@amazon.de 1
thomas.per...@bootlin.com 1
pokyli...@reliableembeddedsystems.com 1
p.lob...@welotec.com 1
martin.ja...@gmail.com 1
mark.asselst...@windriver.com 1
louis.ran...@syslinbit.com 1
jens.ge...@desy.de 1
fathi.bou...@linaro.org 1
alejan...@enedino.org 1
Grand Total 203

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

(*Cell*:(208) 244-4460

* *Email*: *s
jolley.yp...@gmail.com *

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61108): https://lists.yoctoproject.org/g/yocto/message/61108
Mute This Topic: https://lists.yoctoproject.org/mt/101587918/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2023-09-25 Thread Stephen Jolley 
All,

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means
people can find them. They're being listed on the triage page under the
appropriate heading:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:
https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project. If anyone can help,
please take ownership of the bug and send patches! If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 413
unassigned or newcomer bugs.

We're hoping people may be able to spare some time now and again to help
out with these. Bugs are split into two types, "true bugs" where things
don't work as they should and "enhancements" which are features we'd want
to add to the system. There are also roughly four different "priority"
classes right now, “4.3”, “4.4”, "4.99" and "Future", the more
pressing/urgent issues being in "4.3" and then “4.4”.

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com)
an e-mail with the bug number you would like and I will assign it to you
(please make sure you have a Bugzilla account). The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

(*Cell*:(208) 244-4460

* *Email*: *s
jolley.yp...@gmail.com *

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61107): https://lists.yoctoproject.org/g/yocto/message/61107
Mute This Topic: https://lists.yoctoproject.org/mt/101587890/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-raspberrypi][PATCH] rpi-base: wic images depend on the kernel

2023-09-25 Thread Joshua Watt 
wic images depend on the kernel device trees, and therefore should
depend on virtual/kernel:do_deploy to make sure these are present in the
deploy directory.

Most of the time, this dependency is satisfied indirectly since a rootfs
image will depend on the kernel, but add it explicitly for the cases
where it is not.

Signed-off-by: Joshua Watt 
---
 conf/machine/include/rpi-base.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index 895fcfe..64f60ab 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -149,6 +149,7 @@ IMAGE_BOOT_FILES ?= "${BOOTFILES_DIR_NAME}/* \
  ${RPI_EXTRA_IMAGE_BOOT_FILES} \
  "
 do_image_wic[depends] += " \
+virtual/kernel:do_deploy \
 rpi-bootfiles:do_deploy \
 ${@bb.utils.contains('RPI_USE_U_BOOT', '1', 'u-boot:do_deploy', '',d)} \
 "
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61106): https://lists.yoctoproject.org/g/yocto/message/61106
Mute This Topic: https://lists.yoctoproject.org/mt/101583229/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] bbappend not working for recipe with git in name

2023-09-25 Thread John Klug 
Yoann Congal wrote:
>I may be wrong but it looks like you have 2 kernel-module-nxp89xx recipes : 
>* one called kernel-module-nxp89xx_git.bb which is bbappended in you layer
>* another one called kernel-module-nxp89xx.bb (no PV in filename), which is 
>preferred over the _git one.

This is indeed the case, and removing _git in the bbappend file name cured the 
problem.  Thanks.

John Klug
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61105): https://lists.yoctoproject.org/g/yocto/message/61105
Mute This Topic: https://lists.yoctoproject.org/mt/101569034/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] bbappend not working for recipe with git in name

2023-09-25 Thread Yoann Congal 
Hello,

Le lun. 25 sept. 2023 à 06:55, John Klug  a écrit :

> bitbake-layers show-appends reports:
>
>   Summary: There were 3 WARNING messages.
>   === Matched appended recipes ===
>   kernel-module-nxp89xx_git.bb:
>
>  
> /home/jklug/mlinux-kirk2/layers/meta-multitech-nxp/recipes-kernel/kernel-module-nxp89xx/kernel-module-nxp89xx_%.bbappend
>   WARNING: kernel-module-nxp89xx.bb: missing append for preferred version
>

I may be wrong but it looks like you have 2 kernel-module-nxp89xx recipes :
* one called kernel-module-nxp89xx_git.bb which is bbappended in you layer
* another one called kernel-module-nxp89xx.bb (no PV in filename), which is
preferred over the _git one.

I guess you an either :
* Use kernel-module-nxp89xx.bb : rename your bbappend to
kernel-module-nxp89xx.bbappend
* keep kernel-module-nxp89xx_git.bb : remove or inhibit
kernel-module-nxp89xx.bb

I have tried _git instead of _%.
>
> I have also tried 1.0, since bitbake -e reports:
>
>   PV="1.0"
>
> What should I be doing?  Nothing in the bbappend does anything, unless I
> make it invalid, then I get an error.
>
> SRCREV is set in this recipe as a hash.
>
>
> John Klug
> 
>
>
Regards,
-- 
Yoann Congal
Smile ECS - Tech expert

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61104): https://lists.yoctoproject.org/g/yocto/message/61104
Mute This Topic: https://lists.yoctoproject.org/mt/101569034/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-rockchip][PATCH v3] rock-5b: add

2023-09-25 Thread Trevor Woerner 
Add support for the Radxa Rock 5B
https://wiki.radxa.com/Rock5/5b

The device-tree for this board is better in the 6.5 (and later) kernels,
therefore set the kernel to linux-yocto-dev for now (eventually this won't be
needed as linux-yocto moves forward).

Unfortunately the TF-A project does not currently have support for
the rk3588. Therefore, for the time-being, the only way to supply a
TPL/DDR-init for the rk3588 is to use the closed-source rkbin binaries
from Rockchip. If/when TF-A adds support for the rk3588 we can investigate
switching.

The rk3588 comes in two variants: rk3588 and rk3588s. The "s" option is a
stripped-down version of the rk3588. In the Linux kernel these two SoCs are
kept separate, with the rk3588 building on the rk3588s, so we've mimicked that
same behaviour here.

Signed-off-by: Quentin Schulz 
Signed-off-by: Trevor Woerner 
---
v3:
- change name from "rock5b" to "rock-5b", there seem to be more instances
  of the latter on the manufacturer's website than the former
- fix the MACHINEOVERRIDE in conf/machine/include/rk3588s.inc to be
  "rk3588s" and not "rk3588"

v2:
- fix the logic behind the MACHINEOVERRIDES to get the content, and 
  ordering, correct
- improved the commit message around TF-A/rkbin
- correct Quentin's SoB line
---
 README|  1 +
 conf/machine/include/rk3588.inc   |  6 ++
 conf/machine/include/rk3588s.inc  | 17 
 conf/machine/rock-5b.conf | 12 +++
 recipes-bsp/rkbin/rockchip-rkbin_git.bb   | 37 
 recipes-bsp/u-boot/u-boot%.bbappend   |  5 ++
 recipes-kernel/linux/linux-yocto-dev.bbappend |  3 +
 .../rockchip/remove-non-rockchip-arch-arm.cfg | 85 +++
 .../rockchip/remove-non-rockchip-arch-arm.scc |  1 +
 .../remove-non-rockchip-arch-arm64.cfg| 66 ++
 .../remove-non-rockchip-arch-arm64.scc|  1 +
 11 files changed, 234 insertions(+)
 create mode 100644 conf/machine/include/rk3588.inc
 create mode 100644 conf/machine/include/rk3588s.inc
 create mode 100644 conf/machine/rock-5b.conf
 create mode 100644 recipes-bsp/rkbin/rockchip-rkbin_git.bb
 create mode 100644 recipes-kernel/linux/linux-yocto-dev.bbappend
 create mode 100644 
recipes-kernel/linux/linux-yocto-dev/rockchip-kmeta/bsp/rockchip/remove-non-rockchip-arch-arm.cfg
 create mode 100644 
recipes-kernel/linux/linux-yocto-dev/rockchip-kmeta/bsp/rockchip/remove-non-rockchip-arch-arm.scc
 create mode 100644 
recipes-kernel/linux/linux-yocto-dev/rockchip-kmeta/bsp/rockchip/remove-non-rockchip-arch-arm64.cfg
 create mode 100644 
recipes-kernel/linux/linux-yocto-dev/rockchip-kmeta/bsp/rockchip/remove-non-rockchip-arch-arm64.scc

diff --git a/README b/README
index 286dafbe1020..d4576d73c636 100644
--- a/README
+++ b/README
@@ -30,6 +30,7 @@ Status of supported boards:
vyasa-rk3288
firefly-rk3288
nanopi-r4s
+   rock-5b
builds:
marsboard-rk3066
radxarock
diff --git a/conf/machine/include/rk3588.inc b/conf/machine/include/rk3588.inc
new file mode 100644
index ..34f0627dc085
--- /dev/null
+++ b/conf/machine/include/rk3588.inc
@@ -0,0 +1,6 @@
+MACHINEOVERRIDES =. "rk3588:"
+
+# the rk3588s is a "stripped-down" version of the rk3588
+# in the kernel's device-tree the rk3588 builds on top of the rk3588s
+# so anything that is valid for the rk3588s is valid for the rk3588
+require conf/machine/include/rk3588s.inc
diff --git a/conf/machine/include/rk3588s.inc b/conf/machine/include/rk3588s.inc
new file mode 100644
index ..7bfc9474e96e
--- /dev/null
+++ b/conf/machine/include/rk3588s.inc
@@ -0,0 +1,17 @@
+MACHINEOVERRIDES =. "rk3588s:"
+DEFAULTTUNE ?= "cortexa76-cortexa55-crypto"
+
+require conf/machine/include/arm/armv8-2a/tune-cortexa76-cortexa55.inc
+require conf/machine/include/rockchip-defaults.inc
+require conf/machine/include/rockchip-wic.inc
+
+KBUILD_DEFCONFIG ?= "defconfig"
+KERNEL_FEATURES:append:rk3588s = " 
bsp/rockchip/remove-non-rockchip-arch-arm64.scc"
+KERNEL_CLASSES = "kernel-fitimage"
+KERNEL_IMAGETYPE = "fitImage"
+
+PREFERRED_PROVIDER_trusted-firmware-a = "rockchip-rkbin"
+PREFERRED_PROVIDER_optee-os = "rockchip-rkbin"
+
+UBOOT_SUFFIX ?= "itb"
+UBOOT_ENTRYPOINT ?= "0x0600"
diff --git a/conf/machine/rock-5b.conf b/conf/machine/rock-5b.conf
new file mode 100644
index ..d1371084becc
--- /dev/null
+++ b/conf/machine/rock-5b.conf
@@ -0,0 +1,12 @@
+#@TYPE: Machine
+#@NAME: Radxa Rock 5B
+#@DESCRIPTION: ROCK5 is the 5th generation of SBC designed by Radxa.
+#https://wiki.radxa.com/Rock5/5b
+
+require conf/machine/include/rk3588.inc
+
+PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-dev"
+KERNEL_DEVICETREE = "rockchip/rk3588-rock-5b.dtb"
+MACHINE_EXTRA_RRECOMMENDS += "kernel-modules"
+
+UBOOT_MACHINE = "rock5b-rk3588_defconfig"
diff --git a/recipes-bsp/rkbin/rockchip-rkbin_git.bb 
b/recipes-bsp/rkbin/rockchip-rkbin_git.bb
new file

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.0.13.rc2)

2023-09-25 Thread Jing Hui Tham 
Hi all,
 
Intel and WR YP QA is planning for QA execution for YP build yocto-4.0.13.rc2. 
We are planning to execute following tests for this cycle:
 
OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw
 
Runtime auto test for following platforms:
1. MinnowBoard Turbot - 32bit
2. Kaby Lake (7th Generation Intel(r) Core(tm) Processors)
3. Tiger Lake (11th Generation Intel(r) Core(tm) Processors)
4. Alder Lake-S (12th Generation Intel(r) Core(tm) Processors)
5. Raptor Lake-P (13th Generation Intel(r) Core(tm) Processors)
6. Edgerouter
7. Beaglebone

 
ETA for completion 28/09/2023.
 
Best regards,
Jing Hui

> -Original Message-
> From: qa-build-notificat...@lists.yoctoproject.org  notificat...@lists.yoctoproject.org> On Behalf Of Pokybuild User
> Sent: Monday, September 25, 2023 2:49 PM
> To: yocto@lists.yoctoproject.org
> Cc: qa-build-notificat...@lists.yoctoproject.org
> Subject: [qa-build-notification] QA notification for completed autobuilder
> build (yocto-4.0.13.rc2)
> 
> 
> A build flagged for QA (yocto-4.0.13.rc2) was completed on the autobuilder
> and is available at:
> 
> 
> https://autobuilder.yocto.io/pub/releases/yocto-4.0.13.rc2
> 
> 
> Build hash information:
> 
> bitbake: 41b6684489d0261753344956042be2cc4adb0159
> meta-agl: 666f141563fd7fc12b7638479d5c0cd38dae5006
> meta-arm: b187fb9232ca0a6b5f8f90b4715958546fc41d73
> meta-aws: 60891e535ce219b3c473a89d8ae89cdba1d396f4
> meta-gplv2: d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a
> meta-intel: 1342bcdc5bfc6620737e7d195e7d9bd744348577
> meta-mingw: a90614a6498c3345704e9611f2842eb933dc51c1
> meta-openembedded: a88cb922f91fda95e8a584cee3092083d5ad3e98
> meta-virtualization: 2d8b3cba8ff27c9ec2187a52b6a551fe1dcfaa07
> oecore: d90e4d5e3cca9cffe8f60841afc63667a9ac39fa
> poky: e51bf557f596c4da38789a948a3228ba11455e3c
> 
> 
> 
> This is an automated message from the Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder2
> Email: richard.pur...@linuxfoundation.org
> 
> 
> 
> 
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61102): https://lists.yoctoproject.org/g/yocto/message/61102
Mute This Topic: https://lists.yoctoproject.org/mt/101577693/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-rockchip][PATCH v2] rock5b: add

2023-09-25 Thread Trevor Woerner 
On Mon 2023-09-25 @ 03:36:06 PM, Quentin Schulz wrote:
> Hi Trevor,
> 
> On 9/22/23 23:26, Trevor Woerner wrote:
> > Add support for the Radxa Rock 5B
> > https://wiki.radxa.com/Rock5/5b
> > 
> > The device-tree for this board is better in the 6.5 (and later) kernels,
> > therefore set the kernel to linux-yocto-dev for now (eventually this won't 
> > be
> > needed as linux-yocto moves forward).
> > 
> > Unfortunately the TF-A project does not currently have support for
> > the rk3588. Therefore, for the time-being, the only way to supply a
> > TPL/DDR-init for the rk3588 is to use the closed-source rkbin binaries
> > from Rockchip. If/when TF-A adds support for the rk3588 we can investigate
> > switching.
> > 
> > The rk3588 comes in two variants: rk3588 and rk3588s. The "s" option is a
> > stripped-down version of the rk3588. In the Linux kernel these two SoCs are
> > kept separate, with the rk3588 building on the rk3588s, so we've mimicked 
> > that
> > same behaviour here.
> > 
> > Signed-off-by: Quentin Schulz 
> > Signed-off-by: Trevor Woerner 
> > ---
> > v2:
> > - fix the logic behind the MACHINEOVERRIDES to get the content, and
> >ordering, correct
> > - improved the commit message around TF-A/rkbin
> > - correct Quentin's SoB line
> > ---
> >   README|  1 +
> >   conf/machine/include/rk3588.inc   |  6 ++
> >   conf/machine/include/rk3588s.inc  | 17 
> >   conf/machine/rock5b.conf  | 12 +++
> >   recipes-bsp/rkbin/rockchip-rkbin_git.bb   | 37 
> >   recipes-bsp/u-boot/u-boot%.bbappend   |  5 ++
> >   recipes-kernel/linux/linux-yocto-dev.bbappend |  3 +
> >   .../rockchip/remove-non-rockchip-arch-arm.cfg | 85 +++
> >   .../rockchip/remove-non-rockchip-arch-arm.scc |  1 +
> >   .../remove-non-rockchip-arch-arm64.cfg| 66 ++
> >   .../remove-non-rockchip-arch-arm64.scc|  1 +
> >   11 files changed, 234 insertions(+)
> >   create mode 100644 conf/machine/include/rk3588.inc
> >   create mode 100644 conf/machine/include/rk3588s.inc
> >   create mode 100644 conf/machine/rock5b.conf
> >   create mode 100644 recipes-bsp/rkbin/rockchip-rkbin_git.bb
> >   create mode 100644 recipes-kernel/linux/linux-yocto-dev.bbappend
> >   create mode 100644 
> > recipes-kernel/linux/linux-yocto-dev/rockchip-kmeta/bsp/rockchip/remove-non-rockchip-arch-arm.cfg
> >   create mode 100644 
> > recipes-kernel/linux/linux-yocto-dev/rockchip-kmeta/bsp/rockchip/remove-non-rockchip-arch-arm.scc
> >   create mode 100644 
> > recipes-kernel/linux/linux-yocto-dev/rockchip-kmeta/bsp/rockchip/remove-non-rockchip-arch-arm64.cfg
> >   create mode 100644 
> > recipes-kernel/linux/linux-yocto-dev/rockchip-kmeta/bsp/rockchip/remove-non-rockchip-arch-arm64.scc
> > 
> > diff --git a/README b/README
> > index 286dafbe1020..032d9bbb6b34 100644
> > --- a/README
> > +++ b/README
> > @@ -30,6 +30,7 @@ Status of supported boards:
> > vyasa-rk3288
> > firefly-rk3288
> > nanopi-r4s
> > +   rock5b
> > builds:
> > marsboard-rk3066
> > radxarock
> > diff --git a/conf/machine/include/rk3588.inc 
> > b/conf/machine/include/rk3588.inc
> > new file mode 100644
> > index ..34f0627dc085
> > --- /dev/null
> > +++ b/conf/machine/include/rk3588.inc
> > @@ -0,0 +1,6 @@
> > +MACHINEOVERRIDES =. "rk3588:"
> > +
> > +# the rk3588s is a "stripped-down" version of the rk3588
> > +# in the kernel's device-tree the rk3588 builds on top of the rk3588s
> > +# so anything that is valid for the rk3588s is valid for the rk3588
> > +require conf/machine/include/rk3588s.inc
> > diff --git a/conf/machine/include/rk3588s.inc 
> > b/conf/machine/include/rk3588s.inc
> > new file mode 100644
> > index ..65d9054e88d8
> > --- /dev/null
> > +++ b/conf/machine/include/rk3588s.inc
> > @@ -0,0 +1,17 @@
> > +MACHINEOVERRIDES =. "rk3588s:"
> > +DEFAULTTUNE ?= "cortexa76-cortexa55-crypto"
> > +
> > +require conf/machine/include/arm/armv8-2a/tune-cortexa76-cortexa55.inc
> > +require conf/machine/include/rockchip-defaults.inc
> > +require conf/machine/include/rockchip-wic.inc
> > +
> > +KBUILD_DEFCONFIG ?= "defconfig"
> > +KERNEL_FEATURES:append:rk3588 = " 
> > bsp/rockchip/remove-non-rockchip-arch-arm64.scc"
> 
> I believe this is supposed to be an OVERRIDES for rk3588s and not rk3588
> since it applies to both (in addition of being in the rk3588s.inc file).

Great catch!

> 
> The rest looks fine otherwise :)

Thanks :-)

> 
> Thanks!
> 
> Cheers,
> Quentin
> 
> > +KERNEL_CLASSES = "kernel-fitimage"
> > +KERNEL_IMAGETYPE = "fitImage"
> > +
> > +PREFERRED_PROVIDER_trusted-firmware-a = "rockchip-rkbin"
> > +PREFERRED_PROVIDER_optee-os = "rockchip-rkbin"
> > +
> > +UBOOT_SUFFIX ?= "itb"
> > +UBOOT_ENTRYPOINT ?= "0x0600"
> > diff --git a/conf/machine/rock5b.conf b/conf/machine/rock5b.conf
> > new file mode 100644
> > index ..dc31a9f3a4

Re: [yocto] [meta-rockchip][PATCH v2] rock5b: add

2023-09-25 Thread Trevor Woerner 
Hi Anthony,

On Sun 2023-09-24 @ 05:10:41 PM, Anthony Davies wrote:
> Thanks for your work Trevor, I have been waiting for this for a while.
> 
> I am new around here so forgive me if I am being impertinent but my only
> feedback would be to keep the naming of the machines consistent with the dtb
> and uboot defconfig? ie, rock-5b rather then rock5b?

In meta-rockchip we try to follow the naming that the manufacturer gives to
the product. Device-tree names come and go, get munged together, and split
apart. While the kernel might call it rock-5b today, some new board might come
along that causes a refactorisation leading to a whole bunch of renaming.

That said the manufacturer isn't 100% clear on the naming of this product. One
of the original post introducing the product,
https://forum.radxa.com/t/introduce-rock-5-model-b-arm-desktop-level-sbc/8361
shows it written both "Rock5B" and "Rock 5B".

>From the manufacturer's own website, they seem to attach the "5" to the "Rock"
(without a space) when they're just saying "Rock5", but add a space when
they're distinguishing between the "A" and "B" variants:
https://wiki.radxa.com/Rock5
https://wiki.radxa.com/Rock5/5b

So the naming could go either way. Given that there are more instances of
"Rock 5B" we could go with what you suggest.

Thanks!

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61100): https://lists.yoctoproject.org/g/yocto/message/61100
Mute This Topic: https://lists.yoctoproject.org/mt/101530319/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-rockchip][PATCH v2] rock5b: add

2023-09-25 Thread Quentin Schulz via lists.yoctoproject.org 

Hi Trevor,

On 9/22/23 23:26, Trevor Woerner wrote:

Add support for the Radxa Rock 5B
https://wiki.radxa.com/Rock5/5b

The device-tree for this board is better in the 6.5 (and later) kernels,
therefore set the kernel to linux-yocto-dev for now (eventually this won't be
needed as linux-yocto moves forward).

Unfortunately the TF-A project does not currently have support for
the rk3588. Therefore, for the time-being, the only way to supply a
TPL/DDR-init for the rk3588 is to use the closed-source rkbin binaries
from Rockchip. If/when TF-A adds support for the rk3588 we can investigate
switching.

The rk3588 comes in two variants: rk3588 and rk3588s. The "s" option is a
stripped-down version of the rk3588. In the Linux kernel these two SoCs are
kept separate, with the rk3588 building on the rk3588s, so we've mimicked that
same behaviour here.

Signed-off-by: Quentin Schulz 
Signed-off-by: Trevor Woerner 
---
v2:
- fix the logic behind the MACHINEOVERRIDES to get the content, and
   ordering, correct
- improved the commit message around TF-A/rkbin
- correct Quentin's SoB line
---
  README|  1 +
  conf/machine/include/rk3588.inc   |  6 ++
  conf/machine/include/rk3588s.inc  | 17 
  conf/machine/rock5b.conf  | 12 +++
  recipes-bsp/rkbin/rockchip-rkbin_git.bb   | 37 
  recipes-bsp/u-boot/u-boot%.bbappend   |  5 ++
  recipes-kernel/linux/linux-yocto-dev.bbappend |  3 +
  .../rockchip/remove-non-rockchip-arch-arm.cfg | 85 +++
  .../rockchip/remove-non-rockchip-arch-arm.scc |  1 +
  .../remove-non-rockchip-arch-arm64.cfg| 66 ++
  .../remove-non-rockchip-arch-arm64.scc|  1 +
  11 files changed, 234 insertions(+)
  create mode 100644 conf/machine/include/rk3588.inc
  create mode 100644 conf/machine/include/rk3588s.inc
  create mode 100644 conf/machine/rock5b.conf
  create mode 100644 recipes-bsp/rkbin/rockchip-rkbin_git.bb
  create mode 100644 recipes-kernel/linux/linux-yocto-dev.bbappend
  create mode 100644 
recipes-kernel/linux/linux-yocto-dev/rockchip-kmeta/bsp/rockchip/remove-non-rockchip-arch-arm.cfg
  create mode 100644 
recipes-kernel/linux/linux-yocto-dev/rockchip-kmeta/bsp/rockchip/remove-non-rockchip-arch-arm.scc
  create mode 100644 
recipes-kernel/linux/linux-yocto-dev/rockchip-kmeta/bsp/rockchip/remove-non-rockchip-arch-arm64.cfg
  create mode 100644 
recipes-kernel/linux/linux-yocto-dev/rockchip-kmeta/bsp/rockchip/remove-non-rockchip-arch-arm64.scc

diff --git a/README b/README
index 286dafbe1020..032d9bbb6b34 100644
--- a/README
+++ b/README
@@ -30,6 +30,7 @@ Status of supported boards:
vyasa-rk3288
firefly-rk3288
nanopi-r4s
+   rock5b
builds:
marsboard-rk3066
radxarock
diff --git a/conf/machine/include/rk3588.inc b/conf/machine/include/rk3588.inc
new file mode 100644
index ..34f0627dc085
--- /dev/null
+++ b/conf/machine/include/rk3588.inc
@@ -0,0 +1,6 @@
+MACHINEOVERRIDES =. "rk3588:"
+
+# the rk3588s is a "stripped-down" version of the rk3588
+# in the kernel's device-tree the rk3588 builds on top of the rk3588s
+# so anything that is valid for the rk3588s is valid for the rk3588
+require conf/machine/include/rk3588s.inc
diff --git a/conf/machine/include/rk3588s.inc b/conf/machine/include/rk3588s.inc
new file mode 100644
index ..65d9054e88d8
--- /dev/null
+++ b/conf/machine/include/rk3588s.inc
@@ -0,0 +1,17 @@
+MACHINEOVERRIDES =. "rk3588s:"
+DEFAULTTUNE ?= "cortexa76-cortexa55-crypto"
+
+require conf/machine/include/arm/armv8-2a/tune-cortexa76-cortexa55.inc
+require conf/machine/include/rockchip-defaults.inc
+require conf/machine/include/rockchip-wic.inc
+
+KBUILD_DEFCONFIG ?= "defconfig"
+KERNEL_FEATURES:append:rk3588 = " 
bsp/rockchip/remove-non-rockchip-arch-arm64.scc"


I believe this is supposed to be an OVERRIDES for rk3588s and not rk3588 
since it applies to both (in addition of being in the rk3588s.inc file).


The rest looks fine otherwise :)

Thanks!

Cheers,
Quentin


+KERNEL_CLASSES = "kernel-fitimage"
+KERNEL_IMAGETYPE = "fitImage"
+
+PREFERRED_PROVIDER_trusted-firmware-a = "rockchip-rkbin"
+PREFERRED_PROVIDER_optee-os = "rockchip-rkbin"
+
+UBOOT_SUFFIX ?= "itb"
+UBOOT_ENTRYPOINT ?= "0x0600"
diff --git a/conf/machine/rock5b.conf b/conf/machine/rock5b.conf
new file mode 100644
index ..dc31a9f3a4e4
--- /dev/null
+++ b/conf/machine/rock5b.conf
@@ -0,0 +1,12 @@
+#@TYPE: Machine
+#@NAME: Radxa Rock5b
+#@DESCRIPTION: ROCK5 is the 5th generation of SBC designed by Radxa.
+#https://wiki.radxa.com/Rock5/5b
+
+require conf/machine/include/rk3588.inc
+
+PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-dev"
+KERNEL_DEVICETREE = "rockchip/rk3588-rock-5b.dtb"
+MACHINE_EXTRA_RRECOMMENDS += "kernel-modules"
+
+UBOOT_MACHINE = "rock5b-rk3588_defconfig"
diff --git a/recipes-bsp/rkbin/rockchip-rkbin_git.bb 
b/recipe

Re: [yocto] Security processes: YP needs

2023-09-25 Thread Reyna, David via lists.yoctoproject.org 
Hi Marta,

* SRTool: We might decide to use it again. It allows one to do much but 
requires constant commitment.

There are many ways to use the SRTool. 
  (a)  The original design was to perform 100% triage of incoming CVEs. This 
was a business requirement of Wind River, and we have used the SRTool 
successfully for 4-5 year now.
  (b)  The main limitation with the SRTool for Yocto Project was the lack of 
integration with Bugzilla (Ross ran out of time)
 * This is the crucial other half of the workflow
 * There is the automatic creation of appropriate defect records for 
investigation
 * There is also the automatic tracking of the overall CVE status, both 
CVEs in progress and the CVEs completed
 * Wind River has an extension for full integration with Jira, and that 
saves weeks of work for the CVE management
  (c) The guiding rule was that CVE management was in the SRTool, but specific 
defect work was also done in Jira/Bugzilla, for a clean separate of domains
  (d)  The SRTool has a user model
 * Together with Bugzilla, it is easy to track single people and even 
multiple people working on CVEs
  (e) The SRTool also has the built-on ability to look up the CVE status from 
other distributions (Red Hat, Debian, ...) so that one can get a peek of 
existing triages and resolutions
  (f) The SRTool is build like Toaster on top of Django, so development and 
debugging skills for Toaster immediate apply
  (g) Also with the Django base, it is very simple to add any number of modular 
extensions to support for example CVE Scanner integration
  (h) The SRTool also has report generation (in text, CSV, and Excel) in 
addition to email notification support.
  (i) There is also a "private" model for CVEs under embargo, with strict 
access control lists.

PROPOSAL 1: If the full triage is too much to bite off to start with, perhaps 
using it to track and coordinate work will bring immediate benefit.

PROPOSAL 2: I am happy to give you a live demo of Wind River's fully 
operational SRTool, so you can see all of the bells and whistles in action. I 
am available pretty much anytime between 10:00 am Pacific to 2:00 am Pacific.

PROPOSAL 3: I will start refreshing the YP SRTool repository with my current 
implementation level from Wind River (with the Wind River specific modules left 
out of course :-)

David

BTW, I also support an extension to the SRTool that manages CVE scanning of 
build images, with hooks to a  number existing CVE scanners (e.g. Trivy) in 
addition to other vulnerability metrics. This is probably out of scope to YP at 
this time, but it is perhaps something to grow in to.

-Original Message-
From: yocto@lists.yoctoproject.org  On Behalf Of 
Marta Rybczynska via lists.yoctoproject.org
Sent: Wednesday, September 13, 2023 4:52 AM
To: yocto-secur...@lists.yoctoproject.org; OE-core 
; 
openembedded-architect...@lists.openembedded.org; yocto@lists.yoctoproject.org
Cc: Richard Purdie ; Steve Sakoman 
; Khem Raj ; 
mark.ha...@kernel.crashing.org; Ross Burton ; Joshua Watt 

Subject: [yocto] Security processes: YP needs

Hello,
I've been working recently on collecting what works and what doesn't
in YP security processes. The goal is to go forward and define an
actionable strategy!

Today, I'd like to share with you the summary of what I have heard as
needs from several people (those in Cc:).

I want the community to comment and tell us what you find important
and what you'd like to see added or changed from this list.

* CVEs: Visibility if YP is vulnerable or not

People want to be able to check/look up a specific CVE; it might be a
CVE unrelated to YP
(eg. package not included, Windows issue). The cve-checker result is a
part of the solution, but people also want to know which CVEs do not
apply.

* CVEs: synchronization of the work on fixes

Currently, there is no synchronization; multiple parties might be
working on the same fix while nobody is working on another. There
might be duplication of work.
Ross has https://wiki.yoctoproject.org/wiki/CVE_Status

* Triaging of security issues

Related to CVE fixes and includes issues reported directly to the YP.
Some issues are more likely to be serious for embedded products
(attack by network), so not all has the same priority.

* Private security communication

A way to send a notification of a non-public security issue. For
researchers, other projects etc.
The security alias exists, but only some people know about its existence.

* Visibility of the security work of the YP

There is much work on security in the YP, but it lacks visibility.

* Documentation

Related to visibility. We need easy-to-find documentation of subjects
like submitting a CVE fix,
reporting a private issue, and how our processes work... This
documentation should address people who are not regular contributors.

* Additional tooling

We could add additional tooling: a template on how to add cve-check to
the CI (possibly
a different one than the autobuilder), an