public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Eugen.Hristev at microchip.com <Eugen.Hristev@microchip.com>
To: u-boot@lists.denx.de
Subject: [ANN] U-Boot v2020.01 released
Date: Tue, 7 Jan 2020 07:29:31 +0000	[thread overview]
Message-ID: <d0100916-53d6-126a-3e7d-e46a8ae6a7dd@microchip.com> (raw)
In-Reply-To: <20200106205843.GK4866@bill-the-cat>



On 06.01.2020 22:58, Tom Rini wrote:

 > The next thing I'd like to point out is that as part of this release
 > we've re-synced with upstream for libfdt

Hello Tom,

Regarding the DTC parser (/scripts/dtc/version_gen.h)

#define DTC_VERSION "DTC 1.4.6-gaadd0b65"

Is this compatible with the new libfdt that we have , and, are there any 
plans to update this to a newer version? (aadd0b65 is about 2 years old 
-2018/02)

I tried to try out with a new DTC version but most devicetrees have new 
warnings popping out blocking travis/CI etc.

Thanks !
Eugen

  parent reply	other threads:[~2020-01-07  7:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06 20:58 [ANN] U-Boot v2020.01 released Tom Rini
2020-01-07  7:28 ` Eugen.Hristev at microchip.com
2020-01-07 13:28   ` Tom Rini
2020-01-07  7:29 ` Eugen.Hristev at microchip.com [this message]
2020-01-07 13:20 ` Tom Rini

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=d0100916-53d6-126a-3e7d-e46a8ae6a7dd@microchip.com \
    --to=eugen.hristev@microchip.com \
    --cc=u-boot@lists.denx.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