From: Alexander Dahl via ptxdist <ptxdist@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Alexander Dahl <ada@thorsis.com>
Subject: [ptxdist] [RFC PATCH 0/7] libubootenv/swupdate: Introduce new packages
Date: Fri, 21 Mar 2025 09:52:39 +0100 [thread overview]
Message-ID: <mailman.2955.1742547175.466.ptxdist@pengutronix.de> (raw)
[-- Attachment #0: Type: message/rfc822, Size: 3323 bytes --]
From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Subject: [RFC PATCH 0/7] libubootenv/swupdate: Introduce new packages
Date: Fri, 21 Mar 2025 09:52:39 +0100
Message-ID: <20250321085246.21344-1-ada@thorsis.com>
Hei hei,
this week I played around with swupdate to see if it can fit the needs
for one of our projects. Turns out it does not at the moment, but I
prepared these two packages. We won't use swupdate anytime soon, so I
post this as RFC, because I can not maintain these packages. Anyone who
is interested, feel free to pick it up.
Maybe at least libubootenv can be helpful for users building a single
BSP for different boards with different U-Boot environments, though.
Greets
Alex
Link: https://swupdate.org/
Alexander Dahl (7):
libubootenv: Introduce new package
libubootenv: Add option for installing tools
swupdate: Introduce new package
swupdate: Remove targetinstall of example tools
swupdate: Add option to build with OpenSSL support
swupdate: Fix passing libubootenv dependency
swupdate: Add optional zlib support
rules/libubootenv.in | 29 +++++++++
rules/libubootenv.make | 65 +++++++++++++++++++
rules/swupdate.in | 36 +++++++++++
rules/swupdate.make | 141 +++++++++++++++++++++++++++++++++++++++++
4 files changed, 271 insertions(+)
create mode 100644 rules/libubootenv.in
create mode 100644 rules/libubootenv.make
create mode 100644 rules/swupdate.in
create mode 100644 rules/swupdate.make
base-commit: 35e444db1da5f4b01df92feade288b5d71bb65af
--
2.39.5
reply other threads:[~2025-03-21 8:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=mailman.2955.1742547175.466.ptxdist@pengutronix.de \
--to=ptxdist@pengutronix.de \
--cc=ada@thorsis.com \
/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