From: Charles Steinkuehler <charles@steinkuehler.net>
To: "Jan Lübbe" <jlu@pengutronix.de>, rauc@pengutronix.de
Subject: Re: [RAUC] Buildroot + RAUC Example
Date: Tue, 25 Jan 2022 06:28:06 -0600 [thread overview]
Message-ID: <08166093-74bd-ba17-38dd-4c773be898f9@steinkuehler.net> (raw)
In-Reply-To: <9f65fcded8b2aca28e78dc57dc9af4ee120dd1de.camel@pengutronix.de>
On 1/25/2022 3:25 AM, Jan Lübbe wrote:
> Hi Charles,
>
> On Sat, 2022-01-22 at 07:23 -0600, Charles Steinkuehler wrote:
>>
>> 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.
That is the intent, but it's probably not _quite_ ready to be linked as
more than an example. I'm still working through testing corner cases
and trying to get the hardware watchdog timer running.
The project is a Buildroot external tree, so it can be used easily with
any recent version of Buildroot. As RAUC is included with Buildroot, it
will be updated along with the rest of the system when migrating to a
newer version (eg: the upcoming stable release in Feb.).
Currently the only thing pinned down to a specific version is the Linux
kernel, which is built from a git hash copied from the Buildroot RPi
default configs which won't automatically get updated. I'm looking at a
way to use a config fragment along with the Buildroot default configs so
it's easier to update but haven't sorted out the details.
--
Charles Steinkuehler
charles@steinkuehler.net
_______________________________________________
RAUC mailing list
prev parent reply other threads:[~2022-01-25 12:28 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
2022-01-25 12:28 ` Charles Steinkuehler [this message]
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=08166093-74bd-ba17-38dd-4c773be898f9@steinkuehler.net \
--to=charles@steinkuehler.net \
--cc=jlu@pengutronix.de \
--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