From: Niklas Cassel via buildroot <buildroot@buildroot.org>
To: Michael Walle <michael@walle.cc>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>,
"Gaël PORTAY" <gael.portay@rtone.fr>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Martin Bark" <martin@barkynet.com>,
"Julien Grossholtz" <julien.grossholtz@openest.io>,
"Damien Le Moal" <dlemoal@kernel.org>
Subject: Re: [Buildroot] [PATCH v2] linux: add support for device tree overlays
Date: Wed, 23 Oct 2024 14:04:01 +0000 [thread overview]
Message-ID: <ZxkCUCUw5bVSlgRo@ryzen> (raw)
In-Reply-To: <ZtWx2nqI0YTpwb-P@ryzen.lan>
On Mon, Sep 02, 2024 at 02:38:50PM +0200, Niklas Cassel wrote:
> On Mon, Sep 02, 2024 at 01:27:35PM +0200, Michael Walle wrote:
> > The linux kernel can build device tree overlays (.dtbo) itself. Add
> > support to build and copy them along with the actual device trees.
> > These can either be in-tree device tree overlays
> > (BR2_LINUX_KERNEL_INTREE_DTSO_NAMES) or they can be provided outside of
> > the kernel (BR2_LINUX_KERNEL_CUSTOM_DTS_PATH). In the latter case, the
> > overlay source files will be copied into the kernel tree first.
> >
> > Signed-off-by: Michael Walle <michael@walle.cc>
> > ---
Hello Michael,
Considering that this patch supports both in-tree and out-of-tree device
tree overlays.
I just saw this:
https://lore.kernel.org/buildroot/CAFOYHZDQmMRuK76TpOSAOFPdqAb4gpw=LNKfmpu=sqAD1EMhFg@mail.gmail.com/T/#u
https://lore.kernel.org/all/CAK7LNAR4h6NZ+D0BK+q4VQBeHWpjzRBQFQ9ovBrftM=6dHRcUg@mail.gmail.com/
It appears that it will no longer work to copy out-of-tree source files
into the kernel directory (which this patch does).
Does perhaps this patch need a V3 that drops support for out-of-tree
device tree overlays?
Kind regards,
Niklas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-10-23 14:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 11:27 [Buildroot] [PATCH v2] linux: add support for device tree overlays Michael Walle via buildroot
2024-09-02 12:38 ` Niklas Cassel via buildroot
2024-09-02 15:07 ` Michael Walle via buildroot
2024-10-08 14:42 ` Niklas Cassel via buildroot
2024-10-23 14:04 ` Niklas Cassel via buildroot [this message]
2025-02-04 10:44 ` Romain Naour via buildroot
2024-09-02 14:32 ` Fiona Klute via buildroot
2024-09-02 15:02 ` Michael Walle via buildroot
2024-09-02 15:33 ` Fiona Klute via buildroot
2024-09-02 20:52 ` Gaël PORTAY
2024-09-03 9:49 ` Fiona Klute via buildroot
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=ZxkCUCUw5bVSlgRo@ryzen \
--to=buildroot@buildroot.org \
--cc=Niklas.Cassel@wdc.com \
--cc=dlemoal@kernel.org \
--cc=gael.portay@rtone.fr \
--cc=julien.grossholtz@openest.io \
--cc=martin@barkynet.com \
--cc=michael@walle.cc \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.