From: Stefan Koch <stefan-koch@siemens.com>
To: isar-users@googlegroups.com
Cc: stefan-koch@siemens.com, jan.kiszka@siemens.com,
christian.storm@siemens.com, michael.adler@siemens.com,
simon.sudler@siemens.com, cedric.hombourger@siemens.com,
adriaan.schmidt@siemens.com, felix.moessbauer@siemens.com,
ubely@ilbers.de
Subject: [PATCH v4 0/3] linux-custom: Split up binaries from kernel headers to kbuild packages
Date: Mon, 21 Aug 2023 15:44:58 +0200 [thread overview]
Message-ID: <20230821134501.2681654-1-stefan-koch@siemens.com> (raw)
Hi
This updated v4 patchset implement suggestions from reviewed v3 patchset.
It's now a set of five patches:
- linux-custom: Split up binaries from kernel headers to kbuild package
- linux-custom: Provide host and target specific kernel kbuild packages
- docs: Update custom_kernel docs for split up of kernel scripts and tools
The main use-case was to swap out the binaries
from the kernel headers into kernel kbuild package.
This is introduced by the first commit
"Split up binaries from kernel headers to kbuild package"
The second commit "Provide host and target specific kernel kbuild packages"
introduces that the binaries could be swapped out into host and target
specific kernel kbuild packages.
The main development goals were these:
1. Solve already known isar custom kernel
limitations from doc/custom_kernel.inc
- kernel headers package does not support both native
and cross compilation of kernel modules when cross built
2. Honor recommendations for future from doc/custom_kernel.inc
- Generate kernel headers packages for both host and target
when using cross build
3. Add extensions known from debian kernel packages structure
- Generate a kernel headers package without binaries
- Create specific kernel kbuild packages that
will ship the "scripts" and "tools" binaries
- Use symlinks to point to the "scripts" and "tools" binaries
4. Be user friendly
- Avoid redundant configuration of kernel source definitions with user
actions to enable kbuild package generation
- Use already known way to include linux-custom.inc in just one
own bitbake recipe that provides the kernel source definitions
- Keep known user behavior for existing build configurations:
just update isar, request "-compat" (and "-native") bitbake targets
and kbuild packages for target and host will be created automatically
Best regards
Stefan
Stefan Koch (3):
linux-custom: Split up binaries from kernel headers to kbuild package
linux-custom: Provide host and target specific kernel kbuild packages
docs: Update custom_kernel docs for split up of kernel scripts and
tools
doc/custom_kernel.md | 16 ++--
.../linux/files/debian/control.tmpl | 25 ++++++-
.../linux/files/debian/isar/build.tmpl | 12 ++-
.../linux/files/debian/isar/common.tmpl | 10 +++
.../linux/files/debian/isar/install.tmpl | 73 ++++++++++++++-----
.../linux/files/debian/rules.tmpl | 2 +-
meta/recipes-kernel/linux/linux-custom.inc | 53 ++++++++++++--
7 files changed, 155 insertions(+), 36 deletions(-)
--
2.39.2
next reply other threads:[~2023-08-21 13:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 13:44 Stefan Koch [this message]
2023-08-21 13:44 ` [PATCH v4 1/3] linux-custom: Split up binaries from kernel headers to kbuild package Stefan Koch
2023-08-21 13:45 ` [PATCH v4 2/3] linux-custom: Provide host and target specific kernel kbuild packages Stefan Koch
2023-09-06 6:38 ` Schmidt, Adriaan
2023-10-04 15:34 ` Koch, Stefan
2023-10-04 16:15 ` Jan Kiszka
2023-10-10 9:12 ` Koch, Stefan
2023-08-21 13:45 ` [PATCH v4 3/3] docs: Update custom_kernel docs for split up of kernel scripts and tools Stefan Koch
2023-09-01 10:22 ` [PATCH v4 0/3] linux-custom: Split up binaries from kernel headers to kbuild packages Uladzimir Bely
2023-09-05 20:18 ` Jan Kiszka
2023-09-05 20:17 ` Jan Kiszka
2023-10-04 15:36 ` Koch, Stefan
2023-11-21 7:26 ` Uladzimir Bely
2023-12-17 16:50 ` Jan Kiszka
2024-01-08 10:05 ` Koch, Stefan
2024-01-08 12:18 ` Koch, Stefan
2024-01-08 12:20 ` Jan Kiszka
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=20230821134501.2681654-1-stefan-koch@siemens.com \
--to=stefan-koch@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=cedric.hombourger@siemens.com \
--cc=christian.storm@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=michael.adler@siemens.com \
--cc=simon.sudler@siemens.com \
--cc=ubely@ilbers.de \
/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