Tags: YuKnight/dtc
Tags
DTC 1.6.0 Changes since v1.5.1. include: * Some provision for out of tree builds (useful with meson) * Some fixes for win32 builds * Some improvements for FreeBSD builds: * Work with byacc as well as bison * Fix some compilation failures with clang * Default to cc instead of gcc * Add FreeBSD testing via Cirrus CI * Add non-x86 testing on Travis * Add options to allow builds of libfdt which sacrifice safety on bad inputs for reduced size and improved speed. This is important for some embedded cases. * Allow testsuite to be executed on an already-installed dtc/libfdt, rather than just the one built in the source tree
DTC 1.5.1 Changes since v1.5.0 include: * Numerous assorted bugfixes * Add a new fdt_create_with_flags() function, and a FDT_CREATE_FLAG_NO_NAME_DEDUP flag which improves speed at the cost of tree size by not deduplicating property names in the strings section * Run tests against shared library, so it will catch the common mistake of not adding new symbols to the versioning script * Add a number of missing symbols to versioning script * Use Python3 by default for pylibfdt * New fdt_append_addrrange() function in libfdt
DTC 1.5.0 Changes since v1.4.7 include: * Support for Python3 in the pylibfdt bindings * A number of extensions to the pylibfdt bindings * Build properly without valgrind available * Support for YAML encoded output (for use with validation tools) * Annotated dts output mode * Faster handling of unaligned memory acceses for libfdt on ARM as well as numerous assorted bugfixes.
DTC 1.4.4 It turns out that dtc 1.4.3 - and most previous versions - have a serious build bug on a number of distros: libfdt.h incorrectly defines some system reserved __* macros for use with sparse. These conflict with some system headers on RHEL7 and probably several other Linux distributions. This quick fix release includes patches to correct those build failures. It also has a tiny handful of other cleanups.
PreviousNext