mailarchive of the pengutronix oss-tools mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <r.hieber@pengutronix.de>
To: oss-tools@pengutronix.de
Cc: entwicklung@pengutronix.de
Subject: [OSS-Tools] [dt-utils] Release 2019.01.0
Date: Mon, 28 Jan 2019 14:04:14 +0100	[thread overview]
Message-ID: <20190128130414.gtzgarx7rzf6n66k@pengutronix.de> (raw)

Hi,

I've just released version 2019.01.0 of dt-utils [1]. Highlight of this
release is the harmonization of the barebox-state implementation with
upstream barebox, thanks to Ulrich Ölmann for working on this!

[1]: https://public.pengutronix.de/software/dt-utils/dt-utils-2019.01.0.tar.xz
     https://public.pengutronix.de/software/dt-utils/dt-utils-2019.01.0.tar.xz.md5
     https://public.pengutronix.de/software/dt-utils/dt-utils-2019.01.0.tar.xz.sha1
     https://public.pengutronix.de/software/dt-utils/dt-utils-2019.01.0.tar.xz.sha256

This release includes contributions from Andrey Smirnov, Antony Pavlov,
Daniel Schultz, Enrico Jorns, Ian Abbott, Juergen Borleis, Ladislav
Michl, Lucas Stach, Michael Olbrich, Philipp Zabel, Roland Hieber, Sam
Ravnborg, Sascha Hauer, Ulrich Ölmann, and Uwe Kleine-König. Thanks to
all contributors!

Changes:
* libdt: fix leaks of memory returned by read_file() calls
* libdt: xzalloc: die on failure, like the similar-named kernel function
* libdt: add of_property_write_string() as a convenience function to set
  a property to a string
* libdt: add dev_set_name() as a convenience function to set a device's
  name
* state: harmonize our implementation with upstream barebox:
  - Fixes:
    . backend_bucket_circular: fix the case when write size is not a
      power of 2
    . backend_bucket_circular: fix length check when reading old state
      format
    . backend_bucket_circular: fix two memory leaks
    . backend_storage: don't refresh the storage needlessly
    . fix error return value when state_new_from_node() cannot resolve a
      phandle
    . fix use-after-free in state_backend_format_dtb_pack()
    . make finding the backend node more robust by using its
      reproducible name
    . remove checks for xzalloc() returning NULL, which cannot happen
    . do not complain about missing backend-storage-type, which is
      irrelevant for mtd devices
  - Potentially breaking changes:
    . make pointing to the backend using a phandle the only supported
      method
    . state nodes without an alias in the /aliases/ node now lead to an
      error. barebox already creates a missing alias in the fixupped
      device tree automatically since v2017.06.0.
    . refuse to set the read-only 'dirty' state variable
    . remove unused arguments from state_new_from_node()
  - New features:
    . add new 'init_from_defaults' state variable to allow detection
      whether a state has been initialized from default values, i.e.
      state_load() failed.
    . add an internal variable to protect existing data in a state
      bucket and make updates of the
      state implementation more robust
    . add new function state_read_mac() to read a MAC address from state
    . notify when the old state format is detected (this was previously
      a debugging message)
    . provide an error message when an error occurs in
      state_convert_node_variable()
    . add more debugging messages
  - port several changes to barebox's fixup functions, but since device
    trees are already fixupped at boot time, this code is never used by
    dt-utils
  - some further minor refactoring as well fixing some typos and
    documentation comments

-- 
Roland Hieber                     | r.hieber@pengutronix.de     |
Pengutronix e.K.                  | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917-5555 |

_______________________________________________
OSS-Tools mailing list
OSS-Tools@pengutronix.de

                 reply	other threads:[~2019-01-28 13:04 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=20190128130414.gtzgarx7rzf6n66k@pengutronix.de \
    --to=r.hieber@pengutronix.de \
    --cc=entwicklung@pengutronix.de \
    --cc=oss-tools@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