From: Michael Walle via buildroot <buildroot@buildroot.org>
To: "Niklas Cassel" <niklas.cassel@wdc.com>, <buildroot@buildroot.org>
Cc: "Kilian Zinnecker" <kilian.zinnecker@mail.de>,
"Damien Le Moal" <dlemoal@kernel.org>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Niklas Cassel" <cassel@kernel.org>
Subject: Re: [Buildroot] [PATCH v3 1/2] linux: add support for device tree overlays
Date: Fri, 13 Dec 2024 09:53:27 +0100 [thread overview]
Message-ID: <D6AG261DAIGT.19EZJ5IUQQ16R@kernel.org> (raw)
In-Reply-To: <20241213083430.4121422-1-niklas.cassel@wdc.com>
[-- Attachment #1.1: Type: text/plain, Size: 869 bytes --]
Hi Niklas,
> -Dropped support for out-of-tree device tree overlays, as Linux 6.12 no
> longer supports building an out-of-tree device tree by simply copying
> it to the kernel source directory (without also modifying the Makefile).
Why is that? As it seems, it is not possible to compile it by simply
copying to arch/<arch>/dts (which is buildroot doing currently)
anymore. But copying it to arch/<arch>/dts/<vendor>/ is working.
Correct?
In that case, we should work on getting support for that in
buildroot as well. Esp. buildroot is really lacking copying an
actual device tree into that subdir too and currently it's a PITA to
include a soc.dtsi for example. If you're using a device tree in
buildroot you'd have to use '#include "vendor/soc.dtsi"' while in
the kernel (as well as in yocto) you'll just use '#include
"soc.dtsi"'.
-michael
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-12-13 8:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 8:34 [Buildroot] [PATCH v3 1/2] linux: add support for device tree overlays Niklas Cassel via buildroot
2024-12-13 8:34 ` [Buildroot] [PATCH v3 2/2] configs/rock5b: build and install rock5b " Niklas Cassel via buildroot
2024-12-13 8:53 ` Michael Walle via buildroot [this message]
2024-12-13 9:09 ` [Buildroot] [PATCH v3 1/2] linux: add support for " Niklas Cassel via buildroot
2024-12-13 9:35 ` Michael Walle via buildroot
2024-12-13 9:48 ` Niklas Cassel
2024-12-13 10:03 ` Michael Walle via buildroot
2025-02-04 16:36 ` Romain Naour via buildroot
2024-12-20 10:06 ` Niklas Cassel via buildroot
2025-01-02 11:48 ` Niklas Cassel 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=D6AG261DAIGT.19EZJ5IUQQ16R@kernel.org \
--to=buildroot@buildroot.org \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=kilian.zinnecker@mail.de \
--cc=mwalle@kernel.org \
--cc=niklas.cassel@wdc.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox