mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Stefan Riedmüller" <s.riedmueller@phytec.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org,
	Robert Karszniewicz <r.karszniewicz@phytec.de>
Subject: Re: [RFC PATCH 0/4] Introduce global.bootm.root env var for booting via PARTUUID
Date: Wed, 8 Jul 2020 08:55:56 +0200	[thread overview]
Message-ID: <d89ff71b-e442-83aa-9ca5-dcf49002e23f@phytec.de> (raw)
In-Reply-To: <20200701055834.GK15485@pengutronix.de>

Hi Sascha,

let me answer on behalf of Robert.

On 01.07.20 07:58, Sascha Hauer wrote:
> Hi Robert,
> 
> On Tue, Jun 30, 2020 at 04:20:17PM +0200, Robert Karszniewicz wrote:
>> The problem is that we want to be able to have the rootfs and kernel on
>> separate partitions.
> 
> Why do you want to have that? It's kind of traditional to have the
> kernel separated from the rootfs in some extra "kernel" partition, but
> are there good reasons for it? There's an overhead in that the
> bootloader has to read from a filesystem instead of only a raw
> partition. Is that the reason?

Actually the reason is that we have this separate setup for quite some time 
now in the field and changing it would have a whole string of consequences 
attached to it. So we try not to change this setup, at least for existing 
systems.

That is why we would like to be able to get the PARTUUID from another 
Partition than the one containing the kernel image.

What do you think of Roberts proposal?

> 
> Here at Pengutronix we are happy that we only have one partition image
> that has everything needed to boot, including a description how to boot
> it and including the kernel. No extra items that the bootloader has to
> take care of, just put one thing somewhere and be done with it.

This sounds like a good thing to have and I think we should consider this 
for new platforms.

Regards,
Stefan

> 
>> We've looked into the Boot Loader Specification, but
>> from what we saw, it makes A-B systems difficult (according to the spec,
>> there can only be one "$BOOT" filesystem on a device).
> 
> barebox is more relaxed here. What we do here is to put two full root
> filesystems into two different partitions on a SD/MMC. Each of the
> partitions has one or more /loader/entries/*.conf file(s) and kernels.
> You can then boot with "boot mmc0.0" into the first rootfs or with "boot
> mmc0.1" into the second.
> This may not be really conform to the specification, but works in
> barebox and is a supported usecase. We do this for A/B Boot scenarios in
> many projects.
> 
> Regards,
>    Sascha
> 

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

  reply	other threads:[~2020-07-08  6:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30 13:48 Robert Karszniewicz
2020-06-30 13:48 ` [RFC PATCH 1/4] bootm: add env var root_dev Robert Karszniewicz
2020-06-30 13:48 ` [RFC PATCH 2/4] globalvar: add bootm.root Robert Karszniewicz
2020-06-30 13:48 ` [RFC PATCH 3/4] bootm: handle global.bootm.root Robert Karszniewicz
2020-06-30 13:48 ` [RFC PATCH 4/4] bootm: mount root device before accessing linux_rootarg Robert Karszniewicz
2020-06-30 14:20 ` [RFC PATCH 0/4] Introduce global.bootm.root env var for booting via PARTUUID Robert Karszniewicz
2020-07-01  5:58   ` Sascha Hauer
2020-07-08  6:55     ` Stefan Riedmüller [this message]
2020-07-09 14:14 ` Sascha Hauer
2020-07-13 11:18   ` Robert Karszniewicz
2020-07-14 18:37     ` Sascha Hauer

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=d89ff71b-e442-83aa-9ca5-dcf49002e23f@phytec.de \
    --to=s.riedmueller@phytec.de \
    --cc=barebox@lists.infradead.org \
    --cc=r.karszniewicz@phytec.de \
    --cc=s.hauer@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