From: Niklas Cassel <Niklas.Cassel@wdc.com>
To: Romain Naour <romain.naour@smile.fr>
Cc: Fiona Klute <fiona.klute@gmx.de>,
Edgar Bonet <bonet@grenoble.cnrs.fr>,
Buildroot development <buildroot@buildroot.org>,
Michael Walle <mwalle@kernel.org>,
Chris Packham <judge.packham@gmail.com>,
Sergey Matyukevich <geomatsi@gmail.com>,
"dlemoal@kernel.org" <dlemoal@kernel.org>
Subject: Re: [Buildroot] [PATCH v2 1/1] linux: make out-of-tree DTS work with newest kernels
Date: Thu, 30 Jan 2025 10:30:44 +0000 [thread overview]
Message-ID: <Z5tU0zCAiReVPvPY@ryzen> (raw)
In-Reply-To: <d01683ed-cc7e-4c0d-a807-7a76ce7129ba@smile.fr>
Hello Romain,
On Wed, Jan 29, 2025 at 11:10:31AM +0100, Romain Naour via buildroot wrote:
>
> AFAIK, the current BR2_LINUX_KERNEL_CUSTOM_DTS_PATH option doesn't seems to take
> into account any external devicetree overlay files (dtso).
>
> I've send a new version of this patch (but dtso are not supported):
>
> https://lore.kernel.org/buildroot/20250129095716.2511434-1-romain.naour@smile.fr/T/#t
>
> >
> > Would something like that be interesting for Buildroot, whether as a
> > generic DTB build package or infrastructure?
>
> While reviewing this patch, I had to take a look at how to build a dtb file
> outside of the kernel build infrastructure (like Yocto does) but it's not easy.
> Actually we are happy to keep this build process hidden in the kernel Makefiles.
>
> Since the next Buildroot meeting is next week, this is probably a topic we can
> discuss. Feel free to send a patch (even a draft).
The patch series that you link to above only cater to out-of-tree device
trees.
I've send a patch for in-tree device tree overlays (.dtso) that has been
ignored:
https://lore.kernel.org/buildroot/Z2VBjTBKUkn9Mehr@ryzen/T/#u
If there is a Buildroot meeting next week, perhaps you could be nice to
bring up the use case of in-tree device tree overlays (.dtso).
I would be nice if either:
1) My patch is merged.
2) Some other patch that adds support for in-tree device tree overlays
(.dtso) gets accepted.
Kind regards,
Niklas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-01-30 10:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 9:55 [Buildroot] [PATCH v2 1/1] linux: make out-of-tree DTS work with newest kernels Edgar Bonet
2024-12-18 14:55 ` Romain Naour via buildroot
2024-12-24 12:22 ` Edgar Bonet
2025-01-28 13:33 ` Fiona Klute via buildroot
2025-01-29 10:10 ` Romain Naour via buildroot
2025-01-30 10:30 ` Niklas Cassel [this message]
2025-01-30 18:12 ` Romain Naour via buildroot
2025-02-03 15:48 ` Fiona Klute via buildroot
2025-02-04 14:47 ` Bryce Johnson
2025-02-04 18:27 ` 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=Z5tU0zCAiReVPvPY@ryzen \
--to=niklas.cassel@wdc.com \
--cc=bonet@grenoble.cnrs.fr \
--cc=buildroot@buildroot.org \
--cc=dlemoal@kernel.org \
--cc=fiona.klute@gmx.de \
--cc=geomatsi@gmail.com \
--cc=judge.packham@gmail.com \
--cc=mwalle@kernel.org \
--cc=romain.naour@smile.fr \
/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