From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [ANN] U-Boot v2020.01 released
Date: Tue, 7 Jan 2020 08:28:04 -0500 [thread overview]
Message-ID: <20200107132804.GP4866@bill-the-cat> (raw)
In-Reply-To: <fbf43c03-83a2-7441-8812-c5e81f2245b7@microchip.com>
On Tue, Jan 07, 2020 at 07:28:35AM +0000, Eugen.Hristev at microchip.com wrote:
>
>
> 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.
I believe that needing to fix all of the device trees was what put my
last effort to re-sync with upstream dtc on hold. That I think in turn
was blocked by wanting to re-sync dts files with upstream Linux and that
in turn for TI am335x at least got stuck on changes to the cpsw driver
and associated bindings. That last problem I think is either unblocked
now, or can be once I go through my queue of TI related patches to
apply.
On a related note, I also want to start a slow re-sync of the Kbuild
files as they've gone a while without a re-sync and I think just doing
a big jump looked hard, but a release or two at a time didn't seem too
bad.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200107/85d8cb4e/attachment.sig>
next prev parent reply other threads:[~2020-01-07 13:28 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 [this message]
2020-01-07 7:29 ` Eugen.Hristev at microchip.com
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=20200107132804.GP4866@bill-the-cat \
--to=trini@konsulko.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