Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Fiona Klute via buildroot <buildroot@buildroot.org>
To: Bryce Johnson <bryce@redpinelabs.com>
Cc: Romain Naour <romain.naour@smile.fr>,
	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>
Subject: Re: [Buildroot] [PATCH v2 1/1] linux: make out-of-tree DTS work with newest kernels
Date: Tue, 4 Feb 2025 19:27:49 +0100	[thread overview]
Message-ID: <2aa26a7d-04ba-4428-87df-a01397a996be@gmx.de> (raw)
In-Reply-To: <CADXxVSJ-0GtrywPpHwy_naA2Jx=aj31c=qLbNtt+bQ6YVqujnQ@mail.gmail.com>

Hi Bryce!

Am 04.02.25 um 15:47 schrieb Bryce Johnson:
> Hi Fiona,
> I tried the patch and it looks interesting, was there a way to still
> include some dtsi included in the kernel?  For example, I have a
> custom board with TI AM62X.  I might have a myboard.dts that wants to
> include from the kernel, k3-am625.dtsi which includes k3-am62.dtsi,
> which include k3-am62-main.dtsi,k3-am62-mcu.dtsi, k3-am62-wakeup.dtsi,
> etc.

Yes, I actually do that in my setups. E.g. I have a WIP (not posted
publicly yet, but planned) DTS for a certain RPi CM4 based device [1]. I
just have

#include "arm/broadcom/bcm2711-rpi-cm4-io.dts"

in there to start from the mainline CM4 IO-Board DTS. I should probably
switch to bcm2711-rpi-cm4.dtsi instead before sending a kernel patch,
but it works. :-)

Making that work is why $(LINUX_DIR)/scripts/dtc/include-prefixes/ is
added to the include paths for dtc in custom-dtbs.mk. What doesn't work
yet is using extra .dtsi files (as in ones you provide, not from kernel
source), but that should be easy to add.

Best regards,
Fiona

(Patch link for reference)
>> See:
>> https://patchwork.ozlabs.org/project/buildroot/patch/20250203154651.2790784-1-fiona.klute@gmx.de/
[1] https://revolutionpi.com/documentation/revpi-connect-4/
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2025-02-04 18:28 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
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 [this message]

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=2aa26a7d-04ba-4428-87df-a01397a996be@gmx.de \
    --to=buildroot@buildroot.org \
    --cc=bonet@grenoble.cnrs.fr \
    --cc=bryce@redpinelabs.com \
    --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