From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 REPOST 1/9] Validate dtc is new enough
Date: Sat, 3 Aug 2013 11:31:24 -0400 [thread overview]
Message-ID: <51FD224C.2060207@ti.com> (raw)
In-Reply-To: <20130803161109.2c1387a4@lilith>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/03/2013 10:11 AM, Albert ARIBAUD wrote:
> Hi Tom,
>
> On Fri, 2 Aug 2013 20:32:03 -0400, Tom Rini <trini@ti.com> wrote:
>
>> On Fri, Aug 02, 2013 at 04:23:37PM -0600, Stephen Warren wrote:
>>> On 07/24/2013 11:09 AM, Stephen Warren wrote:
>>>> From: Stephen Warren <swarren@nvidia.com>
>>>>
>>>> Subsequent patches assume that dtc supports various recent
>>>> features. These are available in dtc 1.4.0. Validate that
>>>> dtc is at least that version.
>>>
>>> Tom, do these patches look good?
>>
>> So, Albert, Tom W, are we OK with some machines (say the 'tegra'
>> SoCs for example) not building on some distros, until / unless
>> the developer updates their dtc package?
>
> I am fine with this as long as this is documented.
Yes, the error produced is clear: "Your dtc is too old, please upgrade
to dtc 1.4 or newer".
I shall push this shortly, thanks!
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJR/SJLAAoJENk4IS6UOR1WOvcP/31CCKPWepv6yxGWjWm3UO1/
ZC/0EB1y+3UkL+1pFYe2LuTDob3TjJQxKohlG3WWKH4NJ7Vcp29g364WJPkZYT+8
Lg438WS/kkgowpXkIreHNerLE0HKp19CsoBkS78Zci1rUSeUGuVSBg7SKCvrvLK8
3RBgTN5nx5/cTEU9D9DQINSb8P1bhSidoqov8npHULObVK6fo96wRqX5cW9401vU
EhwjeAsjcdcbj4Nrgp3jAalZWu+EfwZeykfixbBUyP5pTKjDs4kLIzDpNbpFefDg
xYWNNVPQ9DNJXK5kVojgwAyJuCzg77PNQfvREnUSvrAbKUJRY0SXiGYgQl8dpgdw
lphSiU7R2yp4o3MVMU+T7uZKMlpz8rz/wqFIJxgoXL2vVvHvzDolnx0ymON6NPZ/
NL7evKtD4GADm5mUZc4JvRoOCZwOZRjC8dvDD0SoanzhSOk5rwBN8XdyC8yropu4
7hND7xdRc0i1ivRlqWZY8Mnj4URdhDeXufZp1DwIpNkyctSyTLUohJ8M/q4DBMyl
2FwlL3hauHPWJTL9Hs6tDxCSYgGCB2dQzpi9jzoISEqkVkq7ZDcDIbRN8itKwVrD
jacFIHAiqTUaOSfsb2kVGrNXRqKlyZelxu7hFi1J17Lhq1Hxl7b3ZQX0DBps/kmg
z4pdAcisRZqLlK3HGJ1h
=/6Du
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-08-03 15:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 17:09 [U-Boot] [PATCH V2 REPOST 0/9] rely on latest dtc, simplify Stephen Warren
2013-07-24 17:09 ` [U-Boot] [PATCH V2 REPOST 1/9] Validate dtc is new enough Stephen Warren
2013-08-02 22:23 ` Stephen Warren
2013-08-03 0:32 ` Tom Rini
2013-08-03 14:11 ` Albert ARIBAUD
2013-08-03 15:31 ` Tom Rini [this message]
2013-07-24 17:09 ` [U-Boot] [PATCH V2 REPOST 2/9] xilinx: move microblaze-generic .dts to standard location Stephen Warren
2013-07-24 17:09 ` [U-Boot] [PATCH V2 REPOST 3/9] dts/Makefile: simplify dtc invocation Stephen Warren
2013-07-24 17:09 ` [U-Boot] [PATCH V2 REPOST 4/9] dts/Makefile: unify cpp/dtc include paths Stephen Warren
2013-07-24 17:09 ` [U-Boot] [PATCH V2 REPOST 5/9] dt: don't use ARCH_CPU_DTS Stephen Warren
2013-07-24 17:09 ` [U-Boot] [PATCH V2 REPOST 6/9] dts/Makefile: don't define ARCH_CPU_DTS, BOARD_DTS Stephen Warren
2013-07-24 17:09 ` [U-Boot] [PATCH V2 REPOST 7/9] config: don't define CONFIG_ARCH_DEVICE_TREE Stephen Warren
2013-07-24 17:09 ` [U-Boot] [PATCH V2 REPOST 8/9] dts/Makefile: don't use cpp -P Stephen Warren
2013-07-24 17:09 ` [U-Boot] [PATCH V2 REPOST 9/9] dts/Makefile: pass -undef -D__DTS__ to cpp Stephen Warren
2013-08-03 19:30 ` [U-Boot] [PATCH V2 REPOST 0/9] rely on latest dtc, simplify 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=51FD224C.2060207@ti.com \
--to=trini@ti.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