From: Michael Walle via buildroot <buildroot@buildroot.org>
To: "Niklas Cassel" <Niklas.Cassel@wdc.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>,
"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 11:03:40 +0100 [thread overview]
Message-ID: <D6AHJX8GO6HT.3K4SPRXLX14U4@kernel.org> (raw)
In-Reply-To: <Z1wC0zRgrhS0jl52@ryzen>
[-- Attachment #1.1: Type: text/plain, Size: 882 bytes --]
Hi Niklas,
> > But I've just tested both compiling .dts and .dtso from within a
> > vendor directory and it seems to be working on next-20241213 (?).
>
> If you say that copying to arch/<arch>/dts/<vendor>/ is still working, then
> most likely it is only copying to arch/<arch>/dts that is no longer working.
Copying it to dts/ was wrong for arch's which had a subdir structure
anyway.
>
> I still think that this patch can be merged as is.
>
> Once the BR2_LINUX_KERNEL_CUSTOM_DTS_PATH mess has been sorted, someone could
> add support for out-of-tree device tree overlays, if anyone wants/needs that.
Well, that was actually the intention of my patch :)
> Adding support for in-tree device tree overlays now, does not make life harder
> for anyone if they want to add support for out-of-tree device tree overlays in
> the future.
Agreed.
-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 10:03 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 ` [Buildroot] [PATCH v3 1/2] linux: add support for " Michael Walle via buildroot
2024-12-13 9:09 ` 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 [this message]
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=D6AHJX8GO6HT.3K4SPRXLX14U4@kernel.org \
--to=buildroot@buildroot.org \
--cc=Niklas.Cassel@wdc.com \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=kilian.zinnecker@mail.de \
--cc=mwalle@kernel.org \
--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