From: Kumar Gala <galak@kernel.crashing.org>
To: Jon Loeliger <jdl@freescale.com>
Cc: Jon Loeliger <jdl@jdl.com>,
"linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>
Subject: Re: DTC/dts modifications
Date: Mon, 1 May 2006 14:52:23 -0500 [thread overview]
Message-ID: <55FD11DB-54AF-4284-9E9A-C313F4232105@kernel.crashing.org> (raw)
In-Reply-To: <1146512732.24239.34.camel@cashmere.sps.mot.com>
[snip]
>> Try running a current .dts through cpp today. You will get errors
>> like:
>>
>> oftree.dts:15:3: error: invalid preprocessing directive #address
>
>> Because of props like:
>>
>> #cpus = <1>;
>> #address-cells = <1>;
>> #size-cells = <0>;
>>
>> If these used some other symbol instead of '#' cpp will be happy and
>> we can use it to create macros for us.
>
> Yeah, we're not going to be able to change those; they
> are "By The Book".
By what book? It would seem to me that BNF for dtc is completely
under our control and if we want to change it we can. I understand
that there is some correspondence to Open Firmware, but it seems that
if its people are ok with the dts format changing that's a lot easier
than implementing tons of support in dtc for features that cpp gives us.
[I'm also guessing no one's really got time to go and implement these
features in dtc]
> Instead, we'll have to make the lexical analysis conscious
> of something like a <newline> context sensitive token or so.
> Or throw some flag to cpp to not emit location markers.
- kumar
next prev parent reply other threads:[~2006-05-01 19:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-29 16:00 DTC/dts modifications Kumar Gala
2006-05-01 19:33 ` Jon Loeliger
2006-05-01 19:39 ` Kumar Gala
2006-05-01 19:45 ` Jon Loeliger
2006-05-01 19:52 ` Kumar Gala [this message]
2006-05-01 20:07 ` Kim Phillips
2006-05-01 20:28 ` Kumar Gala
2006-05-01 21:26 ` Segher Boessenkool
2006-05-01 22:00 ` Gabriel Paubert
2006-05-01 22:59 ` Andreas Schwab
2006-05-01 23:34 ` Benjamin Herrenschmidt
2006-05-02 0:17 ` Segher Boessenkool
2006-05-01 22:14 ` Paul Mackerras
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=55FD11DB-54AF-4284-9E9A-C313F4232105@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=jdl@freescale.com \
--cc=jdl@jdl.com \
--cc=linuxppc-dev@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).