From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: DTC 1.6.1 released
Date: Tue, 8 Jun 2021 20:38:48 +1000 [thread overview]
Message-ID: <YL9IuEauvI81YQOY@yekko> (raw)
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
Hi folks,
It's been a while, and someone asked for it, so I've wrapped up
another numbered release, v1.6.1/
Changes since v1.6.0 include:
* A number of bugfixes
* Fix many warnings with -Wsign-compare
* Add compilation with meson (not used by default so far)
* Yet another revamp of how we handle unaligned accesses
* Added a number of extra checks for common tree errors
* Checks for interrupt providers
* i2c reg properties
* Tighten checking of gpio properties
* Reduce dependencies when building libfdt only
* Allow libfdt.h header to be used from C++ more easily
* Accept .dtbo extension for overlays
* Update valid node and property characters to match current devicetree spec
* Add several checks for root node sanity in fdt_check_full()
* Somewhat more robust type labelling for the benefit of yaml output
You can get it from the v1.6.1 tag in the git tree at
git://git.kernel.org/pub/scm/utils/dtc/dtc.git
Or, you can get tarballs at
https://mirrors.edge.kernel.org/pub/software/utils/dtc/
--
David Gibson | 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:[~2021-06-08 10:38 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=YL9IuEauvI81YQOY@yekko \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).