All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: Martin Schwan <M.Schwan@phytec.de>,
	"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
	"upstream@lists.phytec.de" <upstream@lists.phytec.de>
Subject: Re: [PATCH 1/2] bootstd: Add implementation for bootmeth rauc
Date: Fri, 25 Apr 2025 08:37:52 -0600	[thread overview]
Message-ID: <20250425143752.GU5495@bill-the-cat> (raw)
In-Reply-To: <CAFLszThPcJjhBVLvz=EkdeEP1K948cC=LyZhBk_Upk3iSWXCig@mail.gmail.com>

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

On Fri, Apr 25, 2025 at 08:35:52AM -0600, Simon Glass wrote:
> Hi Tom,
> 
> On Thu, 24 Apr 2025 at 12:49, Tom Rini <trini@konsulko.com> wrote:
> >
> > On Thu, Apr 24, 2025 at 12:31:38PM -0600, Simon Glass wrote:
> > > Hi Martin,
> > >
> > > On Thu, 24 Apr 2025 at 06:43, Martin Schwan <M.Schwan@phytec.de> wrote:
> > > >
> > > > Hi Simon,
> > > >
> > > > thanks for the review and sorry for my delayed reply.
> > > >
> > > > On Mon, 2025-04-14 at 05:32 -0600, Simon Glass wrote:
> > > > > Hi Martin,
> > > > >
> > > > > On Wed, 29 Jan 2025 at 07:25, Martin Schwan <m.schwan@phytec.de>
> > > > > wrote:
> > > > > >
> > > > > > Add a bootmeth driver which supports booting A/B system with RAUC
> > > > > > as
> > > > > > their update client.
> > > > > >
> > > > > > Signed-off-by: Martin Schwan <m.schwan@phytec.de>
> > > > > > ---
> > > > > >  boot/Kconfig         |  11 ++
> > > > > >  boot/Makefile        |   1 +
> > > > > >  boot/bootmeth_rauc.c | 408
> > > > > > +++++++++++++++++++++++++++++++++++++++++++++++++++
> > > > > >  3 files changed, 420 insertions(+)
> > > > >
> > > > > This looks fine to me. Just some nits below.
> > > > >
> > >
> > > [..]
> > >
> > > > > > +
> > > > > > +       partitions = env_get("rauc_partitions");
> > > > > > +       if (!partitions)
> > > > > > +               return log_msg_ret("env", -ENOENT);
> > > > > > +       partitions_list = str_to_list(partitions);
> > > > > > +
> > > > > > +       slots = env_get("rauc_slots");
> > > > > > +       if (!slots)
> > > > > > +               return log_msg_ret("env", -ENOENT);
> > > > > > +       slots_list = str_to_list(slots);
> > > > > > +
> > > > > > +       boot_order = env_get("BOOT_ORDER");
> > > > >
> > > > > Environment variables should be in lower case.
> > > >
> > > > Unfortunately, we are bound to the naming RAUC uses for these
> > > > environment variables, which is upper case. See
> > > > https://rauc.readthedocs.io/en/latest/integration.html#set-up-u-boot-boot-script-for-rauc
> > >
> > > Can't you change it, since you are introducing new support here?
> > >
> > > If not, then you could perhaps set the env variables to lowercase when
> > > you find uppercase variables? I suppose that would require updating
> > > the client to do the same thing too?
> > >
> > > It would be very confusing for a user to have upper-case variables for
> > > some things.
> >
> > Simon, this is an unreasonable request. This is how RAUC has been
> > working and deployed for years and years. It would be a nightmare trying
> > to handle migration of existing deployments for an aesthetic change.
> 
> Yes, I figured. Perhaps it could support lower case in future? This is
> the first I have seen on RAUC in U-Boot, although I do see this file
> which has both lower and upper case:
> 
> include/env/phytec/rauc.env

I don't think there's any need to complicate RAUC support here (nor
in the future Mender nor swupdate nor any other long standing OTA
mechanism that might be more easily integrated via bootstd than
environment patching).

-- 
Tom

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

  reply	other threads:[~2025-04-25 14:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29 14:25 [PATCH 0/2] bootstd: New bootmeth for RAUC A/B systems Martin Schwan
2025-01-29 14:25 ` [PATCH 1/2] bootstd: Add implementation for bootmeth rauc Martin Schwan
2025-01-29 16:03   ` Tom Rini
2025-01-30  9:48     ` Martin Schwan
2025-01-30 14:51       ` Tom Rini
2025-04-14  5:49         ` Wadim Egorov
2025-04-14 11:32   ` Simon Glass
2025-04-24 12:43     ` Martin Schwan
2025-04-24 18:31       ` Simon Glass
2025-04-24 18:49         ` Tom Rini
2025-04-25 14:35           ` Simon Glass
2025-04-25 14:37             ` Tom Rini [this message]
2025-04-25 15:03               ` Simon Glass
2025-04-25 16:19                 ` Tom Rini
2025-04-28  8:25                   ` Martin Schwan
2025-04-28 15:39                     ` Tom Rini
2025-04-29 14:19                   ` Simon Glass
2025-04-28  8:35                 ` Alexander Dahl
2025-05-06  7:05   ` [Upstream] " Wadim Egorov
2025-01-29 14:25 ` [PATCH 2/2] doc: Add description " Martin Schwan

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=20250425143752.GU5495@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=M.Schwan@phytec.de \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    --cc=upstream@lists.phytec.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.