From: Denys Dmytriyenko <denis@denix.org>
To: adrian.freihofer@siemens.com
Cc: Francesco Dolcini <francesco@dolcini.it>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"meta-ti@lists.yoctoproject.org" <meta-ti@lists.yoctoproject.org>,
"hiago.franco@toradex.com" <hiago.franco@toradex.com>
Subject: Re: [meta-ti] [PATCH v7 00/20] FIT image improvements
Date: Fri, 6 Jun 2025 11:52:53 -0400 [thread overview]
Message-ID: <20250606155253.GB18383@denix.org> (raw)
In-Reply-To: <81913717cdad27b7ffb9c29a39fd5b6883190c22.camel@siemens.com>
On Fri, Jun 06, 2025 at 02:11:57PM +0000, Adrian Freihofer via lists.yoctoproject.org wrote:
> Hi Francesco
>
> Congratulate, your CI is faster than I am with updating the
> documentation :-). But in the mean time published the corresponding
> documentation update too:
> https://lists.yoctoproject.org/g/docs/message/7017
>
> Yes, unfortunately there is a breaking change. The modification has
> undergone extensive review through several months of technical meetings
> and patch review sessions. A very brief migration guide is here.
>
> Coming from a configuration like:
> KERNEL_IMAGETYPE = "fitImage"
> KERNEL_CLASSES = "kernel-fitimage"
> and building a kernel like:
> bitbake linux-yocto
>
> needs to be changed to:
> KERNEL_CLASSES = "kernel-fit-extra-artifacts"
> and building a kernel like:
> bitbake linux-yocto-fitimage
Quick question here - can you still produce multple kernel types in a single
go from a single kernel recipe? E.g. old KERNEL_IMAGETYPES = "Image fitImage"
Or are those now mutually exclusive?
> I hope that helps. Otherwise, please let me know.
> Adrian
>
>
>
>
> On Fri, 2025-06-06 at 12:29 +0200, Francesco Dolcini wrote:
> > Hello Adrian,
> >
> > On Tue, Jun 03, 2025 at 10:23:11AM +0200, AdrianF 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.
> >
> > I did not have time to look into the details yet, but it seems that
> > this
> > breaks build with meta-ti.
> >
> > > 06-05:18:06:33 ERROR: ParseError at
> > > /workdir/oe/build/../layers/openembedded-core/meta/classes-
> > > recipe/kernel.bbclass:183: Could not inherit file classes/kernel-
> > > fitimage.bbclass
> > > 06-05:18:06:33 ERROR: Parsing halted due to errors, see error
> > > messages above
> >
> > https://gist.github.com/dolcini/8240a229516e7a93356ebba56631d3c0
> >
> > Francesco
> >
next prev parent reply other threads:[~2025-06-06 15:53 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
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 ` Denys Dmytriyenko [this message]
2025-06-06 16:38 ` [meta-ti] " 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=20250606155253.GB18383@denix.org \
--to=denis@denix.org \
--cc=adrian.freihofer@siemens.com \
--cc=francesco@dolcini.it \
--cc=hiago.franco@toradex.com \
--cc=meta-ti@lists.yoctoproject.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox