Devicetree
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: devicetree-compiler@vger.kernel.org
Cc: devicetree@vger.kernel.org
Subject: Re: DTC 1.8.0 released
Date: Tue, 26 May 2026 19:16:29 +1000	[thread overview]
Message-ID: <ahVk7cy6XnpF3xaZ@zatzit> (raw)
In-Reply-To: <ahVka0oWJ3RApioU@zatzit>

[-- Attachment #1: Type: text/plain, Size: 2800 bytes --]

On Tue, May 26, 2026 at 07:14:19PM +1000, David Gibson wrote:
> DTC 1.8.0
> 
> Changes since v1.7.2 include:
>  * dtc
>    - Add informative error for stray identifiers (e.g. unexpanded macros)
>    - Better decompiling of plugins
>      - Restore labels from __symbols__ node when possible
>      - Restore phandle references from __local_fixups__ and __fixups__
>        when possible
>      - Improve type guessing when compiling to dts format
>    - Add only new data to fixup nodes instead of complete regeneration
> 
>  * libfdt
>    - Add fdt_setprop_namelen() and fdt_setprop_namelen_string()
>    - Add fdt_get_property_namelen_w()
>    - Add fdt_find_string_len_()
>    - Introduce fdt_downgrade_version()
>    - Verify alignment of sub-blocks in dtb
>    - Handle FDT_NOP tags before FDT_END in fdt_check_full()
>    - Document most remaining functions in libfdt.h
>    - Standardise "returns:" annotation in documentation
> 
>  * checks
>    - Warn about missing #address-cells for interrupt parents
>    - Relax avoid_unnecessary_addr_size to allow child ranges properties
>    - Fix detection of 'i2c-bus' child node
>    - Remove check for graph child addresses (redundant with schema validation)
>    - Do not check overlays for alias paths
> 
>  * fdtdump
>    - Remove overly strict dtb version check
> 
>  * pylibfdt
>    - Fix backwards compatibility of return values with SWIG v4.3
>    - Port python bindings to build natively via meson and meson-python
> 
>  * Build
>    - Deprecate Makefile in favor of Meson
>    - Support building libfdt without static library
>    - Don't build test programs by default
>    - Fix -Dtools=false build
>    - Add FreeBSD and non-GNU linker compatibility
> 
>  * CI
>    - Add macOS build to GitHub Actions
>    - Add Cirrus CI for FreeBSD testing
>    - Add GitLab CI for Linux builds
>    - Update GitHub Actions ubuntu runner to 24.04
>    - Skip swig install for mingw32 Windows build
> 
>  * Tests
>    - Add compatibility with uutils (Rust coreutils)
>    - Mark .so from asm output as non-executable stack (glibc-2.41 compat)
> 
>  * General
>    - Consider drive letters when checking absolute paths on Windows
>    - Add AI contribution guidelines
>    - Assorted bugfixes and cleanups
>    - Add clang-format config
>    - Add SBOM file in CycloneDX format
> 
> -- 
> David Gibson (he or they)	| I'll have my music baroque, and my code
> david AT gibson.dropbear.id.au	| minimalist, thank you, not the other way
> 				| around.
> http://www.ozlabs.org/~dgibson



-- 
David Gibson (he or they)	| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you, not the other way
				| around.
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2026-05-26  9:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26  9:14 DTC 1.8.0 released David Gibson
2026-05-26  9:16 ` David Gibson [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=ahVk7cy6XnpF3xaZ@zatzit \
    --to=david@gibson.dropbear.id.au \
    --cc=devicetree-compiler@vger.kernel.org \
    --cc=devicetree@vger.kernel.org \
    /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