similarity index 51%
rename from meta/recipes-kernel/dtc/dtc_1.7.2.bb
rename to meta/recipes-kernel/dtc/dtc_1.8.1.bb
@@ -1,3 +1,25 @@
+# FIXME: the LIC_FILES_CHKSUM values have been updated by 'devtool upgrade'.
+# The following is the difference between the old and the new license text.
+# Please update the LICENSE value if needed, and summarize the changes in
+# the commit message via 'License-Update:' tag.
+# (example: 'License-Update: copyright years updated.')
+#
+# The changes:
+#
+# --- README.license
+# +++ README.license
+# @@ -28,7 +28,7 @@
+# makes that it easier for vendors or authors of such software to do so.
+#
+# This does mean that libfdt code could be "stolen" - say, included in a
+# -proprietary fimware and extended without contributing those extensions
+# +proprietary firmware and extended without contributing those extensions
+# back to the libfdt mainline. While I hope that doesn't happen, I
+# believe the goal of allowing libfdt to be widely used is more
+# important than avoiding that. libfdt is quite small, and hardly
+#
+#
+
SUMMARY = "Device Tree Compiler"
HOMEPAGE = "https://devicetree.org/"
DESCRIPTION = "The Device Tree Compiler is a toolchain for working with device tree source and binary files."
@@ -6,13 +28,14 @@ LICENSE = "GPL-2.0-only | BSD-2-Clause"
LIC_FILES_CHKSUM = "file://GPL;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
file://BSD-2-Clause;md5=5d6306d1b08f8df623178dfd81880927 \
- file://README.license;md5=a1eb22e37f09df5b5511b8a278992d0e"
+ file://README.license;md5=a5696bd07fcc7285cbbacc42c2132248 \
+ "
SRC_URI = " \
git://git.kernel.org/pub/scm/utils/dtc/dtc.git;branch=main;protocol=https \
file://0001-Fix-discarded-const-qualifiers.patch \
"
-SRCREV = "2d10aa2afe35527728db30b35ec491ecb6959e5c"
+SRCREV = "8f48565e5cfedc74d3f7512f1e0188e9d85dc1de"
UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>\d+(\.\d+)+)"
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *dtc* to *1.8.1* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-dtc-upgrade-1.7.2-1.8.1.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper -- >8 -- From c5c15206741ff3ec53d5fa54fab06949b68b6cf2 Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Mon, 1 Jun 2026 12:21:23 +0000 Subject: [PATCH] dtc: upgrade 1.7.2 -> 1.8.1 --- .../dtc/{dtc_1.7.2.bb => dtc_1.8.1.bb} | 27 +++++++++++++++++-- 1 file changed, 25 insertions(+), 2 deletions(-) rename meta/recipes-kernel/dtc/{dtc_1.7.2.bb => dtc_1.8.1.bb} (51%)