Re: [OE-core][PATCH] meta/recipes-bsp: Add recipe for Slim Bootloader

> -Original Message- > From: Konrad Weihmann > Sent: Wednesday, December 15, 2021 15:35 > To: Liu, Yongxin ; openembedded- > c...@lists.openembedded.org; richard.pur...@linuxfoundation.org > Subject: Re: [OE-core][PATCH] meta/recipes-bsp: Add recipe for Slim > Bootloader > > On 15.12.21

Re: [OE-core][PATCH] meta/recipes-bsp: Add recipe for Slim Bootloader

On 15.12.21 08:16, Yongxin Liu wrote: Slim Bootloader is an open-source boot firmware running on Intel x86 architecture. Currently it supports qemu, apl(Apollo Lake), cfl(Coffee Lake), cml(Comet Lake), tgl(Tiger Lake), and ehl(Elkhart Lake). You can set "SLIMBOOT_TARGET" in .bb file or

[OE-core][PATCH] meta/recipes-bsp: Add recipe for Slim Bootloader

Slim Bootloader is an open-source boot firmware running on Intel x86 architecture. Currently it supports qemu, apl(Apollo Lake), cfl(Coffee Lake), cml(Comet Lake), tgl(Tiger Lake), and ehl(Elkhart Lake). You can set "SLIMBOOT_TARGET" in .bb file or .bbappend file to specify or add the target

[OE-core] [hardknott][PATCH 00/20] Pull request

Please merge these changes. Thanks, Anuj The following changes since commit d748ebb61d4dd355265f4a78790b4c30c3ec1a61: cups: Fix missing installation of cups sysv init scripts (2021-11-29 13:07:24 +0800) are available in the Git repository at:

Re: [OE-core] [PATCH] gcc: Fix CVE-2021-42574

Hi, > this is adding a new warning to help mitigate the problem, this is not > a gcc CVE per se. > so perhaps backporting to older branches makes sense, this looks ok The patch "0001-CVE-2021-42574.patch" is a dependency patch required for these 3 CVE patches. It adds 2 MACRO definitions that

[OE-core] [PATCH] gcc: Update status of musl stddef.h patch

This patch has been accepted upstream Signed-off-by: Khem Raj --- .../gcc/gcc/0030-sync-gcc-stddef.h-with-musl.patch | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-devtools/gcc/gcc/0030-sync-gcc-stddef.h-with-musl.patch

Re: [OE-core] [meta-oe][RFC PATCH] insane: Inappropriate patch reasoning

On 14.12.21 21:11, Alexander Kanavin wrote: What I would like to see at least is correctly tagging patches with dead upstreams, now that we have the shiny new status for it, and a report where they can be seen clearly :) The point of that patch is to have everything more machine readable, so

Re: [OE-core] [meta-oe][RFC PATCH] insane: Inappropriate patch reasoning

What I would like to see at least is correctly tagging patches with dead upstreams, now that we have the shiny new status for it, and a report where they can be seen clearly :) Alex On Tue, 14 Dec 2021 at 19:48, Konrad Weihmann wrote: > > > On 14.12.21 19:38, Bruce Ashfield wrote: > > On Tue,

Re: [OE-core] [PATCH][dunfell] lttng-modules: do not search in non-existing folder during install

On Tue, Dec 14, 2021 at 9:36 AM Anibal Limon wrote: > > Hi, > > Any update on push this to dunfell? It is in this morning's pull request: https://lists.openembedded.org/g/openembedded-core/message/159699 Steve -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group.

Re: [OE-core] [PATCH][dunfell] lttng-modules: do not search in non-existing folder during install

Hi, Any update on push this to dunfell?, I'm facing the issue, https://ci.linaro.org/job/lt-qcom-openembedded-meta-qcom-premerge-dunfell/46/MACHINE=dragonboard-410c,TCLIBC=glibc,label=docker-buster-amd64/console Thanks in advance!, Anibal On Wed, 8 Dec 2021 at 14:21, Anibal Limon via

Re: [OE-core] [meta-oe][RFC PATCH] insane: Inappropriate patch reasoning

On 14.12.21 19:38, Bruce Ashfield wrote: On Tue, Dec 14, 2021 at 1:05 PM Konrad Weihmann wrote: [snip] meta/recipes-support/vte/vte/0001-Makefile.docs-correctly-substitute-gtkdoc-qemu-wrapp.patch: 6: Upstream-Status: Inappropriate [oe-core specific] or are simply ignoring it at

Re: [OE-core] [meta-oe][RFC PATCH] insane: Inappropriate patch reasoning

On Tue, Dec 14, 2021 at 1:05 PM Konrad Weihmann wrote: > > The following patches in core don't follow the recommendation > > meta/recipes-bsp/apmd/apmd/legacy.patch: >9: Upstream-Status: Inappropriate [upstream is dead] > > meta/recipes-bsp/efivar/efivar/no-werror.patch: >3:

Re: [OE-core] [meta-oe][RFC PATCH] insane: Inappropriate patch reasoning

The following patches in core don't follow the recommendation meta/recipes-bsp/apmd/apmd/legacy.patch: 9: Upstream-Status: Inappropriate [upstream is dead] meta/recipes-bsp/efivar/efivar/no-werror.patch: 3: Upstream-Status: Inappropriate [https://github.com/rhboot/efivar/issues/131]

Re: [OE-core] [PATCH] gcc: Fix CVE-2021-42574

On Tue, Dec 14, 2021 at 9:31 AM Randy MacLeod wrote: > > On 2021-12-14 5:46 a.m., Pgowda wrote: > > Upstream-Status: Backport > > [https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=bd5e882cf6e0def3dd1bc106075d59a303fe0d1e] > > Upstream-Status: Backport > >

[OE-core] [meta-oe][RFC PATCH] insane: Inappropriate patch reasoning

if a patch uses Upstream-Status: Inappropriate it should provide a machine readable reasoning in square brackets. According to latest wiki entry that would be not author native licensing configuration enable feature disable feature bugfix .* embedded specific no upstream other a detailed

Re: [OE-core] [PATCH] gcc: Fix CVE-2021-42574

On 2021-12-14 5:46 a.m., Pgowda wrote: Upstream-Status: Backport [https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=bd5e882cf6e0def3dd1bc106075d59a303fe0d1e] Upstream-Status: Backport [https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=51c500269bf53749b107807d84271385fad35628] Upstream-Status:

[OE-core][dunfell 00/10] Pull request (cover letter only)

The following changes since commit f788765e1b9832d0da8ec4ce49aa85864b0e: README.OE-Core.md: update URLs (2021-12-06 04:48:48 -1000) are available in the Git repository at: git://git.openembedded.org/openembedded-core-contrib stable/dunfell-next

[OE-core] [meta-oe][PATCH v2 2/2] insane: add Inactive-Upstream to Upstream-Status

as defined by latest addition to the commit message guideline Signed-off-by: Konrad Weihmann --- meta/classes/insane.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass index 125c339942..11532ecd08 100644 ---

[OE-core] [meta-oe][PATCH v2 1/2] insane: move src-uri-bad checks to unpack stage

previously used package_qa_check_src_uri was triggered during package_qa stage, which implies having packages. This isn't the case for native-only recipes or recipe that inherit nopackages. Still the checks performed (src-uri-bad) apply to those as well. Therefore move the check from package_qa

[OE-core] [PATCH 2/2] insane: add Inactive-Upstream to Upstream-Status

as defined by latest addition to the commit message guideline Signed-off-by: Konrad Weihmann --- meta/classes/insane.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass index 70c2d97df1..cc348173d6 100644 ---

[OE-core] [PATCH 1/2] insane: move src-uri-bad checks to unpack stage

previously used package_qa_check_src_uri was triggered during package_qa stage, which implies having packages. This isn't the case for native-only recipes or recipe that inherit nopackages. Still the checks performed (src-uri-bad) apply to those as well. Therefore move the check from package_qa

Re: [OE-core] The state of DKMS in the Yocto community

Converging threads. Thanks all for the feedback. It sounds like there's no appetite for a DKMS recipe, and I agree with the rationale for rejection. I'll motion to have NI's DKMS recipe migrated to our meta-nilrt layer and independently maintained until such a time as we can deprecate it.

[OE-core] Yocto Project Status WW50`21

Current Dev Position: YP 3.5 M1 Next Deadline: 6th Dec. 2021 YP 3.5 M1 build Next Team Meetings: * Bug Triage meeting Thursday Dec. 16th at 7:30am PDT ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)

Re: [OE-core] [RFC PATCH v2 3/3] selftest: recipetool: Add test for handle_license_vars function

Hi Richard, Am 14.12.2021 um 14:01 schrieb Richard Purdie: On Mon, 2021-12-13 at 16:05 +0100, Stefan Herbrechtsmeier wrote: From: Stefan Herbrechtsmeier Signed-off-by: Stefan Herbrechtsmeier --- (no changes since v1) meta/lib/oeqa/selftest/cases/recipetool.py | 62 ++

Re: [OE-core] ROOTFS_POSTPROCESS_COMMAND versus do_install_append() and using ${D}?

On Tue, 14 Dec 2021, Ross Burton wrote: > On Tue, 14 Dec 2021 at 11:39, Robert P. J. Day wrote: > > what i'm looking at now does it in a more curious way. there is a > > catch-all recipe file (call it "catchall.bb") which lists, as its > > DEPENDS list, *all* of the recipes that make up the

Re: [OE-core] ROOTFS_POSTPROCESS_COMMAND versus do_install_append() and using ${D}?

On Tue, 14 Dec 2021 at 11:39, Robert P. J. Day wrote: > what i'm looking at now does it in a more curious way. there is a > catch-all recipe file (call it "catchall.bb") which lists, as its > DEPENDS list, *all* of the recipes that make up the image, which means > that building catchall.bb

Re: [OE-core] [RFC PATCH v2 3/3] selftest: recipetool: Add test for handle_license_vars function

On Mon, 2021-12-13 at 16:05 +0100, Stefan Herbrechtsmeier wrote: > From: Stefan Herbrechtsmeier > > Signed-off-by: Stefan Herbrechtsmeier > --- > > (no changes since v1) > > meta/lib/oeqa/selftest/cases/recipetool.py | 62 ++ > 1 file changed, 62 insertions(+) > > diff

[OE-core] [PATCH 1/2] lttng-tools: Backport ptest fix

Add a backport and a dependency from upstream to help address one of the lttng-tools ptest relayd hangs we've been seeing on the autobuilder. Signed-off-by: Richard Purdie --- ...0ba19aec78f36e301494a03f5678fcb6fbb4.patch | 218 ++ ...46a03fbf31c19b85ec367dc2c3db56e6dbf7.patch

[OE-core] [PATCH 2/2] lttng-tools: Disable problem tests

There is a pattern of the notification tests hanging. Whilst we need to get to the bottom of that, disable them for now as it is causing high load for triage/SWAT and masking other failures. [YOCTO #14263] Signed-off-by: Richard Purdie --- .../lttng/lttng-tools/disable-tests.patch | 34

Re: [OE-core] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.5_M1.rc2)

Hi everyone, Intel and WR YP QA is planning for QA execution for YP build yocto-3.5_M1.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. MinnowTurbot 32-bit 2. Coffee Lake

[OE-core] ROOTFS_POSTPROCESS_COMMAND versus do_install_append() and using ${D}?

i've run across a moderately curious example of doing rootfs-wide tweaking in an odd way. my understanding is that, after i've created my basic image rootfs, i can define that image's ROOTFS_POSTPROCESS_COMMAND variable, and do all sorts of rootfs-wide adjustments relative to

[OE-core] [PATCH] cups: fix typo in flags to disable avahi

one too many 's': dnsssd -> dnssd Signed-off-by: S. Lockwood-Childs --- meta/recipes-extended/cups/cups.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-extended/cups/cups.inc b/meta/recipes-extended/cups/cups.inc index 3175a91ce4..05c1e34a77 100644 ---

[OE-core] [dunfell][PATCH] bluez: fix CVE-2021-0129

From: Marta Rybczynska Improper access control in BlueZ may allow an authenticated user to potentially enable information disclosure via adjacent access. This issue can be fixed in the kernel, in BlueZ or both. This patch fixes it on the BlueZ side, so that the configuration no longer depends