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@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox
