From: Scott Wood <scottwood@freescale.com>
To: Jon Loeliger <jdl@jdl.com>
Cc: Roland Dreier <rdreier@cisco.com>, Stefan Roese <sr@denx.de>,
linuxppc-embedded@ozlabs.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] ppc: Add support for AMCC Taishan 440GX eval board
Date: Mon, 12 Feb 2007 14:32:06 -0600 [thread overview]
Message-ID: <45D0CEC6.3010209@freescale.com> (raw)
In-Reply-To: <E1HGhb3-0001fb-9M@jdl.com>
Jon Loeliger wrote:
> So, like, the other day Benjamin Herrenschmidt mumbled:
>
>>Note that there are still things that we might want to change. For
>>example, I think we really should look into adding a macro mecanism
>>and/or an include mecanism to dtc so that we can do things like #include
>><ibm440gp.dtc> to get the base processor/SoC definition and then
>>"overlay" some properties on top of it (like emac phy mode etc...)
>
>
> What do people prefer here? Straight CPP pre-run?
> Direct support built into dtc to do file-inclusion, macros?
Simple textual macros would make it difficult to define 123A and 123B
SoCs whose device tree nodes are mostly a generic 123, but require a few
changes in various parts. I'd rather see dtc support overlaying trees,
with the "newer" tree able to add, modify, and remove nodes and
properties from the "older", more generic tree.
Parametric macros (or "template" nodes) might be nice for a few things
on top of that, though (preferably with better syntax than CPP).
-Scott
next prev parent reply other threads:[~2007-02-12 20:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 10:29 [PATCH] ppc: Add support for AMCC Taishan 440GX eval board Stefan Roese
2007-02-12 12:06 ` Benjamin Herrenschmidt
2007-02-12 12:23 ` Stefan Roese
2007-02-12 18:30 ` Roland Dreier
2007-02-12 18:54 ` Stefan Roese
2007-02-12 19:55 ` Benjamin Herrenschmidt
2007-02-12 20:16 ` Jon Loeliger
2007-02-12 20:23 ` Benjamin Herrenschmidt
2007-02-12 20:41 ` Kumar Gala
2007-02-13 0:46 ` David Gibson
2007-02-13 5:28 ` Kumar Gala
2007-02-14 0:11 ` David Gibson
2007-02-14 0:30 ` Kumar Gala
2007-02-14 1:33 ` David Gibson
2007-02-12 20:32 ` Scott Wood [this message]
2007-02-13 0:43 ` David Gibson
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=45D0CEC6.3010209@freescale.com \
--to=scottwood@freescale.com \
--cc=jdl@jdl.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rdreier@cisco.com \
--cc=sr@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;
as well as URLs for NNTP newsgroup(s).