All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <Niklas.Cassel@wdc.com>
To: Michael Walle <mwalle@kernel.org>
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 09:48:04 +0000	[thread overview]
Message-ID: <Z1wC0zRgrhS0jl52@ryzen> (raw)
In-Reply-To: <D6AGYGCVAEYN.F84LYRW2DRTV@kernel.org>

Hello Michael,

On Fri, Dec 13, 2024 at 10:35:37AM +0100, Michael Walle wrote:
> 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?
> >
> > I'm assuming that neither works anymore, see:
> > 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/
> > https://lore.kernel.org/buildroot/Z1nq_gneO4ORw3EG@curiosity/T/#t
> 
> Thanks for the pointers.
> 
> 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.

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.

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.


Kind regards,
Niklas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-12-13  9:48 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 [this message]
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=Z1wC0zRgrhS0jl52@ryzen \
    --to=niklas.cassel@wdc.com \
    --cc=buildroot@buildroot.org \
    --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 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.