public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Makefile: Update minimum dtc version to 1.4.3
Date: Sat, 23 Sep 2017 19:33:44 +0200	[thread overview]
Message-ID: <c5caae77-3188-e59b-bdc1-cb115216c999@gmail.com> (raw)
In-Reply-To: <20170923170500.GA30205@bill-the-cat>

On 09/23/2017 07:05 PM, Tom Rini wrote:
> On Sat, Sep 23, 2017 at 08:56:08AM -0400, Tom Rini wrote:
>> On Sat, Sep 23, 2017 at 12:39:44PM +0200, Marek Vasut wrote:
>>> On 09/22/2017 04:20 PM, Tom Rini wrote:
>>>> On Fri, Sep 15, 2017 at 01:15:25PM -0400, Tom Rini wrote:
>>>>
>>>>> With support for overlays and calling the -@ flag to dtc we need to have
>>>>> at least 1.4.3 available now.
>>>>>
>>>>> Cc: Simon Glass <sjg@chromium.org>
>>>>> Reported-by: Stephen Warren <swarren@wwwdotorg.org>
>>>>> Signed-off-by: Tom Rini <trini@konsulko.com>
>>>>
>>>> Applied to u-boot/master, thanks!
>>>
>>> Debian still only has 1.4.2 even in unstable, so u-boot/master no longer
>>> builds on any debian system.
>>
>> Then perhaps we need to mirror the kernel and provide / build dtc, but
>> allow for people to override it.
> 
> This isn't too hard and I'm pushing that through Jenkins now to confirm
> I've got all the logic correct.  I think this will be the least error
> prone method long term.
> 
NAK, this is the same thing which chromium does and what Debian is
trying to stop -- vendoring. We will end up with patched custom DTC out
of sync with upstream.

-- 
Best regards,
Marek Vasut

  reply	other threads:[~2017-09-23 17:33 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
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 [this message]
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=c5caae77-3188-e59b-bdc1-cb115216c999@gmail.com \
    --to=marek.vasut@gmail.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