From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC PATCH 0/3] ARM: use C pre-processor with dtc
Date: Thu, 27 Sep 2012 09:38:12 -0600 [thread overview]
Message-ID: <506472E4.5060107@wwwdotorg.org> (raw)
In-Reply-To: <20120927054038.GL17667@game.jcrosoft.org>
On 09/26/2012 11:40 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 13:06 Tue 25 Sep , Stephen Warren wrote:
>> From: Stephen Warren <swarren@nvidia•com>
>>
>> This series adds some build rules to run cpp on *.dts-cpp prior to
>> invoking dtc, and converts Tegra to the new rule as an example. What do
>> people think?
>>
>> I assume that you've applied the dtc patches I sent yesterday. They
>> aren't in this series. See:
>>
>> https://lists.ozlabs.org/pipermail/devicetree-discuss/2012-September/020182.html
>> https://lists.ozlabs.org/pipermail/devicetree-discuss/2012-September/020183.html
>> https://lists.ozlabs.org/pipermail/devicetree-discuss/2012-September/020181.html
>>
>> Note: those patches are against upstream dtc. If you wish to test this
>> series, apply the dtc patches to upstream dtc, build it, and copy the
>> resultant dtc binary over the top of scripts/dtc/dtc.
>>
>> Stephen Warren (3):
>> kbuild: introduce cmd_dtc_cpp
>> ARM: use cmd_dtc_cpp for compilation of *.dts-cpp to *.dtb
>> ARM: tegra: compile all DT files with cpp
>
> I do not like the extention
It is a bit unwieldy. Perhaps *.dtsp, *.dtsip would be better.
> can we run gcc everytime?
Not without editing all the device tree files; any property (or node)
name the starts with a # must be escaped; changed from "#foo" to "\#foo"
to avoid cpp attempting to interpret it as a pre-processor directive.
> or just do as done for lds
>
> *.dts.S
.S means assembly. (that's why I went with .dts-cpp rather than .dts.cpp).
next prev parent reply other threads:[~2012-09-27 15:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 19:06 [RFC PATCH 0/3] ARM: use C pre-processor with dtc Stephen Warren
2012-09-25 19:06 ` [RFC PATCH 1/3] kbuild: introduce cmd_dtc_cpp Stephen Warren
2012-09-27 5:44 ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-27 15:39 ` Stephen Warren
2012-09-27 17:40 ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-25 19:06 ` [RFC PATCH 2/3] ARM: use cmd_dtc_cpp for compilation of *.dts-cpp to *.dtb Stephen Warren
2012-09-27 5:47 ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-27 15:40 ` Stephen Warren
2012-09-25 19:06 ` [RFC PATCH 3/3] ARM: tegra: compile all DT files with cpp Stephen Warren
2012-09-25 19:35 ` [RFC PATCH 0/3] ARM: use C pre-processor with dtc Scott Wood
2012-09-25 19:51 ` Mark Brown
2012-09-25 19:59 ` Scott Wood
2012-09-25 20:05 ` Stephen Warren
2012-09-25 20:05 ` Mark Brown
2012-09-25 19:51 ` Stephen Warren
2012-09-25 23:46 ` Tony Lindgren
2012-09-27 5:40 ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-27 15:38 ` Stephen Warren [this message]
2012-09-27 17:27 ` Jean-Christophe PLAGNIOL-VILLARD
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=506472E4.5060107@wwwdotorg.org \
--to=swarren@wwwdotorg$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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