public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Koch, Stefan (DI PA DCP R&D 3)" <stefan-koch@siemens.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Storm, Christian (T CED SES-DE)" <christian.storm@siemens.com>,
	"Adler, Michael (T CED SES-DE)" <michael.adler@siemens.com>,
	"Sudler, Simon (DI PA DCP TI)" <simon.sudler@siemens.com>,
	"Hombourger,
	Cedric (DI SW CAS ES LI)" <cedric.hombourger@siemens.com>,
	"Schmidt, Adriaan (T CED SES-DE)" <adriaan.schmidt@siemens.com>,
	"MOESSBAUER, Felix (T CED INW-CN)" <felix.moessbauer@siemens.com>,
	"ubely@ilbers.de" <ubely@ilbers.de>
Subject: Re: [PATCH v3 5/5] docs: Update custom_kernel docs for split up of kernel scripts and tools
Date: Wed, 16 Aug 2023 15:46:33 +0200	[thread overview]
Message-ID: <5277f5b7-1f46-419f-8dc5-85b307c86c83@siemens.com> (raw)
In-Reply-To: <20230816121423.3956608-6-stefan-koch@siemens.com>

On 16.08.23 14:14, Koch, Stefan (DI PA DCP R&D 3) wrote:
> Signed-off-by: Stefan Koch <stefan-koch@siemens.com>
> ---
>  doc/custom_kernel.md | 17 ++++++++++-------
>  1 file changed, 10 insertions(+), 7 deletions(-)
> 
> diff --git a/doc/custom_kernel.md b/doc/custom_kernel.md
> index 73987a5b..52e03b68 100644
> --- a/doc/custom_kernel.md
> +++ b/doc/custom_kernel.md
> @@ -38,12 +38,17 @@ The linux-custom recipe provides support for:
>   7. Allow the name of the kernel image to be changed via `KERNEL_FILE` (defaults
>      to `vmlinuz`)
>  
> - 8. Produce a `linux-headers` package which includes kernel headers and kbuild
> -    scripts/tools
> + 8. Produce a `linux-headers` package which includes kernel headers
>  
> - 9. The `linux-headers` package shall support native and cross compiles of
> -    out-of-tree kernel modules. However, when built in cross-compilation mode,
> -    it cannot be used on the target so far.
> + 9. Produce a `linux-kbuild` package for both `host` and/or `target` arch
> +    which includes kbuild scripts and tools.
> +    Setting `EXTENDED_KBUILD_MODE` to `"1"` will allow using the `-compat` and
> +    `-native` multiarch bitbake targets at cross building to run additional
> +    `target` or `host` specific builds.

Why does this need an extra control? And the semantic of that mode is
also by far not clear when looking at the variable name.

Jan

> +
> +    Then the `linux-headers` package supports native and cross compiles of
> +    out-of-tree kernel modules. Even, when built in cross-compilation mode,
> +    it can be used on the target using the `linux-kbuild` package.
>  
>   10. Produce a `linux-libc-dev` package to support user-land builds
>  
> @@ -72,8 +77,6 @@ In the future, the recipe may be extended to:
>  
>   3. Be compatible with Ubuntu
>  
> - 4. When cross-building, generate kernel-headers for both host and target
> -
>  ## Examples
>  
>  The linux-custom recipe is currently used by the linux-mainline package and is

-- 
Siemens AG, Technology
Linux Expert Center


  reply	other threads:[~2023-08-16 13:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16 12:14 [PATCH v3 0/5] linux-custom: Split up binaries from kernel headers to kbuild packages Koch, Stefan
2023-08-16 12:14 ` [PATCH v3 1/5] linux-custom: Split up binaries from kernel headers to kbuild package Koch, Stefan
2023-08-16 12:14 ` [PATCH v3 2/5] sbuild: Support overriding configured schroot dir Koch, Stefan
2023-08-16 12:14 ` [PATCH v3 3/5] dpkg: Allow overriding build and host parameters for sbuild and schroot Koch, Stefan
2023-08-16 13:55   ` Jan Kiszka
2023-08-16 14:27     ` Koch, Stefan
2023-08-16 14:32       ` Jan Kiszka
2023-08-17 12:25         ` Koch, Stefan
2023-08-16 12:14 ` [PATCH v3 4/5] linux-custom: Provide host and target specific kernel kbuild packages Koch, Stefan
2023-08-16 12:14 ` [PATCH v3 5/5] docs: Update custom_kernel docs for split up of kernel scripts and tools Koch, Stefan
2023-08-16 13:46   ` Jan Kiszka [this message]
2023-08-16 14:25     ` Koch, Stefan
2023-08-16 14:27       ` Jan Kiszka
2023-08-18 11:03         ` Koch, Stefan

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=5277f5b7-1f46-419f-8dc5-85b307c86c83@siemens.com \
    --to=jan.kiszka@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=michael.adler@siemens.com \
    --cc=simon.sudler@siemens.com \
    --cc=stefan-koch@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