U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: "Svyatoslav Ryhel" <clamor95@gmail.com>,
	"Jonas Schwöbel" <jonasschwoebel@yahoo.de>,
	"Thierry Reding" <treding@nvidia.com>,
	"Francesco Dolcini" <francesco.dolcini@toradex.com>,
	"Joe Hershberger" <joe.hershberger@ni.com>,
	"Marcel Ziswiler" <marcel.ziswiler@toradex.com>,
	"Fabio Estevam" <festevam@gmail.com>,
	"Simon Glass" <sjg@chromium.org>,
	"Emanuele Ghidoli" <emanuele.ghidoli@toradex.com>,
	"Martyn Welch" <martyn.welch@collabora.com>,
	u-boot@lists.denx.de
Subject: Re: [PATCH v1 0/1] board: tegra: convert boards to text env
Date: Mon, 5 Aug 2024 12:14:14 -0600	[thread overview]
Message-ID: <20240805181414.GA267004@bill-the-cat> (raw)
In-Reply-To: <20240805053343.GB7516@francesco-nb>

[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]

On Mon, Aug 05, 2024 at 07:33:43AM +0200, Francesco Dolcini wrote:
> Hello Tom,
> 
> On Thu, Aug 01, 2024 at 08:57:37AM +0300, Svyatoslav Ryhel wrote:
> > Move env stuff into dedicated files in boards (1st stage).
> 
> Is there any plan or expectation to move existing boards to text env file?
> And what about newly added boards?

Long term, we would like to eliminate include/configs/<board.h> and so
yes, conversion to plain text environment is needed for that to happen.
Is every use case 1:1 supported? No as for example, boards need to move
from "distro boot" (which uses tons of cpp macros that we just can't do
in plain text env) to "standard boot" and while no functionality is
intended to change with that, it's a conversion that requires the
developer to check the result and verify it does what's expected in that
case (boards that don't use "distro boot" for example can be if not
mechanically converted, at least u-boot-initial-env compared
before/after and verified to match).

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

      parent reply	other threads:[~2024-08-05 18:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-01  5:57 [PATCH v1 0/1] board: tegra: convert boards to text env Svyatoslav Ryhel
2024-08-01  5:57 ` [PATCH v1 1/1] board: tegra: convert tegra-based " Svyatoslav Ryhel
2024-08-05  5:31   ` Francesco Dolcini
2024-08-05  7:01     ` Svyatoslav Ryhel
2024-08-05  7:05       ` Francesco Dolcini
2024-08-05  7:06         ` Svyatoslav Ryhel
2024-08-05  7:08           ` Francesco Dolcini
2024-08-05  7:10             ` Svyatoslav Ryhel
2024-08-05 15:07             ` Svyatoslav Ryhel
2024-08-05  5:33 ` [PATCH v1 0/1] board: tegra: convert " Francesco Dolcini
2024-08-05  6:03   ` Svyatoslav Ryhel
2024-08-05  6:12     ` Francesco Dolcini
2024-08-05 18:14   ` Tom Rini [this message]

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=20240805181414.GA267004@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=clamor95@gmail.com \
    --cc=emanuele.ghidoli@toradex.com \
    --cc=festevam@gmail.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=francesco@dolcini.it \
    --cc=joe.hershberger@ni.com \
    --cc=jonasschwoebel@yahoo.de \
    --cc=marcel.ziswiler@toradex.com \
    --cc=martyn.welch@collabora.com \
    --cc=sjg@chromium.org \
    --cc=treding@nvidia.com \
    --cc=u-boot@lists.denx.de \
    /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