All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
To: "francesco@dolcini.it" <francesco@dolcini.it>, "nm@ti.com" <nm@ti.com>
Cc: "n-francis@ti.com" <n-francis@ti.com>,
	"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
	"ghidoliemanuele@gmail.com" <ghidoliemanuele@gmail.com>,
	Emanuele Ghidoli <emanuele.ghidoli@toradex.com>,
	 "bb@ti.com" <bb@ti.com>
Subject: Re: [PATCH v1 1/2] verdin-am62: add u-boot update wrappers
Date: Mon, 28 Aug 2023 22:11:27 +0000	[thread overview]
Message-ID: <5213a48bb3ec05bec69f78fd480e4be656caedde.camel@toradex.com> (raw)
In-Reply-To: <ZOdsX2VMNf20ioFR@francesco-nb.int.toradex.com>

On Thu, 2023-08-24 at 16:42 +0200, Francesco Dolcini wrote:
> Hello Nishanth,
> 
> On Thu, Aug 24, 2023 at 07:10:57AM -0500, Nishanth Menon wrote:
> > On 13:19-20230824, Francesco Dolcini wrote:
> > > On Thu, Aug 24, 2023 at 10:08:49AM +0200, Emanuele Ghidoli wrote:
> > > > From: Emanuele Ghidoli <emanuele.ghidoli@toradex.com>
> > > > 
> > > > Add update_tiboot3, update_tispl and update_uboot wrappers to update
> > > > R5 SPL, A53 SPL and A53 U-boot respectively.
> > > > 
> > > > Usage example:
> > > > > tftpboot ${loadaddr} tiboot3-am62x-gp-verdin.bin
> > > > > run update_tiboot3
> > > > 
> > > > > tftpboot ${loadaddr} tispl.bin
> > > > > run update_tispl
> > > > 
> > > > > tftpboot ${loadaddr} u-boot.img
> > > > > run update_uboot
> > > > 
> > > > Signed-off-by: Emanuele Ghidoli <emanuele.ghidoli@toradex.com>
> > > 
> > > Acked-by: Francesco Dolcini <francesco.dolcini@toradex.com>
> > 
> > Should you update documentation to indicate the usage?
> 
> Yeah, probably we could add it. I would not remove the existing direct
> command usage since this is adding just env variables that could be
> removed from the env even at runtime.
> 
> In general the reason for these commands is that our users are
> accustomed to have a "guided" way to update u-boot without having to dig
> into the documentation. They are just convenient.
> 
> Marcel: what do you think?

Sure, we took care of it here:

https://lore.kernel.org/all/20230828220154.483362-1-marcel@ziswiler.com

> Francesco

Cheers

Marcel

  reply	other threads:[~2023-08-28 22:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24  8:08 [PATCH v1 0/2] verdin-am62: add u-boot update wrappers and fix check for minimum memory size Emanuele Ghidoli
2023-08-24  8:08 ` [PATCH v1 1/2] verdin-am62: add u-boot update wrappers Emanuele Ghidoli
2023-08-24 11:19   ` Francesco Dolcini
2023-08-24 12:10     ` Nishanth Menon
2023-08-24 14:42       ` Francesco Dolcini
2023-08-28 22:11         ` Marcel Ziswiler [this message]
2023-09-09 13:30   ` Tom Rini
2023-08-24  8:08 ` [PATCH v1 2/2] board: verdin-am62: fix check for minimum memory size Emanuele Ghidoli
2023-08-24 11:20   ` Francesco Dolcini
2023-08-24 12:14   ` Nishanth Menon
2023-08-24 14:37     ` Francesco Dolcini
2023-08-24 14:58       ` Nishanth Menon
2023-08-24 15:52         ` Francesco Dolcini
2023-08-24 16:18           ` Nishanth Menon
2023-09-09 13:30   ` 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=5213a48bb3ec05bec69f78fd480e4be656caedde.camel@toradex.com \
    --to=marcel.ziswiler@toradex.com \
    --cc=bb@ti.com \
    --cc=emanuele.ghidoli@toradex.com \
    --cc=francesco@dolcini.it \
    --cc=ghidoliemanuele@gmail.com \
    --cc=n-francis@ti.com \
    --cc=nm@ti.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 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.