mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Enrico Jörns" <ejo@pengutronix.de>
To: robin <robin@protonic.nl>
Cc: barebox@lists.infradead.org, david@protonic.nl
Subject: Re: Using bootspec with RAUC and redundant partitions
Date: Wed, 30 Sep 2020 10:09:41 +0200	[thread overview]
Message-ID: <5ad7abf6ca49d58b928acceb49bac2225a0629f4.camel@pengutronix.de> (raw)
In-Reply-To: <20200930073946.GG11648@pengutronix.de>

Hi Robin,

Am Mittwoch, den 30.09.2020, 09:39 +0200 schrieb Sascha Hauer:
> > 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.

the road to success here is to not encode any slot-/partition-specific
information in the bootspec entries.

Why this would work anyway is because barebox extends the kernel
commandline with the root= entries required to boot the kernel from
that specific partition where it did read the entry from.

This way it should work having an A+B setup with only two rootfs
partitions that include the kernel, the (generic) bootspec entry and
the rootfs itself (as Sascha already pointed out).

Best regards, Enrico

-- 
Pengutronix e.K.                           | Enrico Jörns                |
Embedded Linux Consulting & Support        | https://www.pengutronix.de/ |
Steuerwalder Str. 21                       | Phone: +49-5121-206917-180  |
31137 Hildesheim, Germany                  | Fax:   +49-5121-206917-9    |


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

  reply	other threads:[~2020-09-30  8:09 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
2020-09-30  8:09   ` Enrico Jörns [this message]
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=5ad7abf6ca49d58b928acceb49bac2225a0629f4.camel@pengutronix.de \
    --to=ejo@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=david@protonic.nl \
    --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