From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Makefile: Update minimum dtc version to 1.4.3
Date: Fri, 15 Sep 2017 13:41:23 -0400 [thread overview]
Message-ID: <20170915174123.GJ4560@bill-the-cat> (raw)
In-Reply-To: <ead3ba38-bafc-10d7-ef9a-609eb9ee1165@wwwdotorg.org>
On Fri, Sep 15, 2017 at 11:33:23AM -0600, Stephen Warren wrote:
> On 09/15/2017 11:15 AM, Tom Rini wrote:
> >With support for overlays and calling the -@ flag to dtc we need to have
> >at least 1.4.3 available now.
>
> >diff --git a/Makefile b/Makefile
>
> > checkdtc:
> >- @if test $(call dtc-version) -lt 0104; then \
> >- echo '*** Your dtc is too old, please upgrade to dtc 1.4 or newer'; \
> >+ @if test $(call dtc-version) -lt 010403; then \
> >+ echo '*** Your dtc is too old, please upgrade to dtc 1.4.3 or newer'; \
> > false; \
> > fi
>
> Can we add a comment here indicating that .travis.yml must be
> updated too if the version requirement changes, and similarly a
> comment in .travis.yml that mentions it must be kept in sync with
> the checkdtc rule in Makefile?
I'm planning to follow up https://patchwork.ozlabs.org/patch/813888/
with one to do -b v1.4.3 so we'll be testing the minimum requirement in
the future.
> For users, it's a bit annoying that we need a newer dtc that is
> present in distros, without any deprecation warning from the
> Makefile for a couple releases before:-(
Well, the other ways to do this are "mirror" the kernel and include a
copy of dtc, or have different version checks for if UT_OVERLAY is
enabled or not.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170915/ca0d9f9d/attachment.sig>
next prev parent reply other threads:[~2017-09-15 17:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 17:15 [U-Boot] [PATCH] Makefile: Update minimum dtc version to 1.4.3 Tom Rini
2017-09-15 17:33 ` Stephen Warren
2017-09-15 17:41 ` Tom Rini [this message]
2017-09-22 14:20 ` [U-Boot] " Tom Rini
2017-09-23 10:39 ` Marek Vasut
2017-09-23 12:56 ` Tom Rini
2017-09-23 13:04 ` Marek Vasut
2017-09-23 16:10 ` Tom Rini
2017-09-23 17:36 ` Marek Vasut
2017-09-24 1:49 ` Bin Meng
2017-09-24 2:07 ` Robert Nelson
2017-09-24 3:22 ` Tom Rini
2017-09-24 8:28 ` Marek Vasut
2017-09-24 11:36 ` Tom Rini
2017-09-24 12:07 ` Marek Vasut
2017-09-24 12:26 ` Łukasz Majewski
2017-09-24 12:52 ` Tom Rini
2017-09-24 13:05 ` Marek Vasut
2017-09-25 2:14 ` Simon Glass
2017-09-25 8:34 ` Marek Vasut
2017-09-23 17:05 ` Tom Rini
2017-09-23 17:33 ` Marek Vasut
2017-09-23 17:37 ` Tom Rini
2017-09-23 17:43 ` Marek Vasut
2017-09-23 17:53 ` Tom Rini
2017-09-24 6:41 ` Heinrich Schuchardt
2017-09-24 11:20 ` Łukasz Majewski
2017-09-24 12:50 ` Tom Rini
2017-09-24 19:08 ` Vagrant Cascadian
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=20170915174123.GJ4560@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