From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fdt: Enhance dts/Makefile to be all things to all men
Date: Thu, 30 May 2013 11:38:01 -0600 [thread overview]
Message-ID: <51A78E79.3060507@wwwdotorg.org> (raw)
In-Reply-To: <20130530075644.2724138308E@gemini.denx.de>
On 05/30/2013 01:56 AM, Wolfgang Denk wrote:
> Dear Stephen,
>
> In message <51A6DF7C.30903@wwwdotorg.org> you wrote:
>>
>> It seems to be aimed specifically at enabling use of new dtc features
>> when present. That seems to be specifically against Wolfgang's goal of
>> not requiring new dtc features. There's no point allowing use of new dtc
>
> Please stop planting statements on me that I did not make.
Sorry, but that's what I believe you meant. If you didn't mean that,
well then let's clear this up, and the rest of the conversation will be
a lot simpler:
I believe that for building the *.dts in U-Boot we should simply require
the user to have a version of dtc that supports the recently added
features such as:
* -i directive.
* Ability to parse the output of cpp well (e.g. #line directives, emit
useful error/warning messages in this case).
* Cell expression support.
Those are all present in the latest git repo for dtc.
If we do that, then we won't need any conditional logic in the U-Boot
makefiles. At least parts of Simon's patch won't be necessary.
I'm quite happy to achieve this requirement by having the user install
that dtc into the $PATH prior to running any U-Boot make, either
manually or via distro packages once they're available.
It is my understanding that you object to requiring such a new version
of dtc, irrespective of the means by which it's provided. If this is not
true, then please do let me know; it would vastly simplify matters.
next prev parent reply other threads:[~2013-05-30 17:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 19:36 [U-Boot] [PATCH] fdt: Enhance dts/Makefile to be all things to all men Simon Glass
2013-05-28 19:53 ` Tom Warren
2013-05-28 20:57 ` Stephen Warren
2013-05-29 15:59 ` Simon Glass
2013-05-29 16:40 ` Stephen Warren
2013-05-29 21:31 ` Wolfgang Denk
2013-05-29 22:18 ` Stephen Warren
2013-05-29 22:36 ` Wolfgang Denk
2013-05-29 23:07 ` Stephen Warren
2013-05-30 4:46 ` Simon Glass
2013-05-30 5:11 ` Stephen Warren
2013-05-30 5:33 ` Simon Glass
2013-05-30 7:56 ` Wolfgang Denk
2013-05-30 17:38 ` Stephen Warren [this message]
2013-05-30 7:49 ` Wolfgang Denk
2013-05-28 21:08 ` Wolfgang Denk
2013-05-29 16:00 ` Simon Glass
2013-05-29 21:02 ` Wolfgang Denk
2013-05-29 17:02 ` Stephen Warren
2013-05-29 21:33 ` Wolfgang Denk
2013-05-29 22:52 ` Stephen Warren
2013-05-30 7:05 ` Wolfgang Denk
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=51A78E79.3060507@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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