From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Gaël PORTAY" <gael.portay@gmail.com>
Cc: "Gaël PORTAY" <gael.portay@rtone.fr>,
"Martin Bark" <martin@barkynet.com>,
"Julien Grossholtz" <julien.grossholtz@openest.io>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 4/8] configs/raspberrypi3_64: remove upstream device-tree blob
Date: Wed, 17 Jul 2024 23:21:13 +0200 [thread overview]
Message-ID: <20240717232113.0f00055d@windsurf> (raw)
In-Reply-To: <20240716054359.92966-5-gael.portay@rtone.fr>
On Tue, 16 Jul 2024 07:43:55 +0200
"Gaël PORTAY" <gael.portay@gmail.com> wrote:
> This removes the upstream device-tree blob for the beauty of
> consistency.
>
> Note: It is possible to load the upstream device-tree using the
> upstream_kernel property[3].
But I suppose this only works if the upstream DTBs are installed... and
we are not installing them, right?
But I guess upstream Device Trees make sense if you use the upstream
kernel, while those defconfigs all use the vendor/downstream kernel, so
it makes complete sense to use the corresponding vendor/downstream
kernel.
Thanks,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-07-17 21:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 5:43 [Buildroot] [PATCH 0/8] configs/raspberrypi*: install missing dtb Gaël PORTAY
2024-07-16 5:43 ` [Buildroot] [PATCH 1/8] configs/raspberrypi: install Raspberry Pi rev 1.0 device-tree blob Gaël PORTAY
2024-07-16 5:43 ` [Buildroot] [PATCH 2/8] configs/raspberrypi2: install Raspberry Pi 2 rev 1.2 " Gaël PORTAY
2024-07-16 5:43 ` [Buildroot] [PATCH 3/8] configs/raspberrypi3_64: install Compute Module 3 " Gaël PORTAY
2024-07-17 21:20 ` Thomas Petazzoni via buildroot
2024-07-16 5:43 ` [Buildroot] [PATCH 4/8] configs/raspberrypi3_64: remove upstream " Gaël PORTAY
2024-07-17 21:21 ` Thomas Petazzoni via buildroot [this message]
2024-07-16 5:43 ` [Buildroot] [PATCH 5/8] configs/raspberrypi4*: install Raspberry Pi 400 " Gaël PORTAY
2024-07-16 5:43 ` [Buildroot] [PATCH 6/8] configs/raspberrypi4*: install Compute Module 4/4s device-tree blobs Gaël PORTAY
2024-07-16 5:43 ` [Buildroot] [PATCH 7/8] configs/raspberrypi5: install BCM2712D0 device-tree blob Gaël PORTAY
2024-07-16 5:43 ` [Buildroot] [PATCH 8/8] configs/raspberrypi*: sort some configs Gaël PORTAY
2024-07-17 21:19 ` [Buildroot] [PATCH 0/8] configs/raspberrypi*: install missing dtb Thomas Petazzoni 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=20240717232113.0f00055d@windsurf \
--to=buildroot@buildroot.org \
--cc=gael.portay@gmail.com \
--cc=gael.portay@rtone.fr \
--cc=julien.grossholtz@openest.io \
--cc=martin@barkynet.com \
--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.