From: "Jan Lübbe" <jlu@pengutronix.de>
To: Charles Steinkuehler <charles@steinkuehler.net>, rauc@pengutronix.de
Subject: Re: [RAUC] Buildroot + RAUC Example
Date: Tue, 25 Jan 2022 10:25:01 +0100 [thread overview]
Message-ID: <9f65fcded8b2aca28e78dc57dc9af4ee120dd1de.camel@pengutronix.de> (raw)
In-Reply-To: <07625be0-2b0f-8cd6-17a3-a24d4efad897@steinkuehler.net>
Hi Charles,
On Sat, 2022-01-22 at 07:23 -0600, Charles Steinkuehler wrote:
> I have created a "works out of the box" example integrating RAUC with
> Buildroot to create a baseline system targeting the RPi 4 / cm4io that
> supports:
>
> * U-Boot bootloader with redundant environment storage
> * Symmetric Root-FS Slots with fallback on failed updates
> * Atomic updates of bootloader vfat (no fallback)
> * Single persistent data partition
>
> I'm working on support for hardware watchdog timeouts.
>
> The project files and instructions are on github:
> https://github.com/cdsteinkuehler/br2rauc
Nice!
> Hopefully this can be of use to others in the community.
>
> Also, as I am new to both RAUC and Buildroot, I would appreciate any
> review and suggestions for improvement or changes.
Neither Enrico or myself are familiar with Buildroot, perhaps you'd find someone
in #rauc on libera.chat (or #rauc:matrix.org) for feedback.
Will you keep maintaining this example over time (i.e. with new buildroot/rauc
releases)? If so, perhaps we could link if from the readme and integration
chapters.
Regards,
Jan
> Thanks for the great project!
--
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 |
_______________________________________________
RAUC mailing list
next prev parent reply other threads:[~2022-01-25 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 13:23 Charles Steinkuehler
2022-01-25 9:25 ` Jan Lübbe [this message]
2022-01-25 12:28 ` Charles Steinkuehler
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=9f65fcded8b2aca28e78dc57dc9af4ee120dd1de.camel@pengutronix.de \
--to=jlu@pengutronix.de \
--cc=charles@steinkuehler.net \
--cc=rauc@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