All of
 help / color / mirror / Atom feed
From: "Mike Looijmans" <>
To: Patches and discussions about the oe-core layer
Subject: Build the "boot" partition image (just like the rootfs)
Date: Mon, 15 Mar 2021 14:13:46 +0100	[thread overview]
Message-ID: <> (raw)

For software updates, I want to have what would have gone into the boot 
partition of the WIC image as a separate file.

If I want to have the contents of the rootfs as an ext4 image, I can 
just specify IMAGE_TYPES="ext4" in my image recipe.

This image I can feed to SWUdate and write to the rootfs storage.

But I also want to be able to update the boot partition (for example, 
the raspberrypi has the annoying property that devicetree and kernel 
reside here).

If I create a WIC image, the boot partition is in there with the proper 
files (from IMAGE_BOOT_FILES) so I would really like to re-use that 
code. I could create the wic image and then cut out the part I want, but 
that doesn't seem particularly nice.

What I want to do at update time is to write the new boot partition to 
another location on disk, and then adjust the partition table to make 
the first partition entry point to the new copy. That way, in case of 
unexpected failure (power loss for example), the device remains bootable.

Mike Looijmans

Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert

TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands

T: +31 (0) 499 33 69 69

Please consider the environment before printing this e-mail

       reply	other threads:[~2021-03-15 13:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
2021-03-15 13:13   ` Mike Looijmans [this message]
2021-03-15 13:47     ` [OE-core] Build the "boot" partition image (just like the rootfs) Stefano Babic
2021-03-15 14:46       ` Mike Looijmans
2021-03-15 14:58         ` Stefano Babic
2021-03-15 15:17           ` Mike Looijmans
     [not found]           ` <>
2021-03-18 13:48             ` Mike Looijmans

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.