mail archive of the rauc mailing list
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: "RAUC@pengutronix.de" <RAUC@pengutronix.de>
Subject: Re: [RAUC] Non reduntant bootloader update
Date: Wed, 04 Jan 2023 12:08:11 +0100	[thread overview]
Message-ID: <87sfgq7e1w.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <0ad147b8-f5f6-9151-8bce-044496d75493@pengutronix.de> (Ahmad Fatoum's message of "Wed, 4 Jan 2023 11:40:50 +0100")

>>>>> "Ahmad" == Ahmad Fatoum <a.fatoum@pengutronix.de> writes:

 > Hello Peter,
 > On 04.01.23 11:36, Peter Korsgaard wrote:
 >> Hi,
 >> 
 >> >> Good to hear. In case you are using meta-rauc, I recently submitted this change,
 >> >> that you may find useful if you are using barebox on 8MN/P:
 >> >> https://github.com/rauc/meta-rauc/commit/f2d051d37008deb4204acd8ab0f5f3f0e9a3971d
 >> 
 >> Not a meta-rauc user, but doesn't this now require that positive offsets
 >> have a + prefix, breaking backwards compatibility?

 > imgoffset is slotflags.get('offset') by default unless it starts
 > with either a + or -. Similarly, padding is "seek" by default.

 > The original RAUC_SLOT_bootloader[offset] = "32K" syntax should
 > thus continue to work normally.

Ahh yes, so the assignment to padding in line 270 is not strictly
needed. Sorry for the noise.

-- 
Bye, Peter Korsgaard



      reply	other threads:[~2023-01-04 11:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03  8:17 BAUER Bernd
2023-01-03  8:31 ` Ahmad Fatoum
2023-01-03  9:39   ` Jan Lübbe
2023-01-03 10:22     ` Jan Lübbe
2023-01-03 14:22       ` BAUER Bernd
2023-01-04 10:14         ` BAUER Bernd
2023-01-04 10:18           ` Ahmad Fatoum
2023-01-04 10:23             ` BAUER Bernd
2023-01-04 10:36               ` Peter Korsgaard
2023-01-04 10:40                 ` Ahmad Fatoum
2023-01-04 11:08                   ` Peter Korsgaard [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=87sfgq7e1w.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=RAUC@pengutronix.de \
    --cc=a.fatoum@pengutronix.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