From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Neal Frager <neal.frager@amd.com>,
buildroot@buildroot.org, luca.ceresoli@bootlin.com,
brandon.maier@collins.com, romain.naour@smile.fr,
michal.simek@amd.com, yann.morin.1998@free.fr
Subject: Re: [Buildroot] [PATCH v4 1/1] configs/versal_vek280_defconfig: new defconfig
Date: Mon, 4 Nov 2024 23:40:57 +0100 [thread overview]
Message-ID: <20241104234057.21de4c2c@windsurf> (raw)
In-Reply-To: <c9bfc18d-9590-40d1-8e77-15ae3f4dc85a@mind.be>
On Mon, 4 Nov 2024 20:31:35 +0100
Arnout Vandecappelle <arnout@mind.be> wrote:
> This DEVICE_TREE= option is already used in 21 defconfigs (and 13 of those are
> Xilinx defconfigs ;-) Perhaps it is time to create an explicit uboot/Config.in
> option for it? Ideally the config interface would be similar to the options we
> have for Linux.
It's indeed an option that almost always *must* be passed these days,
unless by luck there is a board-specific U-Boot defconfig that
references the correct Device Tree.
So I would tend to agree with you on this one.
Best regards,
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-11-04 22:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 5:21 [Buildroot] [PATCH v4 1/1] configs/versal_vek280_defconfig: new defconfig Neal Frager via buildroot
2024-08-12 13:02 ` Brandon Maier via buildroot
2024-08-19 8:39 ` Luca Ceresoli via buildroot
2024-09-09 8:32 ` Frager, Neal via buildroot
2024-11-03 22:09 ` Julien Olivain
2024-11-04 19:31 ` Arnout Vandecappelle via buildroot
2024-11-04 22:40 ` Thomas Petazzoni via buildroot [this message]
2024-11-05 6:19 ` Frager, Neal 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=20241104234057.21de4c2c@windsurf \
--to=buildroot@buildroot.org \
--cc=arnout@mind.be \
--cc=brandon.maier@collins.com \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.com \
--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