Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Gaël PORTAY" <gael.portay@gmail.com>
To: "Fiona Klute" <fiona.klute@gmx.de>,
	"Michael Walle" <michael@walle.cc>, <buildroot@buildroot.org>
Cc: "Niklas Cassel" <Niklas.Cassel@wdc.com>,
	"Gaël PORTAY" <gael.portay@rtone.fr>,
	"Julien Grossholtz" <julien.grossholtz@openest.io>,
	"Damien Le Moal" <dlemoal@kernel.org>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Martin Bark" <martin@barkynet.com>
Subject: Re: [Buildroot] [PATCH v2] linux: add support for device tree overlays
Date: Mon, 02 Sep 2024 22:52:14 +0200	[thread overview]
Message-ID: <D3W3GXLAY046.CI48SHS5EP44@gmail.com> (raw)
In-Reply-To: <a9865fde-0c09-42dd-8cd2-d174412dce28@gmx.de>

All, thank you for your interest in bringing the support for dtbo!

On Mon Sep 2, 2024 at 4:32 PM CEST, Fiona Klute via buildroot wrote:
> > -LINUX_DTS_NAME += $(basename $(filter %.dts,$(notdir $(call qstrip,$(BR2_LINUX_KERNEL_CUSTOM_DTS_PATH)))))
> > +LINUX_CUSTOM_DTS_PATH = $(call qstrip,$(BR2_LINUX_KERNEL_CUSTOM_DTS_PATH))
> > +LINUX_DTS_NAME += $(basename $(filter %.dts,$(notdir $(LINUX_CUSTOM_DTS_PATH))))
> > +LINUX_DTSO_NAMES += $(basename $(filter %.dtso,$(notdir $(LINUX_CUSTOM_DTS_PATH))))
> >
> > -LINUX_DTBS = $(addsuffix .dtb,$(LINUX_DTS_NAME))
> > +LINUX_DTBS = $(addsuffix .dtb,$(LINUX_DTS_NAME)) $(addsuffix .dtbo,$(LINUX_DTSO_NAMES))
>
> This looks like the DTBOs will be installed to $BINARIES_DIR along with
> the DTBs. At least on RPi platforms it'd be preferable to be able to put
> them in an overlays/ directory, to make it easier to create the
> structure expected by the firmware in a genimage config without
> templating. I don't know how common this is across other platforms that
> use DT overlays.
>

IIRC, I have seen platforms that put the dtb and dtbo at the same place.

I strongly think the Pi is the one that put the dtbo in the subdirectory
overlays/.

> Would it be practical to add an option to install DTBOs in a
> (configurable) subdirectory?
>

Well, I do not really like adding an option to set the target directory.

In my patch serie I have completly split the dtbo from the dtb; so you
can keep or not the "top" directory for dtb (broadcom) and for dtbo
(overlays).

I do not think it worth it, but it helps for the Pi.

In the case of the Pi, you set:

	# BR2_LINUX_KERNEL_DTB_KEEP_DIRNAME is not set
	BR2_LINUX_KERNEL_DTBO_KEEP_DIRNAME=y

To install dtbos to $BINARIES_DIR/overlays and dtb to $BINARIES_DIR.

	https://patchwork.ozlabs.org/project/buildroot/patch/20240902203533.3961108-2-gael.portay@rtone.fr/

I have no strong opinion about your work (more simple) and mine (more
duplication).

> Either way thank you for working on this!
>

Yes thank you (again).

> Best regards,
> Fiona
>

Kind Regards,
Gaël
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2024-09-02 20:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-02 11:27 [Buildroot] [PATCH v2] linux: add support for device tree overlays Michael Walle via buildroot
2024-09-02 12:38 ` Niklas Cassel via buildroot
2024-09-02 15:07   ` Michael Walle via buildroot
2024-10-08 14:42     ` Niklas Cassel via buildroot
2024-10-23 14:04   ` Niklas Cassel via buildroot
2025-02-04 10:44     ` Romain Naour via buildroot
2024-09-02 14:32 ` Fiona Klute via buildroot
2024-09-02 15:02   ` Michael Walle via buildroot
2024-09-02 15:33     ` Fiona Klute via buildroot
2024-09-02 20:52   ` Gaël PORTAY [this message]
2024-09-03  9:49     ` Fiona Klute 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=D3W3GXLAY046.CI48SHS5EP44@gmail.com \
    --to=gael.portay@gmail.com \
    --cc=Niklas.Cassel@wdc.com \
    --cc=buildroot@buildroot.org \
    --cc=dlemoal@kernel.org \
    --cc=fiona.klute@gmx.de \
    --cc=gael.portay@rtone.fr \
    --cc=julien.grossholtz@openest.io \
    --cc=martin@barkynet.com \
    --cc=michael@walle.cc \
    --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