mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: robin <robin@protonic.nl>
To: ejo@pengutronix.de
Cc: barebox@lists.infradead.org, david@protonic.nl
Subject: Using bootspec with RAUC and redundant partitions
Date: Tue, 29 Sep 2020 15:02:15 +0200	[thread overview]
Message-ID: <af59b1cfcfbb69990ddc84d9d454f44e@protonic.nl> (raw)

Hi All,

Can anyone help me determine where to place the bootspec data in a 
system
with redundant partitions for kernel and rootfs?

We're migrating from scripts in env/boot for 'system0' and 'system1', to
bootspec. We're using bootchooser combined with the state framework to 
determine
which target needs to be booted.

Our partition table (relevant partitions):
  mmc2.0: kernel.0
  mmc2.1: kernel.1
  ...
  mmc2.4: rootfs.0
  mmc2.5: rootfs.1

Looking into the bootspec, we could add an additional 'boot' partition 
but this
breaks redundancy, and feels trivial since we have the kernel 
partitions.

But adding the loader/entries to the kernel partitions probably requires 
us to
generate them runtime (Rauc post-install?). Since Rauc determines which 
kernel
partition will be written with the contents of 'kernel' image in a 
bundle the
bootspec can't be determined at build time.

Is there a door number 3 or am I missing something here?

Best regards,
Robin van der Gracht

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2020-09-29 13:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29 13:02 robin [this message]
2020-09-30  7:39 ` Sascha Hauer
2020-09-30  8:09   ` Enrico Jörns
2020-09-30  9:19     ` robin
2020-09-30 10:50       ` Robert Karszniewicz
2020-09-30 11:26       ` robin
2020-09-30 11:48         ` Enrico Jörns
2020-09-30 13:18           ` robin

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=af59b1cfcfbb69990ddc84d9d454f44e@protonic.nl \
    --to=robin@protonic.nl \
    --cc=barebox@lists.infradead.org \
    --cc=david@protonic.nl \
    --cc=ejo@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