From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/5] scripts/dtc: Update to upstream version v1.4.3
Date: Tue, 3 Oct 2017 14:28:28 -0400 [thread overview]
Message-ID: <20171003182828.GC22973@bill-the-cat> (raw)
In-Reply-To: <CAL_JsqJtFxP6juWodKQvSZEEA772N6Ak+vhbPraBk_9+ybJh3w@mail.gmail.com>
On Tue, Oct 03, 2017 at 01:24:13PM -0500, Rob Herring wrote:
> On Sun, Sep 24, 2017 at 9:26 AM, Tom Rini <trini@konsulko.com> wrote:
> > Using the update-dtc-source.sh script from Linux v4.14-rc1 import the
> > portions of dtc that we require. We bring in update-dtc-source.sh and
> > scripts/dtc/Makefile from Linux v4.14-rc1. Rework DTC_FLAGS handling to
> > not require a test.
>
> You are missing fdt_addresses.c and fdt_overlay.c (which I thought
> u-boot was dependent on) as the script doesn't automatically add new
> files. I'm about to send out a script fix.
We only need 'dtc', and those aren't listed in DTC_OBJS in Makefile.dtc.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171003/a43cff59/attachment.sig>
next prev parent reply other threads:[~2017-10-03 18:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 14:26 [U-Boot] [PATCH 0/5] Follow the Linux Kernel in building dtc as needed Tom Rini
2017-09-24 14:26 ` [U-Boot] [PATCH 1/5] scripts/dtc: Update to upstream version v1.4.3 Tom Rini
2017-10-03 18:24 ` Rob Herring
2017-10-03 18:28 ` Tom Rini [this message]
2017-10-03 18:30 ` Rob Herring
2017-10-03 18:44 ` Tom Rini
2017-09-24 14:26 ` [U-Boot] [PATCH 2/5] scripts/dtc: Update to upstream version v1.4.4 Tom Rini
2017-09-24 14:27 ` [U-Boot] [PATCH 3/5] scripts/dtc: Update to upstream version v1.4.4-50-gfe50bd1ecc1d Tom Rini
2017-09-24 14:27 ` [U-Boot] [PATCH 4/5] dtc: Switch to building and using our own dtc unless provided Tom Rini
2017-09-24 14:27 ` [U-Boot] [PATCH 5/5] tools/mkimage: Make the path to the dtc binary that mkimage calls configurable Tom Rini
2017-09-24 16:50 ` [U-Boot] [PATCH 0/5] Follow the Linux Kernel in building dtc as needed Marek Vasut
2017-09-24 17:28 ` Tom Rini
2017-09-24 20:39 ` Łukasz Majewski
2017-09-24 22:00 ` Tom Rini
2017-09-25 8:32 ` Marek Vasut
2017-09-25 8:28 ` Wolfgang Denk
2017-09-27 14:15 ` [U-Boot] [PATCH 0/5] REVERT " Wolfgang Denk
2017-09-27 14:15 ` [U-Boot] [PATCH 1/5] Revert "tools/mkimage: Make the path to the dtc binary that mkimage calls configurable" Wolfgang Denk
2017-09-27 14:15 ` [U-Boot] [PATCH 2/5] Revert "dtc: Switch to building and using our own dtc unless provided" Wolfgang Denk
2017-09-27 14:15 ` [U-Boot] [PATCH 3/5] Revert "scripts/dtc: Update to upstream version v1.4.4-50-gfe50bd1ecc1d" Wolfgang Denk
2017-09-27 14:15 ` [U-Boot] [PATCH 4/5] Revert "scripts/dtc: Update to upstream version v1.4.4" Wolfgang Denk
2017-09-27 14:15 ` [U-Boot] [PATCH 5/5] Revert "scripts/dtc: Update to upstream version v1.4.3" Wolfgang Denk
2017-09-27 14:31 ` [U-Boot] [PATCH 0/5] REVERT Follow the Linux Kernel in building dtc as needed Tom Rini
2017-09-27 14:56 ` Wolfgang Denk
2017-09-27 15:23 ` 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=20171003182828.GC22973@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