From: Francesco Dolcini <francesco@dolcini.it>
To: Andrew Davis <afd@ti.com>
Cc: Manorit Chawdhry <m-chawdhry@ti.com>,
Neha Malcom Francis <n-francis@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>,
Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>,
Bryan Brattlof <bb@ti.com>, Jan Kiszka <jan.kiszka@siemens.com>,
Le Jin <le.jin@siemens.com>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH 5/7] arm: mach-k3: am62x: Move board selection to mach-k3
Date: Thu, 2 Nov 2023 09:55:07 +0100 [thread overview]
Message-ID: <ZUNj6yyW/DdMYAV4@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <20231101203530.80359-5-afd@ti.com>
Hello Andrew,
On Wed, Nov 01, 2023 at 03:35:28PM -0500, Andrew Davis wrote:
> Currently each set of board targets from a vendor is selected inside
> the board directory for that vendor. This has the problem of multiple
> targets, one from each vendor, being selectable at the same time.
> For instance you can select both TARGET_AM654_A53_EVM and
> TARGET_IOT2050_A53 in the same build.
>
> To fix this we need to move the target board choice to a common location
> for each parent SoC selection. Do this in arch/arm/mach-k3.
Is this oddity specific of ti k3 based board or is this a generic issue
in u-boot? Asking to understand if a k3-specific fix is the correct one
here.
Francesco
next prev parent reply other threads:[~2023-11-02 8:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 20:35 [PATCH 1/7] board: ti: Add dependency from TARGET selection to SOC Andrew Davis
2023-11-01 20:35 ` [PATCH 2/7] arm: mach-k3: j721e: Move board selection to mach-k3 Andrew Davis
2023-11-01 20:35 ` [PATCH 3/7] arm: mach-k3: am65x: " Andrew Davis
2023-11-01 20:35 ` [PATCH 4/7] arm: mach-k3: am64x: " Andrew Davis
2023-11-01 20:35 ` [PATCH 5/7] arm: mach-k3: am62x: " Andrew Davis
2023-11-02 8:55 ` Francesco Dolcini [this message]
2023-11-02 15:27 ` Andrew Davis
2023-11-01 20:35 ` [PATCH 6/7] arm: mach-k3: am62ax: " Andrew Davis
2023-11-01 20:35 ` [PATCH 7/7] arm: mach-k3: j721s2: " Andrew Davis
2023-11-02 6:25 ` [PATCH 1/7] board: ti: Add dependency from TARGET selection to SOC Neha Malcom Francis
2023-11-22 20:49 ` Tom Rini
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=ZUNj6yyW/DdMYAV4@francesco-nb.int.toradex.com \
--to=francesco@dolcini.it \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=jan.kiszka@siemens.com \
--cc=le.jin@siemens.com \
--cc=m-chawdhry@ti.com \
--cc=marcel.ziswiler@toradex.com \
--cc=n-francis@ti.com \
--cc=nm@ti.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.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