mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: [ptxdist] [PATCH 2/2] dt-utils: version bump 2019.01.0 -> 2021.03.0
Date: Fri, 26 Mar 2021 22:29:09 +0100	[thread overview]
Message-ID: <20210326212909.3472-2-rhi@pengutronix.de> (raw)
In-Reply-To: <20210326212909.3472-1-rhi@pengutronix.de>

Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
 rules/dt-utils.in   | 20 ++++++++++++++++++--
 rules/dt-utils.make |  8 ++++++--
 2 files changed, 24 insertions(+), 4 deletions(-)

diff --git a/rules/dt-utils.in b/rules/dt-utils.in
index 7ce0e579c98c..2ac7383f2ab8 100644
--- a/rules/dt-utils.in
+++ b/rules/dt-utils.in
@@ -1,11 +1,27 @@
 ## SECTION=shell_and_console
 
-config DT_UTILS
+menuconfig DT_UTILS
 	tristate
-	prompt "dt-utils"
+	prompt "dt-utils                      "
 	select UDEV
 	help
 	  Utilities to work with device trees in Linux userspace:
 
 	  * barebox-state: access barebox' state storage
 	  * fdtdump: dump a device tree binary to stdout
+
+if DT_UTILS
+
+config DT_UTILS_STATE_COMPAT
+	bool "ensure state compatibility with older bareboxes"
+	help
+	  Previous variants of the state variable set did not contain metadata.
+	  The read function in the 'direct' storage backend honors this, but the
+	  write function doesn't, which makes an update of the state variable
+	  set impossible in this case.
+	  When enabling this option, barebox-state will keep the storage in a
+	  format that can be read by barebox <= v2016.08.0 when writing
+	  variables into a 'direct' storage backend, or fail if this requirement
+	  cannot be guaranteed.
+
+endif
diff --git a/rules/dt-utils.make b/rules/dt-utils.make
index ce86738bf614..0c2fe87cddb7 100644
--- a/rules/dt-utils.make
+++ b/rules/dt-utils.make
@@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_DT_UTILS) += dt-utils
 #
 # Paths and names
 #
-DT_UTILS_VERSION	:= 2019.01.0
-DT_UTILS_MD5		:= d83ebf99b07fa4516aeaa329afb2a6eb
+DT_UTILS_VERSION	:= 2021.03.0
+DT_UTILS_MD5		:= acf0b5e3b18e40e6172b67fbad2e52fb
 DT_UTILS		:= dt-utils-$(DT_UTILS_VERSION)
 DT_UTILS_SUFFIX		:= tar.xz
 DT_UTILS_URL		:= https://public.pengutronix.de/software/dt-utils/$(DT_UTILS).$(DT_UTILS_SUFFIX)
@@ -31,6 +31,10 @@ DT_UTILS_LICENSE_FILES	:= \
 # ----------------------------------------------------------------------------
 
 DT_UTILS_CONF_TOOL := autoconf
+DT_UTILS_CONF_OPT  := \
+	$(CROSS_AUTOCONF_USR) \
+	$(GLOBAL_LARGE_FILE_OPTION) \
+	--$(call ptx/endis, PTXCONF_DT_UTILS_STATE_COMPAT)-state-backward-compatibility
 
 # ----------------------------------------------------------------------------
 # Target-Install
-- 
2.29.2


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

  reply	other threads:[~2021-03-26 21:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26 21:29 [ptxdist] [PATCH 1/2] dt-utils: add license files Roland Hieber
2021-03-26 21:29 ` Roland Hieber [this message]
2021-03-30 18:07   ` [ptxdist] [APPLIED] dt-utils: version bump 2019.01.0 -> 2021.03.0 Michael Olbrich
2021-03-30 18:07 ` [ptxdist] [APPLIED] dt-utils: add license files Michael Olbrich

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=20210326212909.3472-2-rhi@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=ptxdist@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