From: Francesco Dolcini <francesco@dolcini.it>
To: AdrianF <adrian.freihofer@siemens.com>
Cc: openembedded-core@lists.openembedded.org,
meta-ti@lists.yoctoproject.org, hiago.franco@toradex.com
Subject: Re: [PATCH v7 00/20] FIT image improvements
Date: Fri, 6 Jun 2025 12:29:36 +0200 [thread overview]
Message-ID: <20250606102936.GA29790@francesco-nb> (raw)
In-Reply-To: <20250603082419.409564-1-adrian.freihofer@siemens.com>
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 10:29 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 [this message]
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=20250606102936.GA29790@francesco-nb \
--to=francesco@dolcini.it \
--cc=adrian.freihofer@siemens.com \
--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