All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: adrian.freihofer@siemens.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v7 00/20] FIT image improvements
Date: Tue, 03 Jun 2025 15:02:02 +0100	[thread overview]
Message-ID: <5c8a9461c90a28845cdcafd8dadcce8ec807b306.camel@linuxfoundation.org> (raw)
In-Reply-To: <184582AE5B84DD18.18429@lists.openembedded.org>

On Tue, 2025-06-03 at 11:48 +0100, Richard Purdie via
lists.openembedded.org wrote:
> On Tue, 2025-06-03 at 10:23 +0200, Adrian Freihofer via
> lists.openembedded.org wrote:
> > From: Adrian Freihofer <adrian.freihofer@siemens.com>
> > 
> > This patch series re-writes the FIT image related code. The goal is
> > to
> > fix [YOCTO #12912] which is a long standing issue.
> > 
> > Changes in comparison to v6
> > ---------------------------
> > 
> > * Move the code for exporting the FIT image specific kernel
> > artifacts
> > in a new,
> >   separate kernel-fit-extra-artifacts.bbclass rather than adding it
> > to the
> >   existing kernel-uimage.bbclass.
> > * Improve the devicetree.bbclass to skip error messages of shell
> > globs
> > * Improve the error message in the kernel.bbclass to: "fitImage is
> > no
> > longer
> >   supported as a KERNEL_IMAGETYPE(S). FIT images are built by the
> >   linux-yocto-fitimage recipe."
> > 
> > Revert a non essential refactoring in the kernel.bbclass
> 
> v7 seems to have some new failures:
> 
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/111/builds/497
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/3/builds/1810
> 
> both in musl.

Build is continuing and this showed up in the world build:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/59/builds/1748

Cheers,

Richard


  parent reply	other threads:[~2025-06-03 14:02 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-03  8:23 [PATCH v7 00/20] FIT image improvements AdrianF
2025-06-03  8:23 ` [PATCH v7 01/20] devicetree: minor improvements AdrianF
2025-06-03  8:23 ` [PATCH v7 02/20] oe-selftest: add new ext dtb recipe AdrianF
2025-06-03  8:23 ` [PATCH v7 03/20] oe-selftest: fitimage: test external dtb AdrianF
2025-06-03  8:23 ` [PATCH v7 04/20] oe-selftest: fitimage: test FIT_CONF_PREFIX AdrianF
2025-06-03  8:23 ` [PATCH v7 05/20] oe-selftest: fitimage: test FIT_CONF_DEFAULT_DTB AdrianF
2025-06-03  8:23 ` [PATCH v7 06/20] kernel-signing-keys-native: refactor key generation into a new recipe AdrianF
2025-06-03  8:23 ` [PATCH v7 07/20] maintainers: add myself for kernel-signing-keys-native AdrianF
2025-06-03  8:23 ` [PATCH v7 08/20] oe-selftest: fitimage: cleanup FIT_GENERATE_KEYS AdrianF
2025-06-03  8:23 ` [PATCH v7 09/20] kernel-fitimage: refactor order in its AdrianF
2025-06-03  8:23 ` [PATCH v7 10/20] kernel-uboot.bbclass: do not require the kernel build folder AdrianF
2025-06-03  8:23 ` [PATCH v7 11/20] kernel-fit-image.bbclass: add a new FIT image implementation AdrianF
2025-12-04 14:04   ` AW: [EXT] [OE-core] " Denis OSTERLAND-HEIM
2025-12-04 15:01     ` Freihofer, Adrian
2025-12-05  6:46       ` AW: " Denis OSTERLAND-HEIM
2025-06-03  8:23 ` [PATCH v7 12/20] maintainers: add myself for linux-yocto-fitimage AdrianF
2025-06-03  8:23 ` [PATCH v7 13/20] oe-selftest: fitimage: add tests for fitimage.py AdrianF
2025-06-03  8:23 ` [PATCH v7 14/20] oe-selftest: fitimage: support new FIT recipe as well AdrianF
2025-06-03  8:23 ` [PATCH v7 15/20] oe-selftest: fitimage: run all tests for both FIT implementations AdrianF
2025-06-03  8:23 ` [PATCH v7 16/20] oe-selftest: fitimage refactor classes AdrianF
2025-06-03  8:23 ` [PATCH v7 17/20] kernel-fitimage: re-write its code in Python AdrianF
2025-06-03  8:23 ` [PATCH v7 18/20] oe-selftest: fitimage: remove kernel-fitimage tests AdrianF
2025-06-03  8:23 ` [PATCH v7 19/20] kernel.bbclass: remove support for type fitImage AdrianF
2025-06-03  8:23 ` [PATCH v7 20/20] kernel-fitimage.bbclass: remove it AdrianF
2025-06-03 10:48 ` [OE-core] [PATCH v7 00/20] FIT image improvements Richard Purdie
2025-06-03 13:35   ` Freihofer, Adrian
2025-06-03 14:07     ` Richard Purdie
     [not found]     ` <18458D867A23466E.18429@lists.openembedded.org>
2025-06-04  7:12       ` Richard Purdie
2025-06-04  7:42         ` Freihofer, Adrian
     [not found] ` <184582AE5B84DD18.18429@lists.openembedded.org>
2025-06-03 14:02   ` Richard Purdie [this message]
2025-06-04 11:13 ` Bruce Ashfield
2025-06-06 10:29 ` Francesco Dolcini
2025-06-06 14:11   ` Freihofer, Adrian
2025-06-06 15:52     ` [meta-ti] " Denys Dmytriyenko
2025-06-06 16:38       ` Freihofer, Adrian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5c8a9461c90a28845cdcafd8dadcce8ec807b306.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=adrian.freihofer@siemens.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.