From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] kernel: add make target for the installed device trees
Date: Sun, 24 Sep 2023 07:44:05 +0200 [thread overview]
Message-ID: <20230924054405.121202-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230912165759.3492269-1-rhi@pengutronix.de>
Thanks, applied as 7205e52a301ce552aa5a5c1a5e257b1609822b80.
Michael
[sent from post-receive hook]
On Sun, 24 Sep 2023 07:44:05 +0200, Roland Hieber <rhi@pengutronix.de> wrote:
> This makes it easy to depend on the kernel.targetinstall stage by
> depending on one of the .dtb's that it installs into the image dir, e.g.
> when building a custom recipe for a FIT image. As a nice side-effect,
> you can simply call "ptxdist image <board.dtb>" to build the device
> tree.
>
> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> Message-Id: <20230912165759.3492269-1-rhi@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/kernel.make b/rules/kernel.make
> index 3d200eaecfee..d82aa27fb78e 100644
> --- a/rules/kernel.make
> +++ b/rules/kernel.make
> @@ -283,6 +283,10 @@ endif
> # Target-Install
> # ----------------------------------------------------------------------------
>
> +ifneq ($(KERNEL_DTB_FILES),)
> +$(addprefix $(IMAGEDIR)/,$(KERNEL_DTB_FILES)): $(STATEDIR)/kernel.targetinstall
> +endif
> +
> $(STATEDIR)/kernel.targetinstall:
> @$(call targetinfo)
>
> diff --git a/rules/templates/template-kernel-make b/rules/templates/template-kernel-make
> index c5f0c9303b51..cd1b717c51ba 100644
> --- a/rules/templates/template-kernel-make
> +++ b/rules/templates/template-kernel-make
> @@ -106,6 +106,10 @@ $(STATEDIR)/kernel-@package@.install:
> # Target-Install
> # ----------------------------------------------------------------------------
>
> +ifneq ($(KERNEL_@PACKAGE@_DTB_FILES),)
> +$(addprefix $(IMAGEDIR)/,$(KERNEL_@PACKAGE@_DTB_FILES)): $(STATEDIR)/kernel-@package@.targetinstall
> +endif
> +
> $(STATEDIR)/kernel-@package@.targetinstall:
> @$(call targetinfo)
>
prev parent reply other threads:[~2023-09-24 5:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 16:57 [ptxdist] [PATCH v3 1/3] " Roland Hieber
2023-09-12 16:57 ` [ptxdist] [PATCH v3 2/3] templates: add template for custom FIT images Roland Hieber
2023-09-24 5:44 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-09-12 16:57 ` [ptxdist] [PATCH v3 3/3] doc: ref_make_macros: document world/image-fit macro Roland Hieber
2023-09-24 5:44 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-09-24 5:44 ` Michael Olbrich [this message]
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=20230924054405.121202-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=rhi@pengutronix.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