From: Niklas Cassel via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>, Romain Naour <romain.naour@smile.fr>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>,
"Gaël PORTAY" <gael.portay+rtone@gmail.com>,
"Julien Grossholtz" <julien.grossholtz@openest.io>,
"Martin Bark" <martin@barkynet.com>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
"José Mendes" <jp.baltazar.mendes@gmail.com>
Subject: Re: [Buildroot] [PATCH v3 2/3] board/raspberrypi: allow non-matching globs for DTBs
Date: Mon, 10 Feb 2025 12:47:20 +0000 [thread overview]
Message-ID: <Z6n1V0BQyoJjbn4u@ryzen> (raw)
In-Reply-To: <20250207171458.1127620-3-fiona.klute@gmx.de>
Hello Fiona,
On Fri, Feb 07, 2025 at 06:14:57PM +0100, Fiona Klute via buildroot wrote:
> From: "Fiona Klute (WIWA)" <fiona.klute@gmx.de>
>
> When installing DTBs from the rpi-firmware package
> (BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTBS=y), there's no DTB directly in
> the images directory because the kernel build doesn't provide one.
Your new defconfig does not seem to have BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTBS
set. What am I missing?
Regardless, perhaps clarify/rephrase your commit message.
>
> Using pre-compiled DTBs is discouraged, but useful for using mainline
> kernels until suitable DTS can be merged, or to provide U-Boot with a
> DTB (via the firmware bootloader) independent of whatever kernel DTB
> is in use.
I don't really understand which pre-compiled DTB you are using, since
your series is not adding any DTB, and your defconfig does not have
BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTBS set.
However, wouldn't it be much better to rebase this series on either:
1) Romain's series:
https://lore.kernel.org/buildroot/20250204163622.192932-3-romain.naour@smile.fr/
which introduces BR2_LINUX_KERNEL_CUSTOM_DTS_PATH
or
2) Your own series:
https://lore.kernel.org/buildroot/20250207183455.1468220-1-fiona.klute@gmx.de/
Then this series could provide a DT source file (.dts) instead of a binary
blob (.dtb). Having a DTS file would make it easier for other buildroot
contributors to make changes, and once upstream has a DTS merged, you can
remove your DTS file provided by buildroot.
Kind regards,
Niklas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-02-10 12:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 17:14 [Buildroot] [PATCH v3 0/3] U-Boot on RPi boards Fiona Klute via buildroot
2025-02-07 17:14 ` [Buildroot] [PATCH v3 1/3] board/raspberrypi: Support boot.scr for U-Boot Fiona Klute via buildroot
2025-02-07 17:14 ` [Buildroot] [PATCH v3 2/3] board/raspberrypi: allow non-matching globs for DTBs Fiona Klute via buildroot
2025-02-10 12:47 ` Niklas Cassel via buildroot [this message]
2025-02-17 12:33 ` Fiona Klute via buildroot
2025-02-17 13:36 ` Niklas Cassel
2025-02-07 17:14 ` [Buildroot] [PATCH v3 3/3] configs/raspberrypicm4io_64_uboot_defconfig: new defconfig Fiona Klute via buildroot
2025-02-07 21:36 ` Arnout Vandecappelle via buildroot
2025-02-07 22:36 ` bryce.schober
2025-02-10 7:44 ` Arnout Vandecappelle via buildroot
2025-02-13 19:25 ` Fiona Klute via buildroot
2025-02-14 8:12 ` Arnout Vandecappelle 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=Z6n1V0BQyoJjbn4u@ryzen \
--to=buildroot@buildroot.org \
--cc=Niklas.Cassel@wdc.com \
--cc=fiona.klute@gmx.de \
--cc=gael.portay+rtone@gmail.com \
--cc=jp.baltazar.mendes@gmail.com \
--cc=julien.grossholtz@openest.io \
--cc=martin@barkynet.com \
--cc=romain.naour@smile.fr \
--cc=yann.morin.1998@free.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