[yocto] [meta-zephyr][PATCH] layer.conf: update LAYERSERIES_COMPAT for mickledore

2023-01-03 Thread Naveen Saini
oe-core switched to mickedore in: https://git.openembedded.org/openembedded-core/commit/?id=57239d66b933c4313cf331d35d13ec2d0661c38f Drop support for old releases. Signed-off-by: Naveen Saini --- meta-zephyr-bsp/conf/layer.conf | 4 +--- meta-zephyr-bsp/conf/machine/

Re: [yocto] [meta-rockchip][PATCH] layer.conf: update LAYERSERIES_COMPAT for mickledore

2023-01-03 Thread Trevor Woerner
Applied, with updates*, to meta-rockchip master: https://git.yoctoproject.org/meta-rockchip/commit/?id=5f06c7c018755b0bef6d6f4944ae25b5447535fc * everyone gets a gold star On Tue, Jan 3, 2023 at 11:22 AM Trevor Woerner via lists.yoctoproject.org wrote: > Signed-off-by: Trevor Woerner > --- >

Re: [yocto] [meta-rockchip][PATCH] layer.conf: Update LAYERSERIES_COMPAT for mickledore

2023-01-03 Thread Khem Raj
On Tue, Jan 3, 2023 at 11:13 AM Martin Jansa wrote: > > Trevor already won this race (I was second, you're third) :) LOL :). Depends whose CI was noticed first. > > https://patchwork.yoctoproject.org/project/yocto/list/?series=&submitter=&state=&q=mickledore&archive=&delegate= > > On Tue, Jan 3,

Re: [yocto] [meta-rockchip][PATCH] layer.conf: Update LAYERSERIES_COMPAT for mickledore

2023-01-03 Thread Trevor Woerner
On Tue, Jan 3, 2023 at 2:13 PM Martin Jansa wrote: > Trevor already won this race (I was second, you're third) :) > > > https://patchwork.yoctoproject.org/project/yocto/list/?series=&submitter=&state=&q=mickledore&archive=&delegate= > It's nice knowing someone other than me is using this layer :

Re: [yocto] [meta-rockchip][PATCH] layer.conf: Update LAYERSERIES_COMPAT for mickledore

2023-01-03 Thread Martin Jansa
Trevor already won this race (I was second, you're third) :) https://patchwork.yoctoproject.org/project/yocto/list/?series=&submitter=&state=&q=mickledore&archive=&delegate= On Tue, Jan 3, 2023 at 7:33 PM Khem Raj wrote: > oe-core switched to mickedore [1] > > [1] > https://git.openembedded.org

[yocto] [meta-rockchip][PATCH] layer.conf: Update LAYERSERIES_COMPAT for mickledore

2023-01-03 Thread Khem Raj
oe-core switched to mickedore [1] [1] https://git.openembedded.org/openembedded-core/commit/?id=57239d66b933c4313cf331d35d13ec2d0661c38f Signed-off-by: Khem Raj --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index 9197c

[yocto] [meta-security][PATCH] layer.conf: Mark master as compatible with mickledore

2023-01-03 Thread Armin Kuster
Signed-off-by: Armin Kuster --- conf/layer.conf | 2 +- meta-integrity/conf/layer.conf | 2 +- meta-parsec/conf/layer.conf | 2 +- meta-security-compliance/conf/layer.conf | 2 +- meta-security-isafw/conf/layer.conf | 2 +- meta-tpm/conf/layer.

Re: [yocto] bitbake controlling memory use

2023-01-03 Thread Alexander Kanavin
On Tue, 3 Jan 2023 at 16:58, Ferry Toth wrote: > I know you don't want to spend time on this. So don't. Others may have > an interest or a tip to improve Yocto in this area. > > I'm just trying to get an old patch from Richard Purdie to work > (http://git.yoctoproject.org/cgit.cgi/poky-contrib/co

[yocto] [meta-security][PATCH] layer.conf: update LAYERSERIES_COMPAT for mickledore

2023-01-03 Thread Martin Jansa
* oe-core switched to mickedore in: https://git.openembedded.org/openembedded-core/commit/?id=57239d66b933c4313cf331d35d13ec2d0661c38f Signed-off-by: Martin Jansa --- conf/layer.conf | 2 +- meta-hardening/conf/layer.conf | 2 +- meta-integrity/conf/layer.co

[yocto] [meta-rockchip][PATCH] layer.conf: update LAYERSERIES_COMPAT for mickledore

2023-01-03 Thread Martin Jansa
* oe-core switched to mickedore in: https://git.openembedded.org/openembedded-core/commit/?id=57239d66b933c4313cf331d35d13ec2d0661c38f Signed-off-by: Martin Jansa --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index 91

[yocto] [meta-rockchip][PATCH] layer.conf: update LAYERSERIES_COMPAT for mickledore

2023-01-03 Thread Trevor Woerner
Signed-off-by: Trevor Woerner --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index 9197c3b84ce7..e8c50f8a1f6e 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -14,7 +14,7 @@ BBFILE_PRIORITY_rockchip = "1" # This shou

Re: [yocto] Remove kernel image and modules from rootfs

2023-01-03 Thread Quentin Schulz via lists.yoctoproject.org
Hi Konstantin, On 1/3/23 16:58, Konstantin Kletschke wrote: On Mon, Jan 02, 2023 at 05:11:35PM +0100, Quentin Schulz wrote: but this is now deprecated for kirkstone and should be done this way: RRECOMMENDS:${KERNEL_PACKAGE_NAME}-base = "" This makes sense, I'll send a patch updating the do

Re: [yocto] bitbake controlling memory use

2023-01-03 Thread Ferry Toth
Hi Alex, Op 03-01-2023 om 16:37 schreef Alexander Kanavin: On Tue, 3 Jan 2023 at 16:24, Alexander Kanavin via lists.yoctoproject.org wrote: Sorry guys, but this is venturing into the ridiculous. If you embark on building a whole Linux distribution, you need to start with the correct tools for

Re: [yocto] Remove kernel image and modules from rootfs

2023-01-03 Thread Konstantin Kletschke
On Mon, Jan 02, 2023 at 05:11:35PM +0100, Quentin Schulz wrote: > > but this is now deprecated for kirkstone and should be done this way: > > > > RRECOMMENDS:${KERNEL_PACKAGE_NAME}-base = "" > > > > This makes sense, I'll send a patch updating the documentation to reflect > this change. I thoug

[yocto] Yocto Project Status 3 January 2023 (WW01)

2023-01-03 Thread Stephen Jolley
Current Dev Position: YP 4.2 M2 Next Deadline: 23rd January 2023 YP 4.2 M2 Build Next Team Meetings: * Bug Triage meeting Thursday January 5th 7:30 am PDT ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz0

Re: [yocto] bitbake controlling memory use

2023-01-03 Thread Martin Jansa
On Tue, Jan 3, 2023 at 3:29 PM Ferry Toth wrote: > Op 03-01-2023 om 15:18 schreef Alexander Kanavin: > > I have to note that even the most expensive 16 Gb RAM module is less > > than 100 Euro, and can be obtained for half that much. Surely you > > value your time more than that? > > Of course. An

Re: [yocto] bitbake controlling memory use

2023-01-03 Thread Alexander Kanavin
On Tue, 3 Jan 2023 at 16:24, Alexander Kanavin via lists.yoctoproject.org wrote: > Sorry guys, but this is venturing into the ridiculous. If you embark > on building a whole Linux distribution, you need to start with the > correct tools for it. I mean, one can use a virtual machine inside a windo

Re: [yocto] bitbake controlling memory use

2023-01-03 Thread Alexander Kanavin
On Tue, 3 Jan 2023 at 16:12, Ferry Toth wrote: > Yes, and I note that many people trying to build my image > (meta-intel-edison) do so from a virtual machine as they only have a > windows host. Sorry guys, but this is venturing into the ridiculous. If you embark on building a whole Linux distribu

Re: [yocto] bitbake controlling memory use

2023-01-03 Thread Ferry Toth
Hi Janne, Op 03-01-2023 om 16:03 schreef Janne Kiiskila: Hei, Is not the easiest solution to build the actual full build in steps, rather than build the whole thing? So, instead of doing a Sure, that is easy enough. Setting PARALLEL_MAKE is easy enough too. I was hoping to find a fundamenta

Re: [yocto] bitbake controlling memory use

2023-01-03 Thread Janne Kiiskila
Hei, Is not the easiest solution to build the actual full build in steps, rather than build the whole thing? So, instead of doing a full bitbake Do bitbake nodejs bitbake binutils bitbake rust (if you happen to need it) and only after that do bitbake That way you can control the memory

Re: [yocto] lsusb

2023-01-03 Thread Quentin Schulz via lists.yoctoproject.org
Hi Ron, On 12/24/22 20:17, Mistyron wrote: On 2022-12-24 08:38, Markus Volk wrote: Am Sa, 24. Dez 2022 um 08:34:49 -0800 schrieb Mistyron : $ grep usb path/to/package.manifest   libusb-1.0-0   usbutils usbutils-python lsusb is part of usbutils, so it is not explicitly listed, but should be

Re: [yocto] bitbake controlling memory use

2023-01-03 Thread Ferry Toth
Hi Quentin, Op 03-01-2023 om 15:36 schreef Quentin Schulz: Hi Ferry, On 1/3/23 15:29, Ferry Toth wrote: Hi Alex, Op 03-01-2023 om 15:18 schreef Alexander Kanavin: I have to note that even the most expensive 16 Gb RAM module is less than 100 Euro, and can be obtained for half that much. Surel

Re: [yocto] bitbake controlling memory use

2023-01-03 Thread Quentin Schulz via lists.yoctoproject.org
Hi Ferry, On 1/3/23 15:29, Ferry Toth wrote: Hi Alex, Op 03-01-2023 om 15:18 schreef Alexander Kanavin: I have to note that even the most expensive 16 Gb RAM module is less than 100 Euro, and can be obtained for half that much. Surely you value your time more than that? Of course. And if I d

Re: [yocto] bitbake controlling memory use

2023-01-03 Thread Ferry Toth
Hi Alex, Op 03-01-2023 om 15:18 schreef Alexander Kanavin: I have to note that even the most expensive 16 Gb RAM module is less than 100 Euro, and can be obtained for half that much. Surely you value your time more than that? Of course. And if I didn't I could reduce the number of `PARALLEL_MA

Re: [yocto] bitbake controlling memory use

2023-01-03 Thread Alexander Kanavin
I have to note that even the most expensive 16 Gb RAM module is less than 100 Euro, and can be obtained for half that much. Surely you value your time more than that? Alex On Tue, 3 Jan 2023 at 15:15, Ferry Toth wrote: > > Op 13-06-2021 om 02:38 schreef Randy MacLeod: > > On 2021-06-12 12:31 p.m

Re: [yocto] bitbake controlling memory use

2023-01-03 Thread Ferry Toth
Op 13-06-2021 om 02:38 schreef Randy MacLeod: On 2021-06-12 12:31 p.m., Ferry Toth wrote: Hi Op 10-06-2021 om 22:35 schreef Ferry Toth: Hi, Op 10-06-2021 om 21:06 schreef Trevor Gamblin: On 2021-06-10 5:22 a.m., Ferry Toth wrote: **[Please note: This e-mail is from an EXTERNAL e-mail add

Re: [yocto] DISTRO_FEATURES in custom recipe does not override local.conf setting

2023-01-03 Thread tomzy
On Thu, Dec 29, 2022 at 01:32 AM, Mistyron wrote: > > On 12/28/22 13:24, Mistyron via lists.yoctoproject.org wrote: > >> On 2022-12-28 7:55 a.m., Alexander Kanavin wrote: >> >>> You can't. '_remove' has priority over everything else, and >>> DISTRO_FEATURES cannot be set from a recipe, only fro