mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: robin <robin@protonic.nl>
Cc: barebox@lists.infradead.org, ejo@pengutronix.de, david@protonic.nl
Subject: Re: Using bootspec with RAUC and redundant partitions
Date: Wed, 30 Sep 2020 09:39:46 +0200	[thread overview]
Message-ID: <20200930073946.GG11648@pengutronix.de> (raw)
In-Reply-To: <af59b1cfcfbb69990ddc84d9d454f44e@protonic.nl>

Hi Robin,

On Tue, Sep 29, 2020 at 03:02:15PM +0200, robin wrote:
> 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.

Yes, I wouldn't add an additional boot partition.

> 
> 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?

What's the reason for additional kernel partitions? Things would be
easier if you put the kernel images into the rootfs partitions along
with the bootspec entries.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

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

  reply	other threads:[~2020-09-30  7:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29 13:02 robin
2020-09-30  7:39 ` Sascha Hauer [this message]
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=20200930073946.GG11648@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=david@protonic.nl \
    --cc=ejo@pengutronix.de \
    --cc=robin@protonic.nl \
    /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