From: Michael Walle via buildroot <buildroot@buildroot.org>
To: "Edgar Bonet" <bonet@grenoble.cnrs.fr>,
"Buildroot development" <buildroot@buildroot.org>
Cc: Romain Naour <romain.naour@smile.fr>,
Chris Packham <judge.packham@gmail.com>,
Kilian Zinnecker <kilian.zinnecker@mail.de>,
Sergey Matyukevich <geomatsi@gmail.com>
Subject: Re: [Buildroot] [PATCH v3 1/1] linux: make out-of-tree DTS work with newest kernels
Date: Sun, 05 Jan 2025 22:11:45 +0100 [thread overview]
Message-ID: <D6UG5Z1HUN9N.GWVHB4L823ZC@kernel.org> (raw)
In-Reply-To: <93f83afb-6987-441c-8e06-dab4d43b828f@grenoble.cnrs.fr>
Hi,
> Fulfilling this kernel expectation would require a new
> configuration parameter for the name of the appropriate vendor
> subdirectory.
No, that doesn't work. The vendor part *has* to be included in this
config option as it may contain different device tree (file names).
Don't assume the vendor part will always be the same for different
device trees.
Somehow we have to split the source directory of the OOT device
trees and the (relative) destination within the kernel tree (eg.
'freescale/fsl-ls1028a-my-device-tree.dts', or just
'my-device-tree.dts'). Please keep in mind that the device trees
might also end up in the target filesystem in /boot and these might
also need the vendor prefix (see BR2_LINUX_KERNEL_DTB_KEEP_DIRNAME).
> It would also require changing the relative paths to included
> .dtsi files.
Yes, but I'd argue, that the current solution is broken in this
regard. Yes we shouldn't break things, but newer OOT device trees
should use the same #include directives as the in-tree device trees
to ease sharing the files between u-boot, linux and OOT external
trees. As of today, it's not (always) possible to use the same
(OOT) device tree for u-boot and linux in buildroot, i.e. if the
arch has subdirs and one use the OF_UPSTREAM configuration option in
u-boot.
-michael
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-01-05 21:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 14:33 [Buildroot] [PATCH v3 1/1] linux: make out-of-tree DTS work with newest kernels Edgar Bonet
2025-01-03 22:07 ` Romain Naour via buildroot
2025-01-04 7:21 ` Kilian Zinnecker via buildroot
2025-01-05 21:11 ` Michael Walle via buildroot [this message]
2025-01-22 10:40 ` Romain Naour via buildroot
2025-01-22 10:52 ` Arnout Vandecappelle via buildroot
2025-01-22 11:06 ` Romain Naour via buildroot
2025-01-22 11:09 ` Michael Walle via buildroot
2025-01-22 19:48 ` Edgar Bonet
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=D6UG5Z1HUN9N.GWVHB4L823ZC@kernel.org \
--to=buildroot@buildroot.org \
--cc=bonet@grenoble.cnrs.fr \
--cc=geomatsi@gmail.com \
--cc=judge.packham@gmail.com \
--cc=kilian.zinnecker@mail.de \
--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