[yocto] QA cycle report for yocto-3.0.1.rc3

Hello all, This is the full report for 3.0.1 RC3: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults === Summary No high milestone defects. No new defects are found in this cycle. valgrind ptest failed (BUG id:13666). === Bu

Re: [yocto] Yocto Image Build for NXP i.MX8M

On 11/28/19 7:02 AM, Aj Cit wrote: Dear Josef, I've managed to run build command to generate OS image for the target, which is |core-image-sato| by executing the following command: $ bitbake core-image-sato Can I know how to proceed further? I'm getting the following response from th

Re: [yocto] [OE-core] Removal of Python 2 from oe-core

On 12/2/19 2:27 PM, Ross Burton wrote: > At the time of writing, pythonclock.org tells me that Python 2.7 will > retire in 29 days and 1 hour. > > This means no more releases of Python 2.  No more security fixes.  No > critical bug fixes.  No support at all. > > As such, we're removing Python 2 f

[yocto] Removal of Python 2 from oe-core

At the time of writing, pythonclock.org tells me that Python 2.7 will retire in 29 days and 1 hour. This means no more releases of Python 2. No more security fixes. No critical bug fixes. No support at all. As such, we're removing Python 2 from openembedded-core on Monday 9th December. P

[yocto] KVM Kernel Module not being built for Yocto Kernel

Dear KVM community, First of all I'd like mention I've posted this question on the Yocto mailing list as well as the KVM mailing list because my question has huge ties to the bitbake process (a concept related to the Yocto project). Though I believe I'm mainly addressing the KVM community because

Re: [yocto] Are both TFTPd and TFTPd-HPA handled in one YP version ?

Sorry, I’m a newbie in YP. I use YP Morty 2.2 and from it, I’d like to know which YP version(s) is able to handle both tftpd and atftpd or (tftpd-hpa) ? Are you referring to loading the kernel and dts files from tftp during bootup as part of a TFTP & NFS setup ? If so, that is simply somethin

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

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:

[yocto] Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am on the first Tuesday (PDT)

All, Just a reminder we will hold the monthly Yocto Project Technical Meeting at 8am PST tomorrow. (12/2) Yocto Project Technical Team Meeting: We encourage people attending the meeting to logon and announce themselves on the Yocto Project IRC chancel during the meeting (optional): Yocto

[yocto] Are both TFTPd and TFTPd-HPA handled in one YP version ?

Sorry, I’m a newbie in YP. I use YP Morty 2.2 and from it, I’d like to know which YP version(s) is able to handle both tftpd and atftpd or (tftpd-hpa) ? Thank you for your support ! J-Fr+ -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#47504): https

Re: [yocto] linux-libc-headers - how to handle for older kernels?

On Mon, Dec 02, 2019 at 04:01:41PM +0200, Adrian Bunk wrote: > On Mon, Dec 02, 2019 at 09:33:33AM +, Mikko Rapeli wrote: > >... > > On Mon, Dec 02, 2019 at 09:28:03AM +, Mike Looijmans wrote: > > > One solution I can think of is to put the header into it's own > > > recipe/repository and t

Re: [yocto] linux-libc-headers - how to handle for older kernels?

On Mon, Dec 02, 2019 at 09:33:33AM +, Mikko Rapeli wrote: >... > On Mon, Dec 02, 2019 at 09:28:03AM +, Mike Looijmans wrote: > > One solution I can think of is to put the header into it's own > > recipe/repository and then refer to it like any other library would. Refer > > to > > that r

Re: [yocto] linux-libc-headers - how to handle for older kernels?

On Mon, Dec 2, 2019 at 4:14 AM Mike Looijmans wrote: > > On 01-12-19 22:57, Peter Bergin via Lists.Yoctoproject.Org wrote: > > Hi, > > > > I'm currently working in a project using Yocto 2.6 (thud) release. It has > > default kernel v4.18 and also linux-libc-headers from kernel v4.18. In my > > pro

Re: [yocto] Copy initramfs to rootfs

Hi, I figured out the way to do this, im not sure if this is the good approach, but so far it works for me. So ill just post it here if someone else stumbles upon this issue. I was on good track with ROOTFS_POSTPROCESS_COMMAND, so i did this in my image recipe. In recipe called my-fancy-image.bb

[yocto] [meta-zephyr][PATCH 13/13] zephyr-philosophers: update recipe to build against v2.0

Signed-off-by: Naveen Saini --- recipes-kernel/zephyr-kernel/zephyr-philosophers.bb | 10 +++--- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/recipes-kernel/zephyr-kernel/zephyr-philosophers.bb b/recipes-kernel/zephyr-kernel/zephyr-philosophers.bb index 425bebb..b8262ca 1006

[yocto] [meta-zephyr][PATCH 03/13] zephyr-kernel-src: updated SRC_URI to point to github

Signed-off-by: Naveen Saini --- classes/zephyr-kernel-src.bbclass | 3 ++- recipes-kernel/zephyr-kernel/zephyr-kernel-src_1.6.bb | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/classes/zephyr-kernel-src.bbclass b/classes/zephyr-kernel-src.bbclass index

[yocto] [meta-zephyr][PATCH 12/13] zephyr-helloworld: code clean up

Signed-off-by: Naveen Saini --- recipes-kernel/zephyr-kernel/zephyr-helloworld.bb | 9 ++--- recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc | 10 +++--- 2 files changed, 9 insertions(+), 10 deletions(-) diff --git a/recipes-kernel/zephyr-kernel/zephyr-helloworld.bb b/recipes

[yocto] [meta-zephyr][PATCH 04/13] zephyr-helloworld: add

Signed-off-by: Naveen Saini --- .../zephyr-kernel/zephyr-helloworld.bb | 18 ++ 1 file changed, 18 insertions(+) create mode 100644 recipes-kernel/zephyr-kernel/zephyr-helloworld.bb diff --git a/recipes-kernel/zephyr-kernel/zephyr-helloworld.bb b/recipes-kernel/zephyr-k

[yocto] [meta-zephyr][PATCH 11/13] zephyr-kernel: drop obsolete v1.6

Signed-off-by: Naveen Saini --- .../files/Makefile.toolchain.yocto| 17 - .../zephyr-kernel/zephyr-kernel-src_1.6.bb| 37 --- 2 files changed, 54 deletions(-) delete mode 100644 recipes-kernel/zephyr-kernel/files/Makefile.toolchain.yocto delete mode 10064

[yocto] [meta-zephyr][PATCH 01/13] layer.conf: add LAYERSERIES_COMPAT to warrior & zeus

Signed-off-by: Naveen Saini --- conf/layer.conf | 2 ++ 1 file changed, 2 insertions(+) diff --git a/conf/layer.conf b/conf/layer.conf index f7cd15d..cb0064f 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -14,3 +14,5 @@ BBFILE_PRIORITY_zephyr = "6" LAYERVERSION_zephyr = "1" LAYERDEPEN

[yocto] [meta-zephyr][PATCH 07/13] zephyr-kernel: add Zephyr RTOS version 2.0.0 support

Release notes: https://github.com/zephyrproject-rtos/zephyr/releases/tag/zephyr-v2.0.0 Signed-off-by: Naveen Saini --- classes/zephyr-kernel-src.bbclass | 14 ++-- .../0001-cmake-add-yocto-toolchain.patch | 76 +++ .../zephyr-kernel/zephyr-kernel-common.inc|

[yocto] [meta-zephyr][PATCH 10/13] acrn.conf: add new machine

Add new acrn machine, which actually is $BOARD Signed-off-by: Naveen Saini --- conf/machine/acrn.conf | 10 ++ 1 file changed, 10 insertions(+) create mode 100644 conf/machine/acrn.conf diff --git a/conf/machine/acrn.conf b/conf/machine/acrn.conf new file mode 100644 index 000..96a

[yocto] [meta-zephyr][PATCH 06/13] zephyr-kernel: drop v1.7

Signed-off-by: Naveen Saini --- classes/zephyr-kernel-src.bbclass | 10 - .../zephyr-kernel/zephyr-kernel-src_1.7.bb| 40 --- 2 files changed, 50 deletions(-) delete mode 100644 recipes-kernel/zephyr-kernel/zephyr-kernel-src_1.7.bb diff --git a/classes/zephyr

[yocto] [meta-zephyr][PATCH 05/13] qemu-x86.conf: remove invalid options

Throw below error: runqemu - ERROR - Failed to run qemu: qemu-system-i386: -clock: invalid option Signed-off-by: Naveen Saini --- conf/machine/qemu-x86.conf | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/conf/machine/qemu-x86.conf b/conf/machine/qemu-x86.conf index 8bf1e3

[yocto] [meta-zephyr][PATCH 09/13] zephyr-helloworld: update recipe to build against zephyr v2.0

Signed-off-by: Naveen Saini --- recipes-kernel/zephyr-kernel/zephyr-helloworld.bb | 15 --- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/recipes-kernel/zephyr-kernel/zephyr-helloworld.bb b/recipes-kernel/zephyr-kernel/zephyr-helloworld.bb index 8900bfd..7c0823c 10064

[yocto] [meta-zephyr][PATCH 02/13] qemu: updated version to bbappend latest bb

Signed-off-by: Naveen Saini --- .../qemu/{qemu_2.8.%.bbappend => qemu_4.1.%.bbappend} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename recipes-devtools/qemu/{qemu_2.8.%.bbappend => qemu_4.1.%.bbappend} (100%) diff --git a/recipes-devtools/qemu/qemu_2.8.%.bbappend b/reci

[yocto] [meta-zephyr][PATCH 08/13] qemu-x86.conf: drop deprecated qemu flags

Signed-off-by: Naveen Saini --- conf/machine/qemu-x86.conf | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/conf/machine/qemu-x86.conf b/conf/machine/qemu-x86.conf index ac6fb8f..d85c222 100644 --- a/conf/machine/qemu-x86.conf +++ b/conf/machine/qemu-x86.conf @@ -9,10 +9,

Re: [yocto] linux-libc-headers - how to handle for older kernels?

Hi, On Mon, Dec 02, 2019 at 09:28:03AM +, Mike Looijmans wrote: > One solution I can think of is to put the header into it's own > recipe/repository and then refer to it like any other library would. Refer to > that recipe from the module (or kernel) recipe that needs it. This way you > hav

Re: [yocto] linux-libc-headers - how to handle for older kernels?

On 02-12-19 10:19, mikko.rap...@bmw.de wrote: > Hi, > > On Mon, Dec 02, 2019 at 09:13:47AM +, Mike Looijmans wrote: >> On 01-12-19 22:57, Peter Bergin via Lists.Yoctoproject.Org wrote: >>> Hi, >>> >>> I'm currently working in a project using Yocto 2.6 (thud) release. It has >>> default kernel

Re: [yocto] linux-libc-headers - how to handle for older kernels?

Hi, On Mon, Dec 02, 2019 at 09:13:47AM +, Mike Looijmans wrote: > On 01-12-19 22:57, Peter Bergin via Lists.Yoctoproject.Org wrote: > > Hi, > > > > I'm currently working in a project using Yocto 2.6 (thud) release. It has > > default kernel v4.18 and also linux-libc-headers from kernel v4.18

Re: [yocto] linux-libc-headers - how to handle for older kernels?

On 01-12-19 22:57, Peter Bergin via Lists.Yoctoproject.Org wrote: > Hi, > > I'm currently working in a project using Yocto 2.6 (thud) release. It has > default kernel v4.18 and also linux-libc-headers from kernel v4.18. In my > project we will use kernel v4.1. I would like advice how to handle t

Re: [yocto] linux-libc-headers - how to handle for older kernels?

Hi, On Sun, Dec 01, 2019 at 10:57:15PM +0100, Peter Bergin wrote: > Hi, > > I'm currently working in a project using Yocto 2.6 (thud) release. It has > default kernel v4.18 and also linux-libc-headers from kernel v4.18. In my > project we will use kernel v4.1. I would like advice how to handle th