From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v2 0/3] Deploy DTBs with separate recipe
Date: Fri, 12 Jul 2024 08:09:31 +0300 [thread overview]
Message-ID: <20240712054327.9526-1-ubely@ilbers.de> (raw)
Image task "do_copy_boot_files" is used to deploy kernel, initrd and
devicetree binaries to deploy directory.
When different images for the same target are built (e.g., "-base" and
"-debug") in parallel, this causes issues with DTB deployment since
they have no any image_name-specific stuff in the path, unlike kernel
and initrd.
Here we make a separate recipe responcible for DTB deployment. DTBs are
extracted from a kernel package (provided by distro or self-built).
First (RFC) version of the patchset directly used linux recipes for
this, but such approach still had "multiple execution" issues in case
the same linux recipe was used by different machines. This required
per-machine linux build splitting that increases build time and brings
some other problems (e.g. with kernel modules dependencies).
The recipe 'dtb-files' is MACHINE-dependent, so different DTB_FILES
may be deployed for different machines. At the same time, all these
'dtb-files-${MACHINE}' targets depend on the same kernel package, so
it's built only once.
The case when different distros (e.g., bullseye/bookworm) use the same
name for DTB binaries is covered by a separate patch.
Related topics on maillist:
https://groups.google.com/g/isar-users/c/ht3YmKZcJlM
https://groups.google.com/g/isar-users/c/4BRDM02xC40
https://groups.google.com/g/isar-users/c/qAnjahjjfsw
https://groups.google.com/g/isar-users/c/ZMD4XY4dKWQ
https://groups.google.com/g/isar-users/c/PSGU_AcdPZ8
https://groups.google.com/g/isar-users/c/Va0Ue-ISYeA
Changes since v1:
- Separate `dtb-files` recipe used instead of linux one
- Included older "[PATCH] Fix do_copy_boot_files error" into the
series ( https://groups.google.com/g/isar-users/c/Va0Ue-ISYeA )
Ilia Skochilov (1):
meta: Fix do_copy_boot_files error for different distros of same
machine
Uladzimir Bely (2):
testsuite: Build also debug images for some targets
meta: Move DTB deployment to a separate dtb-files recipe
RECIPE-API-CHANGELOG.md | 8 ++++
meta/classes/image.bbclass | 16 +++-----
meta/conf/bitbake.conf | 2 +-
meta/recipes-kernel/dtb-files/dtb-files.bb | 45 ++++++++++++++++++++++
testsuite/citest.py | 3 ++
5 files changed, 62 insertions(+), 12 deletions(-)
create mode 100644 meta/recipes-kernel/dtb-files/dtb-files.bb
--
2.44.2
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/20240712054327.9526-1-ubely%40ilbers.de.
next reply other threads:[~2024-07-12 5:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 5:09 Uladzimir Bely [this message]
2024-07-12 5:09 ` [PATCH v2 1/3] meta: Fix do_copy_boot_files error for different distros of same machine Uladzimir Bely
2024-07-12 15:06 ` Cedric Hombourger
2024-07-15 6:45 ` 'Florian Bezdeka' via isar-users
2024-07-12 5:09 ` [PATCH v2 2/3] testsuite: Build also debug images for some targets Uladzimir Bely
2024-07-12 5:09 ` [PATCH v2 3/3] meta: Move DTB deployment to a separate dtb-files recipe Uladzimir Bely
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=20240712054327.9526-1-ubely@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.com \
/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